AGILE1 Docx

Object Identifier : TD505-PLM-1 Object Level : 1
1 Project Revision History Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-2 Object Level : 2
<DO NOT DELETE: Placeholder for major sections to align with templates. Revision history is no longer needed. Automatically tracked within DOORS.> Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-3 Object Level : 1
2 Project Approvals Object Type : Comment Status : Approved Release : PPM RFCs :
Formal approvals are no longer required for technical designs (15 Sept 2011) for Trilogy program. (Note: Peer reviews should still be conducted on a minor baseline and documented for defect findings. After any necessary updates, take an additional minor baseline. Then request formal/major baseline.)
Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-563 Object Level : 1
3 Introduction Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-5 Object Level : 2
This document provides the Technical Design of the Design to Release PIP between Agile and EBS/PIM for Release 3. Object Type : Comment Status : Approved
Release : PPM RFCs : Object Identifier : TD505-PLM-620 Object Level : 2
3.1 Scope Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-6 Object Level : 3
This document provides technical design of the Design to Release PIP. Scope of this document is limited to configuration and development related to FMW PIP. Design to Release PIP is an Out of the Box Productized integration solution between Agile PLM and Oracle EBS/PIM. The Out of the Box features do not meet all of the current requirements for the Release 3 project and would require additional configuration, Mapping or Extension. This document describes the technical design of these additional configurations, Mapping or Extension used for development and maintenance of the Solution
The following Out-of-box features are enabled for Release 3 project. o o o o Agile PLM to Oracle EBS/PIM Integration Creation and Maintenance of Item including AML Creation and Maintenance of Standard BOM Creation of ECO/MCO Oracle EBS/PIM to Agile PLM Update of Change Order information
Update of Item attributes
Note: Update of Item Attributes has been moved post Release 3.x
For Pre Release Audit Flow The following Out-of-box features are enabled for Release 3 project.
o o
Agile PLM to Oracle EBS/PIM Integration Validation of Item including AML Validation of Standard BOM o Validation of ECO/MCO
CD3 PBT Customizations:
Please find the table Attributes Mappings below for the detailed info.
PBT Go Live Customizations:
Please find the table Attributes Mappings below for the detailed info and also please find the Global BOM/ Non Global BOm Transformation logic below: Picture : PBT GlobalBOM/Non Global BOM Transformation logic
Object Type : Comment Status : Approved Release : PPM RFCs :
3.1.1 Attributes Mapping Table Object Type : Comment Status : Approved Release : PBT CD3 PBT Go Live PPM RFCs : Project Agile Attribute Name R12 Attribute Name PIP Customizations/Composites Changed DVM's Changed Mapping Information Comments Referance Document Location PBT CD3 Flexi Attribute - MSI Relationship Part MSI_Relationship_Part as part of Procurement Attribute Table. This is configured as a UDA at R12 side. CreateEngineeringChangeOrderListEbizProvABCSImpl ProcessEngineeringChangeOrderAgileReqABCSImpl ValidateEngineeringChangeOrderListAgileReqABCSImpl ValidateEngineeringChangeOrderListEbizProvABCSImpl CUSTOM_UDA_ATTR_SHORT_NAME.dvm CUSTOM_UDA_ATTR_GROUP_SHORT_NAME CUSTOM_AGILE_FLEX_ATTRIBUTE_NAME.dvm CUSTOM_UDA_PROPERTIES.dvm Direct Mapping No new composites / DVMs are created as part of this requirement <http://compass.mot-solutions.com/go/440496716>
PBT CD3 Page2/List12(ECCN) ECCN(Item Category) CreateEngineeringChangeOrderListEbizProvABCSImpl ProcessEngineeringChangeOrderAgileReqABCSImpl ValidateEngineeringChangeOrderListAgileReqABCSImpl
ValidateEngineeringChangeOrderListEbizProvABCSImpl Not applicable Transformation Logic: Removing | from the value sent from Agile. For Example: if the ECCN value from Agile is EAR99|.NR, then PIP code transforms the value to EAR99.NR (removing |) and will be send to R12. No new composites / DVMs are created as part of this requirement <http://compass.motsolutions.com/go/440496716>
PBT CD3 Part Approval status Part Approval status(Configured as Part of Triology) Not applicable CUSTOM_AML_STATUS.dvm. Updated the dvm, with these values: Proposed, Qualified, Waiver Only and Not Required Not applicable No new composites / DVMs are created as part of this requirement <http://compass.mot-solutions.com/go/440496716>
PBT CD3 Manufacture Name Manufacture Name ValidateManufacturerEbizProvABCS_Custom ProcessManufacturerEbizProvABCS_Custom UpdateItemAMLStatusEbizProvABCS_Custom ValidateEngineeringChangeOrderListEbizProvABCSImpl CreateEngineeringChangeOrderListEbizProvABCSImpl N/A Transformation Logic: No new
Manufactur Name has been trimmed to 30 characters length before sending it to Oracle ERP. composites / DVMs are created as part of this requirement
<http://compass.mot-solutions.com/go/440496716>
PBT Go Live Commodity Code Commodity Code(As part of Item Categories) CreateEngineeringChangeOrderListEbizProvABCSImpl ProcessEngineeringChangeOrderAgileReqABCSImpl ValidateEngineeringChangeOrderListAgileReqABCSImpl
ValidateEngineeringChangeOrderListEbizProvABCSImpl CUSTOM_CATEGORY_SETS.dvm Direct Mapping No new composites / DVMs are created as part of this requirement <http://compass.mot-solutions.com/go/440496716>
PBT Go Live Page2/List23(EU ECCN) EU ECCN(Item Category) CreateEngineeringChangeOrderListEbizProvABCSImpl ProcessEngineeringChangeOrderAgileReqABCSImpl ValidateEngineeringChangeOrderListAgileReqABCSImpl ValidateEngineeringChangeOrderListEbizProvABCSImpl CUSTOM_CATEGORY_SETS.dvm Transformation Logic: Removing | from the value sent from Agile. For Example: if the EU ECCN value from Agile is EAR99|.NR, then PIP code transforms the value to EAR99.NR (removing |) and will be send to R12. No new composites / DVMs are created as part of this requirement
<http://compass.mot-solutions.com/go/440496716>
PBT Go Live
BOM.Optional BOM.MutExcl BOM.Minqty BOM.Maxqty OPTIONAL
MUTUALLY_EXCLUSIVE_OPTIONS LOW_QUANTITY HIGH_QUANTITY CreateEngineeringChangeOrderListEbizProvABCSImpl
ProcessEngineeringChangeOrderAgileReqABCSImpl ValidateEngineeringChangeOrderListAgileReqABCSImpl ValidateEngineeringChangeOrderListEbizProvABCSImpl Not Applicable Transformation Logic: For BOM.Optional and BOM.MutExcl attributes, R12 expects those values to be numeric (Either 1-Yes/2No). But from Agile we used to get Yes/No. For this, we have made this transformation by using default OOTB dvms like1.ECO_ENGINEERINGCHANGEORDERLINE_ REVISEDBILLOFMATERIALS_BILLOFMATERIALSCOMPONENTITEM _MUTUALLYEXCLUSIVEOPTIONINDICATOR.dvm 2.ECO_ENGINEERINGCHANGEORDERLINE_REVISEDBILLOFMATERIALS_BILLOFMATERIALSCOMPONENTIT EM_OptionalIndicator.dvm No new composites / DVMs are created as part of this requirement <http://compass.mot-solutions.com/go/440496716>
PBT Go Live Part Transfer-Destination ERP( PAGE_TWO.MULTILIST07) ProcessEngineeringChangeOrderAgileReqABCSImpl Not Required
ValidateEngineeringChangeOrderListAgileReqABCSImpl(On Provider side no composite has been touched. The reason for that is, we have used the OOTB configurations for the mentioned BOM related attributes and we asked R12 team and this been confirmed by Arif R12 team to continue with the existing code) Not Applicable Transformation Logic: Need to check the Item attribute Page2/Multilist07 value whether it is Trilogy R12 or not. If YES, then this part needs to be transferred to R12.No new composites / DVMs are created as part of this requirement <http://compass.mot-solutions.com/go/440496716>
PBT Go Live
Global BOM/Non Global BOM Not Required ProcessEngineeringChangeOrderAgileReqABCSImpl ValidateEngineeringChangeOrderListAgileReqABCSImpl Not Applicable Transformation Logic: If the Destination ERP=Trilogy R12 and Global BOM=Yes, then all the BOM Components will be sending to R12.
If the Destination ERP=Trilogy R12 and Global BOM=No, then we have to traverse all the BOM Components and check for ERP Org(BOM.LIST04).If ERP Org=R12 Trilogy then only that items BOM components will be transformed to R12. No new composites / DVMs are created as part of this requirement <http://compass.mot-solutions.com/go/440496716>
t Object Identifier : TD505-PLM-790 Object Level : 3
<Picture : PBT GlobalBOM/Non Global BOM Transformation logic>
Object Type : Comment Status : Approved
Release : PBT Go Live PPM RFCs : Object Identifier : TD505-PLM-7 Object Level : 2
3.2 Definitions, Acronyms and Abbreviations Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-8 Object Level : 3
Any definitions, acronyms or abbreviations in this document are found at http://compass.motsolutions.com/go/mglossary. Exceptions are listed below: Object Type : Comment Status : Approved Release : PPM RFCs : Term BOM AML CR DR EBO PX Definition Bill of Materials Approved Manufacturer List Customer Requirements Design Requirements Enterprise Business Object Agile Process Extension
D2R AIA NPI PIP ECO MCO
Design To Release Application Integration Architecture New Product Introduction Process Integration Pack Engineering Change Order Manufacturing Change Order
OOTB Out Of The Box component in product from software vendor PIM PLM MDS Product Information Management (Oracle Product) Product Lifecycle Management Meta Data Repository (part of the AIA product)
3.3 Reference Materials Object Type : Comment Status : Approved Release : PPM RFCs : Document Name Document URL http://compass.mot-solutions.com/go/404947104
Technical Design Peer Review Form
Customer Requirements Document DOORS: /Supply Chain Transformation/PLM/Customer Requirements/CR504-PLM-Agile-to-ERP-Interface-CR Development Requirements Document DOORS: /Supply Chain Transformation/PLM/Development Requirements/DR504-PLM-Agile-to-ERP-Interface Agile to ERP Mapping Matrix http://compass.mot-solutions.com/go/401713334
Data Mapping Guide
http://compass.mot-solutions.com/go/405621617
Design to Release Implementation Guide 3.1
http://compass.mot-solutions.com/go/404138435
R12 Development Requirements DOORS:/Supply Chain Transformation/Make/Development Requirements/DR515-MK-Agile-to-ERP-Interface-EBS-Development Technical Design Document for R12 Development DOORS:/Supply Chain Transformation/Make/Technical Designs and MD70s/TD518-MK-Agile-to-ERP-Interface-EBSDevelopment Object Identifier : TD505-PLM-36 Object Level : 1
4 Preliminary Design - Architecture Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-564 Object Level : 2
4.1 Architecture Design Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-37 Object Level : 3
4.2 Data Flow Diagram / Program Flow chart Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-38 Object Level : 3
Design to Release PIP supports two major flows. These are The following Out-of-box features are enabled for Release 3 project. Agile PLM to Oracle EBS/PIM Integration Oracle EBS/PIM to Agile PLM
The Data Flow Diagram for these are described as below.
Object Type : Comment Status : Approved
4.2.1 Agile to Oracle EBS/PIM Data Flow Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-329 Object Level : 4
The change order release comprises of new Part/Product Release (PREL) and Product Design Modification (PDM) flows from Agile PLM triggered by a standard ECO or a manufacturing change order (MCO) release event in Agile PLM. While Agile PLM is the system of record for item description, design, specs, and other information, Oracle E-Business Suite has many more attributes and placeholders for information than the Agile PLM system. Hence, the change order release needs to be updated in the Oracle E-Business Suite. A corresponding ECO is created in Oracle E-Business Manufacturing, in the appropriate Oracle E-Business Inventory Organizations, in near realtime. ECO in Oracle E-Business Suite can be implemented manually or through a low-touch, standard Oracle E-Business Suite ECO AutoImplement process. The release of a change order in Agile PLM acts as a trigger for the synchronization of product design information with Oracle E-Business Suite. Because Agile PLM is a system of records for product design data, the synchronization process involves transfer of the released revision of the product design from Agile PLM to the manufacturing system.
The Agile to Oracle EBS/PIM Flow Supports the following use cases
Item Creation and Maintenance
BOM creation and Maintenance ECO/MCO creation
Change Order Validation Process Integration This process includes the following steps: 1. In Agile PLM, a change order is created and an aXML file of the change order is generated through an Automated Transfer Order (ATO). An ATO is a routable object that triggers and tracks automated transfer of product content information from Agile to XML through Agile PLM Content Service (ACS). 2. If the workflow status of this change order is other than released, the integration determines that the change order is being submitted for validation. 3. The change orders aXML file is not queued, and is not subject to dependency checks. However, it appears in the integration Queue Monitor user interface in a separate section called Validate ECO. In this section, only the following information is displayed as read only:
ECO Number aXML file number Release Audit Status (Pending Processing, In Process, Failed, Passed, Warning). The Warning status indicates that the audit status process could not be completed because of some error (such as unable to connect to Oracle DB) Log file. 4.The change orders queued for validations are processed concurrently unlike the change orders queued for synchronization, which are processed sequentially. If validation of a change order fails, the next change order in the queue is picked up for processing automatically. 5. The integration carries out the process of posting data to Oracle E-Business Suite. However, after processing the whole change order, it does not commit the data. In an event of a failure, the error messages are sent back to Agile PLM. This is followed by a rollback of the transaction. If the process is successful, the status is updated as Validated in Agile PLMs Transfer Status attribute (change order Agile PLM P2 or P3 defined attribute for the Change.TransferStatusAttribute property If the process fails, the status is updated as Validation Failed in Agile PLMs Transfer Status attribute (change order Agile PLM P2 or P3 defined attribute for the Change.TransferStatusAttribute property). In addition, an email notification is sent to the AIAIntegrationAdmin user, which is configured in the weblogic console under Security Realms. 6. Errors are logged or displayed in the Queue Monitoring UI and also stored in the database on the middle tier for future reference if needed (Similar to current ECO release processing)
These diagrams illustrate change order validation integration sequence:
4.2.2 Oracle EBS to Agile PLM Integration Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-330 Object Level : 4
The integration also addresses these key concepts of Design for Supply Chain with an optional bidirectional synchronization (from Oracle E-Business Suite/PIM to Agile PLM) of supply chain data, such as item Lead Times, Costs and On-hand Quantities (calculated by Organization), or any other E-Business or PIM Item Master attributes. The Oracle E-Business Suite to Agile PLM process flows supported by this integration includes: Process integration for item attribute update Process integration for item balance update Process integration for change order update
4.2.3 Agile to Oracle EBS/PIM Custom flows Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-498 Object Level : 4
The following flows are not available Out-of-the Box and will be developed to support the current Customer Requirements
ItemStatus: The Items status in Oracle EBS/PIM would be different in child orgs and this information is not available in Agile PLM. A Custom Flow to Query for this information would be developed per the process Flow
Pending ECO Status: Before release of an ECO the User would like to know if there are any prior ECO's yet to be implemented in any of the Child organizations in Oracle EBS/PIM. The following flow describes the sequence of actions.
Environment Compliance Update: This is a custom flow which is invoked from Agile PLM to update the changes to the environment compliance attributes. The process extension when invoked will enqueue the update messages into the JMS queue of the FMW. The FMW custom process will pickup this message, transforms and invokes the EBS/PIM API to send the updates. The response received is processed for error handling and updating back the status to Agile. This is a batch processing flow and all the calls are asynchronous.
Object Type : Comment Status : Approved Release :
PPM RFCs : Object Identifier : TD505-PLM-39 Object Level : 2
4.3 Entity Relationship Diagram/UML/Sequence Diagram Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-775 Object Level : 3
4.3.1 Agile to Oracle EBS/PIM Validation Sequence Diagram Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-674 Object Level : 3
Object Type : Comment Status : Approved Release : PPM RFCs : PPM60207
4.3.2 Agile to Oracle EBS/PIM Sequence Diagram Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-472 Object Level : 4
The following is the Sequence Diagram for Agile to Oracle EBS/PIM
4.3.3 Oracle EBS/PIM to Agile PLM Sequence Diagram Object Type : Comment
Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-473 Object Level : 4
The following is the Sequence diagram for the ECO writeback Flow from Oracle EBS/PIM to Agile PLM
4.3.4 Item Status Indicator Sequence Diagram Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-505 Object Level : 4
4.3.5 ECO Pending Status Indicator Sequence diagram Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-506 Object Level : 4
4.3.6 AML Approval Status update Sequence Diagram
4.3.7 Manufacturer Create Sequence diagram Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-508 Object Level : 4
Object Type : Comment
4.3.8 Enviroinmental Compliance Update - Non ECO Controlled Sequence Diagram Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-509 Object Level : 4
5 Preliminary Design - Design Components Master List
Object Type : Comment Status : Approved Release : R3.0 PBT CD3 PBT Go Live PPM RFCs : Sect. No (5.X) Component Name Component Type Component Location DR Reference 5.1 CreateQueueControlService Adapter Service Component Description Complexity
The CreateQueueControlService updates the message processing status OOTB $AIA_HOME/services/core/Agile/UtilityServices Common 5.2 CreateQueueService Component Service CreateQueueService is mediator service receives aXML from ACSAXMLJMSConsumer and put the message into AIA Queue. OOTB $AIA_HOME/services/core/Agile/UtilityServices/CreateQueueService Common 5.3 QueueProcessorServiceImpl Component Service responsible for transforming the AXML into ABM message." QueueProcessorServiceImpl is
OOTB $AIA_HOME/services/core/Agile/UtilityServices/QueueProcessorServiceImpl Common 5.4 ProcessEngineeringChangeOrderAgileReqABCSImpl Component Service ProcessEngineeringChangeOrderAgileReqABCSImpl is used for transforming
AgileCreateEngineeringChangeOrderListABM into CreateEngineeringChangeOrderListEBM. This service invokes the CreateEngineeringChangeOrderList operation on EngineeringChangeOrderEBS for creation of an ECO in Oracle E-Business Suite. Based on the status of the ECO creation in Oracle E-Business Suite, this service updates the queue status. In addition, this service updates the transfer status attribute in the change order. This service is implemented as an asynchronous BPEL process. Mapping $AIA_HOME/services/core/Agile/RequesterABCS/ProcessEngineeringChangeOrderAgileReqABC SImpl DR504-PLM-162
DR504-PLM-131 DR504-PLM-133 DR504-PLM-136 DR504-PLM-189 DR504-PLM-190
5.5 EngineeringChangeOrderEBS Component Service EngineeringChangeOrderEBS is a mediator service receives request from the ProcessEngineeringChangeOrderAgileReqABCSImpl and invokes the provider ABCS i.e., CreateEngineeringChangeOrderListEbizProvABCSImpl OOTB $AIA_HOME/pips/AgileToEbiz/EBS/EngineeringChangeOrder/R12/EngineeringChangeOrderEBS Common 5.6 CreateEngineeringChangeOrderListEbizProvABCSImpl Component Service This service is implemented as an asynchronous BPEL Process. It is responsible transform the EngineeringChangeOrder EBM to EBS specific ABM message and invokes CreateEngineeringChangeOrderListEbizAdapter. It invokes the EngineeringChangeOrderResponseEBS service once it receives the response from CreateEngineeringChangeOrderListEbizAdapter. Mapping $AIA_HOME/services/core/Ebiz/ProviderABCS/CreateEngineeringChangeOrderListEbizProvABCS Impl DR504-PLM-131 DR504-PLM-162 5.7 UpdateEngineeringChangeOrderListEbizReqABCSImpl Component Service ABCS, defined as a synchronous process, receives a list of change IDs from the Oracle E-Business Suite concurrent program. The BPEL process then makes an OA Adapter call out that calls the PL/SQL API, which provides the Item details that is sent out. This is the UpdateEngineeringChangeOrderList ABM. A transformation converts UpdateEngineeringChangeOrderListABM to UpdateEngineeringChangeOrderListEBM OOTB $AIA_HOME/services/core/Ebiz/RequesterABCS/UpdateEngineeringChangeOrderListEbizReqAB CSImpl Common 5.8 UpdateEngineeringChangeOrderListAgileProvABCSImpl Component Service implemented as an asynchronous process. This service is The requester
Transform operation is called to convert UpdateEngineeringChangeOrderListEBM into AgileUpdateEngineeringChangeOrderListABM. UpdateEngineeringChangeOrderListAgileProvABCSImpl updates a change order transfer status and attributes in Agile PLM. OOTB $AIA_HOME/services/core/Agile/ProviderABCS/UpdateEngineeringChangeOrderListAgileProvAB CSImpl Common 5.9 EngineeringChangeOrderEBS Adapter Service EngineeringChangeOrderEBS is a mediator service receives the request message from UpdateEngineeringChangeOrderListEbizReqABCSImpl and based routing rules it invokes Agile Provider service UpdateEngineeringChangeOrderListAgileProvABCSImpl OOTB $AIA_HOME/pips/AgileToEbiz/EBS/EngineeringChangeOrder/R12/EngineeringChangeOrderEBS Common 5.10 UpdateItemListEbizReqABCSImpl Component Service The publish item attributes concurrent program in Oracle E-Business Suite invokes UpdateItemListEbizReqABCSImpl. OOTB $AIA_HOME/services/core/Ebiz/RequesterABCS/ OOTB component available for future release. 5.11 UpdateItemListAgileProvABCSImpl Component Service UpdateItemListAgileProvABCSImpl transforms UpdateItemListEBM to AgileUpdateItemListABM and invokes the UpdateItemList service operation on the Agile PLM Web service to update the item cost-related attribute information from Oracle to Agile PLM. OOTB $AIA_HOME/services/core/Agile/ProviderABCS/ OOTB component available for future release. 5.12 ACSAXMLJMSConsumer Adapter Service ACSAXMLJMSConsumer reads aXML sent by Agile from AgilePLMECOJMSQueue and invokes CreateQueueService to put the message into AIA Queue. OOTB $AIA_HOME/services/core/Agile/AdapterServices/ACSAXMLJMSConsumer Common 5.13 QueueProcessorService Adapter Service The QueueProcessorService invokes QueueProcessorServiceImpl with QueueMessage as input. OOTB $AIA_HOME/services/core/Agile/UtilityServices/QueueProcessorService Common 5.14 QueryItemListEbizAdapter Adapter Service Queries the Oracle E-Business Suite and fetches the Item attributes information that got updated. OOTB $AIA_HOME/services/core/Ebiz/AdapterServices OOTB component available for future release. 5.15 CreateEngineeringChangeOrderListEbizAdapter Adapter Service CreateEngineeringChangeOrderListEbizAdapter is mediator service receives ABM from CreateEngineeringChangeOrderListEbizProvABCSImpl and invokes EBS procedure
INV_EBI_CHANGE_ORDER_PUB.PROCESS_CHANGE_ORDER_LIST. OOTB $AIA_HOME/services/core/Ebiz/AdapterServices Common 5.16 AIAConfigurationproperties.xml Configuration File parameters that control the behavior of the flow. This PIP uses various configuration
AIAConfigurationProperties.xml, a standard AIA XML configuration file, is used for capturing the Configuration. This AIA configuration file supports the system-level configuration parameters, servicelevel parameters, and module configuration parameters. DR504-PLM-162 DR504-PLM-149 OOTB $AIA_HOME/AIAMetaData/config
5.17 Domain Value Maps Configuration The domain value maps is used for storing data transformations required from Agile PLM to Oracle EBS/PIM. DVMs store data is used for static lookups. They are stored in the MDS repository, which uses database persistence and are managed using tools provided by JDeveloper or Foundation Pack. The Agile to EBS/PIM Design to Release PIP is shipped with the dvms for most of the transformations, however depending on the requirement in each implementation the domain values have to be setup based on the Agile and EBS / PIM configurations. Additionally new DVM may need to be created for the customizations which require transformation of some of the static values between the domain Moderate $AIA_HOME/AIAMetaData/DVM DR504-PLM-133
DR504-PLM-52
5.18 QueryPendingECOIndicatorforItem Component Service The request is initiated from Agile through a web service call to a custom composite, which transforms the request and queries the ECO status or Item status from the EBS/PIM. The response from EBS / PIM is in turn received by the composite and the composite again transforms the data into the data format required by Agile and sends it back to Agile. Agile will receive the response from the custom composite and display it in the status page. Complex $AIA_HOME/services/core/Ebiz/Custom DR504-PLM-134 DR504-PLM-186
5.19 UpdateItemComplaince Component Service A custom composite is required to be developed which will handle the updates from Agile to EBS/PIM. Essentially this composite will be invoked through a web service call from Agile. The composite will receive the input for the compliance attributes for an Item and uses the transformation logic to convert to the EBS/PIM required format. Complex $AIA_HOME/services/core/Ebiz/Custom DR504-PLM-132 5.20 CreateManufacturer Component Service This Component is used for creation of a Manufacturer in Oracle EBS when an AML is released in Agile and the Manufacturer does not exists in EBS/PIM Complex $AIA_HOME/services/core/Ebiz/Custom DR504-PLM-139 5.21 Error Handling and Exception Framework Component Service Agile to EBS/PIM Design to Release PIP uses Oracle AIA Foundation Pack Error Handling Framework to handle errors and exceptions. OOTB $AIA_HOME/services/core/Agile/UtilityServices DR504-PLM-64 DR504-PLM-152 DR504-PLM-153 5.22 Error Handling and Reporting Requirements Component Service Agile to EBS/PIM Design to Release PIP uses Oracle AIA Foundation Pack Error Handling Framework Reporting Requirements. OOTB $AIA_HOME/services/core/Agile/UtilityServices 5.23 ValidateEngineeringChangeOrderListAgileReqABCSImpl Component Service The QueueController creates the AgileValidateEngineeringChangeOrderListABM and invokes the ValidateEngineeringChangeOrderListAgileReqABCSImpl.
ValidateEngineeringChangeOrderListAgileReqABCSImpl receives AgileValidateEngineeringChangeOrderListABM as input and transforms to ValidateEngineeringChangeOrderListEBM and calls EngineeringChangeOrderEBS
In the return flow, ValidateEngineeringChangeOrderListAgileReqABCSImpl recieves ValidateEngineeringChangeOrderListResponseEBM as input from EngineeringChangeOrderResponseEBS
ValidateEngineeringChangeOrderListAgileReqABCSImpl transforms ValidateEngineeringChangeOrderListResponseEBM to AgileValidateEngineeringChangeOrderListResponseABM.
ValidateEngineeringChangeOrderListAgileReqABCSImpl invokes QueueProcessorServiceImpl by passing AgileValidateEngineeringChangeOrderListResponseABM as input to update the status back to the Queue .
ValidateEngineeringChangeOrderListAgileReqABCSImpl transforms ValidateEngineeringChangeOrderListResponseEBM to UpdateEngineeringChangeOrderListEBM.
ValidateEngineeringChangeOrderListAgileReqABCSImpl transforms UpdateEngineeringChangeOrderListEBM to AgileUpdateEngineeringChangeOrderListABM
ValidateEngineeringChangeOrderListAgileReqABCSImpl invokes AgilePLM Web Service by passing AgileUpdateEngineeringChangeOrderListABM as input . OOTB AIA_HOME/services/core/Agile/RequesterABCS/ValidateEngineeringChangeOrderListAgileReqA BCSImpl 5.24 ValidateEngineeringChangeOrderListEbizProvABCSImpl Component Service This is a single operation service. This accepts an ECO containing item and a BOM information message as a request and returns a response.
In the Agile PLM to Oracle E-Business Suite flow, ValidateEngineeringChangeOrderListEbizProvABCSImpl is used for transforming ValidateEngineeringChangeOrderListEBM into ValidateECOABM, which invokes the ValidateEngineeringChangeOrderList operation in Oracle E-Business Suite. In the return flow, the EBS adapter service sends ValidateECOResponseABM, which is transformed by ValidateEngineeringChangeOrderListEbizProvABCSImpl into ValidateEngineeringChangeOrderListResponseEBM. OOTB AIA_HOME/services/core/Ebiz/ProviderABCS/ValidateEngineeringChangeOrderListEbizProvABCS Impl
5.25 ValidateManufacturerEbizProvABCS_Custom Component Service used to check whether the manucaturer exists in R12 or not. Custom $AIA_HOME/services/core/Ebiz/Custom
This custom process is
5.26 ProcessManufacturerEbizProvABCS_Custom Component Service This custom process is used to check whether the manucaturer exists in R12 or not. If it exists, it will update the manufacturer information in R12. If it doesn't exists, it will create the manufacturer in R12. Custom $AIA_HOME/services/core/Ebiz/Custom 5.27 UpdateItemAMLStatusEbizProvABCS_Custom Component Service The manufacturer details we are creating or updating in R12 will be available in AML (Approved Manufacturer List) format in Agile PLM. Every manufacturer registered which goes to R12 need to have some approvals so that the parts from the manufacturer can be used in the BOM. To get the status of these approvals we created the process. Custom $AIA_HOME/services/core/Ebiz/Custom Object Identifier : TD505-PLM-56 Object Level : 1
6 Detailed Design Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-576 Object Level : 2
6.1 CreateQueueControlService Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-57
Object Level : 3
CreateQueueControlService Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-58 Object Level : 3
6.1.1 New/Reuse/Copy from Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-242 Object Level : 4
Reuse Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-577 Object Level : 3
6.1.2 Layout Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-59 Object Level : 4
N/A Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-60 Object Level : 3
6.1.3 Functionality Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-517 Object Level : 4
The CreateQueueControlService updates the status of the message during the message processing flow. Functionaity for WorkFlow status Released : The QueueProcessorService picks the message from the queue and sends to ProcessEngineeringChangeOrder for processing. This in turn will call CreateQueueControlService to update the status of the message to Processing state. If the process fails again the ProcessEngineeringChangeOrder will call CreateQueueControlService to update the status to Errored. When the processing completes successfully the status is updated to Completed. Functionaity for WorkFlow status other than Released : The QueueProcessorService picks the message from the queue and sends to ValidateEngineeringChangeOrder for validation.
This service is implemented as-is and no changes are required Object Type : Requirement Status : Approved Release : R3.0 PPM RFCs : PPM55772 PPM60207 Object Identifier : TD505-PLM-61 Object Level : 3
6.1.4 Error Conditions and Handling Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-518 Object Level : 4
All errors in the integration flow are managed in RequestorABCS. Any such errors leading to failure of the queue processing will be handled in this process. Because of such error, the queue status and result with failure status is updated in the Queue DB.
Object Type : Requirement Status : Approved Release : R3.0 PPM RFCs : PPM55772 Object Identifier : TD505-PLM-578 Object Level : 2
6.2 CreateQueueService Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-205 Object Level : 3
CreateQueueService Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-579 Object Level : 3
N/A
The CreateQueueService is implemented as a routing mediator service. An adapter service (File/JMS Adapter) polls the destinations for any event payloads. The payload is in the form of aXML files. This service receives message as a binary element (aXML file). For each payload received the service inserts a new row into the QUEUE table. An Adapter Service (DB Adapter) is used for the same. The Toplink solution generates the required schema from the table for this DB Adapter.
This service is implemented as-is and no changes are required. Object Type : Requirement Status : Approved Release : R3.0 PPM RFCs : PPM55772
6.3 QueueProcessorServiceImpl Object Type : Comment Status : Approved Release : PPM RFCs :
6.3.2 Layout Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-212
Object Level : 4
Functionaity for WorkFlow status Released : The primary task of this service is to invoke the ProcessEngineeringChangeOrderAgileRequestorABCS. The response from RequestorABCS is processed and the queue is updated with the processing status.
Functionaity for WorkFlow status other than Released :The primary task of this service is to invoke the ValidateEngineeringChangeOrderAgileRequestorABCS based on the Work flow status which is other than Released. The response from RequestorABCS is processed and the queue is updated with the processing status
Input: The QueueMessage generated by the Toplink solution in the QueueProcessorService is used as the input for this Service. Output: QueueStatusMessage, which contains the status and result of the processed queue message. This service is implemented as-is and no changes are required.
Object Type : Requirement Status : Approved Release : R3.0 PPM RFCs : PPM55772 PPM60207 Object Identifier : TD505-PLM-214 Object Level : 3
Object Type : Requirement Status : Approved
Release : R3.0 PPM RFCs : PPM55772 Object Identifier : TD505-PLM-583 Object Level : 2
6.4 ProcessEngineeringChangeOrderAgileReqABCSImpl Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-215 Object Level : 3
ProcessEngineeringChangeOrderAgileReqABCSImpl Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-584 Object Level : 3
6.4.1 New/Reuse/Copy from Object Type : Comment Status : Approved Release :
N/A Object Type : Comment Status : Approved Release : PPM RFCs :
This service is implemented as an asynchronous BPEL process: Here are the Step by Step flow of this process 1. The QueueController creates AgileCreateEngineeringChangeOrderListABM and invokes ProcessEngineeringChangeOrderAgileReqABCSImpl. 2. ProcessEngineeringChangeOrderAgileReqABCSImpl transforms AgileCreateEngineeringChangeOrderListABM into CreateEngineeringChangeOrderListEBM and invokes the CreateEngineeringChangeOrderList operation on EngineeringChangeOrderEBS with CreateEngineeringChangeOrderListEBM as an input. During transformation, following logic should be added for below mappings:
a)
ClassificationCode
Agile sends classification code as 4 segment value for separated by | pip symbol. For example: I - PACKAGING/ADHESIVES/LABELS/MANUALS|DICUT-DIE CUTS|ADHES-ADHESIVES|MISCMISCELLANEOUS
Each segment value is stored as Code and Description separated as - hyphen. For example: DICUT-DIE CUTS, DICUT is a code and DIE CUTS is a description.
EBS expects classification code as 3 segment value separated by . dot symbol and each segment contains only code. For example: DICUT.ADHES.MISC
While doing the transformation from ABM to EBM, transformation logic should be added to convert 4 segment Agile value to 3 segment EBS value for Classification Code.
b)
Product Hierarchy
Agile sends product hierarchy value seperated by | pip symbol. For example: 5834|SEAR|SEAR1
EBS expects product hierarchy value seperated by . dot symbol. For example: 5834.SEAR.SEAR1
While doing the transformation from ABM to EBM, transformation logic should be added to replace pip symbol with dot symbol for product hierarchy.
c)
Oracle Item Type
While doing the transformation from ABM to EBM, transformation logic should be added to get Oracle Item Type name from DVM instead of hard coding and use it in condition statement for Flex Attribute.
d)
Feature License
In Agile feature license is a Multi list type and can send multiple values. For example: Advanced Guest Access License; Advanced IDS/IPS; Advanced Security License
EBS expects only one value in feature license UDA attribute. For example: Advanced Guest Access License; Advanced IDS/IPS; Advanced Security License
While doing the transformation from ABM to EBM, transformation logic should be added to concatenated with ; semi colon symbol.
e)
Sellable Flag
For documents, Agile doesnt contain any field for sellable flag. In EBS, Sellable flag is mandatory. While doing the transformation from ABM to EBM, transformation logic should be added to set Sellable flag as Non-Sellable for documents whose Oracle Item Type value is For Reference. For parts, set Sellable flag to Non-Sellable if its Oracle Item Type value is For Reference. For other values in Oracle Item Type set Sellable flag as-is from Agile.
f)
Handling Comma for License Max
In Agile, item Attribute "License Max#" puts a comma automatically if the number of digits is four or more.
In EBS, License Max UDA defined as Number
While doing the transformation from ABM to EBM, transformation logic should be added to suppress comma in license max value.
g)
Change order UDA
While doing the transformation from ABM to EBM, transformation logic should be added to mapping for Change Order User Defined Attribute.
h)
Filter AML information for items whose Oracle Item Type value is Phantom and As Required
While doing the transformation from ABM to EBM, add transformation logic to not to send AML information to EBS for items whose Oracle Item Type value is Phantom and As Required.
i)
Process Analyst UDA
While doing the transformation from ABM to EBM, transformation logic should be added to mapping for Process Analyst User Defined Attribute.
PBT CD3 Customizations:
j)
MSI Relationship Part on Part:
This attribute is a list attribute in Agile PLM on for this attribute are as follows N/A (Default Value) Buy/Sell Motorola Relationship Pricing
Parts. The valid values
k)
ECCN:
This attribute is present on the Parts Import Export heading and is of cascading list type.
The Source Organization attribute is the one which will segregate the part as WES or WRS. Its a list attribute and has the values as follows: Agile BMS Frozen MD Frozen Networks Frozen PDM1 Shared Frozen
If the attribute value for the Source Organization is Agile then, its a WES part. If the attribute value for the Source Organization is not Agile then, its a WRS part.
Based on the part type (WES/WRS) the US EECN or EU ECCN attributes need to be populated.
ECCN has been configured in Item Categories and here as part of transformation logic, we are removing the "|" from the Agile value and sending it to R12.
For Example : If the ECCN has the value "EAR99|.NR", then in PIP the "|" will be removed and the reansformed value EAR99.NR will be send to R12.
l)
Part Approval Status on AML:
This attribute is present on Parts Manufacturer Tab (AML) and is of type List. This attribute was part of CD1 implementation which has been postponed to CD3. Agile Trilogy valid values for this attribute are different from newly proposed PBT values.
Trilogy valid values are as follows: Approved Approved - See Comments Disqualified Obsolete Rejected
PBT mentioned valid values are as follows: Proposed Qualified Waiver Only Not Required
NOTE: Please find the Agile to R12 mappings in the below mentioed Picture.
m)
Commodity Code:
As part of PIP, we have to change the attribute configuration from PageTwo to TitleBlock (remaining will be same) under Item Categories.This is the direct mapping between the attributes, there is no transformation logic involved.
n)
EU ECCN:
EU ECCN has been configured as Item Category Set in R12 and here as part of transformation logic, we are removing the "|" from the Agile value and sending it to R12.
For Example : If the EU ECCN has the value "EAR99|.NR", then in PIP the "|" will be removed and the reansformed value EAR99.NR will be send to R12.
o)
BOM Attributes:
For the sub class MODEL/Option Class, we have to add 4 additional attributes in BOM related attributes. They are as follows: 1) BOM. Optional: In PIP, the value for this attribute will be transformed. The value "Yes"will be transformed to "1" and the value "No" will be transformed to "2". 2) BOM. MutExcl: In PIP, the value for this attribute will be transformed. The value "Yes"will be transformed to "1" and the value "No" will be transformed to "2". 3) BOM. Minqty: Direct mapping. 4) BOM. Maxqty: Direct Mapping.
p) Part Tansfer : We have to check the condition whether the DetinationERP attribute has "Trilogy R12 or SAP" or not as a value. If yes, then that part will be transferred to R12.
q) Global BOM/ Non Global BOM: For this, we have to consider below mentioed scenarios. They are as follows:
1.)If the Destination ERP=Trilogy R12 or SAP and Global BOM=Yes, then all the BOM Components will be sending to R12. 2.) If the Destination ERP! =Trilogy R12 or SAP and Global BOM=Yes, BOM Components will not be sending to R12. then all the
3.)If the Destination ERP! =Trilogy R12 or SAP and Global BOM=No, then all the BOM Components will not be sending to R12. 4.)If the Destination ERP=Trilogy R12 or SAP and Global BOM=No, then we have to traverse all the BOM Components and check for ERP Org(BOM.LIST04).If ERP Org=R12 Trilogy then only that items BOM components will be transformed to R12.
3. CreateEngineeringChangeOrderListResponseEBM is received from EngineeringChangeOrderEBS and based on the status of the ECO creation in Oracle EBusiness Suite; the QueueController is invoked to update the status of the queue message. 4. ProcessEngineeringChangeOrderAgileReqABCSImpl transforms CreateEngineeringChangeOrderListResponseEBM into AgileUpdateEngineeringChangeOrderListABM, which is sent as an input to the Agile PLM Web service 5. The Web services update the transfer status of the change order in Agile PLM, which is a predefined P2 or P3 attribute on the change order object in Agile PLM. AgileUpdateEngineeringChangeOrderListResponseABM is sent to ProcessEngineeringChangeOrderAgileReqABCSImpl. 6. Filter SAPLoad Template components.
PIP shouldnt send items/components where SAPLoadTemplate (in aXML is list19)has the value like ROH(F,10)|ROH|ROYALTY
This service is implemented as-is and no changes are required._ Object Type : Requirement Status : Approved
Release : R3.0 PBT CD3 PBT Go Live PPM RFCs : PPM55772 Object Identifier : TD505-PLM-784 Object Level : 4
<Picture : Agile To R12 Attribute Mappings>_
Object Type : Comment Status : Approved Release : PBT CD3 PPM RFCs : Object Identifier : TD505-PLM-219 Object Level : 3
All errors in the integration flow are managed in RequestorABCS. Any such errors leading to failure of the queue processing will be handled in this process. Because of such error, the queue status and result
with failure status is updated in the Queue DB.
6.5 EngineeringChangeOrderEBS Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-220 Object Level : 3
EngineeringChangeOrderEBS Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-587 Object Level : 3
6.5.1 New/Reuse/Copy from
N/A Object Type : Comment
EngineeringChangeOrderEBS exposes the operations related to the ECO integration on the EngineeringChangeOrder EBO. The following list itemizes the routing rules: EngineeringChangeOrderEBS service:CreateEngineeringChangeOrderList: Routes CreateEngineeringChangeOrderListEBM to CreateEngineeringChangeOrderListEbizProvABCSImpl EngineeringChangeOrderResponseEBS service:CreateEngineeringChangeOrderListResponse: Routes CreateEngineeringChangeOrderListResponseEBM to ProcessEngineeringChangeOrderAgileReqABCSImpl This service is implemented as-is and no changes are required.
Object Type : Requirement
Status : Approved Release : R3.0 PPM RFCs : PPM55772 Object Identifier : TD505-PLM-224 Object Level : 3
6.6 CreateEngineeringChangeOrderListEbizProvABCSImpl Object Type : Comment
6.6.2 Layout Object Type : Comment Status : Approved
This is a single operation service. This accepts an ECO-containing item and BOM information message as a request and returns a response. In Agile PLM to Oracle E-Business Suite flow, CreateEngineeringChangeOrderListEbizProvABCSImpl is used for transforming CreateEngineeringChangeOrderListEBM into CreateECOABM, which invokes the CreateEngineeringChangeOrderList operation in Oracle E-Business Suite.In the return flow, the OA
Adapter sends CreateECOResponseABM, which is transformed by CreateEngineeringChangeOrderListEbizProvABCSImpl into CreateEngineeringChangeOrderListResponseEBM.
During EBM to ABM transformation, following logic should be added for below mappings:
a.
Filter BOMTEXT components.
PIP shouldnt send items/components name starting with BOMTEXT to EBS(R12).
b.
Filter SAPLoad Template components.
PBT CD3 Customizations: As part of PBT CD3 "Manufacture Name" has been trimmed to 30 characters length before reaching to R12. This service is implemented as an asynchronous BPEL Process. Object Type : Requirement Status : Approved Release : R3.0 PBT CD3 PBT Go Live PPM RFCs : PPM55772 Object Identifier : TD505-PLM-338
Object Level : 3
6.7 UpdateEngineeringChangeOrderListEbizReqABCSImpl Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-591
Object Level : 3
The requester ABCS, defined as a synchronous process, receives a list of change IDs from the Oracle E-Business Suite concurrent program. The list contains IDs that have last_update_date greater than the last run date of the concurrent program. The requester BPEL process filters the list of IDs to a list of IDs that are present in the crossreference tables in the FMW layer. This provides a list of change orders that were actually from the Agile PLM System alone. Theoriginal list of change IDs may be those that are from non-Agile PLM sources as well.
The BPEL process then makes an OA Adapter call out that calls the PL/SQL API, which provides the Item details that is sent out. This is the UpdateEngineeringChangeOrderList ABM.
A transformation converts UpdateEngineeringChangeOrderListABM to UpdateEngineeringChangeOrderListEBM. An asynchronous request-delayed response call is made to EngineeringChangeOrderEBS with UpdateEngineeringChangeOrderListEBM. This call is routed to the appropriate provider. The BPEL instance is reactivated from dehydration store when the asynchronous call returns
from the provider and provides the status of the transaction to the caller concurrent program (because it is a synchronous call). This service is implemented as-is and no changes are required. Object Type : Requirement Status : Approved Release : R3.0 PPM RFCs : PPM55772 Object Identifier : TD505-PLM-354 Object Level : 3
6.8 UpdateEngineeringChangeOrderListAgileProvABCSImpl Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-593 Object Level : 3
6.8.3 Functionality
This service is implemented as an asynchronous process. UpdateEngineeringChangeOrderListAgileProvABCSImpl is invoked by EngineeringChangeOrderEBS with UpdateEngineeringChangeOrderListReqMsg, which contains UpdateEngineeringChangeOrderListEBM as input. Transform operation is called to convert UpdateEngineeringChangeOrderListEBM into AgileUpdateEngineeringChangeOrderListABM.
AgileUpdateEngineeringChangeOrderListABM is passed as an input to the Web service operation and the following steps are processed Updates the transfer status-related attributes on the change order Updates effectivity dates and implementation status.
If all affected items statuses are implemented, changes status of the change order to implemented (for Oracle E-Business Suite to Agile PLM flow). Moving of the ECO to an Implemented status is an optional step and can be disabled. Per the CR the ECO status and the Implementation date will be updated in Agile attribute.
The ECO status of "Scheduled" in R12 should be mapped to "Scheduled" in Agile
AgileUpdateEngineeringChangeOrderListResponseABM is received after the successful run of the Coarse Grained API UpdateChange. If the UpdateChange service operation fails in Agile PLM, a new fault is generated and sent across with an appropriate error message
For ECO update / ECO write back to occur the ECO subclass should match the Oracle Change Order types setup in Oracle EBS/PIM for the out of the box product. As a part of the Release 3.0 Scope the ECO subclasses will not match the Oracle EBS/PIM change order types and this would require modification to support the Many to One relationship of Agile ECO/MCO to Oracle EBS ECO types. Object Type : Requirement Status : Approved Release : R3.0 PPM RFCs : PPM55772 Object Identifier : TD505-PLM-359 Object Level : 3
Object Type : Requirement Status : Approved Release : R3.0 PPM RFCs : PPM55772
6.9 EngineeringChangeOrderEBS Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-595 Object Level : 3
Reuse Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-596
Object Level : 3
EngineeringChangeOrderEBS exposes the operations related to the validate ECO and ECO integration on the EngineeringChangeOrder EBO.
The following list itemizes the routing rules: EngineeringChangeOrderEBS ValidateEngineeringChangeOrderList: Routes ValidateEngineeringChangeOrderListEBM to ValidateEngineeringChangeOrderListEbizProvABCSImpl
EngineeringChangeOrderResponseEBS ValidateEngineeringChangeOrderListResponse: Routes ValidateEngineeringChangeOrderListResponseEBM to ValidateEngineeringChangeOrderListAgileReqABCSImpl Object Type : Requirement Status : Approved Release : R3.0 PPM RFCs : PPM55772 Object Identifier : TD505-PLM-364 Object Level : 3
6.9.4 Error Conditions and Handling Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-534
Object Level : 4
6.10 UpdateItemListEbizReqABCSImpl Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-597 Object Level : 3
6.10.1 New/Reuse/Copy from Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-366
Object Level : 4
This service is called when multiple items in Agile PLM with all the operational attributes as well as the attributes from Oracle E-Business Suite, such as unit cost, need to be updated. This is a push from Oracle E-Business Suite to Agile PLM through a batch process. OOTB component not currently required, but available for future release.
This process includes: The requester ABCS, defined as a synchronous process which receives a list of item IDs from the Oracle E-Business Suite concurrent program. The list contains only those IDs that have last_update_date greater than the last run date of the concurrent program.
The requester BPEL process filters the list of IDs to a list of IDs that are present in the cross-reference tables in the Fusion Middleware (FMW) layer. This provides a list of items that are in Agile PLM. The original list of item IDs can contain items that are from the non-Agile PLM sources as well. The BPEL process then makes an OA Adapter call to the PL/SQL API, which provides the details of the sent item. This is the item ABM. Object Type : Requirement Status : Approved Release : R3.0 PPM RFCs : PPM55772 Object Identifier : TD505-PLM-626 Object Level : 4
A transformation converts the ABM to an EBM and an asynchronous request-delayed response call is made to ItemEBSV2 with UpdateItemListEBM. This service is routed to the appropriate provider.
Object Type : Requirement Status : Approved Release : R3.0
PPM RFCs : PPM55772 Object Identifier : TD505-PLM-627 Object Level : 4
The BPEL instance is reactivated from dehydration store when the asynchronous call returns from the provider and provides the status of the transaction back to the caller concurrent program (because it is a synchronous call). The concurrent program logs the status of this call. Object Type : Requirement Status : Approved Release : R3.0 PPM RFCs : PPM55772 Object Identifier : TD505-PLM-369 Object Level : 3
OOTB component not currently required, but available for future release.
6.11 UpdateItemListAgileProvABCSImpl Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-599 Object Level : 3
6.11.3 Functionality
The UpdateItemListAgileProvABCSImpl is used to facilitate the communication between the ItemEBSV2 and the Agile PLM Web service used for updating the item attribute information in a batch mode in Agile PLM.
OOTB component not currently required, but available for future release. Object Type : Requirement Status : Approved Release : R3.0 PPM RFCs : PPM55772 Object Identifier : TD505-PLM-628 Object Level : 4
The process includes: The UpdateItemListAgileProvABCSImpl receives the UpdateItemListReqMsg that contains the UpdateItemListEBM then the transform operation is called to convert the UpdateItemListEBM into the AgileUpdateItemListABM. Object Type : Requirement Status : Approved Release : R3.0 PPM RFCs : PPM55772 Object Identifier : TD505-PLM-630
Object Level : 4
The AgileUpdateItemListABM is sent as input to the Web service operation UpdateItemList (coarsegrained APIs in Agile PLM) to update the items in Agile PLM. The AgileUpdateItemListResponseABM is received upon successful implementation of the coarse-grained API. Object Type : Requirement Status : Approved Release : R3.0 PPM RFCs : PPM55772 Object Identifier : TD505-PLM-631 Object Level : 4
The transform operation is called to convert AgileUpdateItemListResponseABM to UpdateItemListResponseEBM, which is returned as an output of this BEPL process. If the UpdateItemList service operation fails on the Agile PLM side, a new fault is generated and is sent across with an appropriate error message. Object Type : Requirement Status : Approved Release : R3.0 PPM RFCs : PPM55772 Object Identifier : TD505-PLM-404 Object Level : 3
6.11.4 Error Conditions and Handling Object Type : Comment Status : Approved Release :
6.12 ACSAXMLJMSConsumer Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-601 Object Level : 3
6.12.1 New/Reuse/Copy from
N/A Object Type : Comment
ACSAXMLJMSConsumer reads aXML sent by Agile in the form of binary format from AgilePLMECOJMSQueue and invokes CreateQueueService to post the message into AIA Queue. Object Type : Requirement Status : Approved Release : R3.0 PPM RFCs : PPM55772 Object Identifier : TD505-PLM-399 Object Level : 3
6.12.4 Error Conditions and Handling Object Type : Comment Status : Approved
6.13 QueueProcessorService Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-602 Object Level : 3
6.13.1 New/Reuse/Copy from Object Type : Comment Status : Approved
N/A Object Type : Comment Status : Approved Release :
The QueueProcessorService is implemented as a routing mediator service that acts like an Interface and provides a faade in front of the QueueProcessorServiceImpl service. A DB Adapter polls on the QUEUE_CONTROL table for any Pending messages. A pending message in the table is routed to the QueueProcessorServiceImpl service, which processes the message. Based on the result from the implementation service, the status of the message is updated in the control table. This service is implemented as-is and no changes are required. Object Type : Requirement Status : Approved Release : R3.0 PPM RFCs : PPM55772 Object Identifier : TD505-PLM-394 Object Level : 3
6.14 QueryItemListEbizAdapter Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-604 Object Level : 3
N/A
From a list of item IDs from the Oracle E-Business Suite concurrent program, queries and fetches the Item attributes information that got updated.
Object Type : Requirement Status : Approved Release : R3.0 PPM RFCs : PPM55772 Object Identifier : TD505-PLM-389
Object Level : 3
6.15 CreateEngineeringChangeOrderListEbizAdapter Object Type : Comment Status : Approved
6.15.2 Layout Object Type : Comment Status : Approved Release :
Used for the OA adapter INV_EBI_CHANGE_ORDER_PUB/PROCESS_CHANGE_ORDER_LIST PL/SQL function call. Object Type : Requirement Status : Approved Release : R3.0 PPM RFCs : PPM55772
The Out of the Box error handler is invoked to update the error message in the queue. At a later point in time when the adapter is up this message can be re processed from the queue.
6.16 AIAConfigurationproperties.xml Object Type : Comment Status : Approved Release : PPM RFCs :
Object Level : 4
The D2R PIP provides a flexible architecture and options to customize the Integration using various configuration options These configuration parameters control the behavior of the flow as well as provide some default settings for the Integration AIAConfigurationProperties.xml is a standard AIA XML configuration file used for capturing these configuration parameters.
During runtime all the properties in the AIAConfigurationProperties.xml are referenced from the MDS (Meta Data Repository). Thus, any changes made to the AIAConfigurationProperties.xml will reflect only after the MDS is updated with the new changes.
The AIA Configuration file offers these configuration at the following levels System level - used by all the PIPs configured on server Service level - used by ihe individual service level components such as Application Business Connector Service (ABCS) Object Type : Requirement Status : Approved Release : R3.0 PPM RFCs : PPM55772 Object Identifier : TD505-PLM-633 Object Level : 4
As a Part of the installation the PIP provides a few seeded parameters and defaults. These Defaults can be modified to control the Integration based on the customer requirements
The following Configuration parameters have been modified for use in this release.
<Property name="UDA.ATTR_GROUP_SHORT_NAME.LICENSING">LICENSING</Property>
<Property name="UDA.ATTR_SHORT_NAME.PRODUCT_CATEGORY">PRODUCT_CATEGORY</Property> <Property name="UDA.ATTR_GROUP_SHORT_NAME.LICENSING">Licensing</Property>
<Property name="UDA.ATTR_SHORT_NAME.PRODUCT_CATEGORY">Product Category</Property> <Property name="UDA.ATTR_SHORT_NAME.SECONDARY_PRODUCT_CAT">Secondary Product Category</Property> <Property name="UDA.ATTR_SHORT_NAME.UPG_SW_MTL_SP_ENTITLEMNT">Upgradeable Software Material - Specific Entitlement</Property> <Property name="UDA.ATTR_SHORT_NAME.UPG_SW_MTL_LC_TYPE">Upgradeable Software Material - License Type</Property> <Property name="UDA.ATTR_SHORT_NAME.UPG_HW_MTL_MAX_ENTITLEMNT">Upgradeable Hardware Material - Max Entitlement</Property> <Property name="UDA.ATTR_SHORT_NAME.1_LC_TYPE">1 - License Type</Property> <Property name="UDA.ATTR_SHORT_NAME.1_LC_MAX">1 - License Max #</Property> <Property name="UDA.ATTR_SHORT_NAME.2_LC_TYPE">2 - License Type</Property> <Property name="UDA.ATTR_SHORT_NAME.2_LC_MAX">2 - License Max #</Property> <Property name="UDA.ATTR_SHORT_NAME.3_LC_TYPE">3 - License Type</Property> <Property name="UDA.ATTR_SHORT_NAME.3_LC_MAX">3 - License Max #</Property> <Property name="UDA.ATTR_SHORT_NAME.4_LC_TYPE">4 - License Type</Property> <Property name="UDA.ATTR_SHORT_NAME.4_LC_MAX">4 - License Max #</Property> <Property name="UDA.ATTR_SHORT_NAME.5_LC_TYPE">5 - License Type</Property> <Property name="UDA.ATTR_SHORT_NAME.5_LC_MAX">5 - License Max #</Property> <Property name="UDA.ATTR_SHORT_NAME.FEATURE_LC">Feature Licenses</Property>
Object Type : Requirement Status : Approved Release : R3.0 PPM RFCs : PPM55772 Object Identifier : TD505-PLM-379
Object Level : 3
During the transformation of the message from ABM to EBM and from EBM to ABM, if the service encounters any data error say for example Duplicate values in DVM, the Error handler is invoked and the flow fails at that point. The error message is displayed in the fault section of the instance flow trace. The flow can be recovered from the failure point onward and if there is no further error in the flow. Similarly when the EBS adapter is down the processing fails while invoking the EBS adapter. The error handler is invoked to update the error message in the queue. At a later point in time when the adapter is up this message can be re processed from the queue.
6.17 Domain Value Maps Object Type : Comment
DVMs are a standard feature of the Oracle SOA Suite. They enable you to equate lookup codes and other static values across applications, for example, FOOT and FT or US and USA. DVMs are static in nature, though administrators can add additional maps as needed. Transactional business processes never update DVMs; they only read from them. DVMs are stored in XML files and cached in memory at run time. Object Type : Requirement
During installation, the DVMs used for the PIP are imported with default data mappings. The values mapped by these DVMs must be changed as needed. Many DVMs are seeded and do not need to be changed. Because most of the Agile PLM attributes being mapped are list values, the Agile PLM data is not seeded and should be changed accordingly. Object Type : Requirement Status : Approved Release : R3.0 PPM RFCs : PPM55772 Object Identifier : TD505-PLM-634 Object Level : 4
The following are the List of Mandatory DVM's used for the Integration. AGILE_INTEGRATION_USERS AGILE_SITE_TARGET_MAPPING AGILE_TARGET_SITE_MAPPING ECO_STATUS_CODE ITEM_PRIMARYCLASSIFICATIONCODE ITEM_STATUS_CODE ITEM_UOM_CODE ITEM_PRIMARYCLASSIFICATIONCODE Object Type : Requirement
These are the custom DVM's that will be used for the Integration
AGILEROHS_TO_EBIZROHS_MAPPING CUSTOM_UDA_APPLICATION_SHORT_NAME CUSTOM_UDA_ATTR_GROUP_TYPE CUSTOM_UDA_PROPERTIES CUSTOM_UDA_ATTR_SHORT_NAME CUSTOM_UDA_ATTR_GROUP_SHORT_NAME CUSTOM_CATEGORY_SETS CUSTOM_UDA_ATTR_LICENSE_TYPE CUSTOM_UDA_ATTR_PRODUCT_CATEGORY CUSTOM_CATEGORY_SETS_CMM CUSTOM_CATEGORY_SETS_BATTERY_DIRECTIVE CUSTOM_CATEGORY_SETS_ROHS CUSTOM_DVM_NAME_LOOKUP Object Type : Requirement Status : Approved Release : R3.0 PPM RFCs : PPM55772
6.17.4 Error Conditions and Handling Object Type : Comment Status : Approved Release : PPM RFCs : PPM55772 Object Identifier : TD505-PLM-550 Object Level : 4
During the transformation of the message from ABM to EBM and from EBM to ABM, if the service encounters any data error say for example Duplicate values in DVM, the Error handler is invoked and the flow fails at that point. The error message is displayed in the fault section of the instance flow trace. The flow can be recovered from the failure point onward and if there is no further error in the flow. Similarly when the EBS adapter is down the processing fails while invoking the EBS adapter. The error handler is invoked to update the error message in the queue. At a later point in time when the adapter is up this message can be re processed from the queue. Object Type : Requirement Status : Approved Release : R3.0 PPM RFCs : PPM55772 Object Identifier : TD505-PLM-474 Object Level : 2
6.18 QueryPendingECOIndicatorforItem Object Type : Comment
New Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-612 Object Level : 3
A Process extension (PX) from Agile PLM will call this process through a SOAP call. The process will get the list of items and processes each item individually and queries the EBS / PIM for the status of the previous ECOs on the item which are yet to be implemented and the Item Status through an API call. The details are returned to the Agile PX through a SOAP Response. Object Type : Requirement Status : Approved
This is a custom composite that will be developed to provide Pending ECO Status: ECOs pending to be implemented in the EBS / PIM module for all the items that are to be released through an ECO process from Agile PLM. This will be achieved by creating a Process extension (PX) from Agile PLM which will call this process through a SOAP call. The process will get the the status of the previous ECOs on the item which are yet to be implemented and the Item Status through an API call. The details are returned to the Agile PX through a SOAP Response. Object Type : Requirement Status : Approved Release : R3.0 PPM RFCs : PPM55772 Object Identifier : TD505-PLM-645 Object Level : 4
The following is the schema definition of the request / response for Pending ECO status for the item. <?xml version="1.0" encoding="windows-1252" ?> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://xmlns.oracle.com/EnterpriseObjects/Core/Custom/EBO/EngineeringChangeOrder/Custo m/V1"
targetNamespace="http://xmlns.oracle.com/EnterpriseObjects/Core/Custom/EBO/EngineeringChangeO rder/Custom/V1" elementFormDefault="qualified">
<xsd:element name="ItemsPendingECOListRequest"> <xsd:complexType> <xsd:sequence> <xsd:element ref="ItemNumber" minOccurs="1" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType> </xsd:element>
<xsd:element name="ItemNumber" type="xsd:string"/>
<xsd:element name="ItemsPendingECOListResponse"> <xsd:complexType> <xsd:sequence> <xsd:element ref="Item" minOccurs="1" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType> </xsd:element>
<xsd:element name="Item" type="ItemType"/>
<xsd:complexType name="ItemType"> <xsd:sequence> <xsd:element name="ItemNumber" type="xsd:string" minOccurs="1"/> <xsd:element name="ItemStatus" type="xsd:string" minOccurs="0"/>
<xsd:element ref="ECOList" minOccurs="1" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType>
<xsd:element name="ECOList" type="ECOListType"/>
<xsd:complexType name="ECOListType"> <xsd:sequence> <xsd:element name="OrganizationCode" type="xsd:string"/> <xsd:element name="ECOStatus" type="xsd:string"/> </xsd:sequence> </xsd:complexType>
</xsd:schema> Object Type : Requirement Status : Approved Release : R3.0 PPM RFCs : PPM55772 Object Identifier : TD505-PLM-646 Object Level : 4
For ECO Status msifnd_isg_common_process.ack_ebs_txn (
piv_interface_name = 'MSIAGILINTERFACE-ECO-STATUS' piv_interface_type = 'PLSQL', piv_mw_tool = 'SOA', piv_mw_txn_id = EBS_TXN_ID, pin_mw_instance_id=> Main Composites Instance ID, piv_status = 'A' if Success, 'E' if you have any error, piv_error_msg => Error Message, pov_success=>'Success' if everything is good, 'Error :<<Error message>> if any );
This is a custom composite that will be developed to provide Item Status: The status of the Item implemented in all the orgs This will be achieved by creating a Process extension (PX) from Agile PLM which will call this process through a SOAP call. The process will get the list of items and processes each item individually and queries the EBS / PIM for the status of the previous ECOs on the item which are yet to be implemented and the Item Status through an API call. The details are returned to the Agile PX through a SOAP Response. Object Type : Requirement Status : Approved Release : R3.0
PPM RFCs : PPM55772 Object Identifier : TD505-PLM-648 Object Level : 4
The following is the schema definition of the request / response for Item Status. <?xml version="1.0" encoding="windows-1252" ?> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://xmlns.oracle.com/EnterpriseObjects/Core/Custom/EBO/EngineeringChangeO rder/Custom/V1" elementFormDefault="qualified">
<xsd:element name="ItemsListRequest"> <xsd:complexType> <xsd:sequence> <xsd:element ref="ItemNumber" minOccurs="1" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType> </xsd:element>
<xsd:element name="ItemNumber" type="xsd:string"/>
<xsd:element name="ItemsListResponse"> <xsd:complexType>
<xsd:sequence> <xsd:element ref="Item" minOccurs="1" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType> </xsd:element>
<xsd:element name="Item" type="ItemType"/>
<xsd:complexType name="ItemType"> <xsd:sequence> <xsd:element name="ItemNumber" type="xsd:string" minOccurs="1"/> <xsd:element name="OrganizationCode" type="xsd:string" minOccurs="1"/> <xsd:element name="ItemStatus" type="xsd:string" minOccurs="1"/> </xsd:sequence> </xsd:complexType>
</xsd:schema> Object Type : Requirement Status : Approved Release : R3.0 PPM RFCs : PPM55772 Object Identifier : TD505-PLM-647 Object Level : 4
Prior to the response from EBS, the Following packages has to be executed
For Item Status msifnd_isg_common_process.ack_ebs_txn ( piv_interface_name = 'MSIAGILINTERFACE-ITEM-STATUS' piv_interface_type = 'PLSQL', piv_mw_tool = 'SOA', piv_mw_txn_id = EBS_TXN_ID, pin_mw_instance_id=> Main Composites Instance ID, piv_status = 'A' if Success, 'E' if you have any error, piv_error_msg => Error Message, pov_success=>'Success' if everything is good, 'Error :<<Error message>> if any
6.18.4 Error Conditions and Handling Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-552
Object Level : 4
In Case of an Error while invoking the PL/SQL API the Tivoli Error Handling API will be invoked. Object Type : Requirement Status : Approved Release : R3.0 PPM RFCs : PPM55772 Object Identifier : TD505-PLM-621 Object Level : 2
6.19 UpdateItemComplaince Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-651 Object Level : 3
The Standard PIP requires update to an Item through Release of either an ECO /MCO Process. The Following component is developed to support the update of an item without an ECO/MCO Process.
Object Type : Comment Status : Approved Release : PPM RFCs :
Object Level : 4
The Environmental attributes are updated either through a user update or through a compliance roll-up program in Agile PLM. During this process an Event will be triggered to update these information in Oracle EBS. A flow will be developed to parse the List of items that is being updated in agile along with the corresponding values. This information will be processed by the PIP using the required data transformations. The following is the schema definition expected by FMW: <?xml version="1.0" encoding="windows-1252" ?> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://xmlns.oracle.com/EnterpriseObjects/Core/Custom/EBO/EngineeringChangeO rder/Custom/V1" elementFormDefault="qualified"> <xsd:element name="ItemsListRequestABM"> <xsd:complexType> <xsd:sequence> <xsd:element ref="Item" minOccurs="1" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:element name="ItemsListResponseABM"> <xsd:complexType> <xsd:sequence> <xsd:element ref="Item" minOccurs="1" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:element name="Item" type="ItemType"/> <xsd:complexType name="ItemType"> <xsd:sequence> <xsd:element name="ItemNumber" type="xsd:string" minOccurs="1"/> <xsd:element ref="PageTwoAttributes" minOccurs="1"/> </xsd:sequence>
</xsd:complexType> <xsd:element name="PageTwoAttributes" type="PageTwoAttributesType"/> <xsd:complexType name="PageTwoAttributesType"> <xsd:sequence> <xsd:element name="List01" type="xsd:string" minOccurs="0" /> <xsd:element name="List02" type="xsd:string" minOccurs="0" /> <xsd:element name="List03" type="xsd:string" minOccurs="0" /> <xsd:element name="List04" type="xsd:string" minOccurs="0" /> <xsd:element name="List05" type="xsd:string" minOccurs="0" /> <xsd:element name="List06" type="xsd:string" minOccurs="0" /> <xsd:element name="List07" type="xsd:string" minOccurs="0" /> <xsd:element name="List08" type="xsd:string" minOccurs="0" /> <xsd:element name="List09" type="xsd:string" minOccurs="0" /> <xsd:element name="List10" type="xsd:string" minOccurs="0" /> <xsd:element name="Multilist01" type="MultiListType" minOccurs="0" /> <xsd:element name="Multilist02" type="MultiListType" minOccurs="0" /> <xsd:element name="Multilist03" type="MultiListType" minOccurs="0" /> <xsd:element name="Multilist04" type="MultiListType" minOccurs="0"/> <xsd:element name="Multilist05" type="MultiListType" minOccurs="0" /> </xsd:sequence> </xsd:complexType>
<xsd:complexType name="MultiListType"> <xsd:sequence> <xsd:element name="Value" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence> </xsd:complexType> </xsd:schema>
The actual attributes used is subject to change and will be updated accordingly
In Case of an Error the Standard Out of the Box Error handler will be invoked and all transactions will be rolled back. The Errored records will by published to a file server location along with a Log file and a list of items that were not updated. The name of the return file will match the input file processed by the PIP with a log file extension. Object Type : Requirement
6.20 CreateManufacturer
The Standard PIP does not support the Creation of Manufacturer in Oracle EBS/PIM. It requires the Manufacturers to exist in EBS before releasing the ECO/MCO with an AML infroamtion. To support this process PIP will be extended to create manufacturers if the particular Manufacturer does not exist in Oracle EBS/PIM.
The Create Manufacturer process will be invoked after an existence check is performed in EBS. For all manufacturer that does not exist the process will invoke a custom flow to create these Manufacturers.
Design to Release PIP supports user exits at different process levels for customizing the PIP. Inorder to support the Manufacturer creation and transfer of the approval status the PostProcessEBM will enabled and an additional flow will be created.
The Create manufacturer will transfer the following information from Agile to EBS/PIM
Name Address
City State Country Postal Code
The Address information would be concatenated to a single DFF in Oracle as per the requirements.
All errors returned from the EBS API will be processed and corresponding AIA Error handler will be invoked with the error messages which will be published to the PIP queue. All transactions will be rolledback in case of the error.
6.21 Error Handling and Exception Framework Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-617 Object Level : 3
Reuse Object Type : Comment
6.21.3 Functionality Object Type : Comment Status : Approved
The Oracle Application Integration Architecture (AIA) Error Handling Framework groups BPEL process errors into two categories: Run-time faults Business faults
Run-time Faults A run-time fault can occur in one of two scenarios: The partner link invocation fails. The partner link receives a named fault indicating that it is a run-time fault.
These faults are not user-defined and are issued by the system. Some of the situations in which a BPEL process can encounter a run-time fault include the following: The process tries to use a value incorrectly. A logic error occurs. A SOAP fault occurs in a SOAP call.
An exception is issued by the server, and so forth.
Business Faults A business fault can occur in one of two scenarios: A BPEL process runs a throw activity after evaluating a condition as a fault. An Invoke activity receives a named fault indicating that it is a business fault.
Business faults are the application-specific faults that are generated when erroneous conditions take place when the message is being processed. These faults are specified by the BPEL process component and are defined in the WSDL. Object Type : Requirement Status : Approved Release : R3.0 PPM RFCs : PPM55772 Object Identifier : TD505-PLM-640 Object Level : 4
AIA Services built as BPEL processes should be enabled and configured to catch and handle the run-time, as well as business faults. All out of the box functionality's has this inbuilt error / exception handling framework which is enabled by configuring the error handling framework. For all the customizations, AIA provides the facility to implement the error handling framework. Any failure in the processing of a change order is captured by Queue Manager. Object Type : Requirement
To View the error, click the link Errored in the Process Status column. This Error Message comprises two parts: Error Text - This is the description of the error source, which can be from any of the
participating ABCS services that faulted. Details - The error details consist of: Service Name: The name of the service where an instance failed to run. Instance ID: The identification number of the instance that failed. Object Type : Requirement Status : Approved Release : R3.0 PPM RFCs : PPM55772 Object Identifier : TD505-PLM-642 Object Level : 4
Multiple faults generated by the service are captured and displayed in this UI. In addition to this, any failures in the flows are captured in the AIA Error Logs. These can be seen from the Enterprise Manager Console logs section. In an event in which a certain service is down and the error is not related to the payload, users can resubmit the change in the Queue Manager UI. Object Type : Requirement Status : Approved
The PIP uses the SOA infrastructure to send email notifications on Error. Oracle User Messaging Service enables users to receive notifications sent from SOA applications that are developed and deployed to the Oracle WebLogic Server using Oracle JDeveloper.To enable the workflow participants to receive and forward notifications, use Oracle 11g Enterprise Manager to set the Oracle User Messaging Service environment by configuring the appropriate driver instances that reside on the same Oracle WebLogic Server on which you deploy the workflow application Object Type : Requirement Status : Approved Release : R3.0 PPM RFCs : PPM55772 Object Identifier : TD505-PLM-483 Object Level : 3
All errors in the integration flow are managed in RequestorABCS. Any such errors leading to failure of the queue processing will be handled in this process. Because of such error, the queue status and result
6.22 Error Handling and Reporting Requirements Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-661 Object Level : 3
New
6.22.3 Functionality Object Type : Comment
PIP will be setup to generate an email to a configurable distribution list, when an error occurs notifing of an error.
PIP will allow the user to view all errors per start and end time.
A consolidated report will be generated from PIP to show all ECO errors with description of errors during a timeframe. Users will be able to login to a GUI interface to generate the report. The report data elements are defined in the following spreadsheet: <http://compass.mot-solutions.com/go/418453610>
Agile will have a standard report to view all ECOs and MCOs with Transfer Status of Error. Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-670 Object Level : 3
6.22.4 Report Layout Design
None Object Type : Comment
6.23 ValidateEngineeringChangeOrderListAgileReqABCSImpl Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-754 Object Level : 3
ValidateEngineeringChangeOrderListAgileReqABCSImpl
6.23.1 New/Reuse/Copy from Object Type : Comment
N/A
Object Type : Comment
This service is implemented as an asynchronous BPEL process: Here are the Step by Step flow of this process:
1. The QueueController creates the AgileValidateEngineeringChangeOrderListABM and invokes the ValidateEngineeringChangeOrderListAgileReqABCSImpl.
2 ValidateEngineeringChangeOrderListAgileReqABCSImpl receives AgileValidateEngineeringChangeOrderListABM as input and transforms to ValidateEngineeringChangeOrderListEBM and calls EngineeringChangeOrderEBS
3 In the return flow, ValidateEngineeringChangeOrderListAgileReqABCSImpl recieves ValidateEngineeringChangeOrderListResponseEBM as input from EngineeringChangeOrderResponseEBS
4 ValidateEngineeringChangeOrderListAgileReqABCSImpl transforms ValidateEngineeringChangeOrderListResponseEBM to AgileValidateEngineeringChangeOrderListResponseABM.
5 ValidateEngineeringChangeOrderListAgileReqABCSImpl invokes QueueProcessorServiceImpl by passing AgileValidateEngineeringChangeOrderListResponseABM as input to update the status back to the Queue .
6. ValidateEngineeringChangeOrderListAgileReqABCSImpl transforms ValidateEngineeringChangeOrderListResponseEBM to UpdateEngineeringChangeOrderListEBM.
7 ValidateEngineeringChangeOrderListAgileReqABCSImpl transforms UpdateEngineeringChangeOrderListEBM to AgileUpdateEngineeringChangeOrderListABM
8 ValidateEngineeringChangeOrderListAgileReqABCSImpl invokes AgilePLM Web Service by passing AgileUpdateEngineeringChangeOrderListABM as input .
a)
ClassificationCode
Agile sends classification code as 4 segment value for separated by | pip symbol. For example: I - PACKAGING/ADHESIVES/LABELS/MANUALS|DICUT-DIE CUTS|ADHES-ADHESIVES|MISCMISCELLANEOUS
Each segment value is stored as Code and Description separated as - hyphen. For example: DICUT-DIE CUTS, DICUT is a code and DIE CUTS is a description.
EBS expects classification code as 3 segment value separated by . dot symbol and each segment contains only code.
For example: DICUT.ADHES.MISC
While doing the transformation from ABM to EBM, transformation logic should be added to convert 4 segment Agile value to 3 segment EBS value for Classification Code.
b)
Product Hierarchy
Agile sends product hierarchy value seperated by | pip symbol. For example: 5834|SEAR|SEAR1
EBS expects product hierarchy value seperated by . dot symbol. For example: 5834.SEAR.SEAR1
While doing the transformation from ABM to EBM, transformation logic should be added to replace pip symbol with dot symbol for product hierarchy.
c)
Oracle Item Type
While doing the transformation from ABM to EBM, transformation logic should be added to get Oracle Item Type name from DVM instead of hard coding and use it in condition statement for Flex Attribute.
d)
Feature License
In Agile feature license is a Multi list type and can send multiple values. For example: Advanced Guest Access License; Advanced IDS/IPS; Advanced Security License
EBS expects only one value in feature license UDA attribute. For example: Advanced Guest Access License; Advanced IDS/IPS; Advanced Security License
While doing the transformation from ABM to EBM, transformation logic should be added to concatenated with ; semi colon symbol.
e)
Sellable Flag
For documents, Agile doesnt contain any field for sellable flag. In EBS, Sellable flag is mandatory. While doing the transformation from ABM to EBM, transformation logic should be added to set Sellable flag as Non-Sellable for documents whose Oracle Item Type value is For Reference. For parts, set Sellable flag to Non-Sellable if its Oracle Item Type value is For Reference. For other values in Oracle Item Type set Sellable flag as-is from Agile.
f)
Handling Comma for License Max
In Agile, item Attribute "License Max#" puts a comma automatically if the number of digits is four or more.
In EBS, License Max UDA defined as Number
While doing the transformation from ABM to EBM, transformation logic should be added to suppress comma in license max value.
g)
Change order UDA
While doing the transformation from ABM to EBM, transformation logic should be added to mapping for Change Order User Defined Attribute.
h) Filter AML information for items whose Oracle Item Type value is Phantom and As Required While doing the transformation from ABM to EBM, add transformation logic to not to send AML information to EBS for items whose Oracle Item Type value is Phantom and As Required.
i)
Process Analyst UDA
While doing the transformation from ABM to EBM, transformation logic should be added to mapping for Process Analyst User Defined Attribute.
PBT CD3 Customizations:
j)
MSI Relationship Part on Part:
This attribute is a list attribute in Agile PLM on Parts. The valid values for this attribute are as follows N/A (Default Value) Buy/Sell Motorola Relationship Pricing
k)
ECCN:
This attribute is present on the Parts Import Export heading and is of cascading list type.
The Source Organization attribute is the one which will segregate the part as WES or WRS. Its a list attribute and has the values as follows: Agile BMS Frozen MD Frozen
Networks Frozen PDM1 Shared Frozen
If the attribute value for the Source Organization is Agile then, its a WES part. If the attribute value for the Source Organization is not Agile then, its a WRS part.
Based on the part type (WES/WRS) the US EECN or EU ECCN attributes need to be populated. ECCN has been configured in Item Categories and here as part of transformation logic, we are removing the "|" from the Agile value and sending it to R12.
For Example : If the ECCN has the value "EAR99|.NR", then in PIP the "|" will be removed and the reansformed value EAR99.NR will be send to R12.
l)
Part Approval Status on AML:
This attribute is present on Parts Manufacturer Tab (AML) and is of type List. This attribute was part of CD1 implementation which has been postponed to CD3. Agile Trilogy valid values for this attribute are different from newly proposed PBT values.
Trilogy valid values are as follows: Approved Approved - See Comments Disqualified
Obsolete Rejected
PBT mentioned valid values are as follows: Proposed Qualified Waiver Only Not Required
NOTE: Please find the Agile to R12 mappings in the below mentioed Picture.
m)
Commodity Code:
As part of PIP, we have to change the attribute configuration from PageTwo to TitleBlock (remaining will be same) under Item Categories.This is the direct mapping between the attributes, there is no transformation logic involved.
n)
EU ECCN:
EU ECCN has been configured as Item Category Set in R12 and here as part of transformation logic, we are removing the "|" from the Agile value and sending it to R12.
For Example : If the EU ECCN has the value "EAR99|.NR", then in PIP the "|" will be removed and the reansformed value EAR99.NR will be send to R12.
o)
BOM Attributes:
For the sub class MODEL/Option Class, we have to add 4 additional attributes in BOM related attributes. They are as follows: 1) BOM. Optional: In PIP, the value for this attribute will be transformed. The value "Yes"will be transformed to "1" and the value "No" will be transformed to "2". 2) BOM. MutExcl: In PIP, the value for this attribute will be transformed. The value "Yes"will be transformed to "1" and the value "No" will be transformed to "2". 3) BOM. Minqty: Direct mapping. 4) BOM. Maxqty: Direct Mapping.
p) Part Tansfer : We have to check the condition whether the DetinationERP attribute has "Trilogy R12 or SAP" or not as a value. If yes, then that part will be transferred to R12.
q) Global BOM/ Non Global BOM: For this, we have to consider below mentioed scenarios. They are as follows:
1.)If the Destination ERP=Trilogy R12 or SAP and Global BOM=Yes, then all the BOM Components will be sending to R12. 2.) If the Destination ERP! =Trilogy R12 or SAP and Global BOM=Yes, BOM Components will not be sending to R12. then all the
3.)If the Destination ERP! =Trilogy R12 or SAP and Global BOM=No, then all the BOM Components will not be sending to R12. 4.)If the Destination ERP=Trilogy R12 or SAP and Global BOM=No, then we have to traverse all the BOM Components and check for ERP Org(BOM.LIST04).If ERP Org=R12 Trilogy then only that items BOM components will be transformed to R12.
9. The Web services update the transfer status of the change order in Agile PLM, which is a predefined P2 or P3 attribute on the change order object in Agile PLM .
11. In case of Validation Failed, update reason in message text of the change order in Agile PLM, which is a predefined P2 or P3 attribute on the change order object in Agile PLM .
12. Filter SAPLoad Template components.
13. In case of failure we will not be creating any BMC ticket and we will not call the Tivoli service and we will not send any notification.
Object Type : Requirement Status : Approved Release : R3.0 PBT CD3 PBT Go Live PPM RFCs : PPM60207 Object Identifier : TD505-PLM-785 Object Level : 4
<Picture : Agile to R12 Attributes mappings>
Object Type : Comment Status : Approved Release : PBT CD3 PPM RFCs :
6.24 ValidateEngineeringChangeOrderListEbizProvABCSImpl Object Type : Comment Status : Approved Release :
ValidateEngineeringChangeOrderListEbizProvABCSImpl
Reuse Object Type : Comment Status : Approved Release :
6.24.3 Functionality Object Type : Comment Status : Approved Release : PPM RFCs :
This service is implemented as an asynchronous BPEL process.
This is a single operation service. This accepts an ECO containing item and a BOM information message as a request and returns a response.
In the Agile PLM to Oracle E-Business Suite flow, ValidateEngineeringChangeOrderListEbizProvABCSImpl is used for transforming ValidateEngineeringChangeOrderListEBM into ValidateECOABM, which invokes the ValidateEngineeringChangeOrderList operation in Oracle E-Business Suite. In the return flow, the EBS adapter service sends ValidateECOResponseABM, which is transformed by ValidateEngineeringChangeOrderListEbizProvABCSImpl into ValidateEngineeringChangeOrderListResponseEBM.
During EBM to ABM transformation, following logic should be added for below mappings:
a.
Filter BOMTEXT components.
PIP shouldnt send items/components name starting with BOMTEXT to EBS(R12).
b. Filter SAPLoad Template components.
. In case of failure we will not be creating any BMC ticket and we will not call the Tivoli service and we will not send any notification.
c. In case of failure we will not be creating any BMC ticket and we will not call the Tivoli service and we will not send any notification.
PBT CD3 changes: As part of PBT CD3 "Manufacture Name" has been trimmed to 30 characters length before reaching to R12.
This service is implemented as an asynchronous BPEL Process.
Object Type : Requirement Status : Approved Release : R3.0 PBT CD3 PBT Go Live PPM RFCs : PPM60207 Object Identifier : TD505-PLM-771 Object Level : 3
6.24.4 Error Conditions and Handling Object Type : Comment Status : Approved Release : PPM RFCs :
6.25 ValidateManufacturerEbizProvABCS_Custom Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-1085 Object Level : 3
6.25.1 New/Reuse/Copy from Reuse Object Type : Comment Status : Approved
6.25.2 Layout N/A Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-1087 Object Level : 3
6.25.3 Functionality This custom process is used to check whether the manucaturer exists in R12 or not.
As part of PBT CD3 "Manufacture Name" has been trimmed to 30 characters length before reaching to R12. Object Type : Comment Status : Approved Release : PBT CD3 PPM RFCs : Object Identifier : TD505-PLM-1088 Object Level : 3
6.25.4 Error Conditions and Handling All errors in the integration flow are managed in RequestorABCS. Any such errors leading to failure of the queue processing will be handled in this process. Because of such error, the queue status and result with failure status is updated in the Queue DB.
6.26 ProcessManufacturerEbizProvABCS_Custom Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-1097 Object Level : 3
6.26.1 New/Reuse/copy from Reuse Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-1100
Object Level : 3
6.26.3 Funtionality This custom process is used to check whether the manucaturer exists in R12 or not. If it exists, it will update the manufacturer information in R12. If it doesn't exists, it will create the manufacturer in R12
6.26.4 Error Conditions and Handling All errors in the integration flow are managed in RequestorABCS. Any such errors leading to failure of the queue processing will be handled in this process. Because of such error, the queue status and result
6.27 UpdateItemAMLStatusEbizProvABCS_Custom Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-1103 Object Level : 3
6.27.1 New/Reuse/Copy from Reuse Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-1104 Object Level : 3
6.27.3 Functionality The manufacturer details we are creating or updating in R12 will be available in AML (Approved Manufacturer List) format in Agile PLM. Every manufacturer registered which goes to R12 need to have some approvals so that the parts from the manufacturer can be used in the BOM. To get the status of these approvals we created the process.
6.27.4 Error Conditions and Handling All errors in the integration flow are managed in RequestorABCS. Any such errors leading to failure of the queue processing will be handled in this process. Because of such error, the queue status and result
7 Appendix Object Type : Comment Status : Approved Release : R3.0 PPM RFCs : PPM55772 Object Identifier : TD505-PLM-777 Object Level : 2
7.1 DVM Details Object Type : Comment Status : Approved Release : PPM RFCs : Object Identifier : TD505-PLM-778 Object Level : 3
Below are the DVM's used for out of the box functionality
ECO_REASON_CODE.dvm ECO_TYPE_CODE ECO_STATUS_CODE.dvm ITEM_PRIMARYCLASSIFICATIONCODE.dvm ITEM_STATUS_CODE.dvm ITEM_UOM_CODE.dvm AGILE_INTEGRATION_USERS.dvm AGILE_SITE_TARGET_MAPPING.dvm AGILE_TARGET_SITE_MAPPING.dvm
Below are the DVM's used for Custom functionality
CUSTOM_AGILE_FLEX_ATTRIBUTE_NAME.dvm CUSTOM_AGILE_TEMPLATE_NAME.dvm CUSTOM_AML_STATUS.dvm CUSTOM_CATEGORY_SETS.dvm CUSTOM_CATEGORY_SETS_BATTERY_DIRECTIVE.dvm CUSTOM_CATEGORY_SETS_CMM.dvm CUSTOM_CATEGORY_SETS_EMC.dvm CUSTOM_CATEGORY_SETS_MATERIAL_GROUP_TYPES.dvm CUSTOM_CATEGORY_SETS_ROHS.dvm CUSTOM_CATEGORY_SETS_RTTE.dvm CUSTOM_CATEGORY_SETS_WEEE.dvm CUSTOM_DVM_NAME_LOOKUP.dvm
CUSTOM_EBIZUSER.dvm CUSTOM_UDA_APPLICATION_SHORT_NAME.dvm CUSTOM_UDA_ATTR_GROUP_SHORT_NAME.dvm CUSTOM_UDA_ATTR_GROUP_TYPE.dvm CUSTOM_UDA_ATTR_LICENSE_TYPE.dvm CUSTOM_UDA_ATTR_PRODUCT_CATEGORY.dvm CUSTOM_UDA_ATTR_SERVICE_ONLY.dvm CUSTOM_UDA_ATTR_SHORT_NAME.dvm CUSTOM_UDA_PROPERTIES.dvm CUSTOM_AML_FILTER_USER_ITEM_TYPE.dvm
7.2 Mapping Details Object Type : Comment Status : Approved Release : R3.0 PPM RFCs : PPM55772 Object Identifier : TD505-PLM-653
Object Level : 3
The following location stores the Mapping document for the Agile to Oracle EBS/PIM. http://compass.mot-solutions.com/go/405621617 Object Type : Comment Status : Approved Release : R3.0 PPM RFCs : PPM55772 Object Identifier : TD505-PLM-654 Object Level : 2
7.3 Monitoring with iMonit Object Type : Comment Status : Approved Release : R3.0 PPM RFCs : PPM55772 Object Identifier : TD505-PLM-655 Object Level : 3
The schedule run of the composite instances will be tracked & monitored in the EM console. Console details are updated at compass http://compass.mot-solutions.com/go/396906496
Monitoring with iMonit
Monitoring of this integration would be done through iMonit. The process model can be found at the following link.
http://il06linappl128.corp.mot.com:7777/pls/apex/f?p=104:18:2026724053257532::NO::P18_MODEL_ NAME:SP3423_ITM_514
http://il0linappl128.corp.mot.com:7777/pls/apex/f?p=104:18:2026724053257532::NO::P18_MODEL_N AME:SP3426_ITM_514
The milestones for all the interfaces integration are as follows.
1. N/A 2. In the PreProcessEBM user exit 3. N/A 4. In the PreProcessABM user exit 5. In the PostProcessABM user exit
At every milestone, this integration will send data to iMonit through the JMS Queue. In case of any error in the integration, iMonit needs to be invoked with the corresponding Ticket number. Details can be viewed in the document below.
iMonit - Publishing Mechanism document - JMS Queue - http://compass.motsolutions.com/doc/401454769/TD_iMonit_Publishing_Mechanism_-_JMS_Queue.
The iMonit input parameter structure (iMonit_Parameter_Structure.xlsx) and the unique Transaction ID implementation (Unique_Txn_ID_Implementation_For_Imonit.docx) for all the interfaces concerning Agile PIP are uploaded at the following compass location: http://compass.mot-solutions.com/go/418999833
On boarding document can be found at http://compass.mot-solutions.com/go/403410238 Object Type : Comment Status : Approved Release : R3.0 PPM RFCs : PPM55772

AGILE1 Docx

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AGILE1 Docx

Uploaded by

Copyright:

Available Formats

Object Identifier : TD505-PLM-1 Object Level : 1

Object Identifier : TD505-PLM-4 Object Level : 2

Release : PPM RFCs : Object Identifier : TD505-PLM-620 Object Level : 2

Update of Item attributes

CD3 PBT Customizations:

PBT Go Live Customizations:

Object Type : Comment Status : Approved Release : PPM RFCs :

Object Identifier : TD505-PLM-820 Object Level : 3

PBT CD3 Page2/List12(ECCN) ECCN(Item Category) CreateEngineeringChangeOrderListEbizProvABCSImpl ProcessEngineeringChangeOrderAgileReqABCSImpl ValidateEngineeringChangeOrderListAgileReqABCSImpl

BOM.Optional BOM.MutExcl BOM.Minqty BOM.Maxqty OPTIONAL

MUTUALLY_EXCLUSIVE_OPTIONS LOW_QUANTITY HIGH_QUANTITY CreateEngineeringChangeOrderListEbizProvABCSImpl

PBT Go Live Part Transfer-Destination ERP( PAGE_TWO.MULTILIST07) ProcessEngineeringChangeOrderAgileReqABCSImpl Not Required

t Object Identifier : TD505-PLM-790 Object Level : 3

<Picture : PBT GlobalBOM/Non Global BOM Transformation logic>

Object Type : Comment Status : Approved

D2R AIA NPI PIP ECO MCO

Object Identifier : TD505-PLM-22 Object Level : 2

Technical Design Peer Review Form

Data Mapping Guide

Design to Release Implementation Guide 3.1

The Data Flow Diagram for these are described as below.

Object Type : Comment Status : Approved

Release : PPM RFCs : Object Identifier : TD505-PLM-566 Object Level : 3

Item Creation and Maintenance

BOM creation and Maintenance ECO/MCO creation

These diagrams illustrate change order validation integration sequence:

Object Type : Comment Status : Approved Release :

PPM RFCs : Object Identifier : TD505-PLM-39 Object Level : 2

Object Type : Comment Status : Approved Release : PPM RFCs : PPM60207

Object Identifier : TD505-PLM-569 Object Level : 3

The following is the Sequence Diagram for Agile to Oracle EBS/PIM

4.3.6 AML Approval Status update Sequence Diagram

Object Type : Comment

5 Preliminary Design - Design Components Master List

DR504-PLM-131 DR504-PLM-133 DR504-PLM-136 DR504-PLM-189 DR504-PLM-190

In the return flow, ValidateEngineeringChangeOrderListAgileReqABCSImpl recieves ValidateEngineeringChangeOrderListResponseEBM as input from EngineeringChangeOrderResponseEBS

ValidateEngineeringChangeOrderListAgileReqABCSImpl transforms ValidateEngineeringChangeOrderListResponseEBM to AgileValidateEngineeringChangeOrderListResponseABM.

ValidateEngineeringChangeOrderListAgileReqABCSImpl transforms ValidateEngineeringChangeOrderListResponseEBM to UpdateEngineeringChangeOrderListEBM.

ValidateEngineeringChangeOrderListAgileReqABCSImpl transforms UpdateEngineeringChangeOrderListEBM to AgileUpdateEngineeringChangeOrderListABM

This custom process is

Object Identifier : TD505-PLM-209 Object Level : 3

Object Identifier : TD505-PLM-581 Object Level : 3

Object Type : Requirement Status : Approved

6.4.1 New/Reuse/Copy from Object Type : Comment Status : Approved Release :

PPM RFCs : Object Identifier : TD505-PLM-216 Object Level : 4

N/A Object Type : Comment Status : Approved Release : PPM RFCs :

Object Identifier : TD505-PLM-218 Object Level : 3

Oracle Item Type

Handling Comma for License Max

In EBS, License Max UDA defined as Number

Change order UDA

Process Analyst UDA

PBT CD3 Customizations:

MSI Relationship Part on Part:

Parts. The valid values

Part Approval Status on AML:

PBT Go Live Customizations:

<Picture : Agile To R12 Attribute Mappings>_

with failure status is updated in the Queue DB.

6.5.1 New/Reuse/Copy from

N/A Object Type : Comment

Object Type : Requirement

6.6 CreateEngineeringChangeOrderListEbizProvABCSImpl Object Type : Comment