.png)
Oracle JD Edwards EnterpriseOne Integration Guide
Integrate JD Edwards EnterpriseOne with enterprise applications through AIS REST APIs, Orchestrator endpoints, BSSV SOAP services, scheduled workflows, and selected event notifications.
Oracle JD Edwards EnterpriseOne integration options at a glance
Oracle JD Edwards EnterpriseOne primarily integrates through Application Interface Services (AIS) Server REST APIs, including endpoints exposed by the EnterpriseOne Orchestrator for applications, data, reports, and business processes. Existing implementations can also use Business Services Server (BSSV) SOAP services. Selected configured events may support outbound notifications, while scheduled polling, reports, and batch or asynchronous jobs cover processes without direct callbacks. Media objects and attachments are available for selected services. Martini can consume REST and SOAP APIs, invoke orchestrations, expose APIs to downstream applications, transform JSON or XML, schedule synchronization workflows, and manage status polling, retries, and reconciliation.
| Integration point | Supported by Oracle JD Edwards EnterpriseOne? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | AIS Server exposes REST services for EnterpriseOne applications, data, reports, orchestrations, and related operations. These are the preferred path for many new integrations. | Martini can consume the AIS REST API, send JSON payloads, map responses, invoke orchestrations, and expose a separate REST API to downstream systems. |
| SOAP APIs | Yes | Business Services Server exposes BSSV business services through SOAP, particularly for existing integrations or capabilities not available through REST. | Martini can consume WSDL-backed SOAP services, construct XML requests, process SOAP faults, and transform responses for downstream applications. |
| Orchestrations | Yes | The EnterpriseOne Orchestrator packages applications, reports, queries, rules, and external calls into controlled REST-accessible business logic. | Martini can invoke published orchestrations, pass parameters, interpret results, and coordinate them with external workflows and APIs. |
| Webhooks / outbound callbacks | Limited | Configured events and orchestrations can support selected event-driven notification scenarios, but coverage is not universal across EnterpriseOne objects. | Martini can receive supported callback or webhook-style notifications and use scheduled polling or an intermediary for events without direct outbound notification. |
| Bulk / async / batch APIs | Limited | Reports, batch applications, orchestrations, and background jobs support batch-oriented processing. Asynchronous behavior varies by service. | Martini can submit work, retain job identifiers, poll status, handle timeouts, and reconcile successful or failed results. |
| File / attachment APIs | Limited | Media objects and attachments are available for selected records and services; file import and export depend on deployment and service configuration. | Martini can process attachment metadata and binary content where the selected service exposes it, and can orchestrate approved file-based exchanges. |
| Authentication | Yes | AIS access uses configured EnterpriseOne authentication and authorization, including Basic Authentication or OAuth 2.0 in supported deployments, with EnterpriseOne roles and service security. | Martini can store credentials, client information, and tokens as environment-specific secrets and apply the configured authentication to API requests. |
| Database / analytics access | Not confirmed | EnterpriseOne may use Oracle Database, but direct database access is not the preferred general-purpose transactional interface and can bypass application logic. | Martini can connect to approved databases when required, but transactional EnterpriseOne integrations should use AIS, orchestrations, or BSSV instead. |
How Oracle JD Edwards EnterpriseOne exposes data and business events
EnterpriseOne REST APIs
AIS Server exposes REST services for EnterpriseOne applications, data, reports, orchestrations, and related operations. The available fields and actions depend on the release, configuration, enabled services, and security model.
Martini implementation pattern
Martini implementation pattern: a Martini workflow authenticates to AIS, sends a mapped JSON request, invokes an application service or orchestration, validates the response body and business status, and maps the result to a canonical or downstream model.
Implementation sequence
EnterpriseOne SOAP services
Business Services Server provides SOAP-based business services for existing integrations and capabilities that may not be exposed through the REST layer.
Martini implementation pattern
Martini implementation pattern: Martini consumes the WSDL-backed service, maps canonical data into XML, sends the SOAP request, handles SOAP faults and transport errors, and transforms the response for the target system.
Implementation sequence
EnterpriseOne Orchestrator
The Orchestrator assembles EnterpriseOne applications, reports, queries, rules, and external REST calls into controlled business logic that can be published as REST services.
Martini implementation pattern
Martini implementation pattern: the workflow calls a secured orchestration rather than reproducing complex EnterpriseOne rules externally, passes controlled parameters, interprets the orchestration response, and coordinates downstream actions.
Implementation sequence
Selected event notifications
EnterpriseOne event-driven scenarios can be configured for selected events and orchestrations, but outbound notification coverage is not universal for every business object or transaction.
Martini implementation pattern
Martini implementation pattern: Martini receives a supported callback through an API, validates the event and correlation data, retrieves the current EnterpriseOne resource when necessary, and uses scheduled reconciliation for missed or unsupported events.
Implementation sequence
Batch and asynchronous jobs
Reports, batch applications, orchestrations, and background jobs can process work asynchronously depending on the selected EnterpriseOne service.
Martini implementation pattern
Martini implementation pattern: a workflow submits the job, stores its identifier, polls status at a controlled interval, retrieves results when complete, and routes timeout or failure outcomes to reconciliation.
Implementation sequence
Common Oracle JD Edwards EnterpriseOne integration patterns
Pattern 1: Synchronize Address Book records
When to use this pattern
Use this pattern when customers, suppliers, employees, or contacts must be kept aligned between EnterpriseOne and a downstream business application. Incremental criteria, stable Address Book numbers, and duplicate prevention are important for reliable synchronization.
Integration direction
Example Mapping
| Oracle JD Edwards EnterpriseOne Field | Canonical Field | Target Field |
|---|---|---|
| Address Book Number | partyId | Account.externalId |
| Alpha Name | partyName | Account.name |
| Search Type | partyRole | Account.type |
| Address Number | contactId | Contact.externalId |
Martini implementation pattern
A scheduled Martini workflow retrieves changed Address Book records through AIS or an orchestration, validates party roles and required fields, maps them to a canonical party model, and upserts the target records. It stores source identifiers and routes authorization, validation, and duplicate conflicts to retry or reconciliation paths.
Martini capabilities used
- workflows
- API consumption
- scheduling
- data mapping
- business rules
- error handling
Pattern 2: Create Sales Orders from commerce or CRM
When to use this pattern
Use this pattern when an external application owns order capture but EnterpriseOne owns fulfillment, inventory, or financial processing. It protects against duplicate orders after timeouts and preserves EnterpriseOne document identifiers.
Integration direction
Example Mapping
| Oracle JD Edwards EnterpriseOne Field | Canonical Field | Target Field |
|---|---|---|
| Order ID | externalOrderId | Order reference |
| Customer ID | customerId | Address Book Number |
| Line Items | orderLines | Sales Order detail lines |
| Quantity | quantity | Ordered quantity |
Martini implementation pattern
Martini exposes an API for the source application, validates the order and line data, maps the payload to an EnterpriseOne orchestration or REST service, and returns the resulting document number and status. Before retrying a timed-out create operation, the workflow checks for an existing order using the external correlation identifier.
Martini capabilities used
- APIs
- workflows
- data mapping
- validation
- business rules
- idempotency
- error handling
Pattern 3: Synchronize Purchase Orders and receipts
When to use this pattern
Use this pattern when procurement applications need EnterpriseOne purchase-order and receipt status or when EnterpriseOne remains the system of record for supplier purchasing.
Integration direction
Example Mapping
| Oracle JD Edwards EnterpriseOne Field | Canonical Field | Target Field |
|---|---|---|
| Order Number | purchaseOrderId | Purchase order number |
| Supplier Address Number | supplierId | Supplier |
| Quantity Ordered | orderedQuantity | Quantity |
| Receipt Status | receiptStatus | Receiving status |
Martini implementation pattern
A scheduled workflow retrieves purchase orders and receipt changes using approved EnterpriseOne services, converts company and document context into the target model, and updates downstream records idempotently. Batch results and partial line failures are separated from transport failures so that only safe operations are retried.
Martini capabilities used
- scheduled workflows
- API consumption
- data transformation
- business rules
- reconciliation
- retry handling
Pattern 4: Distribute Items and inventory availability
When to use this pattern
Use this pattern when a commerce or analytics platform requires current EnterpriseOne item, branch, unit-of-measure, and availability information. Incremental retrieval and controlled throughput reduce load on AIS Server.
Integration direction
Example Mapping
| Oracle JD Edwards EnterpriseOne Field | Canonical Field | Target Field |
|---|---|---|
| Item Number | itemId | Product.sku |
| Description | itemDescription | Product.title |
| Branch / Plant | locationId | Inventory location |
| Quantity Available | availableQuantity | Inventory level |
Martini implementation pattern
Martini retrieves changed Items and availability through AIS services or an orchestration, normalizes units, numbers, and branch context, and publishes validated updates to the target platform. The workflow records the last successful checkpoint, throttles requests, and sends rejected or stale updates to reconciliation.
Martini capabilities used
- scheduling
- API consumption
- mapping
- transformation
- checkpointing
- monitoring
- error handling
Applications commonly integrated with Oracle JD Edwards EnterpriseOne
Organizations can integrate EnterpriseOne with adjacent business applications using AIS REST services, orchestrations, BSSV SOAP services, and Martini workflows. The exact scope depends on the EnterpriseOne release, enabled services, modules, and customer-specific business rules.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Salesforce | Synchronize customer and contact information, sales orders, fulfillment status, and selected financial data between Salesforce and EnterpriseOne. | Salesforce → Martini → Oracle JD Edwards EnterpriseOne | Expose a Martini API for Salesforce-originated orders, invoke an EnterpriseOne orchestration, return the EnterpriseOne document number, and run a scheduled workflow for fulfillment and status updates. |
| ServiceNow | Exchange supplier, asset, purchase order, work order, and fulfillment information with EnterpriseOne. | Oracle JD Edwards EnterpriseOne → Martini → ServiceNow | Consume AIS REST responses or batch results, map EnterpriseOne identifiers into ServiceNow records, validate required fields, and route failures for reconciliation. |
| Shopify | Publish EnterpriseOne items, pricing, inventory availability, and fulfillment status while sending ecommerce orders into EnterpriseOne. | Shopify → Martini → Oracle JD Edwards EnterpriseOne | Receive Shopify order requests through a Martini API, transform lines and customer data, invoke an EnterpriseOne sales-order orchestration, and synchronize status on a schedule. |
| NetSuite | Coordinate customer, supplier, item, order, and financial information when organizations operate both ERP platforms or are migrating between them. | Oracle JD Edwards EnterpriseOne → Martini → NetSuite | Use scheduled extraction and controlled bidirectional workflows with canonical financial and master-data mappings, stable document identifiers, and duplicate checks. |
| Oracle Fusion Cloud ERP | Exchange financial, supplier, customer, and procurement information during coexistence, migration, or division-level integration. | Oracle JD Edwards EnterpriseOne → Martini → Oracle Fusion Cloud ERP | Orchestrate REST-based extraction and submission, normalize company, fiscal-year, document-type, and currency context, and reconcile responses across both ERP systems. |
| Workday | Synchronize selected employee, cost-center, supplier, and financial reference data with EnterpriseOne. | Workday → Martini → Oracle JD Edwards EnterpriseOne | Schedule retrieval of approved reference data, validate organizational identifiers, map the result to EnterpriseOne service payloads, and report rejected rows separately. |
| Jira | Link EnterpriseOne work orders or project activities with software and project tracking information. | Oracle JD Edwards EnterpriseOne → Martini → Jira | Poll or retrieve relevant work-order changes, map statuses and identifiers, expose controlled update endpoints, and apply idempotency rules to prevent duplicate issues. |
| Microsoft Power BI | Provide curated EnterpriseOne sales, inventory, purchasing, and financial data for analytics. | Oracle JD Edwards EnterpriseOne → Martini → Microsoft Power BI | Extract data through approved REST services, reports, or orchestrations, transform it into an analytical model, and deliver it to an approved reporting or data platform. |
How to build a Oracle JD Edwards EnterpriseOne integration in Martini
Objective
Establish environment-specific access to AIS, an orchestration endpoint, or BSSV using the authentication configured by the EnterpriseOne administrator.
Instructions in Martini
- Confirm the EnterpriseOne release, AIS or BSSV endpoint, environment, role, and service contract.
- Configure Basic Authentication or OAuth 2.0 as supported by the deployment.
- Store credentials, client information, and tokens in Martini environment-specific secrets.
- Test authorization separately from payload and business validation.
Objective
Select the event, API request, or schedule that starts the integration according to EnterpriseOne coverage and process timing.
Instructions in Martini
- Use a Martini API when an external application initiates the transaction.
- Use a supported EnterpriseOne callback only for configured event scenarios.
- Use a scheduler for polling, incremental synchronization, batch status, or reconciliation.
- Define a checkpoint or query window for repeatable retrieval.
Objective
Acquire the EnterpriseOne payload while accounting for pagination, filtering, asynchronous processing, and selected attachment behavior.
Instructions in Martini
- Call the approved AIS REST service, orchestration, or BSSV operation.
- Capture response identifiers, job identifiers, correlation IDs, and processing status.
- Poll long-running jobs separately from submission.
- Retrieve media objects only when the selected service explicitly supports them.
Objective
Coordinate EnterpriseOne calls with external applications, canonical models, business rules, and durable processing state.
Instructions in Martini
- Build the workflow around the EnterpriseOne business operation rather than a transport-only request.
- Separate submission, status polling, result retrieval, and reconciliation for asynchronous work.
- Route validation, security, transport, and business-rule failures through distinct handling paths.
- Preserve EnterpriseOne document, line, Address Book, and job identifiers.
Objective
Convert EnterpriseOne JSON or XML structures into a stable canonical model and the target application's schema.
Instructions in Martini
- Map company, fiscal year, document type, branch, ledger, currency, and line context explicitly.
- Preserve document numbers and line numbers without lossy numeric conversion.
- Normalize dates, time zones, decimals, units of measure, and localized fields.
- Validate required fields and customer-specific extensions before submission.
Objective
Ensure that requests comply with EnterpriseOne application rules and that duplicate or partial processing is handled safely.
Instructions in Martini
- Prefer EnterpriseOne applications and orchestrations for platform validations.
- Use lookup-before-create or supported idempotency controls for non-idempotent operations.
- Check response bodies and business status, not only HTTP status codes.
- Handle partial order, purchase-order, or batch outcomes explicitly.
Common Oracle JD Edwards EnterpriseOne data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Address Book records | Represent customers, suppliers, employees, contacts, and other parties. | Salesforce, ServiceNow, Workday, NetSuite, Oracle Fusion Cloud ERP | Martini retrieves or submits records through approved AIS services or orchestrations, maps party roles and stable Address Book numbers, validates required fields, and applies duplicate checks. |
| Sales Orders | Capture order headers, detail lines, quantities, prices, and fulfillment information. | Salesforce, Shopify, NetSuite, Oracle Fusion Cloud ERP | Martini transforms external order structures into EnterpriseOne requests, invokes an orchestration or REST service, preserves document and line identifiers, and checks processing status before retrying. |
| Purchase Orders | Represent procurement orders, suppliers, lines, quantities, receipts, and related status. | ServiceNow, NetSuite, Oracle Fusion Cloud ERP, Microsoft Power BI | Martini retrieves or submits purchase-order data, maps supplier and company context, handles batch or asynchronous responses, and routes rejected lines for reconciliation. |
| Items | Store item master information, branches, units of measure, and inventory attributes. | Shopify, Salesforce, Microsoft Power BI, NetSuite | Martini synchronizes item and branch data using incremental criteria where available, normalizes units and numeric values, and distributes validated inventory or catalog updates. |
| Work Orders | Track manufacturing, maintenance, or project-related work and status. | ServiceNow, Jira, Microsoft Power BI | Martini retrieves work-order changes, maps status and operational identifiers, applies business rules, and uses idempotent updates for downstream work items. |
| Invoices and vouchers | Represent accounts receivable invoices, accounts payable vouchers, payment status, and related financial transactions. | NetSuite, Oracle Fusion Cloud ERP, Salesforce, Microsoft Power BI | Martini normalizes financial context such as company, fiscal year, document type, ledger, and currency, then reconciles transaction identifiers and processing results. |
Authentication and security considerations
Authentication and authorization
EnterpriseOne access is configured at the AIS Server, BSSV, or service layer. Supported deployments may use Basic Authentication or OAuth 2.0, while EnterpriseOne users, roles, environments, and service permissions control access to applications, data, and orchestrations.
- Use a dedicated integration user with least-privilege access.
- Store credentials, OAuth client information, refresh tokens, and other secrets in Martini environment configuration.
- Maintain separate endpoints and credentials for development, test, and production.
- Do not assume API keys or JWT authentication unless enabled by the specific deployment or an intermediary identity service.
Operational considerations for Oracle JD Edwards EnterpriseOne integrations
Reliable EnterpriseOne operations
Integration behavior depends on the EnterpriseOne release, AIS configuration, application versions, custom orchestrations, enabled services, and security model.
- Confirm pagination, filtering, incremental queries, and query-volume limits before implementing synchronization.
- Use stable identifiers such as document number, company, document type, line number, item number, and Address Book number for correlation and idempotency.
- Control concurrency and retry backoff to protect AIS Server capacity and coordinate high-volume loads with batch windows.
- Separate transport, authentication, validation, business-rule, and asynchronous job failures.
- Inspect response bodies and processing status rather than treating every successful HTTP response as a completed transaction.
- Monitor schema changes to service definitions, orchestrations, application versions, custom fields, enumerations, and date or number formats.
- Capture request identifiers, job identifiers, correlation IDs, and reconciliation outcomes.
Why use Martini instead of scripts or point-to-point integrations?
More maintainable than point-to-point scripts
Martini provides a workflow-based integration layer between EnterpriseOne and the rest of the enterprise landscape. It can consume REST and SOAP services, expose stable APIs, apply mappings and business rules, and coordinate synchronous and asynchronous processing without embedding the entire integration in a single script.
- Reuse canonical mappings and workflow logic across Salesforce, Shopify, ServiceNow, analytics, and other targets.
- Keep EnterpriseOne credentials and environment differences outside workflow definitions.
- Handle polling, retries, idempotency, validation, partial results, and reconciliation consistently.
- Use EnterpriseOne orchestrations for EnterpriseOne-native business logic while keeping cross-system orchestration in Martini.
- Centralize monitoring, error handling, testing, and deployment of integration assets.
Frequently asked questions
EnterpriseOne can be integrated through AIS Server REST APIs, EnterpriseOne Orchestrator endpoints, and BSSV SOAP services. Selected configured events may provide outbound notifications, while scheduled polling, reports, batch jobs, and approved file or attachment services support other synchronization scenarios.
Yes. Martini can consume EnterpriseOne AIS REST APIs and orchestrations, consume BSSV SOAP services, expose APIs for external applications, transform JSON or XML, schedule synchronization workflows, and manage asynchronous status polling and reconciliation.
No. A dedicated EnterpriseOne connector is not required. Martini can integrate using EnterpriseOne's confirmed native mechanisms, including AIS REST APIs, Orchestrator endpoints, BSSV SOAP services, configured callbacks, scheduled retrieval, and supported authentication methods.
Lonti does not charge an additional per-connector or per-vendor fee to integrate EnterpriseOne. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Oracle, infrastructure providers, or other third-party systems based on subscriptions, usage, and deployment model.
Use AIS REST services or published orchestrations when the required operation is available through them. Use BSSV SOAP when an existing business service is required or when the needed capability is not exposed through the REST layer. The appropriate choice depends on the release, enabled services, and business process.
Selected event-driven notifications can be implemented through configured EnterpriseOne events and orchestrations, but coverage is not universal for every object or transaction. Martini can receive supported callbacks and use scheduled polling, reports, or an intermediary for unsupported events.
Martini can separate job submission from status polling, retain EnterpriseOne job and document identifiers, and reconcile completed or failed results. For non-idempotent creates, the workflow should check whether EnterpriseOne committed the transaction before retrying after a timeout.
Yes. Martini can expose a controlled REST API for Salesforce, Shopify, ServiceNow, or internal applications and translate those requests into EnterpriseOne REST, orchestration, or SOAP operations. This can isolate consumers from EnterpriseOne-specific payloads and service changes.
Related Martini documentation
APIs
Mapping
Integrate Oracle JD Edwards EnterpriseOne with confidence
Use Martini to connect EnterpriseOne AIS REST APIs, orchestrations, and BSSV SOAP services with the applications, workflows, and data platforms that support your enterprise.