| Agile Product Lifecycle Management Integration Pack for SAP: Design to Release Implementation Guide Release 3.6 E88840-01 |
|
 Previous |
 Next |
| Agile Product Lifecycle Management Integration Pack for SAP: Design to Release Implementation Guide Release 3.6 E88840-01 |
|
Previous |
Next |
Integration of Change Order Release, namely the Engineering Change Order (ECO) and New Part/Product Release (PREL) from Agile to System Application and Products (SAP) is about introducing a new product, components, and structure into SAP upon the release of design from Agile or updating existing design metadata or structure. This process is triggered from Agile.
|
Note: The integration flow is similar for both ECO and PREL use cases. |
The process of Change Order Release, which comprises of new part introduction and manufacturing update, is the flow of Item and Bill of Material (BoM) information from Agile to SAP. This information is pushed from Agile, triggered by an event tied to the change in status of a Change Order (CO) object. The information is then parsed in an integration object format and sent to SAP for implementation. A confirmation of the implementation status is sent back to Agile.
This integration process supports the following flow:
Release of CO in Agile
Agile XML (aXML) generation by Agile Content Server (ACS)
Parsing and transformation of aXML data
Posting Changer Order data to SAP
Communicating order processing status to Agile
When a change analyst approves the CO in Agile, it is marked as Released. This makes all the changes specified in the CO take effect in Agile.
Before the CO is released, it is pre-validated at the approval stage. This involves validation of certain business rules to ascertain that the flow of the CO from Agile to SAP meets all the conditions set in the destination system.
The ACS generates an aXML file from the CO data. This file contains information of items, BoM, manufacturers, as well as the CO itself.
For the purpose of the Agile to SAP integration process, the ACS is configured to ensure the following:
The aXML file is configured to carry the following elements from a CO:
Change Order Data: Cover Page, Page Two, Page Three, Affected Items tab attributes
Revised Item Data: Title Block, Page Two, Page Three
BoM Data: BoM tab of Items (including reference designators) with delta BoMs only for the revision on CO.
Upon release of a CO, the aXML file goes to a JMS Queue.
The data contained in aXML file generated by Agile is not in the format that is understood by enterprise business objects. Therefore, this data must be parsed and transformed.
The parsing and transformation of aXML data entails the following:
Segregation of business objects
Sequencing and queuing of COs
Translating Agile Site specific objects into SAP Plant specific objects
Translating Agile CO Types into SAP CO Type.
All the change types from Agile are mapped to the Engineering Change Master record in SAP.
Ascertaining the business objects existence from SAP to prepare the data in either Create or Update mode.
Mapping Agile CO attributes to corresponding attributes in SAP
Defining User Exit Points for custom transformations
The aXML file contains collective information about the business objects - CO, Item Attributes, Revised Item Lines, BoM Redlines, Reference designators, and so on. This information is broken down into individual components and mapped one to one with corresponding Enterprise Business Objects (EBOs), namely Item, Change and Structure.
In order to maintain referential integrity, the Change Number is associated with each individual business object.
The CO release process begins with the queuing of CO Number in Process Queue Controller, which sequences the COs for transfer of parsed data to SAP. Once the data is processed by SAP and its implementation status received, the CO is removed from the process queue.
The data coming from Agile is split into individual SAP organization specific business objects. This is because the data in Agile can be either:
Centralized - all design locations share the same product design information
De-centralized - the Item Attributes, change control, and so on are implemented to multiple sites.
The data in SAP is segregated by Plants.
In Agile, a CO is categorized into the following change types:
Engineering Change Order (ECO)
Manufacturing Change Order (MCO)
Site Change Order (SCO)
These categories are called Classes in Agile. A class may have one or more sub-classes.
SAP does not have separate categories for each of these change types and cannot be differentiated. Therefore, during the parsing and processing of these change types in Agile, they are translated in SAP with the following characteristics:
| Feature | ECO | MCO | SCO |
|---|---|---|---|
| Customer adoption | All installations | All installations | --- |
| New Revisions for revised items | Mandatory | Not supported | Not supported |
| Tables redlined | BOMs;
Global as well as site-specific |
Global BOM as well as site-specific | Site-specific BOMs. |
| Effectivity Date | At line level;
Global when multi-site is not enabled; Separate for each site when multi-site is enabled |
Not specified on Change Order | At line level; site-specific only |
| Other line-level attributes | Global when multi-site is not enabled;
Separate for each site when multi-site is enabled |
Global when multi-site is not enabled;
Separate for each site when multi-site is enabled |
Site-specific only |
| New Item Release | Supported | Supported | Only item updates are supported |
An Item is created in the SAP Plant in two ways:
Agile releases New Part Introduction information to SAP through a CO as a First Time release.
The Item information is loaded in SAP by an external system other than SAP and Agile.
If the Item already exists in the SAP Plant, and Agile releases a CO to create the same Item, the system updates the item. Because Agile does not explicitly pass information about first time or subsequent release of Item; a cross-reference table is employed to ascertain the existence of the Item in SAP.
This cross-reference table maintains unique identifiers for the Items received from Agile as well as the corresponding Items created in SAP. It also maintains the unique identifiers for the Items created in SAP by an external application. These unique identifiers help in ascertaining the existence of an Item in SAP, thereby eliminating any duplicate errors.
The source system attributes are mapped to destination system attributes. This mapping also defines the direction of the data flow. This is accomplished as follows:
Different sets of mappings are defined for:
§ Information flowing from Agile to Enterprise Business Objects (EBOs).
§ Iinformation flowing from EBOs to Agile.
These are accessed in the user interface (UI) as different 'mapping profiles'.
A parameter is specified with each mapping done from the UI. This parameter determines whether the mapping applies to one or both of the directions of data flow.
For more information about Agile to SAP mappings, see "Agile PLM to SAP Entity Maps".
Agile PLM records the design specifications of a part. This information is updated either on an ECO or a MCO. A new part is created in the ERP using reference material in SAP. Revisions to a part, effective dateBoM, item, and reference designator information are controlled by the ECO, which transfers the information from Agile to the ERP system.
The release of change order in the PLM system acts as a trigger for the synchronization of product design information with the ERP system. A synchronization process is the transfer of the released revision of the product design from Agile PLM to the manufacturing system.
The Process Queue Controller drives the integration of the change order release process between Agile PLM and the SAP system. To maintain the integrity of data in the ERP system, it is important that COs are transferred to that system in the same sequence they were released by the source system.
The Agile PLM to SAP process flow consists of two phases: Pre-Process ECO and Post-Process ECO:
Pre-Process ECO
Application Business Message (ABM) to Enterprise Business Message (EBM) transformations:
Invoke Provider
Receive Response
Send Response to the Queue
Post-Process ECO
Update the transfer status in Agile PLM
The processing of CO data into the ERP system is the backbone of this integration. As part of this step, the following activities must be performed:
Item Master synchronization: For all items pushed to the ERP system, verify whether or not the items already exist. If the item does not exist in ERP then create it. If the Item already exists in ERP, then update the Item. It is assumed that the source and target systems are in sync before the integration begins so that it is not necessary for the integration to check if both the systems are in sync before posting the data.
Create Change Order: The actual CO is created as Change Master Object in the ERP system. When the Change Master record is posted to SAP, the status is set to Inactive. When all the line items on this change are posted successfully to SAP then the integration changes the Change Master status in SAP to Active. This means this Change Master is complete and all the changes effective on this change are in-force from scheduled effectivity and valid from date. This Active CO status from SAP is transferred to the corresponding mapped Page Two field in Agile as Transferred.
Item Plant Assignment: Items are assigned to plants based on criteria specified in the section on supporting distributed manufacturing above.
BoM Update (including reference designator): The aXML data from Agile contains only the changes made to BoMl and not the complete BoM. As a result, BOM data must be in sync between Agile and ERP for the older revision in order for the new revision of BOM data to be posted successfully.
When the process of posting Change Order data into the SAP system completes (successfully or with errors), the following steps are taken
If the parameter Change.TransferStatusAttribute is assigned to Page Two field in Agile, then upon successful creation of the CO in SAP with status Active it is propagated back to Agile as Transferred in the specified Page Two field, else Errored status is propagated.
From Agile PLM 9.3.3 onwards, you are provided with a new Action Items tab that corresponds to each ATO. If ECO processing fails in the AIA layer, a corresponding error details is displayed in the Action Items tab in Agile PLM.
To track business or system errors, a business user does not have to use the Queue Monitoring UI. The actions taken by the Change Analyst are as follows:
■ For business errors, modifies the CO and resubmits. This creates a new ATO.
■ For system errors, resubmits the same ATO back into AIA, either from AIA Queue UI or from Agile ATO Actions tab. To avoid inconsistency in the Action Items tabs data, we recommend that you use re-submit/re-process functionality.
COs must be transferred to ERP in the order in which they were released by the source system.
If a part does not exist in ERP, then create the part.
If a part exists in ERP system, then update the part.
Design changes, Effectivity Date, BoM, Item, and Reference Designators are all controlled by the ECO.
Part information and design specifications are updated from Agile to ERP system using the ECO.
There is a business process that prioritizes and monitors the Change Order Process.
Only one CO (first one in the queue) undergoes ERP Processing at a time. The next process can start its execution only after the execution of the first process is completed.
The integration administrator has the provision of error handling and reporting the same to the end user.
Action Item gets assigned to Change Analyst of the Change Order. In case Change Order is not assigned to any Change Analyst, then Action Item gets assigned to Agile PLM user provided at the time of PIP installation. It is assumed that User Name does not contain any special character such as "(*" and so on. Only one Change Analyst is assigned to any Change Order.
In case an ATO is re-sent through re-process action in ATO Action Item tab, previously sent message is automatically removed from the queue and no additional action is required on Queue UI to be reprocessed. Queue is automatically unblocked.
SOA Auto Recovery must be turned off when Action Items tab of an ATO is used for Error handling from Agile 9.3.3 onwards.
The integration flow is same for both ECO and PREL:
An ECO is created with items in Affected Items (AI) tab with new revisions and lifecycle phases specified. The ECO is routed for Approval (workflow step).
An ACS Workflow Event is generated on Approval of the ECO in Agile to trigger the ECO process flow.
The Queue framework captures the ACS payload (aXML) generated for the event and adds it to the integration Queue.
The Queue framework identifies the highest priority Queue Message, processes it to create an ECO ABM and triggers the Requestor ABCS.
The Requestor ABCS transforms the ECO ABM to ECO EBM and triggers an operation on the Enterprise Business Service (EBS), which routes the EBM to the ECO business flow with ECO EBM as the input.
The ECO Business Flow:
§ Creates new items in ERP
§ Creates an ECO in the SAP.
§ Associates the list of revised items with new revisions and effectivity dates, and schedules the ECO for effectivity date.
§ Creates new BoM
§ Updates existing Item in SAP
§ Updates existing BoM in SAP
§ Updates the Transfer Status in Agile.
6. The status of Queue Message is updated in the Integration Queue, for monitoring.
Exceptions
The following exception conditions create error messages for this integration process:
If Agile PLM and SAP are not in sync with regards to the earlier revision of the revised item (that is, per the data from Agile PLM, the old revision of the item does not match the current revision of the item in SAP), an error occurs.
Failure to update the queue status.
Errors raised during the transformations.
The below diagram illustrates the Change Order Services orchestration from Agile Application to SAP ERP.
This table list the activities involved in the Change Order Release Services orchestration:
| # |
Activity | Remarks |
|---|---|---|
| 1 | Agile ACS acts as a trigger for ECO Use case. | Agile ACS transmits Agile Engineering Change Order Data in payload in the form of predefined XML format known as aXML. This file will get queued up for the further processing. |
| 2 | QueueController processes the payload | The Queue Controller Framework reads the highest priority Queue Message and transforms the payload (aXML) to AgileCreateEngineeringChangeOrderListABM. |
| 3 | Invoke ProcessEngineeringChangeOrderAgileReqABCS | QueueController invokes the ProcessEngineeringChangeOrderAgileReqABCS with AgileCreateEngineeringChangeOrderListABM as input. |
| 4 | ProcessEngineeringChangeOrderAgileReqABCS makes call back to Agile Web services, if needed. | ProcessEngineeringChangeOrderAgileReqABCS calls the web services exposed in agile side to enrich AgileCreateEngineeringChangeOrderListABM.
AgileCreateEngineeringChangeOrderListABM is transformed into CreateEngineeringChangeOrderEBM. |
| 5 | ProcessEngineeringChangeOrderAgileReqABCS invokes EngineeringChangeOrderEBS | ProcessEngineeringChangeOrderAgileReqABCS invokes CreateEngineeringChangeOrder operation on EngineeringChangeOrderEBS with CreateEngineeringChangeOrderEBM as input |
| 6 | EngineeringChangeOrderEBS routes CreateEngineeringChangeOrderListEBM to CreateEngineeringChangeOrderListEBF | CreateEngineeringChangeOrderListEBM is passed to CreateEngineeringChangeOrderListEBF as input. |
| 7 | CreateEngineeringChangeOrderEBF invokes SyncItemListSAPProvABCS | CreateItemListEBM is passed to SyncItemListSAPProvABCS as input |
| 9 | SyncItemListSAPProvABCS transforms the input and calls the SAP service | SyncItemListSAPProvABCS transforms CreateItemListEBM to the input of SAP service and calls that service.Creates items in ERP |
| 10 | SyncItemListSAPProvABCS calls ItemResponseEBS (Response Port) with CreateItemListResponseEBM | SyncItemListSAPProvABCS invokes the CreateItemListResponse operation on ItemResponseEBS with CreateItemListResponseEBM as input |
| 11 | CreateEngineeringChangeOrderListEBF calls ProcessBillOfMaterialsListSAPProvABCS | CreateEngineeringChangeOrderListEBM will be passed to ProcessBillOfMaterialsListSAPProvABCS as the input |
| 12 a) | Based on the existence of the BOM ProcessBillOfMaterialsListSAPProvABCS invokes routes to CreateBillOfmaterialsListSAPProvABCSImpl (or) UpdateBillOfMaterialsListSAPProvABCSImpl | |
| 12 b) | ProcessBillOfMaterialsListSAPProvABCSImpl is invoked before ProcessBillOfMaterialsListSAPProvABCS calls UpdateBillOfMaterialsListSAPProvABCSImpl | CreateEngineeringChangeOrderListEBM is passed to ProcessBillOfMaterialsListSAPProvABCSImpl & after this UpdateBillOfMaterialsListEBM is passed to UpdateBillOfMaterialsListSAPProvABCSImpl |
| 13 a) | CreateBillOfMaterialsListSAPProvABCSImpl transforms the input and calls the SAP service | CreateBillOfMaterialsListSAPProvABCSImpl will transform CreateBillOfMaterialsListEBM to the input of SAP service and calls that service.
Creates the BillOfMaterialsList in ERP |
| 13 b-i) | ProcessBillOfMaterialsListSAPProvABCSImpl transforms the input and calls the SAP service | ProcessBillOfMaterialsListSAPProvABCSImpl transforms CreateEngineeringChangeOrderListEBM to the input of SAP service and calls that service |
| 13 b.ii) | UpdateBillOfMaterialsListSAPProvABCSImpl transforms the input and calls the SAP service | UpdateBillOfMaterialsListSAPProvABCSImpl transforms UpdateBillOfMaterialsListEBM to the input of SAP service and calls that service.
Updates the BillOfMaterialsList in ERP |
| 14 a) | CreateBillOfMaterialsListSAPProvABCSImpl calls ProcessBillOfMaterialsListSAPProvABCS (Response Port) with CreateBillOfMaterialsListResponseEBM | CreateBillOfMaterialsListSAPProvABCSImpl invokes CreateBillOfMaterialsListResponse operation on ProcessBillOfMaterialsListSAPProvABCS with CreateBillOfMaterialsrListResponseEBM as input |
| 14 b) | UpdateBillOfMaterialsListSAPProvABCSImpl calls ProcessBillOfMaterialsListSAPProvABCS (Response Port) with UpdateBillOfMaterialsListResponseEBM | UpdateBillOfMaterialsListSAPProvABCSImpl invokes UpdateBillOfMaterialsListResponse operation on UpdateBillOfMaterialsListSAPProvABCSImpl with UpdateBillOfMaterialsListResponseEBM as input |
| 15 | CreateEngineeringChangeOrderEBF calls CreateEngineeringChangeOrderSAPProvABCS | CreateEngineeringChangeOrdeListEBM is passed to CreateEngineeringChangeOrderListSAPProvABCS as input |
| 16 | CreateEngineeringChangeOrderListSAPProvABCS transforms the input and calls the SAP service | CreateEngineeringChangeOrderListSAPProvABCS transforms CreateEngineeringChangeOrderListEBM into the input of SAP Service and calls that service.
Creates items in ERP, creates an ECO, associates revised items to it and creates BOM |
| 17 | CreateEngineeringChangeOrderListEBF calls EngineeringChangeOrderResponseEBS (Response Port) with the CreateEngineeringChangeOrderResponseEBM | CreateEngineeringChangeOrderListEBF invokes CreateEngineeringChangeOrderListResponse operation on EngineeringChangeOrderResponseEBS with CreateEngineeringChangeOrderListResponseEBM as input. |
| 18 | EngineeringChangeOrderResponseEBS routes the response message to ProcessEngineeringChangeOrderAgileReqABCS. | EngineeringChangeOrderResponseEBS routes CreateEngineeringChangeOrderListResponseEBM to ProcessEngineeringChangeOrderAgileReqABCS. |
| 19 | ProcessEngineeringChangeOrderAgileReqABCS sends the status back to the QueueController to update the queue. | ProcessEngineeringChangeOrderAgileReqABCS replies back to the QueueController with the status of the ECO business process.
This status is updated against the Queue message in the database by the QueueController |
| 20 | ProcessEngineeringChangeOrderAgileReqABCS invokes the Agile Web Services. | ProcessEngineeringChangeOrderAgileReqABCS transforms CreateEngineeringChangeOrderListResponseEBM into AgileUpdateEngineeringChangeOrderListABM.
AgileUpdateEngineeringChangeOrderListABM is sent as an input to the Agile Web Service. The web services would update transfer status on the Change Order in Agile which will be predefined P2 or P3 attributes on ECO object in Agile. In an error scenario, error message is set in a P2 or P3 attribute. From Agile PLM 9.3.2 onwards, you are provided with a new Action Items tab that corresponds to each ATO. A previously errored ATO is re-sent through a re-process action in ATO Action Item tab. (AgileUpdateEngineeringChangeOrderListResponseABM is sent back to ProcessEngineeringChangeOrderAgileReqABCS.) |
The process integration for ECO and PREL uses the following industry components:
| EBOs | 1. EngineeringChangeOrderEBO
2. BillOfMaterialsEBO 3. ItemEBO |
| EBMs | 4. CreateEngineeringChangeOrderListEBM
5. CreateEngineeringChangeOrderListResponseEBM 6. CreateBillOfMaterialsListEBM 7. CreateBillOfMaterialsListResponseEBM 8. UpdateBillOfMaterialsListEBM 9. UpdateBillOfMaterialsListResponseEBM 10. CreateItemListEBM 11. CreateItemListResponseEBM |
| EBSs | 12. EngineeringChangeOrderListEBS (CreateEngineeringChangeOrderListResponseEBM)
13. ItemEBS ( CreateItemListResponseEBM) |
Core Components Locations
| EBO & EBM XSD files | $AIA_HOME/AIAMetaData/AIAComponents/EnterpriseObjectLibrary/Core/EBO/EngineeringChangeOrder/
$AIA_HOME/AIAMetaData/AIAComponents/EnterpriseObjectLibrary/Core/EBO/BillOfMaterials/ $AIA_HOME/AIAMetaData/AIAComponents/EnterpriseObjectLibrary/Core/EBO/Item/ |
| WSDL files | $AIA_HOME/AIAMetaData/AIAComponents/EnterpriseBusinessServiceLibrary/Core/EBO/ |
For detailed documentation of individual EBOs, click the EBO Name link on the Integration Scenario Summary page in the Oracle AIA Console. You can also use the Integration Scenario Summary page to search for and view integration scenarios that utilize a particular EBO or EBS.
EBOs can be extended, for instance, to add new data elements. These extensions are protected, and will remain intact after a patch or an upgrade.
For more information, see Oracle Application Integration Architecture - Foundation Pack: Integration Developer's Guide,, "Extensibility for AIA Artifacts."
| Services | Agile (Requester) | SAP (Provider) |
|---|---|---|
| ABMs | AgileCreateEngineeringChangeOrderListABM
AgileCreateEngineeringChangeOrderListResponseABM AgileUpdateEngineeringChangeOrderListABM AgileUpdateEngineeringChangeOrderListResponseABM |
BAPI_MATERIAL_GET_ALL
BAPI_MATERIAL_GET_ALLResponse BAPI_MATERIAL_GET_DETAIL BAPI_MATERIAL_GET_DETAILResponse BAPI_MATERIAL_SAVEDATA BAPI_MATERIAL_SAVEDATAResponse CSAP_MAT_BOM_READ CSAP_MAT_BOM_READResponse CCAP_REV_LEVEL_MAINTAIN CCAP_REV_LEVEL_MAINTAINResponse BAPI_MAT_BOM_EXISTENCE_CHECK BAPI_MAT_BOM_EXISTENCE_CHECKResponse CSAP_MAT_BOM_ALLOC_CREATE CSAP_MAT_BOM_ALLOC_CREATEResponse CSAP_MAT_BOM_CREATE CSAP_MAT_BOM_CREATEResponse CSAP_MAT_BOM_MAINTAIN CSAP_MAT_BOM_MAINTAINResponse CCAP_ECN_MAINTAIN CCAP_ECN_MAINTAINResponse |
| ABCS | ProcessEngineeringChangeOrderAgileReqABCS | CreateEngineeringChangeOrderListSAPProvABCSImpl
CreateEngineeringChangeOrderListEBF ProcessBillOfMaterialsListSAPProvABCS ProcessBillOfMaterialsListSAPProvABCSImpl CreateBillOfMaterialsListSAPProvABCSImpl UpdateBillOfMaterialsListSAPProvABCSImpl SyncItemListSAPProvABCS |
| EBS | EngineeringChangeOrderEBS (CreateEngineeringChangeOrderList Operation) | EngineeringChangeOrderResponseEBS (CreateEngineeringChangeOrderListResponse Operation)
ItemEBS ItemResponseEBS |
| BPEL | CreateQueueService
QueueProcessorServiceImpl |
--- |
| Mediator Service | ACSAXMLJMSConsumer
ACSAXMLFileConsumer CreateQueueControlService QueueProcessorService EngineeringChangeOrderService |
ItemService
BOMServiceESB ReserveItemservice ECORouterService |
Component Locations
| ABO XSD files | $AIA_HOME/AIAMetaData/AIAComponents/ApplicationObjectLibrary/Agile/V1/schemas |
| ABM XSD files | $AIA_HOME/AIAMetaData/AIAComponents/ApplicationObjectLibrary/Agile/ V1/schemas
$AIA_HOME/AIAMetaData/AIAComponents/ApplicationObjectLibrary/SAP/Release1/Core/ABM/EngineeringChangeOrder |
These are the integration services for Change Order release:
EngineeringChangeOrderEBS is the EBS, which exposes the operations related to the Engineering Change Order Integration on the EngineeringChangeOrder EBO. The following are the routing rules:
EngineeringChangeOrderEBS Mediator service
ProcessEngineeringChangeOrderAgileReqABCS
Route CreateEngineeringChangeOrderListEBM to CreateEngineeringChangeOrderListSAPProvABCSImpl
EngineeringChangeOrderResponseEBS Mediator Service
CreateEngineeringChangeOrderListSAPProvABCSImpl
Route CreateEngineeringChangeOrderListResponseEBM to ProcessEngineeringChangeOrderAgileReqABCS
ItemEBS Mediator Service
CreateEngineeringChangeOrderListEBF
Route CreateItemListEBM to SyncItemListSAPProvABCS
ItemResponseEBS Mediator service
SyncItemListSAPProvABCS
Route CreateItemListResponseEBM to CreateEngineeringChangeOrderListEBF
ProcessEngineeringChangeOrderAgileReqABCS is used for transforming AgileCreateEngineeringChangeOrderListABM into CreateEngineeringChangeOrderListEBM. This service invokes the CreateEngineeringChangeOrder operation on EngineeringChangeOrderEBS for creation of the ECO in SAP.
Based on the status of ECO creation in SAP this service updates the queue status. Also the Transfer status attribute in CO is updated by this service. This service is implemented as Asynchronous Business Process Execution Language (BPEL) composite.
The QueueController creates the AgileCreateEngineeringChangeOrderListABM and invokes the ProcessEngineeringChangeOrderAgileReqABCS.
Transforms the AgileCreateEngineeringChangeOrderListABM to CreateEngineeringChangeOrderListEBM and invokes the CreateEngineeringChangeOrder operation on EngineeringChangeOrderEBS with CreateEngineeringChangeOrderListEBM as input. This is routed for creation of the ECO in SAP.
CreateEngineeringChangeOrderListResponseEBM is received from EngineeringChangeOrderEBS and based on the status of ECO creation in SAP; the QueueController is invoked to update the status of the Queue Message.
ProcessEngineeringChangeOrderAgileReqABCS transforms CreateEngineeringChangeOrderListResponseEBM into AgileUpdateEngineeringChangeOrderListABM and is sent as an input to the Agile Web Service.
The web services updates the transfer status of the CO in Agile, which is predefined P2 or P3 attributes on the ECO object in Agile. AgileUpdateEngineeringChangeOrderListResponseABM is sent back to ProcessEngineeringChangeOrderAgileReqABCS.
Transformations
AgileCreateEngineeringChangeOrderListABM_to_CreateEngineeringChangeOrderEBM.xsl
Transforms AgileCreateEngineeringChangeOrderListABM to CreateEngineeringChangeOrderListEBM
CreateEngineeringChangeOrderResponseEBM_to_AgileUpdateEngineeringChangeOrderListABM.xsl
Transforms CreateEngineeringChangeOrderResponseEBM to AgileUpdateEngineeringChangeOrderListABM
This is a single operation service. This accepts an ECO containing Item and BoMs information message as a request and returns a response.
In Agile to SAP flow, CreateEngineeringChangeOrderListSAPProvABCSImpl is used for transforming CreateEngineeringChangeOrderListEBM into CCAP_ECN_MAINTAINABM, which invokes the CreateEngineeringChangeOrder operation in SAP.
In return flow, CCAP_ECN_MAINTAIN BAPI sends CCAP_ECN_MAINTAINResponse which is transformed by CreateEngineeringChangeOrderListSAPProvABCSImpl into CreateEngineeringChangeOrderListResponseEBM.
This service is implemented as an asynchronous BPEL Composite
This table lists the CO integration customization information:
Agile
| Name | Property | Description |
|---|---|---|
| ProcessEngineeringChangeOrderAgileReqABCS
(Agile Process ECO requestor flow) |
AgileCreateEngineeringChangeOrderListABM_to_CreateEngineeringChangeOrderListEBM_ Impl .xsl | ReqABM to ReqEBM (main) |
| AgileCreateEngineeringChangeOrderListABM_to_CreateEngineeringChangeOrderListEBM_ Custom.xsl | ReqABM to ReqEBM (custom elements) | |
| CreateEngineeringChangeOrderListEBM_EBMHeader_Custom.xsl | EBM to EBMHeader (custom elements) | |
| CreateEngineeringChangeOrderListEBM_EBMHeader_Impl.xsl | EBM to EBMHeader (main) | |
| CreateEngineeringChangeOrderListResponseEBM_to_UpdateEngineeringChangeOrderListEBM_Impl.xsl | RespEBM to ReqEBM (main) | |
| UpdateEngineeringChangeOrderListEBM_to_AgileUpdateEngineeringChangeOrderListABM_Impl.xsl | ReqEBM to ReqABM (main) |
SAP
| Name | Property | Description |
|---|---|---|
| CreateEngineeringChangeOrderListSAPProvABCSImpl
CreateEngineeringChangeOrderListEBF |
CreateEngineeringChangeOrderListEBMtoABM_Custom.xsl | Custom transformations for Engineering Change Order Request EBM to Request ABM |
| XformReqEBMToResEBM_Custom.xsl | Custom transformations for Engineering Change Order Request EBM to Engineering Change Order Response EBM | |
| CreateECOEBMtoItemListEBM_Custom.xsl | Custom transformations for Engineering Change Order Request EBM to Item List EBM | |
| UpdateXformEngineeringChangeOrderListEBMtoEBM_Custom.xsl | Custom transformations for update Engineering Change Order list EBM to Engineering Change Order list EBM | |
| XformEBMtoBillOfMaterialProcess_Custom.xsl | Custom transformations for Engineering Change Order list EBM to Engineering Change Order list EBM for BOM | |
| XformECOListEBMtoECOListResponseEBM_Custom.xsl | Custom transformations for Engineering Change Order list request EBM to Engineering Change Order list Response EBM | |
| XformEngineeringChangeOrderListEBMtoEBM_Custom.xsl | Custom transformations for create Engineering Change Order list EBM to Engineering Change Order list EBM | |
| ECOEBMToExistenceCheck_Custom.xsl | Custom transformations for Engineering Change Order list EBM to BOM_Existence_Check ABM | |
| ProcessBillOfMaterialsListSAPProvABCS | ECOEBMToGlobalBOMExistenceCheck_Custom.xsl | Custom transformations for Engineering Change Order list EBM to global BOM_Existence_Check ABM |
| ECOEBMToGlobalUpdateBOMEBM_Custom.xsl | Custom transformations for Engineering Change Order list EBM to global Update BillOfMaterials List EBM | |
| ECOListEBMToBOMListEBM_Custom.xsl | Custom transformations for Engineering Change Order list EBM to Create BillOfmaterials List EBM | |
| ECOListEBMToUpdateBOMListEBM_Custom.xsl | Custom transformations for Engineering Change Order list EBM to Update BillOfMaterials List EBM | |
| XformEBMHeadertoECOListResponseEBM_Custom.xsl | Custom transformations for EBM Header to Create EngineeringChangeOrder List EBM | |
| XformECOListEBMtoEBMHeader_Custom.xsl | Custom transformations for Create EngineeringChangeOrder List EBM to EBM Header | |
| CreateBillOfMaterialsListSAPProvABCSImpl | BOMEBMToCreateGlobalBOMABM_Custom.xsl | Custom transformations for Create BillOfMaterials List EBM to Create Global BOM ABM |
| BOMEBMToExistenceCheck_Custom.xsl | Custom transformations for Create BillOfMaterials List EBM to global BOM Existence Check ABM | |
| BOMEBMToPlantExistenceCheck_Custom.xsl | Custom transformations for Create BillOfMaterials List EBM to BOM Existence Check ABM | |
| BOMEBMToPlantExtensionABM_Custom.xsl | Custom transformations for Create BillOfMaterials List EBM to BOM Plant Extension ABM | |
| BillOfMaterialsListEBMToCreateBOM_Custom.xsl | Custom transformations for Create BillOfMaterials List EBM to Create BOM ABM | |
| XformBOMReqEBMToResEBM_Custom.xsl | Custom transformations for Create BillOfMaterials List EBM to Create BillOfMaterials List Response EBM | |
| UpdateBillOfMaterialsListSAPProvABCSImpl | BOMEBMToGlobalBOMABM_Custom.xsl | Custom transformations for Update BillOfMaterials List EBM to Update global BOM ABM |
| BOMEBMToPlantExistenceCheck_Custom.xsl | Custom transformations for Update BillOfMaterials List EBM to BOM Existence Check ABM | |
| BOMEBMToPlantExtensionABM_Custom.xsl | Custom transformations for Update BillOfMaterials List EBM to BOM Plant Extension ABM | |
| BOMEBMToUpdateBOMABM_Custom.xsl | Custom transformations for Update BillOfMaterials List EBM to Update BOM ABM | |
| XformBOMReqEBMToResEBM_Custom.xsl | Custom transformations for Update BillOfMaterials List EBM to Update BillOfMaterials List Response EBM | |
| ProcessBillOfMaterialsListSAPProvABCSImpl | XformECOEBMtoABM.xsl | Custom transformations for CreateEngineeringChangeOrderListEBM to Read BOM ABM |
| XformABMtoECOEBM.xsl | Custom transformations for Read BOM ResponseABM to CreateEngineeringChangeOrderList EBM | |
| SyncItemListSAPProvABCS | XFormItemEBMToGetDetailRefMaterial_Custom.xsl | Custom transformations for CreateItem List EBM to Get detail Reference Material ABM |
| XFormItemEBMToReferenceMaterial_Custom.xsl | Custom transformations for CreateItem List EBM to Get Reference Material ABM | |
| XFormItemEBMToRevisionABM_Custom.xsl | Custom transformations for CreateItem List EBM to Create Revision ABM | |
| XFormItemListEBMToSavedData_Custom.xsl | Custom transformations for CreateItem List EBM to Create Item List ABM | |
| XFormItemListEBMToUpdateItem_Custom.xsl | Custom transformations for CreateItem List EBM to Update Item list ABM(for Get All ReferenceMaterial-4.6) | |
| XFormItemListEBMToUpdate_Item_Custom.xsl | Custom transformations for CreateItem List EBM to Update Item list ABM(for Get Detail ReferenceMaterial) | |
| XformItemListEBMtoItemListResponseEBM_Custom.xsl | Custom transformations for CreateItem List EBM to Create ItemList Response EBM |
The following mandatory DVMs and Properties (in AIAConfigProperties.xml) must be set for the CO Release process:
AGILE_SITE_TARGET_MAPPING
AGILE_TARGET_SITE_MAPPING
LANGUAGE_CODE
ECO_ENGINEERINGCHANGEORDERLINE_REVISEDBILLOFMATERIALS_BILLOFMATERIALSCOMPONENTITEM_CHANGETYPECODE
ITEM_PRIMARYCLASSIFICATIONCODE
ITEM_STATUS_CODE
ITEM_UOM_CODE
ECO_STATUS_CODE
REFERENCE MATERIALS
