Your book is great. By narrowly and widely do you mean SalesOrg/DistrCh/Div/Customer versus Sales Org./Sold-to Party? I'll explore the choices in output types and experiment.
Thanks for the responses! >>> Emmanuel Hadzipetros <[email protected]> 7/26/2012 10:07 AM >>> There are a number of output types that you can use to generate DESADV from the Delivery. Look under shipping in NACE. You'll need to determine what the best access sequence to use is based on how narrowly or widely you want to generate these IDocs. Once you have the access sequence, you can figure out what you need to enter into what condition record. From: Loren Huffman Sent: Thursday, July 26, 2012 1:01 PM To: Michael Mattias/LS ; [email protected] Subject: Re: [EDI-L] outbound 858 I agree that DESADV may be a good basic IDoc type to use. I'm trying to figure out the output control or message control and the condition record to configure in transaction NACE in SAP. Many years ago an ABAP program was written to create a file that was then sent via FTP to an entity that handles our freight payables for us. I have heard that we are about to switch to a new outfit that will handle our freight payables, they asked for the 858 and then a 810 in return. I have requested and received their specs. I could easily grab the file currently created and populate the 858 but I would rather incorporate the whole process into SAP for uniformity of error checking and ease of making future changes. >>> "Michael Mattias/LS" <mailto:mcmlserve%40talsystems.com> 7/26/2012 8:07 AM >>> >>> 7/26/12 > We are going to send shipment information (858) outbound to the bank. I need > to find out the message type and basic IDoc to use. Well...... the ANSI (004010) 858 'Shipment Information' document defines 117 segments and 13 loops; you don't say which ones you need. But just browsing thru the segment/element info from the standard, sure looks like you can get whatever info you might need from whatever you currently use to create your 856/DESADV Advance Shipment Manifest documents. Michael C. Mattias Tal Systems Inc. Racine WI mailto:mmattias%40talsystems.com [Non-text portions of this message have been removed] [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: [email protected] [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/
