E1: 47: EDI 856 R47032 ASN Outbound For Intercompany Orders / Multiple Detail Branch Plants With Different Companies Write Different EDI Key Company EKCO in F47036/F470371
(Doc ID 2656464.1)
Last updated on MAY 15, 2023
Applies to:JD Edwards EnterpriseOne EDI - Version 9.2 and later
Information in this document applies to any platform.
When an Outbound ASN R47032 is created for an Intercompany sales order that has multiple branch plants in different companies, the EKCO EDI Document Company does not write the same EKCO for all the detail lines. This creates a mismatch/disconnect of the key field EKCO between the EDI header/detail table F47036/F470371 causing inquiry and extraction issues.
- Unless you keep the inquiry generic with wildcard asterisk *, you cannot see all detail records associated to the EDI document EDOC in Work with Shipment.
- When extracting data for transmission into EDI with header and detail tables F47036/F47037, unless you data select specifically by the EDOC or another field with like data the detail lines are not picked up and not transmitted to the companies for which you transact business via EDI. When this occurs, there are related fines for incorrect data associated to incorrect Shipment Information, customers are not aware of entire shipment in advance, and both sides of the business lose time and monies associated with the transactions in research and correction of data. It is typical to data select via EDI company.
This can also occur for any regular sales order types with multiple detail Branch Plants in different companies during ASN extraction.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document