Well, there is a fourth option, though it is admittedly rarely successful. You can get the business involved and see if they can make the requirement go away. Generally, if they are paying you, you are at their mercy.
Your *best* bet is to stuff it into the system along with the inbound document. Smart code (bastardize) some field, use delimiters within the data and shove it in. This way, the data is available to the outbound document with all of the other data that is normally present. A bit of code to peel the data out of the smartcoded field, and bob's your uncle. You can put the data in external tables. I have done this many many times. Your issue is one of re-association. You need to find a way to tie the outbound data back to the original inbound data. This is not always easy to do. You have one of two choices. Either you send some unique number through with the inbound document, or you use brute force logic to derive your way back to the original document. And you need to be right every single time. Let me know if you need more datail. On Tue, Mar 12, 2013 at 11:06 AM, Thorsten Evans <[email protected]>wrote: > Question for my EDI friends...Customers require us to send back data on > the invoice/ASN that we don't require in our ERP system such as customer > item number, ordered UOM (we translate to our default UOM, but customer > requires theirs back on the invoice)...and a few others. > > How do people maintain/get this data from the PO onto the outbound > document? To make things more difficult, some of these orders are hand > keyed, but require EDI invoicing. > > Here are the 3 options I see: > - Look back at the original PO (PO's hand keyed fail) > - Maintain this data in tables...either in ERP or in the middle somewhere > - Push required data into the delivered Order load interface and carry > data through outbound process (PO's hand keyed would require more data > entry) > > Are there other options? > > Appreciate any feedback and experience from the group. > > -Thorsten > > [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 > > > > [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/
