Hi Thorsten, Lots of interesting answers. You didn’t name your ERP (how about “Fred”; Fred’s a nice name), but for customer item number, SAP has CMIR/VD53 for that (Customer Material Information Record). It’s not too onerous because you enter the items once at the SoldTo level (although you can enter variations at the ShipTo level as needed), and we only maintain this for those partners who require it (surprisingly few, but not surprisingly who). Regarding UOM, we handle everything in Case, but we do have a couple of TPs who order in EAches and require Eaches on the outbound documents (invoice/ASN). Since they are consistent, we just have it mapped this way in the translator for those TPs.
In a previous job, we mapped additional information we needed into TEXT segments (presented positionally, can be done at header and/or at item detail) so that on outbound we could substring for the data we needed. This could also be used for Customer Item & UOM. For SAP you would not likely use this for the customer item, as there is already a field for that on the order. The reason to use CMIR anyway (and not only the field on the order) as someone pointed out in one of the other answers, is for when manual entry becomes involved. Manual entry does not only affect orders entered completely by hand; it also appears in EDI orders that have had subsequent maintenance. It’s been pretty common for an item to be cancelled off an order (inventory not available), only to be added back later (as a different line, and therefore missing all that good info from the EDI order). Using the already available Text field handling avoids creating custom tables & custom programming code as it is there for import and for export from the system. Regarding 'customer "must" place his orders via EDI ... or ... your "order entry" personnel ... MUST enter it somewhere ...', LOL. or perhaps even ROTFLMAO. Hope this helps, -- Ken Cox From: Thorsten Evans Sent: Tuesday, March 12, 2013 11:06 AM To: [email protected] Subject: [EDI-L] Required customer data 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] No virus found in this message. Checked by AVG - www.avg.com Version: 2013.0.2904 / Virus Database: 2641/6169 - Release Date: 03/13/13 [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/
