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.
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.
Invoke the Purchase Order Inquiry (P4310) form through AIS to read open purchase orders with header and line detail, supplier reference, and receipt status.
Use AIS to read Sales Order Header (F4201) and Detail (F4211) records for order-visibility and customer-service workflows in your product.
Read Address Book (F0101) entries for customers, suppliers, and employees. Used to resolve JDE address numbers without a separate data extract.
Fetch Item Master (F4101) records and Item Location (F41021) quantities per branch/plant. Lets your product resolve item numbers and stock levels directly.
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.
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.
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.
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.
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.
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.
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.
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.
© 2025 Askel.ai. All rights reserved.