Sean Hoppe Consulting Group

The inbound EDI 856 (Advanced Ship Notice) can be translated into the JD Edwards F47031/F47032 (ASN) tables. We also use F4706 (address override table), F4714 (Header Notes), and F4715 (Detail Notes).

Once F47031 and F47032 are populated users are to run the EDI Shipping Notice Edit/Create program (R47031) to update the status of a purchase order.

Review of Inbound EDI 856 Detail - F47032 Fields

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)
• Transaction Set Purpose (TPUR)
• Address Number (AN8)
• Address Number – Ship To (SHAN)

Additional Fields:

• Order Suffix (SFXO)
• Batch Number (EDBT)
• Business Unit (MCU)
• Purchase Order Number (VR01)
• Actual Ship Date (ADDJ)
• Ship Date (PPDJ)   
• Order Date (TRDJ)
• Trading Partner ID (PNID)
• Remark (RMK)
• Shipment ID (SPID)
• User Id (USER)
• Transaction Originator (TORG)
• Program Id (PID)
• Work Station Id (JOBN)
• Date Updated (UPMJ)
• Time of Day (TDAY)

Reference Fields

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

F47031 Notes Specific for EXTOL mapping: Contact for more details

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

Additional Fields: Fields that should be populated to assist the ASN 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.

Copyright 2013 @ www.seanhoppe.com