I think it is true to say that the requirements for invoices and ASNs are not driven by the SDQ order. But it is also true that each trading partner may have specific requirements for invoices and ASNs regardless of the way the order was placed.
I have been involved in a few implementations and in all of them we broke up the customer SDQ order into multiple sales orders by the partner function represented in the SDQ. Usually the mark for location. The ASN was driven by what was actually shipped and the invoices were generally one per sales order in my system. Many customers provide the ship to distribution center in the header and the mark for store for labeling in the SDQ. This order could be filled and sent to the DC as one shipment and one ASN would then be sent. But my system would still send one invoice per store. There is one large department store that does not send the ship to DC on the order they just send the mark for stores and expect the supplier to know which stores go to which DCs. And they send all stores on one order. We have to figure out which set of stores go to which DC and in this case there will be at least as many ASNs sent as there are DCs to which we actually shipped. Tim ----- Original Message ---- From: Travis Truax <[EMAIL PROTECTED]> To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>; [email protected] Sent: Thursday, February 1, 2007 7:24:44 PM Subject: RE: [EDI-L] PO SDQ Segment Processing and Response Jim, As a supplier, I wish the logical scenario you have spoken about were always the case, but I would say it's more likely just the rule of thumb. This list has seen its share of the debate between "what the standard is" and "what the customer wants". It *always* ends at "what the customer wants". If you happen to be lucky enough to have a product with tremendous demand - maybe you can wield some hand. But as a supplier, we've got no hand. :) Travis- -----Original Message----- From: James Sykes [mailto:[EMAIL PROTECTED] net] Sent: Thursday, February 01, 2007 5:16 PM To: [EMAIL PROTECTED] com Subject: RE: [EDI-L] PO SDQ Segment Processing and Response Ken, I agree there is no single answer for all situations; however, the scenario I presented was a real implementation of a large supplier, and not uncommon across many suppliers. It works with direct shipments to the store as well as shipments to a DC and marked for the store. I still content it is the processor of the order that for the most part control how to process orders. I think most retailers have already built in the flexibility based on prior experience. Best Regards, Jim [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 ____________________________________________________________________________________ Need Mail bonding? Go to the Yahoo! Mail Q&A for great tips from Yahoo! Answers users. http://answers.yahoo.com/dir/?link=list&sid=396546091 [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/
