JD Edwards EDI Full Cycle: Inbound, Outbound, ASN, and Acknowledgments Explained

ByKenji Alvarez

What “EDI Full Cycle” Actually Means in JD Edwards

An EDI full cycle means a transaction travels both ways — you receive a document, process it, and send a response back — with goods and money eventually settled on both ends. In JD Edwards EnterpriseOne, the whole thing lives under the G47 menu. That is your starting point for every EDI program, inquiry form, and interface table the system touches.

The Core Transaction Set

Before digging into JDE specifics, it helps to know which X12 transaction codes do what. The main ones in a typical supply-chain cycle:

  • 850 — Purchase Order (inbound from your buyer)
  • 855 — Purchase Order Acknowledgment (outbound, confirming you received the 850)
  • 856 — Advance Ship Notice / ASN (outbound, sent when goods leave your facility)
  • 810 — Invoice (outbound, billing the buyer after shipment)
  • 997 — Functional Acknowledgment (confirms EDI document receipt at the system level — can flow in either direction)

A full cycle typically runs: 850 in → 855 out → ship goods → 856 out → 810 out → 997 in. Some trading partners also return a 997 to confirm they received your 855. The exact sequence depends on your trading partner agreement, but those five document types cover most scenarios.

How JDE’s EDI Subsystem Is Actually Built

JDE does not talk to your EDI translator directly. Everything flows through a two-step hand-off. This is the part the standard documentation glosses over, and it is the source of most first-time confusion.

Step 1 — Flat File Conversion

Your EDI translator — the middleware that speaks X12 or EDIFACT — maps incoming data to a flat file. JDE’s R47002C, the Inbound Flat File Conversion program, reads that flat file and loads the records into JDE’s EDI inbound interface tables (the F47-series tables). This step is mandatory before any edit or update programs can run. If R47002C has not run, or if the flat file is not mapped correctly, the downstream programs see nothing and fail silently.

Step 2 — Edit and Update Programs

Once data is in the interface tables, the transaction-specific programs take over. Each document type has its own edit/update pair. For an inbound 850, you run the edit program first (which validates the data and flags errors) and then the update program (which creates the actual sales order in JDE). Do not skip straight to update — errors that slip through without the edit pass cause hard-to-trace order problems downstream.

Inbound Flow: The 850 Purchase Order

The buyer sends an 850. Your translator maps it to a flat file. R47002C loads it into the inbound interface tables. You run the edit program to check for errors, fix anything flagged, then run the update program to generate a JDE sales order. Straightforward in theory; the tricky part is field mapping in the flat file — all fields must appear in exactly the order the inbound interface table expects them.

Once the sales order exists in JDE, you can generate an outbound 855 Purchase Order Acknowledgment. That data gets written to the outbound interface tables, a flat file conversion writes it out, and your translator sends it to the buyer.

The ASN: Outbound 856

The Advance Ship Notice is usually the most complex piece of the cycle. In JDE, the extraction report R47032 pulls confirmed shipment data and writes it into the outbound ASN interface tables (F47036 and F470371). The hierarchical configuration in P47HL controls the ASN structure — typical options are ship/pack/item or ship/item. Get the hierarchy wrong and R47032 returns a blank report or drops detail lines entirely.

Once ASN data is in the interface tables, outbound flat file conversion writes it to a flat file and the translator formats it into a proper 856 before transmission. Timing matters here. Most large retailers require the 856 to arrive before the physical shipment does — late ASNs often trigger chargebacks.

Outbound Invoice: The 810

After shipment, the 810 Invoice goes out. JDE’s outbound invoice extraction pulls from confirmed shipments or sales orders and populates the outbound interface tables. Same two-step pattern as everything else: JDE writes to interface tables, flat file conversion generates the file, translator formats and sends. The key processing option to get right here is whether the extraction runs per shipment or per order — that determines how invoices consolidate.

Acknowledgments: The 997 in Detail

The 997 is frequently misread. It does not say “your order is accepted” or “shipment confirmed.” It only says the EDI document arrived and passed syntax checks at the receiving system. An “A” (accepted) code means the document was technically valid. An “R” (rejected) means a formatting or segment-level problem — the underlying transaction still needs to be corrected and re-sent.

In JDE, if you receive a 997 with a rejection against an outbound document you sent, the system can generate a workflow notification so someone knows to investigate. That configuration lives in the acknowledgment processing options on the relevant outbound program. Most shops leave this unconfigured and end up chasing silent failures manually.

You also send 997s back to your trading partners when you receive inbound documents from them. From your system’s perspective those are outbound, even though the 997 is a response to their inbound.

Workflow and Work Process

JDE’s EDI subsystem can trigger workflow messages for exceptions — rejected documents, missing mandatory fields, or records that fail the edit pass. These surface in the employee work center. Configuring this properly means the system tells you when something breaks rather than you discovering it when a trading partner calls. Most EDI implementations leave the workflow piece under-configured. That is worth revisiting early, not after you have your first chargeback from a missed ASN.

Key Programs and Menus at a Glance

  • G47 — Main EDI menu in JDE; all EDI programs hang off here
  • R47002C — Inbound Flat File Conversion (loads flat file into interface tables)
  • R47032 — ASN Extraction report (builds outbound 856 data from shipments)
  • P47HL — Hierarchical Configuration for ASN structure
  • F47036 / F470371 — Outbound ASN interface tables

Oracle’s Data Interface for Electronic Data Interchange implementation guide for EnterpriseOne 9.2 covers each program’s processing options in full and includes the F47 table layouts you need when troubleshooting bad flat files. It is dense reading but it is the authoritative reference once you have the basic flow working.

Frequently Asked Questions

What is the EDI full cycle in JD Edwards?

The full cycle covers the complete exchange of electronic documents between you and a trading partner — receiving an inbound 850 Purchase Order, acknowledging it with an 855, shipping goods and sending an 856 ASN, billing with an 810 Invoice, and exchanging 997 Functional Acknowledgments at each step. Everything is managed through JDE’s G47 menu and the F47-series interface tables.

What does R47002C do in JDE EDI?

R47002C is the Inbound Flat File Conversion program. It reads the flat file your EDI translator produces and loads that data into JDE’s inbound interface tables. It must run before any edit or update program can process an inbound transaction.

What is the purpose of an EDI 997 acknowledgment?

The 997 confirms that an EDI document was received and passed syntax validation at the recipient’s system. It does not indicate business acceptance or order approval — only that the document arrived and was technically valid. A rejection code means there was a formatting error; the document needs to be corrected and re-sent.

What is the difference between R47032 and R47002C?

R47032 is the Outbound ASN Extraction program — it pulls shipment data from JDE and populates the outbound interface tables for the 856. R47002C is the Inbound Flat File Conversion — it loads your translator’s flat file output into the inbound interface tables. One handles outbound ASN generation; the other handles inbound document intake for any transaction type.

Sources


Similar Posts