| Oracle® Application Integration Architecture Agile Product Lifecycle Management Integration Pack for Oracle E-Business Suite: Design to Release Implementation Guide Release 11.3 E40004-02 |
|
|
PDF · Mobi · ePub |
| Oracle® Application Integration Architecture Agile Product Lifecycle Management Integration Pack for Oracle E-Business Suite: Design to Release Implementation Guide Release 11.3 E40004-02 |
|
|
PDF · Mobi · ePub |
This chapter provides an overview of the process integration for change order update and discusses solution assumptions and constraints, interfaces, core Oracle Application Integration Architecture (Oracle AIA) components, and integration services.
This chapter includes the following sections:
The change order update process flow is triggered by Oracle E-Business Suite. Change order information needs to flow from the Oracle E-Business Suite system to Agile PLM in the following cases:
Change order is completely implemented in Oracle E-Business Suite.
This step can be configured to trigger a change order status change in Agile PLM and a change order Page Two or Page Three field update in Agile PLM. Because a change order can be created in multiple organizations in Oracle E-Business Suite and the change order can have different statuses in each organization, this operation is carried out only when the change order is completely implemented in all the organizations for which it has been created in Oracle E-Business Suite.
Change order line status or effectivity date changes in Oracle E-Business Suite.
In either case, the effectivity date of the change order line in Oracle E-Business is reflected on the corresponding line in Agile PLM. This update can be carried out only if the change order is created in only one organization in Oracle E-Business, or if a one-to-one correspondence between the Oracle E-Business organizations and Agile PLM sites for posting change order data exists.
Change status for a change object in Oracle E-Business Suite.This includes a success or failure status of a new part number generation or of a change order validation.
Note:
Some of these cases have restrictions in a multi-org environment because of the centralized (Agile PLM) to decentralized (Oracle E-Business Suite) nature of the interface.
Four types of events can cause a change:
An update to the implementation status of a change order line.
While the implementation status in Oracle E-Business Suite is tracked at a Bills of Material (BOM) line level, this is tracked at a change order line level in Agile PLM.
A modification of the scheduled effectivity date of a change order line.
While the effectivity dates in Oracle E-Business Suite are tracked at a BOM line level, these are tracked at a change order line level in Agile PLM.
An update to the status of a new part request of a change order line.
An update to the status of a change order validation.
Note:
The cancellation or purge of a change order in Oracle E-Business Suite is not interfaced back to Agile PLM as part of this integration. These events should be handled manually in both applications.
The change order update process includes:
The effectivity date and item status is modified in the BOM line item in Oracle E-Business Suite.
The batch process for publishing the changed information initiates at a specified frequency (configurable).
While the update to information in Agile PLM is driven through the scheduled batch processes, it is also possible to trigger the information update event from Oracle E-Business Suite through the Integrations Administrator and running the Publish Engineering Change Order Updates function.
The change number and specified item record is queried for modification.
The effectivity date is modified in the mapped column in Agile PLM.
The change status is updated in the mapped attribute in Agile PLM.
If the complete update is processed successfully, the integration updates the date and time of the last successful run.
The following parameters are used by the change order update process in Agile PLM:
Change order number, which will uniquely identify the change object.
In case of modification to the effective dates, the item number that will uniquely identify the change order line (affected items) and the effective date as of which the change line is scheduled to be implemented.
Field to be updated with the transfer or implementation status of the change in Oracle E-Business Suite.
When a change order is first transferred to Oracle E-Business Suite, the change order status in Oracle E-Business Suite is open or scheduled. All the possible statuses for a change order in Oracle E-Business Suite are:
Open
Hold
Scheduled
Rescheduled
Implemented
Canceled
Agile PLM's Transfer Status attribute (such as Transferred, Implemented, and Canceled).
Status to be promoted or demoted in case of the change status for a new part generation or a change or validation.
The process includes the following steps:
The change order number and the specific affected item attributes are queried for modification.
Agile PLM's change order line is updated.
This can be done in a batch mode through a scheduled process. This means that the effectivity information is read for a group of change lines in Oracle E-Business Suite and sent through the interface. This process may also be triggered by the event of a change line being implemented in Oracle E-Business Suite.
The update step can process all the change order lines in the batch before committing, or it can commit each change order line individually before moving on to the next one. This decision should be taken from a technical efficiency perspective.
When processing a batch of change order lines, if the update for one record ends due to error, the process continues to process the other records in the batch. A list of all errors that occur when the batch is being processed is accumulated and logged.
Note:
The effectivity date for the affected items is not updated if the multisite is enabled but the sites are not assigned to that particular affected item.
In case of effective date changes, the new effectivity date for the change order line is updated on the mapped column in Agile PLM.
The mapped effectivity date column in Agile PLM is updated with the incoming effectivity date only if the incoming status is implemented.
The configured column in Agile PLM is updated with a configured value based on the incoming status. The following examples illustrate a sample of these rules:
If the change order status in Oracle E-Business Suite is Scheduled, update the Affected Items.Status (an Affected Items tab list-validated flex-field) in Agile PLM with the value Not Implemented.
If the change order status in Oracle E-Business Suite is Implemented, update the Affected Items.Status field in Agile PLM with the value of Implemented, and update the Affected Items.ERP Implementation Date (an Affected Items tab date flex-field) with the effective date from Oracle E-Business Suite.
Agile PLM's Transfer Status attribute is updated.
After a successful transfer, the change order update process updates the Agile PLM's Transfer Status attribute (change order Agile PLM P2 or P3 defined attribute value for the Change.TransferStatusAttribute property) with a value of Transferred.
In case of multiple organizations, Agile PLM contains only a single instance of the change order and not site-specific ones but Oracle E-Business can contain multiple organizations. So in case of multiple organizations within Oracle E-business Suite:
The Transfer Status attribute (change order Agile PLM P2 or P3 defined attribute value for the Change.TransferStatusAttribute property) in Agile PLM reflects the status of Transferred until the change order is completely implemented in all the Oracle E-Business organizations. After all the Oracle E-Business Suite organizations are implemented, Agile PLM's transfer status will be updated with a status of Implemented.
f the change order errors when implemented in one or more Oracle E-Business Suite organizations and is waiting for implementation in other organizations or has been implemented successfully in some of the organizations, Agile PLM's transfer status value will remain as Transferred.
If the change order errors when implemented in all the Oracle E-Business organizations, Agile PLM's transfer status value will be changed to Errored.
If the change order has been canceled in all the Oracle E-Business organizations, Agile PLM's transfer status will be changed to Canceled.
Because the change status name depends on the workflow being used, the CHANGE_STATUS configuration table is provided as part of the integration setup. This table allows the administrators to specify the next status for each possible combination of the change object type and the workflow being used for each event that qualifies for the Change Status operation. The administrators can add as many rows as they require, because the number of sub-classes of the change objects and the number of workflows is unlimited in Agile PLM. Table 8-1 illustrates a partially configured table:
Table 8-1 Partially Configured Change Status and Workflow Table
|
EVENT |
OUTCOME |
SUBCLASS |
WORKFLOW |
NEXT_STAUS |
|
Change Implemented |
SUCCESS |
ECO |
Default Change Orders |
Implemented |
The EVENT column key is Change Implemented.
The OUTCOME column key is SUCCESS.
In the SUBCLASS column, set up the change order subclass as ECO, MCO, etc.
In the WORKFLOW column, set up the workflows. For example, if you are using Default Change Order workflow for ECO, then enter Default Change Order in this column. These values can be picked up from Agile PLM Java client.
In the NEXT_STATUS column, enter the status of the workflow you want it to move to when the conditions are met. For example, when a Change is implemented (identified by event - this is a key. do not change it) and the OUTCOME is SUCCESS (identified by outcome, gets checked while changing status here), and the WORKFLOW chosen is Default Change Orders, the set up requesting the Change to be moved to the Implemented status (NEXT_STATUS).
In a new installation, this table will be empty. The integration administrator must add rows in this table if the change status process needs to be supported for any of the given processes.
The value of the EVENT column must be limited to the values corresponding to the processes supported: New Part Request, Pre-release Audit, and Change Implementation. The change implementation process can also be associated with a status update back to a flexfield on the change order.
The value of the OUTCOME column must be limited to Success and Failure.
The value of the SUBCLASS column must be limited to the set of subclasses of the Change Requests Class, Change Orders Class, Manufacturing Orders Class, and Site Change Orders Class.
The value of the WORKFLOW column must be limited to the set of workflows for the selected subclass. For example, if you are using the default change order workflow for ECO, then enter the default change order in this column. These values can be picked up from the Agile PLM Java client.
In the NEXT_STATUS column, enter the status of the workflow that you want to move to when the conditions are met. For example, when a change is implemented (identified by event; this is a key, so do not change it) and the OUTCOME is SUCCESS (identified by outcome; this is checked while changing status here) and the WORKFLOW chosen is Default Change Orders, the setup requesting the change to be moved to the implemented status (NEXT_STATUS).
Release an ECO, C0001, from Agile PLM to Oracle E-Business Suite.
In Oracle E-Business Suite, create this ECO in three organizations: Org1, Org2, and Org3.
Change the status of this ECO in Org1 as implemented.
Oracle E-Business Suite triggers an event to send the ECO list to Agile PLM.
This list has C0001 in Org1, C0001 in Org2, and C0001 in Org3. Only C0001 of Org1 carries the complete data, including the affected items data, while C0001 in the other organizations carries only the header information.
When Agile PLM receives the ECO list, the ECO data is updated and the workflow status of ECO is changed.
The change of workflow status is based on the following rules:
When the status of ECO is implemented in all organizations in Oracle E-Business Suite, move the ECO in Agile PLM to the implemented status.
The Transfer Status field in Agile PLM is updated only when the status of ECO is the same in all the Oracle E-Business Suite organizations.
Hence, if the status is implemented across all the C0001 ECOs in all organizations, the transfer status field on ECO in Agile PLM is updated as implemented.
If an entry in the CHANGE_STATUS table corresponding to the event Change Implemented and SubClass ECO exists, and the workflow is mentioned on ECO C0001 in Agile PLM, read the next status and send it to the next status mentioned.
If no entry is in the CHANGE_STATUS table for the data, no ECO C0001 is sent to the next status.
Figure 8-1 illustrates the integration sequence for the change order update from Oracle E-Business Suite to Agile PLM:
The following exception conditions create error messages for this integration process:
Insufficient privilege to discover, read, or update attributes on the Change object
Invalid field value (indicate the field for which the value is incorrect, and the value that is being passed on to the field)
Change object does not exist
Change line does not exist
Invalid status name
Missing exit or entry required fields
Figure 8-2 illustrates the integration services orchestration of Oracle E-Business Suite for change order update:
Table 8-2 lists the activities involved in the change order update integration services orchestration:
Table 8-2 Activities in Change Order Update integration Orchestration
| Step | Activity | Remarks |
|---|---|---|
|
1 |
The Publish Engineering Change Order Updates concurrent program in Oracle E-Business Suite invokes the UpdateEngineeringChangeOrderListEbizReqABCS. |
When user triggers the CP, the UpdateEngineeringChangeOrderListEbizReqABCS proxy service gets invoked. |
|
2 |
UpdateEngineeringChangeOrderListEbizReqABCS proxy service invokes the UpdateEngineeringChangeOrderListEbizReqABCSImpl. |
An invoke activity in UpdateEngineeringChangeOrderListEbizReqABCS invokes the UpdateEngineeringChangeOrder operation on UpdateEngineeringChangeOrderListEbizReqABCSImpl. It also sends the response back to the CP. If the invokation is successful, the Response status is sent as 'S' with message:- "Synchronization In Progress, please check the BPEL instance id" and the CP is completed. Otherwise, the Response status is sent as 'E' with message:- "Synchronization failed, please check the BPEL instance id" and the CP errors out. |
|
3. |
Invoke UpdateEngineeringChangeOrderListEbizReqABCSImpl process. |
When change order lines are auto-implemented after reaching effectivity dates, UpdateEngineeringChangeOrderListEbizReqABCSImpl is triggered which then triggers UpdateEngineeringChangeOrderListEbizReqABCSImpl process. UpdateEngineeringChangeOrderListEbizReqABCSImpl transforms UpdateEngineeringChangeOrderListABM into UpdateEngineeringChangeOrderListEBM. |
|
4. |
UpdateEngineeringChangeOrderListEbizReqABCSImpl invokes the UpdateEngineeringChangeOrderListAgileProvABCSImpl with the UpdateEngineeringChangeOrderList operation. |
An invoke activity in UpdateEngineeringChangeOrderListEbizReqABCSImpl invokes the UpdateEngineeringChangeOrderList operation on UpdateEngineeringChangeOrderListAgileProvABCSImpl with UpdateEngineeringChangeOrderListEBM as the input. |
|
5 |
UpdateEngineeringChangeOrderListAgileProvABCSImpl does the transformation. |
UpdateEngineeringChangeOrderListAgileProvABCSImpl transforms UpdateEngineeringChangeOrderListEBM into AgileUpdateEngineeringChangeOrderListABM. |
|
6 |
UpdateEngineeringChangeOrderListAgileProvABCSImpl invokes Agile PLM Web Services. |
Agile PLM Web services are invoked with AgileUpdateEngineeringChangeOrderListABM as input. Note: The UpdateEngineeringChangeOrderListAgileProvABCSImpl composite uses the oracle/wss_http_token_client_policy client security policy while calling ChangeABS and MergeABS services hosted on the Agile server. The security credentials for this are stored in the csf-key AgileWebServicesKey on Fusion Middleware (FMW). The Agile username and password need to be setup correctly so that the Agile service is invoked successfully from the AIA composite in the FMW layer. The effectivity dates and implementation status of change order are updated in Agile PLM. A check determines whether all affected item rows are moved into implemented status. The change order status will be moved to Implemented when all affected items are implemented. AgileUpdateEngineeringChangeOrderListResponseABM is sent to UpdateEngineeringCUpdateEngineeringChangeOrderListAgileProvABCSImpl. |
The process integration for change order update flow includes a list of services and three transaction boundaries. This flow includes the following services:
UpdateEngineeringChangeOrderListEbizReqABCS
UpdateEngineeringChangeOrderListEbizReqABCSImpl
QueryEngineeringChangeOrderListEbizAdapter
UpdateEngineeringChangeOrderListAgileProvABCSImpl
ChangeStatusDBAdapter
The following table describes the transactions, database operations involved and solutions in case of any errors.
Table 8-3 Transaction Boundaries and Recovery details
| S.No | Transaction | DB Operations | In Case of Error | Recovery |
|---|---|---|---|---|
|
1 |
When change order lines are auto-implemented after reaching effectivity dates, UpdateEngineeringChangeOrderListEbizReqABCS is triggered. UpdateEngineeringChangeOrderListEbizReqABCS invokes UpdateEngineeringChangeOrderListEbizReqABCSImpl |
None |
Publish Engineering Change order from Ebiz |
|
|
2 |
UpdateEngineeringChangeOrderListEbizReqABCSImpl transforms UpdateEngineeringChangeOrderListABM into UpdateEngineeringChangeOrderListEBM. UpdateEngineeringChangeOrderListEbizReqABCSImpl invokes QueryEngineeringChangeOrderListEbizAdapter to makes an OA Adapter call out that calls the PL/SQL API UpdateEngineeringChangeOrderListEbizReqABCSImpl invokes UpdateEngineeringChangeOrderListAgileProvABCSImpl with UpdateEngineeringChangeOrderListEBM as input. |
None |
Publish Engineering Change order from Ebiz |
|
|
2 |
UpdateEngineeringChangeOrderListAgileProvABCSImpl transforms UpdateEngineeringChangeOrderListEBM into AgileUpdateEngineeringChangeOrderListABM and invokes Agile PLM Web Services. Agile PLM Web services are invoked with AgileUpdateEngineeringChangeOrderListABM as input. AgileUpdateEngineeringChangeOrderListResponseABM is sent back to UpdateEngineeringChangeOrderListAgileProvABCSImpl which is transformed to UpdateEngineeringChangeOrderListResponseEBM and invokes UpdateEngineeringChangeOrderListEbizReqABCSImpl with UpdateEngineeringChangeOrderListResponseEBM as input. UpdateEngineeringChangeOrderListEbizReqABCSImpl also updates status by invoking ChangeStatusDBAdapter service. |
|||
|
3 |
UpdateEngineeringChangeOrderListEbizReqABCSImpl after receiving the UpdateEngineeringChangeOrderListResponseEBM and performs PostProcessEBM and update Ebiz with Success status |
None |
Publish Engineering Change order from Ebiz |
For more information about rollback procedures, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Configuring Oracle AIA Processes for Error Handling and Trace Logging", "Configuring Fault Policies to Not Issue Rollback Messages".
This release of the integration intends to solve a use case in which any given change interfaces to only one destination.
The assumption is that the log information pertaining to the complete end-to-end process of transferring a change object from Agile PLM to Oracle E-Business Suite is available as a file to this operation.
Verifications for the setup validations of the sub-class, workflow, and status values not part of the scope.
The change object should already have an assigned workflow.
Table 8-4 lists the Agile PLM Web Services Definition Language (WSDL) files:
Table 8-4 Agile PLM Web Services Definition Language (WSDL) files
| Interface | Description |
|---|---|
|
UpdateEngineeringChangeOrderListAgileProvABCSImpl |
|
|
ChangeABS.wsdl ChangeMerge.wsdl |
Used to update change order information in Agile PLM. |
Table 8-5 lists the Agile PLM XML Schema Definition (XSD) files:
Table 8-6 lists the Oracle E-Business Suite WSDL files:
Table 8-6 Oracle E-Business Suite WSDL files
| Interface | Description |
|---|---|
|
UpdateEngineeringChangeOrderListEbizReqABCSImpl |
|
|
QueryEngineeringChangeOrderListEbizAdapter.wsdl |
Used for the OA adapter "INV_EBI_CHANGE_ORDER_PUB.GET_ECO_LIST_ATTR" pl/sql function call |
|
UpdateEngineeringChangeOrderListEbizReqABCS |
This is a synchronous proxy service which will be invoked by the Ebiz Concurrent Program and will in turn invoke the asynchronous UpdateEngineeringChangeOrderListEbizReqABCSImp service. |
Table 8-7 lists the Oracle E-Business Suite XSD files:
Table 8-7 Oracle E-Business Suite XSD files
| Interface | Description |
|---|---|
|
UpdateEngineeringChangeOrderListEbizReqABCSImpl |
|
|
EngineeringChangeOrderABM.xsd |
ABM for EngineeringChangeOrderABO |
|
UpdateEngineeringChangeOrderListEbizReqABCS |
This is a synchronous proxy service which will be invoked by the Ebiz Concurrent Program and will in turn invoke the asynchronous UpdateEngineeringChangeOrderListEbizReqABCSImpl service. |
|
EngineeringChangeOrderABO.xsd |
Created based on the input from the Concurrent Program to BPEL process and output to the Concurrent Program from BPEL process |
|
APPS_INV_EBI_CHANGE_ORDER_PUB_GET_ECO_LIST_ATTR.xsd |
Used for input/output ABM of INV_EBI_CHANGE_ORDER_PUB.GET_ECO_LIST_ATTR API call |
Table 8-8 lists the core AIA components for this process integration:
| Component | Name |
|---|---|
|
EBOs |
EngineeringChangeOrderEBO |
|
EBMs |
UpdateEngineeringChangeOrderListEBM UpdateEngineeringChangeOrderLisResponeEBM |
Table 8-9 lists the core components locations:
Table 8-9 Core components Locations
| Component | Location |
|---|---|
|
EBO and EBM XSD files |
$AIA_HOME/AIAMetaData/AIAComponents/EnterpriseObjectLibrary/Core/EBO/ $AIA_HOME/AIAMetaData/AIAComponents/ ApplicationObjectLibrary /Ebiz/Release1/Core |
|
WSDL files |
$AIA_HOME/AIAMetaData/AIAComponents/ EnterpriseBusinessServiceLibrary/Core/EBO/ $AIA_HOME/AIAMetaData/AIAComponents/ ExtensionServiceLibrary/Ebiz $AIA_HOME/AIAMetaData/AIAComponents/ApplicationConnectorServiceLibrary/Ebiz/V1 |
For detailed documentation of individual EBOs and EBMs, click the AIA Reference Doc link on EBO and EBM detail pages in Oracle Enterprise Repository.
EBOs can be extended, for instance, to add new data elements. These extensions are protected and will remain integral after a patch or an upgrade.
For more information, see Oracle Fusion Middleware Concepts and Technologies Guide for Oracle Application Integration Architecture Foundation Pack 11g Release 1, "Understanding Extensibility."
Table 8-10 lists the Oracle E-Business Suite and Agile PLM components for change order update:
Table 8-10 Oracle E-Business Suite and Agile PLM components for change order update
| Services | Oracle E-Business Suite (Requester) | Agile PLM (Provider) |
|---|---|---|
|
ABMs |
UpdateEngineeringChangeOrderListABM |
AgileUpdateEngineeringChangeOrderListABM AgileUpdateEngineeringChangeOrderListResponseABM |
|
ABCS |
UpdateEngineeringChangeOrderListEbizReqABCSImpl UpdateEngineeringChangeOrderListEbizReqABCS |
UpdateEngineeringChangeOrderListAgileProvABCSImpl |
Table 8-11 lists the core components locations:
Table 8-11 Core components locations
| Component | Location |
|---|---|
|
Application Business Objects, ABM and Common XSD files |
$AIA_HOME/AIAMetaData/AIAComponents/ ApplicationObjectLibrary/Agile PLM/V1/schemas $AIA_HOME/AIAMetaData/AIAComponents/ ApplicationObjectLibrary/Ebiz/V1/schemas $AIA_HOME/AIAMetaData/AIAComponents/ ApplicationObjectLibrary /Ebiz/Release1/Core |
|
WSDL files |
$AIA_HOME/AIAMetaData/AIAComponents/ ApplicationObjectLibrary/Agile PLM/V1/wsdls $AIA_HOME/AIAMetaData/AIAComponents/ ApplicationObjectLibrary/Ebiz/wsdls $AIA_HOME/AIAMetaData/AIAComponents/ ExtensionServiceLibrary/Ebiz $AIA_HOME/AIAMetaData/AIAComponents/ApplicationConnectorServiceLibrary/Ebiz/V1 |
The integration services for the change order update are:
UpdateEngineeringChangeOrderListEbizReqABCS
UpdateEngineeringChangeOrderListEbizReqABCSImpl
UpdateEngineeringChangeOrderListAgileProvABCSImpl
This is a synchronous proxy service which will be invoked by the Ebiz Concurrent Program and will in turn invoke the asynchronous UpdateEngineeringChangeOrderListEbizReqABCSImpl service.
An invoke activity in UpdateEngineeringChangeOrderListEbizReqABCS invokes the UpdateEngineeringChangeOrder operation on UpdateEngineeringChangeOrderListEbizReqABCSImpl. It also sends the response back to the CP. If the invokation is successful, the Response status is sent as 'S' with message:- "Synchronization In Progress, please check the BPEL instance id" and the CP is completed. Otherwise, the Response status is sent as 'E' with message:- "Synchronization failed, please check the BPEL instance id" and the CP errors out.
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 cross-reference tables in the FMW layer.
This provides a list of change orders that were actually from the Agile PLM System alone. The original 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 tans formation converts UpdateEngineeringChangeOrderListABM to UpdateEngineeringChangeOrderListEBM.
An asynchronous request-delayed response call is made to UpdateEngineeringChangeOrderListAgileProvABCSImpl 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).
The concurrent program logs the status of this call.
UpdateEngineeringChangeOrderListAgileProvABCSImpl updates a change order transfer status and attributes in Agile PLM.
This service is implemented as an asynchronous process.
UpdateEngineeringChangeOrderListAgileProvABCSImpl is invoked by UpdateEngineeringChangeOrderListAgileProvABCSImpl 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:
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).
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.
|
 Copyright © 2001, 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
