Sonia, As one of those Trading Partners that would send this same kind of document (if you were one of our TPs!), I may be able to shed some light on WHY they are doing it....
The way that we create a PO internally is a kind of convoluted process - and one I'm hoping to change.... Our buyer will create a PO worksheet - with all the pertinant information as to what he/she wants to order. This handwritten form is given to an assistant to enter into the system. Once the PO is generated, the assistant will change the EDI flag from Y to N. They will then print a hard copy of the PO. This is the ORIGINAL ORIGINAL PO. This printed copy is given to the buyer for approval. If it's OK, it is then given to the buying VP to approve. Once "final" approval is given for the PO, the buying assistant will go and revise the PO to change the EDI flag to Y and then release the PO. It is then put into a file to be picked up by the EDI load program. This PO is, in fact, no longer an ORIGINAL PO, as it has been revised... Because of this, all of our POs (with the exception of a handful of vendors/POs) are technically REVISIONS. So, because of this, we cannot use the 05 "replace" in the BEG segment. Nor can we use the 860 POC document for any TRUE revisions or changes needing to be made to the document (such as quantity, price, shipping terms, etc., etc., etc.). As has been mentioned in other posts - there are a myriad of ways around this.... Finding the best solution that works for you and your trading partners is going to be the tougher part and require that bit of babysitting on your side. Many of our TPs have differet solutions for handling any "revisions" sent with a BEG of '00' on an 850. On our PO, the revision number is included in the BEG segment. Some vendors look to that element (we use RELEASE NUMBER) and compare that to an existing PO in their system. Some just immediately get a message showing the duplicated PO and stops the PO and throws a "red flag".... yet others will not accept ANY revisions via the 850 and we must call/fax/e-mail the revisions to the PO. Much of this depends on your system and how it all works... since your system is set to delete the POs, it may be best to request that the TP not send revisions via EDI and you handle them manually (via fax, phone, e-mail, etc.).... Just My 2 bits on the concept.... Craig Dunham EDI Coordinator Big 5 Sporting Goods. --- In [email protected], "Sonia Zhu" <[EMAIL PROTECTED]> wrote: > > Thanks all! > > As our system doesn't accept duplicate PO so the 2nd time sent PO was > deleted automatically or manually before they reach our internal system, > customer rep. won't see it.... > > Yes, I guess that's my role to baby sitter for this kind of situation > since customer can't send POC, or maybe I can convince them at least > send 05 for replacement. > > Have a good day! > > Sonia > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of > Sonia Zhu > Sent: Monday, June 18, 2007 11:00 AM > To: [email protected] > Subject: [EDI-L] PO change request. > > I am wondering how you handle this kind of situation when customer > doesn't send POC/860 but re-send 850 again and again with the PO change > information? Especially when PO has been brought over into your internal > system but hasn't started for shipping yet... > > Thanks, > Sonia > ... 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/
