Sean Hoppe Consulting Group

The inbound EDI 810 (Invoice) can be translated into the JD Edwards F47041/F47042/F47044 (ASN) tables. We also use F4714 (Header Notes) and F4715 (Detail Notes).

Users will run EDI Inbound Invoice/Match to P.O. Edit/Create (R470412) from the Invoice with Receipt Match menu to match invoices.

Review of Inbound EDI 810 Detail - F47042 Fields

The following F47041 fields must contain data before you can effectively use the EDI Inbound Invoice/Match to P.O. Edit/Create (R470412) for invoices with Receipt Match:

Mandatory Fields:

• EDI Document Number (EDOC)
• EDI Document Type (EDCT)
• EDI Order Type (DCTO)
• EDI Document Key Company (EKCO)
• EDI Transaction Set (EDST)
• Order Number (DOCO)
• Order Key Company (KCOO)
• Send/Receive Flag = R (EDER)
• Address Number (AN8)
• Invoice Number (VINV)
• GL Date (DGJ)

Additional Fields:

• Document Type - Voucher Only (DCTV)
• Invoice Date (DIVJ)
• Company (CO)
• Transaction Originator (TORG)
• Supplier Remark (RMK)
• Batch Number (EDBT)
• Processed (Y/N) (EDSP)
• EDI Transmission Date (EDDT)
• Reference 1 (Purchase Order Number) (VR01)
• Trading Partner ID (PNID)
• Reference 2 (VR02)
• Order Suffix (SFXO)
• Business Unit (MCU)
• User Id (USER)
• Program Id (PID)
• Work Station Id (JOBN)
• Date Updated (UPMJ)

Reference Fields

• User Reserved Number (URAB)
• User Reserved Amount (URAT)
• User Reserved Code (URCD)
• User Reserved Date (URDT)
• User Reserved Reference (URRF)

F47041 Notes Specific for EXTOL mapping: Contact for more details

Mandatory Fields: Fields JDEdwards has identified as fields that should be populated to process inbound invoice.

Additional Fields: Fields that should be populated to assist the invoice in processing. Ie, VR01 (PO Number) and PNID (EDI Trading Partner)

Reference Fields: Fields in JDEdwards table that can be used to store additional data.