Skip Headers
Oracle® Application Integration Architecture Oracle Design to Release Integration Pack for Agile PLM Product Lifecycle Management and JD Edwards EnterpriseOne Implementation Guide
Release 11.1

Part Number E22282-03
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Feedback page
Contact Us

Go to previous page
Go to next page
PDF · Mobi · ePub

5 Process Integration for Product Design Changes

This chapter provides an overview of the integration flow for product design changes and discusses:

5.1 Overview

The new part or product release and the product design modification process within Agile PLM results in the publication of an Engineering Change Order (ECO). The ECO that results from a new product contains lines with all of the new components used in a bill of material (BOM) followed by details about the BOM. Similarly, a product design modification results in an ECO containing all of the new or changed components used on the BOM followed by just the changes to the BOM.

Agile PLM can send all BOM information or only net changes to a BOM in an ECO. When Agile PLM releases a new product, it should include all BOM information. After an ECO is created and processed in JD Edwards EnterpriseOne, it should send only net changes in an ECO.

The Agile PLM requester ABCS (ProcessEngineeringChangeOrderAgileReqABCSImpl) sends the ECO enterprise business message (EBM) to EngineeringChangeOrderEBS. The EngineeringChangeOrderEBS does routes the JD Edwards EnterpriseOne Provider Application Business Connector Services (ABCS): CreateEngineeringChangeOrderListJDEE1ProvABCSImpl. The CreateEngineeringChangeOrderListJDEE1ProvABCSImpl performs the following actions:

The JD Edwards EnterpriseOne ECO processor provides a response to the requestor by invoking the EngineeringChangeOrderResponseEBS.


The Create ECO flow is one way from Agile PLM to JD Edwards EnterpriseOne. The system does not send any ECOs created in JD Edwards EnterpriseOne to Agile PLM.

5.2 Process Flow for Product Design Changes

This section discusses:

5.2.1 Creating ECO Flow

To create an ECO flow, complete these steps:

  1. Submit the ECO for approval (workflow step).

  2. After the ECO is approved, the system generates an Agile Content Service (ACS) workflow event to trigger the ECO process flow.

  3. The queue framework captures the ACS payload (aXML), which is generated for the event, and adds it to the integration queue.

  4. The queue framework identifies the highest priority queue message, processes it to create an ECO ABM, and triggers the requestor ABCS.

  5. The requestor ABCS transforms the ECO ABM to ECO EBM and triggers an operation on the Enterprise Business Service (EBS) that routes the EBM to JD Edwards EnterpriseOne with ECO EBM as the input.

  6. The EBS invokes the provider ABCS with EBM as input; the provider transforms EBM to JD Edwards EnterpriseOne ABM before invoking the EngineeringChangeOrderManager PBSSV (web service).

  7. The ECO business flow completes these steps:

    • Creates and/or updates items in JD Edwards EnterpriseOne and links them to branches or plants.

    • Creates an ECO in JD Edwards EnterpriseOne.

    • Associates the list of revised items with new revisions and effectivity dates, and schedules the ECO for implementation.

  8. The system updates the status of the queue message in the integration queue for monitoring.

  9. In JD Edwards EnterpriseOne, execute the UBE R30510 for creating BOMs.

Figure 5-1 illustrates the Create ECO flow:

Figure 5-1 Create ECO sequence diagram

This image is described in surrounding text Monitoring ECO Processes

To monitor each ECO process:

  1. Log in to the Oracle Enterprise Manager Console with user name and password.

  2. Navigate to SOA > soa-infra > default > CreateEngineeringChangeOrderListJDEE1ProvABCSImpl.

  3. Click the Instances tab to view the successful and unsuccessful runs.

  4. Click the instance id to display the Flow trace window.

  5. Select the CreateEngineeringChangeOrderListJDEE1ProvABCSImpl flow.

  6. Select the Flow tab.

  7. Scroll down and click InvokeEngineeringChangeOrderManager.

    The Activity Audit Trail page is displayed.

  8. Scroll down to find the ECO number under the CreateEngineeringChangeOrderManagerAppRespMsg tag > ConfirmEngineeringChangeOrders.

  9. If multiple ECOs are created in this flow, all such ECOs are displayed in a sequential order, Figure 5-2:

Figure 5-2 ECO created in a sequence

This image is described in surrounding text

Item Product and Item Catalog hold the part number that comes in from Agile PLM. JD Edwards EnterpriseOne generates the Item ID. The user is given this number for reference.

5.2.2 Orchestrating ECO Flow

Table 5-1 lists the flow for orchestrating an ECO:

Table 5-1 Flow for Orchestrating an ECO

Step Activity Remarks


Agile ACS transmits Agile PLM ECO data in payload in the form of predefined XML format known as aXML. The system queues this file for further processing.

Agile ACS acts as a trigger for ECO use case.


The QueueController framework reads the highest priority queue message and transforms the payload (aXML) to AgileCreateEngineeringChangeOrderListABM.

QueueController processes the payload.


QueueController invokes the ProcessEngineeringChangeOrderAgileReqABCSImpl with AgileCreateEngineeringChangeOrderListABM as input.



AgileCreateEngineeringChangeOrderListABM is transformed into CreateEngineeringChangeOrderListEBM.

ProcessEngineeringChangeOrderAgileReqABCSImpl makes call backs to Agile web services if needed.


ProcessEngineeringChangeOrderAgileReqABCSImpl invokes the CreateEngineeringChangeOrderList operation on EngineeringChangeOrderEBS with CreateEngineeringChangeOrderListEBM as input.



EngineeringChangeOrderEBS routes CreateEngineeringChangeOrderListEBM to CreateEngineeringChangeOrderListJDEE1ProvABCSImpl.



CreateEngineeringChangeOrderListJDEE1ProvABCSImpl transforms CreateEngineeringChangeOrderListEBM into EngineeringChangeOrderManagerABM and invokes the JD Edwards EnterpriseOne web service with this input payload.

Creates or updates items in JD Edwards EnterpriseOne and links them to the branch/plants, creates an ECO, associates revised items to it, and creates a BOM.


CreateEngineeringChangeOrderListJDEE1ProvABCSImpl invokes CreateEngineeringChangeOrderListResponse operation on EngineeringChangeOrderResponseEBS with CreateEngineeringChangeOrderListResponseEBM as input.



EngineeringChangeOrderResponseEBS routes CreateEngineeringChangeOrderListResponseEBM to ProcessEngineeringChangeOrderAgileReqABCSImpl.

Routes a response message


ProcessEngineeringChangeOrderAgileReqABCSImpl sends the status back to the QueueController to update the queue.

QueueController updates this status against the queue message in the database.


ProcessEngineeringChangeOrderAgileReqABCSImpl transforms CreateEngineeringChangeOrderListResponseEBM into AgileUpdateEngineeringChangeOrderListABM.

AgileUpdateEngineeringChangeOrderListABM is sent as input to the Agile Web service.

The Web service updates the status on the change order in Agile PLM, which is predefined P2 or P3 attributes on ECO object in Agile PLM.

Note: The ProcessEngineeringChangeOrderAgileReqABCSImpl composite uses the oracle/wss_http_token_client_policy client security policy while calling the ChangeABS service hosted on the Agile server. The security credentials for this are stored in the csf-key AgileWebServicesKey on Fusion Middleware (FMW). The Agile username and password must be setup correctly so that the Agile service is invoked successfully from the AIA composite in the FMW layer.

5.3 Solution Assumptions and Constraints

This design assumes that the following statements are true:

  1. Do not use JD Edwards EnterpriseOne to create any new item or BOM.

  2. In Agile PLM, we use the term change order generically to describe an ECO, a Manufacturing Change Order (MCO), and a Site Change Order (SCO).

  3. This integration does not support MCOs.

    This integration supports SCOs and ECOs only with BOM information.

  4. The system does not import any AML data passed to JD Edwards EnterpriseOne in this integration into JD Edwards EnterpriseOne.

  5. You should use ECO to transfer the new part and update part information from Agile PLM to JD Edwards EnterpriseOne.

    An Agile PLM user must ensure that new and updated items are available on the Affected Items tab before releasing the ECO to JD Edwards EnterpriseOne.

  6. Use ECOs to redline BOMs for associating new revisions, effectivity date changes, and inclusion of new items on BOMs.

    When creating new items, an Agile PLM user must ensure that the new items are available on the Affected Items tab before releasing the ECO to JD Edwards EnterpriseOne.

  7. Agile PLM user can redline a BOM and add a new site in one change order.

  8. If multiple sites are associated in Agile PLM for a single ECO, then multiple ECOs are created for each branch plant (site) in JD Edwards EnterpriseOne.

  9. You must approve ECOs in Agile PLM before initiating the integration flow.

  10. ECOs are pre-approved in Agile PLM; therefore, an approval layer in JD Edwards EnterpriseOne is not required before implementing these ECOs through the scheduled Batch Process - R30510 for creating BOMs.

    However, if the JD Edwards EnterpriseOne user decides to add an approval layer, the system does not support any rejection in this approval process.

  11. If BOM creation through R30510 fails for any reason, the message is not sent back to Agile PLM automatically.

  12. If the JD Edwards EnterpriseOne user decides to notify Agile PLM about an ECO rejection or failure to create a BOM, then the user must manually update the appropriate status code on the ECO.

    The subsequent run of the update ECO flow from JD Edwards EnterpriseOne to Agile PLM will send the status message to Agile PLM.

  13. These processes are synchronous.

  14. Because, Agile PLM maintains effectivity dates at the parent level, JD Edwards EnterpriseOne forwards the same date to all related component items.

  15. The BOMs loaded from JD Edwards EnterpriseOne as part of an initial load might have a mixture of stock and nonstock component items.

    You can modify the stock items on the BOM and send them successfully to JD Edwards EnterpriseOne through ECO. However, you cannot change the nonstock components.

  16. The maximum description length of ECOs and items in JD Edwards EnterpriseOne is 30.

    If an Agile PLM user sends a description that exceeds this length, the message is truncated and the first 30 characters are inserted or updated into JD Edwards EnterpriseOne.

  17. The Stocking type DVM (ITEM_TYPE.dvm) must be in sync with the stocking types in JD Edwards EnterpriseOne.

5.4 Agile PLM Interfaces

Table 5-2 lists the Agile PLM Web Services Definition Language (WSDL) files:

Table 5-2 Agile LM Web Services Definition Language (WSDL) files:

Interfaces Description



Sends the released ECO to be created as an EngineeringChangeOrder in JD Edwards EnterpriseOne

Table 5-3 lists the Agile PLM XML Schema Definition (XSD) files:

Table 5-3 Agile PLM XML Schema Definition (XSD) files

Interface Description




Contains CreateEngineeringChangeOrderListABM and CreateEngineeringChangeOrderListResponseABM, and corresponding ABOs

5.5 JD Edwards EnterpriseOne Interfaces

Table 5-4 lists the JD Edwards EnterpriseOne WSDL files:

Table 5-4 JD Edwards EnterpriseOne WSDL files

Interface Description



Creates an ECO in JD Edwards EnterpriseOne

5.6 Core AIA Components

Table 5-5 lists the components used in the process integration for Create ECO flow:

Table 5-5 Components in ECO Flow

Service Description

Enterprise Business Object (EBO)








Table 5-6 lists the locations of components:

Table 5-6 Location of Components

Component Location

EBO and EBM XSD files


WSDL files

$AIA_HOME/AIAMetaData/AIAComponents/EnterpriseBusinessServiceLibrary /Core/EBO/

For detailed documentation of individual EBOs and EBMs, click the AIA Reference Doc link on EBO and EBM detail pages in Oracle Enterprise Repository.

For more information about using the Oracle Enterprise Repository and configuring it to provide the AIA Reference Doc link, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack 11g Release 1, "Configuring and Using Oracle Enterprise Repository as the Oracle AIA SOA Repository."

You can extend EBOs, for instance, to add new data elements. These extensions are protected and remains intact after a patch or an upgrade.

For more information, see Oracle Fusion Middleware Concepts and Technologies Guide for Oracle Application Integration Architecture Foundation Pack 11g Release 1, "Understanding Extensibility."

5.6.1 Agile PLM and JD Edwards EnterpriseOne Components for Creating ECO

Table 5-7 lists the Agile PLM and JD Edwards EnterpriseOne components for creating ECO flow:

Table 5-7 Agile PLM and JD Edwards EnterpriseOne components for creating ECO flow:

Services Agile PLM (Requester) JD Edwards EnterpriseOne (Provider)












Business Process Execution Language (BPEL)




Table 5-8 lists the locations of the components:

Table 5-8 Location of Components



Application Business Objects, ABM, and Common XSD files

$AIA_HOME/AIAMetaData/AIAComponents/ ApplicationObjectLibrary/Agile/V1/schemas

$AIA_HOME/AIAMetaData/AIAComponents/ ApplicationObjectLibrary/JDEE1/V1/schemas

WSDL files

$AIA_HOME/AIAMetaData/AIAComponents/ ApplicationObjectLibrary/Agile/V1/wsdls

$AIA_HOME/AIAMetaData/AIAComponents/ ApplicationObjectLibrary/JDEE1/V1/wsdls

5.7 Integration Services

These services are delivered with the process integration for product design changes from Agile PLM to JD Edwards EnterpriseOne:

5.7.1 EngineeringChangeOrderEBS

EngineeringChangeOrderEBS is the EBS that exposes the operations related to the EngineeringChangeOrder Integration on the EngineeringChangeOrder EBO. The routing rules are:

  • EngineeringChangeOrderEBS

    ProcessEngineeringChangeOrderAgileReqABCSImpl routes CreateEngineeringChangeOrderListEBM to CreateEngineeringChangeOrderListJDEE1ProvABCSImpl.

  • EngineeringChangeOrderResponseEBS

    CreateEngineeringChangeOrderListJDEE1ProvABCSImpl routes CreateEngineeringChangeOrderListResponseEBM to ProcessEngineeringChangeOrderAgileReqABCSImpl.

5.7.2 ProcessEngineeringChangeOrderAgileReqABCSImpl

ProcessEngineeringChangeOrderAgileReqABCSImpl transforms the Agile PLM message (AgileCreateEngineeringChangeOrderListABM) into CreateEngineeringChangeOrderListEBM and invokes the EBS service to Create ECOs in JD Edwards EnterpriseOne. JD Edwards EnterpriseOne processes these ECOs and sends a CreateEngineeringChangeOrderListResponseEBM response to Agile PLM. ProcessEngineeringChangeOrderAgileReqABCSImpl receives the CreateEngineeringChangeOrderListResponseEBM and transforms it to Agile ABM message (AgileUpdateEngineeringChangeOrderListABM) before invoking ACS.

The process flow:

  • Receives AgileCreateEngineeringChangeOrderListABM from ProcessEngineeringChangeOrderAgileReqABCSImpl, which gets the same from ACS

  • Transforms this message into the CreateEngineeringChangeOrderListEBM

  • Populates the EBM header by determining the target system IDs and adding them to the EBM header to control routing

  • Validates required fields

  • Transforms ABM to EBM

  • Calls target CreateEngineeringChangeOrderList service with operation CreateEngineeringChangeOrderList

  • Receives CreateEngineeringChangeOrderListResponseEBM

  • Transforms response EBM to AgileUpdateEngineeringChangeOrderListABM

  • Invokes ACS for propagating the response to queue and Agile PLM

ProcessEngineeringChangeOrderAgileReqABCSImpl has the following transformation:

  • AgileCreateEngineeringChangeOrderListABM_to_CreateEngineeringChangeOrderListEBM

  • CreateEngineeringChangeOrderListResponseEBM_to_AgileUpdateEngineeringChangeOrderListABM

5.7.3 CreateEngineeringChangeOrderListJDEE1ProvABCSImpl

CreateEngineeringChangeOrderListJDEE1ProvABCSImpl receives the CreateEngineeringChangeOrderListEBM message from ECOEBS and transforms the EBM into the JD Edwards EnterpriseOne-specific CreateECOABM. It then invokes the JD Edwards EnterpriseOne EngineeringChangeOrderManager service for creating and updating items and creating ECOs. JDEE1EngineeringChangeOrderManager service returns the list of items and ECOs created for a success or throws the appropriate fault for a failure.

It then transforms the JD Edwards EnterpriseOne-specific response message CreateEngineeringChangeOrderResponseABM to CreateEngineeringChangeOrderListResponseEBM and invokes the routing service EngineeringChangeOrderResponseEBS for sending the response message back to Agile PLM.

The process flow is:

  • Receives CreateEngineeringChangeOrderListEBM from EngineeringChangeOrderEBS

  • Transforms CreateEngineeringChangeOrderListEBM into JD Edwards EnterpriseOne-specific message CreateEngineeringChangeOrderABM

    Populates EBM header by determining Target System IDs and adds them to the EBM header to control routing

    Validates required fields

  • Assigns implemented status if the payload only contains items

    If the payload contains BOM information, then the status does not change. BOM's will be created in "Approved" state.

  • Uses DynamicPartnerlink to determine TargetEndpointLocation

  • Invokes EngineeringChangeOrderManager web service

  • Transforms the JD Edwards EnterpriseOne-specific message CreateEngineeringChangeOrderResponseABM into the CreateEngineeringChangeOrderListResponseEBM

  • Invokes the EngineeringChangeOrderResponseEBS service to send the response message (CreateEngineeringChangeOrderListResponseEBM) to ProcessEngineeringChangeOrderAgileReqABCSImpl

ProcessEngineeringChangeOrderListJDEE1ProvABCSImpl has the following transformation:

  • Xform_EngineeringChangeOrderListEBM_To_EngineeringChangeOrderManagerReqMsgABM

  • Xform_EngineeringChangeOrderManagerRespMsg_To_