1. Data Interface for Electronic Data Interchange Implementation Guide
  2. Using Mapping Guidelines

Using Mapping Guidelines

Mapping is the process of converting information from one table structure to another.

In the F47071 table, the following fields must contain data before you can use the Inbound Edit/Update program for receiving advice into sales effectively:

  • EDI Document Number (EDOC).

  • EDI Document Type (EDCT).

  • EDI Document Key Company (EKCO).

  • EDI Transaction Set (EDST).

  • Send/Receive Flag = R (EDER).

  • Order Number* (DOCO).

  • Order Type* (DCTO).

  • Order Key Company* (KCOO).

  • Order Suffix* (SFXO).

  • Customer Order Number (VRO1).

  • Sold To Address Book Number (AN8).

    Note: Map either these fields or the Customer Order Number (VRO1) field.

In the F47072 table, these fields must contain data before you can use the Inbound Edit/Update program for receiving advice into sales effectively:

  • EDI Document Number (EDOC).

  • EDI Document Type (EDCT).

  • EDI Document Key Company (EKCO).

  • EDI Transaction Set (EDST).

  • Send/Receive Flag = R (EDER).

  • Total Quantity received (VREC).

  • Short Item Number (ITM), Second Item Number (LITM), Third Item Number (AITM), or Customer Item Number (CITM).

  • Document Line Number (LNID).

  • Sold To Address Book Number (AN8).

Map the JD Edwards EnterpriseOne sales order detail line number in the EDI receiving advice detail record.

Map the total quantity received to UREC. Other quantities that are informational only should be mapped to URET, UDMG, UREJ, UIQ1, UIQ2, and UIQ3. The informational quantities display on the Damaged/Rejected Goods Report along with their corresponding reason code, but they are not used in processing.