HI Jayne,
I have worked for a couple of footwear/apparel manufactuers and none of their
systems could handle the same PO for different orders coming in. Once a sales
order has been created from a PO and then another PO comes in with the same
number trying to create a new sales order, it would go into error status.
Unless your TP is using a system that was written 10 years ago and not kept up
to date, it should be able to handle the SDQ with no problem. I know that SAP,
Jesta IS, JD Edwards can all handle it.
Andy Anderson
PUMA North America
Jayne Gillette <[EMAIL PROTECTED]> wrote:
Dear Group:
Due to the upcoming implementation (next summer) of a new merchandising system,
we are reviewing the current format of our 850s and 860s (as well as several
other EDI documents) to determine where changes are needed.
Under the current system, we issue purchase orders with a unique PO number for
each ship-to location (i.e., 1 PO number = 1 ship-to location). In the new
world, the same purchase order number could be used for multiple ship-to
locations.
We know we could change our 850 / 860 EDI format to utilize the SDQ format like
this:
BEG segment: PO #12345
LIN segment: Item #ABC, Total Quantity 4000
SDQ segment: Ship-to Location 1, quantity 2000; Ship-to Location 2, quantity
1500; Ship-to Location 3, quantity 500
...but, we are hoping to minimize the impact to our EDI trading partners as
much as possible, so as not to jeopardize the go-live date for the new
merchandising system.
Since we do not currently issue SDQ-format 850s and 860s, we are considering
sending the documents in the same EDI format we send today, which for the same
order described above would look like this:
850 TRANSACTION #1:
-------------------------------------------------
BEG segment: PO #12345
N1 segment: Ship-to Location 1
LIN segment: Item #ABC, Quantity 2000
850 TRANSACTION #2:
-------------------------------------------------
BEG segment: PO #12345 (same PO number as transaction #1)
N1 segment: Ship-to Location 2
LIN segment: Item #ABC, Quantity 1500
850 TRANSACTION #3:
-------------------------------------------------
BEG segment: PO #12345 (same PO number as transactions #1 and #2)
N1 segment: Ship-to Location 3
LIN segment: Item #ABC, Quantity 500
The EDI format is the same as what we send today, but the difference is the
same purchase order number could now appear in multiple 850s / 860s, for
individual ship-to locations.
We are being told we really can't consider doing this because manufacturers
can't process "duplicate" PO numbers such as that described above. Based on
your experience / knowledge, is it true that "duplicate" PO numbers like this
will cause major problems in manufacturers' order entry / shipping / invoicing
/ etc. systems?
As always, thanks for all your help and advice!
Jayne
---------------------------------
Stay in the know. Pulse on the new Yahoo.com. Check it out.
[Non-text portions of this message have been removed]
...
Please use the following Message Identifiers as your subject prefix: <SALES>,
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>
Job postings are welcome, but for job postings or requests for work: <JOBS> IS
REQUIRED in the subject line as a prefix.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/EDI-L/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/EDI-L/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
