JD Edwards E1 logo

JD Edwards E1

ERP & FinanceBasic authLive

Connect your customers' JD Edwards EnterpriseOne servers so your product can invoke AIS forms and orchestrations for reads and writes. The customer provides their AIS host, username, password, and optionally an environment and role; Askel composes the Basic auth header and the JDE-AIS auth headers per request.

What you can do

Invoke AIS orchestrations for reads and writes

Call any published orchestration on the customer's AIS server with a JSON request body. Orchestrations can read business data, update records, or trigger JDE business functions. All data flows through Askel without touching your servers.

Read purchase orders via AIS form interop

Invoke the Purchase Order Inquiry (P4310) form through AIS to read open purchase orders with header and line detail, supplier reference, and receipt status.

Read sales orders from the Sales Order Header and Detail

Use AIS to read Sales Order Header (F4201) and Detail (F4211) records for order-visibility and customer-service workflows in your product.

Fetch address book records

Read Address Book (F0101) entries for customers, suppliers, and employees. Used to resolve JDE address numbers without a separate data extract.

Read inventory item master and quantity on hand

Fetch Item Master (F4101) records and Item Location (F41021) quantities per branch/plant. Lets your product resolve item numbers and stock levels directly.

Write transactions through AIS orchestrations

Create sales orders, receipts, or inventory adjustments by calling a write-enabled orchestration published on the customer's AIS server. The orchestration handles JDE business rule validation.

Sample use case

Pulling open purchase orders into a procurement-visibility dashboard

You sell a procurement-analytics platform. A new customer, Fairfield Industrial Supply, runs JD Edwards EnterpriseOne for ERP. Their purchasing team needs a real-time view of open POs, expected delivery dates, and receipt status in your dashboard without exporting from E1 manually each morning.

  1. 1

    Customer provides AIS credentials

    Fairfield's IT admin provides your product's connection wizard with their AIS server host URL (ais.fairfield-ind.com), the JDE username, password, environment (PRODDTA), and role (*ALL). Askel validates the credentials with a test AIS token request.

  2. 2

    Orchestration identified

    Fairfield's JDE developer confirms the name of the PO inquiry orchestration published on their AIS server. Your product stores the orchestration name against the customer connection for subsequent calls.

  3. 3

    Daily PO fetch

    Your platform calls Askel each morning to invoke the PO inquiry orchestration on Fairfield's AIS server. Askel composes the Basic auth header and the JDE-AIS-Auth-Environment and JDE-AIS-Auth-Role headers, then POSTs the orchestration request.

  4. 4

    Results parsed and loaded

    The AIS server returns a JSON payload with open PO headers and lines. Your platform parses the response, maps the field names to your schema, and loads the data into the procurement dashboard.

  5. 5

    Dashboard live every morning

    Fairfield's purchasing team opens your dashboard and sees a live view of open POs, with amounts in USD, expected delivery dates, and receipt status. No one exports from JDE or sends a spreadsheet.

Authentication

Basic auth

The customer provides their AIS host URL, JDE username, password, and optionally the JDE environment (such as PRODDTA) and role (such as *ALL). Askel base64-encodes the username and password for the Authorization: Basic header and adds JDE-AIS-Auth-Environment and JDE-AIS-Auth-Role headers where provided, on every request to the AIS server. Credentials are stored encrypted per connection and never forwarded to your servers.

Data flow

How Askel sits between your product and the customer's system

Data flow between Customer's JDE EnterpriseOne AIS server, Askel, and Your productCustomer's JDE EnterpriseOne AIS serverAPI endpointAskelauth · mapping · driftYour productyour backend
Orchestration resultsPurchase ordersSales ordersAddress book recordsItem master and inventory

FAQ for JD Edwards E1

Does the AIS server need to be accessible from the internet?+
Yes. Askel reaches the customer's AIS server over HTTPS. For on-premises JDE installations, the customer needs to allow inbound traffic from Askel's egress IP range on the AIS server port (default 9300 for HTTPS). Many customers expose AIS behind a load balancer or reverse proxy with a public DNS name.
What JDE Tools Release version is required?+
AIS in its REST form is available from JDE Tools Release 9.2 onwards. Orchestrations require TR 9.2.1 or later. Askel targets the standard AIS REST interface; earlier versions that use only the legacy JDE connector layer are not supported.
Can we call JDE business functions directly, or only orchestrations?+
Askel calls the AIS server, which supports both form interop (calling JDE forms via the AIS form endpoint) and orchestrations (calling published orchestrations via the orchestrator endpoint). Both patterns are supported. Direct BSFN calls require a custom orchestration wrapper on the JDE side.
What if the customer uses JDE environment-based security (multiple environments)?+
The JDE environment and role are passed as header values on every request. If the customer has separate environments for production and testing, your product can maintain separate Askel connections for each environment under the same customer record, each with a different JDE-AIS-Auth-Environment value.
Ready to ship integrations faster?customers faster?implementations faster?
Join onboarding teams delivering integrations without the engineering queue,
catching drift before it breaks, and hitting go-live dates.
Security & Compliance
ISO 27001 Certified
GDPR Compliant

© 2025 Askel.ai. All rights reserved.