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

> Source: https://netray.co/stack/oracle-cpq-configure-to-order-jd-edwards-orchestrator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Stack

## Short answer

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.

## Erp

JD Edwards EnterpriseOne

## Erp Key

jd-edwards

## On Prem

true

## Product

Oracle CPQ to JDE configure-to-order integration

## Vendor

Birlasoft (Oracle partner)

## Category

CPQ

## Integration

**Method:** Oracle SOA Suite plus JDE Orchestrator, real time

**Detail:** 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.

**Method:** Unchanged standard JDE sales order application

**Detail:** 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.

## Data Flows

**From:** Oracle CPQ

**To:** JD Edwards

**Data:** Configured sales order lines with selected options

**Trigger:** Quote is accepted

**From:** Oracle CPQ

**To:** JD Edwards

**Data:** Work order parts list built from configured options

**Trigger:** Order creation in JDE

**From:** JD Edwards

**To:** Oracle CPQ

**Data:** Sales order and work order numbers

**Trigger:** Successful creation in JDE

**From:** JD Edwards

**To:** Oracle CPQ

**Data:** Error messages for failed order or work order creation

**Trigger:** Validation failure in JDE

## Setup

### Replace fixed BOMs with option logic

**Detail:** Work with engineering to define which options drive which components, quantities and operations.

### Design the work order parts list mapping

**Detail:** Decide how a configuration becomes a parts list on a JDE work order, and how it handles substitutions and phantom items.

### Build the orchestrations

**Detail:** Create Orchestrator services for sales order and work order creation, and secure them with an integration user.

### Build the SOA Suite flow

**Detail:** Implement mediation, transformation and error handling between CPQ and Orchestrator.

### Test real configurations

**Detail:** Run complex configurations end to end and compare the resulting parts list with a hand-built one.

### Plan change control

**Detail:** Set a release process for configuration model changes so they are tested against JDE before production.

## Pitfalls

- 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.

## Ai Layer

### Failed order diagnosis

**Description:** 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

**Description:** 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

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

## Alternatives

- 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.

## Faq

### What did this implementation achieve?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Source

https://www.birlasoft.com/case-studies/transforming-configure-order-workflows-oracle-jde-cpq-integration

## Search terms

oracle cpq jde orchestrator configure to order, jd edwards configure to order, jde work order parts list cpq, birlasoft jd edwards cpq, oracle soa suite jde orchestrator, jde configurator

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json