Denise, How you deal with it depends on your mapping software.
Here's how I did it using Softshare Delta Enterprise. For every detail line loop, I stored the information I would need for the detail loop in the 856 in an array with the original line number as key, adding the quantities when the original line appeared more than once. After I had accumulated everything (breaking at pallet if necessary), I used the accumulated values in the table to create the 856. If your mapping software can't handle this kind of logic, you might make a two-step process, first writing to a database, then querying the DB and summing the quantities, then using the query results to create your ASN. If you can't do a DB, maybe you could map to a flat file, sort it, then map from the sorted file. Regardless, your HL hierarchy should not be a problem. Whoever originated the map may have cheated, making assumptions that s/he could use application data in the HL elements. The right way to do it is to keep track of the last-used number at each level. Hope this helps. Art Douglas Senior Technology Consultant Fujitsu Consulting 877-464-8915 -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of lampteyden Sent: Tuesday, January 08, 2008 1:10 PM To: [email protected] Subject: [EDI-L] ASN's from Oracle Hello, We've been experiencing issues with duplicate line items (Item Tare) due to delivery lines splitting -- something with sub-lot creations, what's happening is we're generating the item twice see sample below, this throws off the hierarchical count HL*15*14*I LIN**CB*224640358 SN1**320*EA HL*16*14*I LIN**CB*224640358 SN1**320*EA I'm being told that this is an Oracle standard, is anyone else run into this, if yes, how did you resolve? Any help would be greatly appreciated. Thanks, Denise ... 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 ... 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/
