Oracle® Application Integration Architecture Oracle Product Master Data Management Integration Implementation Guide Release 11.2 Part Number E50309-01 |
|
|
PDF · Mobi · ePub |
This chapter provides an overview and discusses the process flow from OPH to Oracle E-Business Suite, as well as solution assumptions and constraints.
This chapter includes the following sections:
Section 4.2, "Synchronizing Items and BOMs from Oracle Product Hub to Oracle E-Business Suite"
Section 4.5, "Assumptions and Constraints for the Oracle E-Business Suite Option"
Oracle E-Business Suite is available as an installation option in the Oracle Product MDM integration.
The flows available in the Product MDM integration when you choose Oracle E-Business Suite as a participating application are described in Chapter 2, "Oracle Product Master Data Management Integration Base Pack".
For more information about Oracle E-Business Suite web services and documentation prior to Release 12.1.3, see the library on Oracle Technology Network: http://www.oracle.com/technetwork/documentation/applications-167706.html?
. For Oracle E-Business Suite documentation for R12.1.3 and beyond, see this library: http://download.oracle.com/docs/cd/E18727_01/index.htm
Oracle Product Hub supports seeded operational attributes that control the behavior of the item in various functional Oracle E-Business Suite modules such as Order Management and Procurement. The operational attributes are part of the definition of the item and are intended for consumption by Oracle E-Business Suite.
For more information about seeded operational attributes, see Oracle Product Hub, Oracle Inventory User's Guide.
Synchronization of items and BOMs from Oracle Product Hub to Oracle E-Business Suite is one-way and is triggered on demand by the publish mechanism of the Oracle Product Hub. The synchronization reduces the manual effort involved in maintaining a common set of products and facilitates transactional processes.
For create and update operations, routing rules need to be set up to identify the application services to invoke for the target systems. This setting should take precedence over any configuration settings defined earlier.
The synchronization enables having the item definition standardized between the standalone Oracle Product Hub and Oracle E-Business Suite that model inventory organizations and support supply chain and fulfillment processes.
Publication of an item associated with a BOM synchronizes all components for that item and BOM. The message routing rules use domain value maps that enable you to define the alternate structures that are of use to Siebel CRM. For an item, if a revision other than A or the first revision is published, Oracle E-Business Suite automatically creates revision A for that item.
The synchronization of an item also synchronizes the associated primary bill of material. This allows a single event for both the item and the related root BOM or primary BOM, but whether Oracle E-Business Suite uses this BOM is managed by configuration settings.
Primary item structure synchronization to Oracle E-Business Suite always has the effective date equal to the system date at the time of creation.
BOM synchronization involves two discrete services, namely, synchronization of component items and synchronization of structures to maximize performance and allow appropriate routing. Oracle E-Business Suite supports creating only future-dated BOM components.
For more information about the functional and technical details of this flow, see the Section 2.2, "Synchronization of Items and BOMs".
These are the interfaces specific to Oracle E-Business Suite:
Item Synchronization: Inbound to EBS Web Services
Service name: SyncItemListEbizAdapter
Operation name: SyncItemListEbizAdapter
Request and response: args_in_msg, args_out_msg
Item Synchronization: Outbound from EBS Event Interfaces
There are no outbound services.
BOM Synchronization: Inbound to EBS Web Services
Service name: SyncBillOfMaterialsListEbizAdapter
Operation name: SyncBillOfMaterialsListEbizAdapter
Request and response: args_in_msg, args_out_msg
BOM Synchronization: Outbound from EBS Event Interfaces
There are no outbound services.
For more information about Oracle E-Business Suite web services and documentation prior to Release 12.1.3, see the library on Oracle Technology Network: http://www.oracle.com/technetwork/documentation/applications-167706.html?
. For Oracle E-Business Suite documentation for R12.1.3 and beyond, see this library: http://download.oracle.com/docs/cd/E18727_01/index.htm?
These are the integration services required for Oracle E-Business Suite to integrate with Oracle Product Hub:
Note:
Oracle E-Business Suite integration services can perform insert and update operations from Oracle Product Hub (OPH) to Oracle E-Business Suite.
SyncItemListEbizProvABCSImpl
SyncBillOfMaterialsListEbizProvABCSImpl
SyncItemListEbizAdapter
SyncBillOfMaterialsListEbizAdapter
TransformAppContextEbizService
QueryResponsibilityEbizAdapter
This single operation service accepts a SyncItemListEBM product message as a request. This service transforms the SyncItemListEBM product message into an Oracle E-Business Suite application business message (ABM) format and runs Oracle E-Business Suite application programming interface (API) INV_EBI_ITEM_PUB. The PROCESS_ITEM_LIST through Oracle applications adapter synchronizes the item list in the Oracle E-Business Suite System.
SyncItemListPIMReqABCSImpl invokes the service SyncItemListEbizProvABCSImpl through ItemEBSV2. The response is sent back to SyncItemListPIMReqABCSImpl through ItemResponseEBSV2 with the status after the synchronization, or in case of failure.
This single operation service accepts SyncBillOfMaterialsListEBM message as a request and returns a SyncBillOfMaterialsListResponseEBM as a response. This service follows all the standards of a provider ABCS.
SyncItemListPIMReqABCSImpl invokes SyncBillOfMaterialsListEbizProvABCSImpl through BillOfMaterialEBS. The response is sent back to SyncItemListPIMReqABCSImpl with the status in case of success or failure through BillOfMaterialsResponseEBS.
The SyncBillOfMaterialsListEbizProvABCSImpl service transforms the SyncBillOfMaterialsListEBM to SyncBillOfMaterialsListAdapter ABM. The SyncBillOfMaterialsListAdapter calls Oracle API BOM_BPEL_SYNCBILLOFMATERIALSLI.BOM_BO_PUB$PROCESS_BOM through the Oracle applications adapter for synchronizing the BOM.
This Oracle applications adapter service invokes the Oracle E-Business Suite API INV_EBI_ITEM_PUB.PROCESS_ITEM_LIST.
This is an Oracle applications adapter service that invokes the Oracle E-Business Suite API, BOM_BPEL_SYNCBILLOFMATERIALSLI.BOM_BO_PUB$PROCESS_BOM.
This two-operation service is a BPEL service, which invokes another database adapter service QueryResponsibilityEbizAdapter that sets the AppsContext based on the integration user.
The user, responsibility, and the default operating-unit are picked from the AIAConfigurationProperties.xml file. The default user is OPERATIONS; default Responsibility is Order Management Super User, Vision Operations (USA); and default Operating Unit is 204.
The assumptions and constraints for the Oracle E-Business Suite option are:
In case of the participating application being Oracle E-Business Suite and the items being associated with multiple inventory organizations, the item associated with the primary organization as defined in Oracle E-Business Suite must be synchronized prior to synchronization of items associated with any other organization.
In case of the participating application being Oracle E-Business Suite, the assumption is that the primary BOM associated with the BOM must be synchronized prior to invoking synchronization of alternate BOMs to Oracle E-Business Suite.
Oracle Product Hub must be deployed as an instance that is separate from Oracle E-Business Suite.
Synchronization of user-defined attributes (UDAs) to descriptive flexible fields in Oracle E-Business Suite is not supported as part of this release; therefore, a solution is delivered that does not map UDAs for Oracle E-Business Suite provider service.
For Oracle E-Business Suite, account IDs used for the integration remain synchronized for OPH and Oracle E-Business Suite. The locator code and subinventory need to be manually set up in Oracle E-Business Suite.
Item messages from Oracle Product Hub may come from multiple organizations that have been set up in Oracle Product Hub; therefore:
For any Oracle Product Hub organization that invokes the item synchronization, a corresponding organization (inventory organization) and operating unit must be pre-established in Oracle E-Business Suite to provide a destination organization for the message.
Oracle Product Hub published message must include the organization ID (inventory organization ID) and the operating unit associated with the organization ID that needs to consume the message.
Cross-referencing is required even when organizations and items are identical between Oracle Product Hub and Oracle E-Business Suite.
For more information about Oracle E-Business Suite web services and documentation prior to Release 12.1.3, see the library on Oracle Technology Network: http://www.oracle.com/technetwork/documentation/applications-167706.html?
. For Oracle E-Business Suite documentation for R12.1.3 and beyond, see this library: http://download.oracle.com/docs/cd/E18727_01/index.htm?