Free tool for JD Edwards EnterpriseOne

JD Edwards EnterpriseOne Integration and EDI Designer

Pick the business objects and the systems you need to connect, and get a JD Edwards EnterpriseOne integration inventory that names the real interface for each flow: orchestrations on the AIS Server, published business services such as SalesOrderManager (JP420000), real-time events such as RTSOOUT, or Z file batch interfaces such as F0911Z1 with R09110Z. Switch to EDI mode to see how X12 850, 855, 856 and 810 (and the EDIFACT equivalents) map to the EDI interface tables (F47011, F47026, F47036, F47046) and the programs that load or extract them.

Business objects

Toggle what moves between systems. Presets add a typical set.

Targets, direction and frequency

Direction is seen from JDE E1.

Nothing in scope yet

Pick an object or a preset in step 1.

Integration inventory

JD Edwards EnterpriseOne exposes synchronous integration through the AIS Server (REST: orchestrations, form service, data service, business function service) and the Business Services Server (SOAP published business services). Outbound events come from real-time events on the Transaction Server, and batch flows use Z file interoperability tables and the EDI interface tables (F47xxx) processed by UBEs.

Your inventory appears here

Each interface gets the JDE E1 method, the exact artifact and a relative effort score.
Free, optional. Reopen it on any device.
Download the design:

Exports include the inventory, rationale, field maps with your target names, selected EDI maps and risks. No sign-in needed.

How to use it

  1. 1

    Pick the objects

    Select the business objects in scope, such as customers, items, sales orders and shipments.

  2. 2

    Add the target systems

    For each object choose the system on the other side, the direction seen from JD Edwards and how often it must move.

  3. 3

    Read the inventory

    Each row names the JDE interface (orchestration, business service, real-time event, Z table or EDI table), why it fits and what to watch for.

  4. 4

    Check the field map

    Open the starter map for an object, fill in the target field names and note the keys, required fields and Julian date columns.

  5. 5

    Export or save

    Download the design as PDF, Excel, Word or CSV, save it to your account, or send it to an engineer for review.

JDE E1 interfaces in this tool

Orchestrator (AIS REST) synchronous
Orchestrations built in Orchestrator Studio chain form requests, data requests, business function calls, rules and cross references, and are called as REST at /jderest/v3/orchestrator/{orchestration}. The usual first choice for new inbound and outbound integrations because application logic and processing options run on every call.
AIS REST services (form, data, bsfn) synchronous
Lower level AIS endpoints: /jderest/v2/formservice runs an interactive application form, /jderest/v2/dataservice queries or aggregates tables and views, /jderest/v2/bsfnservice calls a business function, /jderest/v2/report/execute launches a UBE. Authenticate with /jderest/v2/tokenrequest or HTTP basic auth.
Published business services (BSSV, SOAP) synchronous
Java web services on the Business Services Server, for example AddressBookManager (JP010000), CustomerManager (JP010020), InventoryManager (JP410000), SalesOrderManager (JP420000) and ProcurementManager (JP430000). They call the same master business functions as the applications. Common in existing integrations; new builds often wrap the same logic in an orchestration.
Real-time events (Transaction Server) asynchronous
Container events such as RTABOUT (address book), RTCMOUT (customer), RTIMOUT (item), RTSOOUT (sales order), RTPOOUT (purchase order), RTSHPNOUT (ship confirm), RTINVOUT (invoice) and RTWOOUT (work order) are published as XML when the master business function commits. Subscribers receive them through the Transaction Server; configure the subscriber and delivery method in your tools release.
Z file interoperability tables asynchronous
Batch staging tables named after the application table with a Z suffix (F0101Z2, F03012Z1, F4101Z1, F4301Z1/F4311Z1, F0911Z1, F0411Z1). An external process inserts rows with EDI user, batch and transaction numbers and a transaction action (A, C, D); an inbound processor UBE (R01010Z, R4101Z1I, R4311Z1I, R09110Z, R04110Z) validates and posts them, with errors in the Employee Work Center. Outbound Z files are written by the application when the Interop processing option names a transaction type.
JDE Data Interface for EDI (F47 tables) asynchronous
Delivered EDI interface tables per document (for example F47011/F47012 for inbound 850). A third-party translator produces flat files, Inbound Flat File Conversion (R47002C) loads them using the flat file cross-reference (F47002), and an edit/create UBE such as R47011 creates the transaction. Outbound extraction UBEs (R42565, R47032, R43500) fill the outbound tables, which flat file conversion programs write out for the translator.
Read-only SQL (reporting) asynchronous
Read the business data tables or a replica for warehouse extracts. Dates are Julian (CYYDDD), amounts are stored without decimals per the data dictionary display decimals, and UDC values need joins to F0005. Never insert into application tables: master business functions, ledgers and next numbers are bypassed.

Questions

Should I use Orchestrator, business services or Z files for a new JD Edwards integration?

For synchronous calls from a web app, CRM or middleware, use an orchestration on the AIS Server: it is REST, it runs the same applications and processing options a user would, and it can be changed in Orchestrator Studio without a package build. Published business services (BSSV) are SOAP and still common in older integrations. Use Z files or EDI interface tables for high volume batch loads such as journal entries (F0911Z1 with R09110Z) or vouchers (F0411Z1 with R04110Z).

What are JD Edwards Z files?

Z files are interoperability staging tables named after the application table, for example F0101Z2 for address book, F4101Z1 for items, F4301Z1 and F4311Z1 for purchase orders and F0911Z1 for journal entries. Each row carries EDI user ID, batch number, transaction number, line number and a transaction action (A add, C change, D delete). An inbound processor UBE validates the rows, posts them and sets the successfully processed flag to Y; errors go to the Employee Work Center.

How does an inbound EDI 850 become a sales order in JDE?

The translator converts the 850 to a flat file, Inbound Flat File Conversion (R47002C) loads it into F47011 (header) and F47012 (detail) plus optional F47013, F4706 and text tables, and EDI Inbound Purchase Order Edit/Create (R47011) creates the order in F4201 and F4211 using the P4210 version in its processing options. Required fields include EDI document number, type, key company, transaction set, send/receive flag R, sold-to or ship-to and business unit.

Which EDI documents does JD Edwards EnterpriseOne support out of the box?

Sales: inbound 850, 860, 861 and outbound 855, 865, 856 and 810. Procurement: outbound 850, 860 and 862, inbound 855, 856, 861 and 810. Inventory: 852 product activity in both directions. Finance: inbound 810 to vouchers, 823 lockbox and outbound 820 payments. The 846 inventory advice is not in the delivered list and needs a custom extract.

How do I call a JD Edwards orchestration from outside?

POST JSON inputs to /jderest/v3/orchestrator/{orchestration} on the AIS Server, authenticating with HTTP basic auth or a token from /jderest/v2/tokenrequest (log out with /jderest/v2/tokenrequest/logout). The OpenAPI 3.0 catalog at /jderest/v3/open-api-catalog3 returns definitions of the available orchestrations.

How does JD Edwards send events to other systems?

Real-time events such as RTSOOUT (sales order), RTCMOUT (customer), RTIMOUT (item), RTPOOUT (purchase order), RTSHPNOUT (ship confirm) and RTINVOUT (invoice) are published by the master business functions when a transaction commits and delivered through the Transaction Server. Orchestrations can also call external REST services as steps, which suits simpler notifications.

Why do my JDE integration dates look wrong?

JDE stores dates as Julian numbers in CYYDDD format, where C is the century (1 for 2000s), YY the year and DDD the day of the year, so 126295 is 22 October 2026. Amounts and line numbers are also stored without decimals. Convert both in the mapping layer, not in the source system.

Can I insert directly into F4211 or F0911 for an integration?

No. Direct inserts bypass the master business functions, so commitments, ledgers (F42199, F0902), next numbers and audit fields are not updated. Use orchestrations, business services, Z files with their inbound processors, or the EDI interface tables, and keep SQL to read-only reporting.