CPQJD Edwards EnterpriseOneRuns on-prem

Oracle CPQ configure-to-order with JD Edwards via SOA Suite and Orchestrator

Birlasoft describes moving a cash-technology equipment manufacturer from fixed BOMs to configure-to-order. CPQ options feed the JDE work order parts list, and sales and work orders are created automatically in real time using Oracle SOA Suite and JDE Orchestrator, with the standard JDE sales order application left unchanged.

How Oracle CPQ to JDE configure-to-order integration connects to JD Edwards EnterpriseOne

Oracle SOA Suite plus JDE Orchestrator, real time

Per the case study, SOA Suite mediates between CPQ and JDE while Orchestrator exposes JDE sales and work order creation. Real time means the configurator can create orders without batch files.

Unchanged standard JDE sales order application

The case study notes the standard JDE sales order application stays unchanged. That lowers upgrade risk, because customization is concentrated in the integration and the configuration model.

What data moves

FromToDataWhen
Oracle CPQJD EdwardsConfigured sales order lines with selected optionsQuote is accepted
Oracle CPQJD EdwardsWork order parts list built from configured optionsOrder creation in JDE
JD EdwardsOracle CPQSales order and work order numbersSuccessful creation in JDE
JD EdwardsOracle CPQError messages for failed order or work order creationValidation failure in JDE

Setting it up

  1. 1Replace fixed BOMs with option logicWork with engineering to define which options drive which components, quantities and operations.
  2. 2Design the work order parts list mappingDecide how a configuration becomes a parts list on a JDE work order, and how it handles substitutions and phantom items.
  3. 3Build the orchestrationsCreate Orchestrator services for sales order and work order creation, and secure them with an integration user.
  4. 4Build the SOA Suite flowImplement mediation, transformation and error handling between CPQ and Orchestrator.
  5. 5Test real configurationsRun complex configurations end to end and compare the resulting parts list with a hand-built one.
  6. 6Plan change controlSet a release process for configuration model changes so they are tested against JDE before production.

What usually breaks

  • !Option rules that produce parts missing in a branch/plant fail work order creation.
  • !A failure after the sales order is created but before the work order exists leaves an inconsistent state unless you handle compensation.
  • !Phantom and substitute components in JDE BOM logic do not map one to one with configurator options.
  • !A new option added in CPQ with no matching JDE item goes live and errors on the first order.
  • !Real-time calls make CPQ users wait on JDE performance, so timeouts need a defined behavior.

A private AI layer across both systems

Failed order diagnosis

A private assistant reads integration errors and JDE records, explains why a configured order failed, and drafts the corrected item or branch/plant setup for approval.

Parts list sanity check

It compares a generated work order parts list with similar past orders and flags missing or unusual components before production starts.

Configuration model gap report

Reading orders that engineering changed after release, it suggests which option rules were incomplete, for the model owner to review.

Try it here, free

JD Edwards Orchestrator Design Template

Open full tool

A fill-in design document for a JD Edwards Orchestrator orchestration: purpose, inputs, steps, rules, outputs, security and test cases.

When something else fits better

  • If configurations are few, JDE kits or planning bills may handle variants without a separate configurator.
  • The packaged ICS integration may be adequate if you do not need work order creation from options.
  • Where only a handful of variants exist, engineering-to-order with manual BOM creation may still be simpler.

Frequently asked questions

What did this implementation achieve?

Per Birlasoft's case study, it moved a cash-technology equipment manufacturer from fixed BOMs to configure-to-order, with CPQ options feeding the JDE work order parts list and orders created automatically. Treat it as one vendor case, not a guarantee.

How does the integration connect?

The case study describes Oracle SOA Suite and JDE Orchestrator in real time, leaving the standard JDE sales order application unchanged. Your design will differ with your BOM structure and network layout.

Can a private AI layer help here?

Yes, mainly as a read-only reviewer: diagnosing failed orders, sanity-checking parts lists and finding rule gaps. It runs on your own servers, and any correction to JDE records goes through a person.

Pairing documented at www.birlasoft.com/case-studies/transforming-configure-order-workflows-oracle-jde . Oracle CPQ to JDE configure-to-order integration is a product of Birlasoft (Oracle partner); Netray is independent and not affiliated with either vendor.

Keep exploring

Free tools

ERP fixes and how-tos

Runs with your ERP

Guides

AI on your ERP

Integrations

Software