Skip Headers
Oracle® Application Integration Architecture Siebel CRM Integration Pack for Oracle Order Management: Order to Cash Implementation Guide
Release 3.1.1

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

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

4 Process Integration for Product Management

This chapter provides an overview of the process integration for Product Management and discusses Item and Bill of Material (BoM) synchronization, Siebel Customer Relationship Management (Siebel CRM) and Oracle E-Business Suite (Oracle EBS) interfaces, core Oracle Application Integration Architecture (Oracle AIA) components, and integration services.

This chapter includes the following sections:

4.1 Process Integration for Product Management

The process integration for product management supports the following integration flows:

For more information about initial data loads, see Chapter 2, "Loading Initial Data."

4.1.2 Solution Assumptions and Constraints

The integration design assumes that the following statements are true:

  1. After items and BoMs are synchronized to Siebel CRM, any modifications made to the products or BoMs in Siebel CRM are not synchronized back to Oracle EBS.

  2. The initial load must use Oracle Data Integrator (ODI).

  3. The following assumptions pertain to the synchronization of BoM structures:

    • All of the BoM product (parent) and BoM components (children) are available in Siebel CRM before creation of the relationship by the BoM synchronization process.

    • Nonorderable items that are part of the product BoM structure are synchronized as part of the BoM synchronization process.

    • Although the relationships between the parent and children are synchronized, the characteristics of the child components, such as Optional, Mandatory and SubAssembly, are not synchronized or maintained in Siebel CRM.

  4. There are no mechanism is available to identify which products have a sales BoM structure in Oracle EBS.

    The Siebel product administrator must be made aware of which BoMs that exist in Oracle EBS can be requested for synchronization to Siebel CRM.

  5. Table 4-1 illustrates the association that exists between the BOM ITEM TYPE item attribute in Oracle EBS and the STRUCTURE TYPE product attribute in Siebel CRM for synchronizing BoM structures into Siebel and making them configurable and customizable.

    Table 4-1 Oracle EBS and Siebel CRM Attribute Association

    Oracle EBS BOM Item Type Siebel CRM Structure Type BOM Sync Button Enabled

    Standard

    Bundled

    No

    Model

    Customizable

    Yes

    Option Class

    Customizable

    Yes


  6. Siebel CRM cannot make requests to synchronize BoM structures for any items in Oracle EBS that have been set up with a BOM ITEM TYPE of Standard.

    Because these bundle structures have a static configuration, they are not likely to have a functional usage for Siebel CRM product administrators.

  7. Only selected item attributes are synchronized to Siebel CRM. These attributes are supported:

    • Item Name (part of the Key Flex Field structure)

    • Item Description

    • Item Type

    • Item Status

    • Primary UOM

    • Order Management-related attributes (orderable flag, customer-ordered flag)

    • Oracle inventory item ID (required for Oracle Product Configurator)

  8. Configured items (* items) are synchronized as part of the product synchronization, but they may include configured items that cannot be ordered from Siebel. For example, an Assemble to Order (ATO) model that is a child component of a Pick to Order ((PTO) model.

  9. BoM synchronization must be invoked manually from Siebel CRM, and is not driven by an event in Oracle EBS when a structure is modified or created.

  10. Item synchronization is initiated from Oracle EBS as an asynchronous process, and does not include any related item structures.

    If the simple product imported into Siebel CRM is associated to BoM structures that must be imported into Siebel CRM, then the product administrator in Siebel does a manual request for BoM from the Product Admin screens.

  11. Nonorderable items are not loaded into Siebel CRM as simple products. However, nonorderable items that are part of a BoM structure are loaded into Siebel CRM as component products when a BoM is requested and synchronized to Siebel CRM.

  12. If an existing item name in Oracle EBS is updated and synchronized to Siebel CRM, a new product is created in Siebel CRM.

  13. A known and identified interdependency exists between the Price Type field values and the Unit of Measure (UOM) field values assigned to an item in Siebel CRM.

    Because price type is not an attribute mapped in the integration between Oracle EBS and Siebel CRM, you must set up a onetime price type in Siebel CRM. You must also explicitly assign any UOM value used in the definition of the item to this price type to ensure that UOM values are synchronized correctly between Oracle EBS and Siebel CRM.

  14. Deleting items in Oracle EBS does not result in a request to delete simple products in Siebel CRM because no event mechanisms exist to accomplish this operation.

    Any deletions of simple products in Siebel CRM must be run as a manual process by an administrator in Siebel CRM.

  15. Only items associated with Oracle EBS OE Item Validation Org are synchronized from Oracle EBS to Siebel CRM.

  16. Oracle does not support custom and user-defined attributes for items or BoMs in this release.

Figure 4-1 illustrates the overall flow for the process integration.

Figure 4-1 Overall Product Management Integration Flow

Overall Product Management Integration Flow

Oracle EBS is the source for core item information, attributes, and BoM structures. This information is propagated to the Siebel CRM product master to facilitate the order capture process and to enable you to view saleable products in the Siebel CRM application.

Oracle EBS stores the item definitions in these categories:

  • Items are childless, single-level structures in Oracle EBS that correspond to simple products in Siebel CRM.

    After a simple product is synchronized in Siebel CRM, any changes to the product attributes or definition in Siebel CRM are not synchronized back to Oracle EBS.

  • BoMs are multi-level structures that contain child components and correspond to a complex product in Siebel CRM.

    Complex (configurable) products have a BoM with mandatory components, optional components, or both. After a complex product is synchronized in Siebel CRM, the hierarchical structure of a configurable product is available in Siebel CRM, but updates to the product structure or simple product component attributes are not synchronized back to Oracle EBS.

After products are synchronized in Siebel CRM, product attributes and BoM structures cannot be changed. However, product administrators can leverage eligibility and compatibility rules in Siebel CRM. They can also enrich products with Siebel-specific attributes.

The initial load process ensures that the full array of currently orderable items is synchronized to the Siebel front office application. The set of items synchronized to Siebel CRM include all of the orderable items that can be ordered as standalone items or that function as component (child) items in a complex BoM structure. This initial load process synchronizes only the individual items in a BoM. The relationships or structures of the BoM must be synchronized as an independent process.

Subsequent creation or updates to simple products in the Oracle product master triggers a business event in Oracle EBS that synchronizes these products to Siebel CRM in real time.

Creating or updating BoM structures in Oracle EBS does not automatically trigger a synchronization process to Siebel CRM. Instead, Siebel identifies the complex products to synchronize and invokes a process that allows these structures to be updated in Siebel CRM, based on the most current version of the BoM in the Oracle item master. Siebel CRM users can request a BoM synchronization for multiple BoMs in the same event process.

The complex products synchronized to Siebel CRM cannot be updated, but advanced pricing, eligibility, and compatibility rules can be applied. Any updates to Siebel-specific attributes are not synchronized back to Oracle EBS.

This flow is used for incremental loads; high-volume initial loads should use the Initial Data Load integration flow that is supported by the Order to Cash integration.

For more information about initial data loads, see Chapter 2, "Loading Initial Data."

4.2 Item Synchronization

The Synchronize Items integration flow enables the real-time one-way synchronization of items from Oracle EBS to Siebel CRM. After items are either created or updated in Oracle EBS, a business event is triggered that enables the synchronization of items from Oracle EBS to Siebel CRM.

Items from Oracle EBS are synchronized as products in Siebel CRM:

Based on the above, there can be various combinations of Organization set up, and Item and Product definitions across the two applications.

For more information about best practice scenarios for setting up the Organization cross-reference mappings, and how product synchronization to Siebel CRM takes place based on this setup, see Appendix B, "Organization Data Setup for Product Synchronization."

Note:

There may be other Item Organization (in Oracle EBS) or Business Unit (in Siebel CRM) related set up options that the implementations make that may not be supported, and may require customization.

Only customer orderable items are synchronized as part of this flow. The following attributes of an item are synchronized and passed to Siebel CRM:

Figure 4-2 illustrates the flow for synchronizing items between Oracle EBS and Siebel CRM.

Figure 4-2 Synchronize Items Integration Flow

Synchronize Items Integration Flow

4.2.1 Create Items Flow

This integration flow uses the following interfaces:

  • CreateProductEbizReqABCSImpl

  • ItemEBS

  • SyncProductSiebelProvABCSImpl

  • ItemResponseEBS

Figure 4-3 illustrates the Create Item integration scenario.

Figure 4-3 Create Item Flow Sequence Diagram

Create Item Flow Sequence Diagram

When you initiate the process, the following events occur:

  1. The CreateItemEbizEventConsumer listens to Business events and receives the WF_EVENT_T_msg event payload for the Create event.

    The CreateItemEbizEventConsumer routes to the CreateProductEbizReqABCSImpl with the complete event payload.

  2. The CreateProductEbizReqABCSImpl service calls the Oracle EBS service based on the event payload and then transforms to the SyncItemListEBM and invokes the ItemEBS with the operation SyncItemList.

    • As part of the enrichment process, the CreateProductEbizReqABCSImpl queries the EGO_ITEM_SYNC_OP_V view object through the Oracle EBS adapter QuerySimpleItemAdapter, based on event payload, to get the EgoItemSyncOpVCollection_msg.

    • As part of the transformation process, the CreateProductEbizReqABCSImpl transforms the EgoItemSyncOpVCollection_msg message into the SyncItemListEBM.

      SyncItemListEBM invokes the ItemEBS with the operation SyncItemList. The ItemEBS is a routing service with several operations on the Item enterprise business message (EBM). In the process, the cross-reference is created by concatenation of the Operating Unit and the Inventory Item ID.

  3. The ItemEBS routes the SyncItemListEBM to the SyncProductSiebelProvABCSImpl.

  4. The SyncProductSiebelProvABCSImpl transforms the SyncItemListEBM to the Siebel Product message and then calls the Siebel product web service SWIProductImport to synchronize the product.

    The Siebel web service completes the request and returns a response message. In the process, the cross-reference is linked to the Siebel IDs of the product.

4.2.2 Update Items Integration Flow

This integration flow uses the following interfaces:

  • UpdateProductEbizReqABCSImpl

  • ItemEBS

  • SyncProductSiebelProvABCSImpl

Figure 4-4 illustrates the Update Items integration scenario.

Figure 4-4 Update Items Flow Sequence Diagram

Update Items Flow Sequence Diagram

When you initiate the process, the following events occur:

  1. The UpdateItemEbizEventConsumer listens to Business events and receives the WF_EVENT_T_msg event payload for the Update event.

    The UpdateItemEbizEventConsumer routes to UpdateProductEbizReqABCSImpl with the complete Event payload.

  2. UpdateProductEbizReqABCSImpl service calls the Oracle EBS service based on the event payload, and then transforms to the SyncItemListEBM and invokes the ItemEBS with operation SyncItemList.

    • As part of the enrichment process, the UpdateProductEbizReqABCSImpl queries the EGO_ITEM_SYNC_OP_V view object through the Oracle EBS adapter QuerySimpleItemUpdateAdapter, based on the event payload, to get the EgoItemSyncOpVCollection_msg.

    • As part of the transformation process, the UpdateProductEbizReqABCSImpl transforms the EgoItemSyncOpVCollection_msg message into the SyncItemListEBM.

    • SyncItemListEBM invokes the ItemEBS with the operation SyncItemList.

    • The ItemEBS is a routing service with several operations on the Item EBM.

    • In the process, the cross-reference is created by concatenation of the Operating Unit and the Inventory Item ID.

  3. The ItemEBS routes the SyncItemListEBM to the SyncProductSiebelProvABCSImpl.

  4. The SyncProductSiebelProvABCSImpl transforms the SyncItemListEBM to the Siebel Product message and then calls the Siebel product web service SWIProductImport to synchronize the product.

    The Siebel web service completes the request and returns a response message. In the process, the cross-reference is linked to the Siebel IDs of the product.

4.3 Bill of Material Synchronization

The Synchronize BoM integration flow enables the synchronization of BoMs from Oracle EBS to Siebel CRM. This synchronization is a one-way feed from Oracle EBS to Siebel CRM. Siebel CRM must make a manual request for a structure that provides the applicable product ID for the complex product that must be synchronized. This flow is designed for real time synchronizations; it is not intended for high-volume initial loads.

The Synchronize BoM integration flow brings over all nonorderable items and item relationships based on the requested BoM structure.

The ability to synchronize the structure relies on the existence of the parent item and all of the orderable items in the structure in Siebel CRM at the time the request is made.

This integration flow uses the following interfaces:

Figure 4-5 illustrates the flow for synchronizing BoMs from Oracle EBS to Siebel CRM.

Figure 4-5 Synchronize BoM Integration Flow

Synchronize BOMs Integration Flow

Figure 4-6 illustrates the Synchronize BoM integration scenario.

Figure 4-6 Synchronize BoM Flow Sequence Diagram

Synchronize BOM Flow Sequence Diagram

When you initiate the process, the following events occur:

  1. The SyncProductStructureSiebelJMSProvider enqueues the Product ID, Inventory Location ID, and Business Unit ID to the Java Message Service (JMS) Queue for which the Complex Product and the structure must be available in Siebel CRM.

  2. The SyncProductStructureSiebelJMSConsumer process subscribes to the JMS queue and dequeues the Product ID and invokes the RequestProductStructureSiebelReqABCSImpl Siebel requester ABCSImpl.

  3. The RequestProductStructureSiebelReqABCSImpl transforms the Siebel product message RequestProductStructureABM into the EBM message QueryItemCompositionListEBM and invokes the ItemCompositionOrchestrationEBS.

    The ItemCompositionOrchestrationEBS is a routing service that routes the request to the InterfaceSyncProductStructurelEBF enterprise business flow.

  4. The InterfaceSyncProductStructurelEBF invokes the ItemCompositionEBS with the operation GetComplexProduct

    The ItemCompositionEBS routes the QueryItemCompositionListEBM to the QueryItemCompositionListEbizProviderABCSImpl implementation with EBM Code: GET_ITEMS.

  5. The QueryItemCompositionListEbizProviderABCSImpl transforms the QueryItemCompositionListEBM into the Oracle EBS product message EbizQueryMissingItemsInputABM. It then calls the Oracle application processing interface (API) BOM_STRUCT_SYNC_PUB.EXPLODE_STRUCTURE, through the Oracle Apps Adapter, to explode the BOM and query the Oracle View object EGO_ITEM_SYNC_V, BOM_STRUCTURE_SYNC_V through Oracle Apps adapter to fetch nonorderable items from the back office.

    Next, it transforms the Oracle response message EbizQueryMissingItemsResponse into the EBM message QueryItemCompositionListResponseEBM. The QueryItemCompositionListEbizProviderABCSImpl returns a response message QueryItemCompositionListResponseEBM to the ItemCompositionEBS. The ItemCompositionEBS returns a response message, QueryItemCompositionListResponseEBM, to the InterfaceSyncProductStructurelEBF.

  6. The InterfaceSyncProductStructurelEBF transforms the QueryItemCompositionListResponseEBM message into the SyncItemCompositionListEBM message and invokes the ItemCompositionEBS with the operation SyncComplexProduct.

    The ItemCompositionEBS routes the SyncItemCompositionListEBM to the SyncProductSiebelProvABCSImpl implementation. In the process, the cross-reference is created by concatenation of the Operating Unit ID and the Inventory Item ID.

  7. The SyncProductSiebelProvABCSImpl transforms the SyncItemEBM to the Siebel Product message and then calls the Siebel product web service SWIProductImport to synchronize the product.

    The Siebel web service completes the request and returns a response message. The SyncProductSiebelProvABCSImpl then transforms the Siebel response message to the SyncItemCompositionListResponseEBM and sends it back to the ItemCompositionEBS.

    The ItemCompositionEBS returns the response message SyncItemCompositionListResponseEBM to the InterfaceSyncProductStructurelEBF. In the process, the cross-reference links to the Siebel IDs of the product.

  8. The InterfaceSyncProductStructurelEBF invokes the ItemCompositionEBS with the operation GetComplexProduct.

    The ItemCompositionEBS routes the QueryItemCompositionListEBM to the RequestBOMStructureEbizProvABCSImpl implementation with the EBM Code: GET_STRUCTURE.

  9. The QueryItemCompositionListEbizProviderABCSImpl transforms the QueryItemCompositionListEBM into the Oracle EBS product message EbizQueryStructureInputABM.

    It then calls the Oracle EBS API BOM_STRUCT_SYNC_PUB.GET_STRUCTURE_PAYLOAD through the Oracle Apps adapter to fetch the Product Structure and transform the Oracle service response message EbizQueryStructureResponseABM into the EBM message QueryItemCompositionListResponseEBM.

    The QueryItemCompositionListEbizProviderABCSImpl returns a response message, QueryItemCompositionListResponseEBM, to the ItemCompositionEBS.

    The ItemCompositionEBS returns a response message, QueryItemCompositionListResponseEBM, to the InterfaceSyncProductStructurelEBF.

  10. The InterfaceSyncProductStructurelEBF transforms the QueryItemCompositionListResponseEBM message into the SyncItemCompositionListEBM message and invokes the ItemCompositionEBS with the operation SyncComplexProduct.

    The ItemCompositionEBS routes the SyncItemCompositionListEBM message to the SyncItemCompositionListSiebelProvABCSImpl implementation.

  11. The SyncItemCompositionListSiebelProvABCSImpl calls the Siebel web service SWIProductImport to synchronize the item structure.

    The SyncItemCompositionListSiebelProvABCSImpl transforms the SyncItemCompositionListEBM to the Siebel product message and then calls the Siebel product web service SWIProductImport to synchronize the product structure.

    The Siebel web service completes the request and returns a response message. The SyncItemCompositionListSiebelProvABCSImpl then transforms the Siebel response message to the SyncItemCompositionListResponseEBM and sends it back to the ItemCompositionResponseEBS. The ItemCompositionResponseEBS returns a response message, SyncItemCompositionListResponseEBM, to the InterfaceSyncProductStructurelEBF.

4.4 Siebel CRM Interfaces

For the Product Management integration flow, these are the Siebel CRM web services:

Inbound Siebel CRM Web Service

Outbound Siebel CRM Web Service

For more information about Siebel web services, see CRM Web Services Reference.

4.5 Oracle EBS Interfaces

For the Product Management integration flow, these are the Oracle EBS web services:

Inbound to Oracle EBS Web Services

Outbound from Oracle EBS Event Interfaces

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?

4.6 Core Oracle AIA Components

The Product Management integration flow uses the following delivered core components:

The industry enterprise business object (EBO) and enterprise business message XML schema (EBM XSD) files are located here: $AIA_HOME/AIAMetaData/AIAComponents/EnterpriseObjectLibrary/Core/EBO/

The industry enterprise business service (EBS) WSDL files are located here: $AIA_HOME/AIAMetaData/AIAComponents/EnterpriseBusinessServiceLibrary/Core/EBO/

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

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

EBOs can be extended, for instance, to add new data elements. These extensions are protected, and they remain intact after a patch or an upgrade.

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

4.7 Integration Services

These services are delivered with this integration:

For more information, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Configuring and Using Oracle Enterprise Repository as the Oracle AIA SOA Repository."

4.7.1 ItemEBSV2

The ItemEBSV2 is a lightweight routing service that exposes all of the enterprise operations that can be performed on an ItemEBO.

The SyncItemList operation is provided by the ItemEBS.

SyncItem (Simple Product): Whenever an Item is created or updated in the Item master in Oracle EBS; a business event is raised to sync the item in Siebel CRM.

The synchronization is required only for items that belong to OE Item Validation Org, are customer orderable, and have Item Type = {Model, Option Class, and Standard}. The business event does not discriminate between items based on this mentioned constraint-the event is triggered regardless of these constraints.

Post Item Create: oracle.apps.ego.item.postItemCreate

Post Item Update: oracle.apps.ego.item.postItemUpdate

Post Item BulkLoad: Oracle.apps.ego.item.postItemBulkload

For more information about this EBS, see the Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Designing and Developing Enterprise Business Services" and Oracle Fusion Middleware Concepts and Technologies Guide for Oracle Application Integration Architecture Foundation Pack, "Understanding Enterprise Business Services."

4.7.2 ItemCompositionResponseEBSV2

The ItemCompositionResponseEBSV2 is a lightweight routing service that exposes all of the enterprise response operations that can be performed with an ItemComposition enterprise object. All of the Order to Cash complex product integration flows make use of the response operations provided by this enterprise business service. This service is provided as a front end to other implementation services.

ItemCompositionResponseEBSV2 provides the SyncItemCompositionListResponse operation.

4.7.3 ItemResponseEBSV2

The ItemResponseEBSV2 is a lightweight routing service that exposes all of the enterprise response operations that can be performed with an Item enterprise object. As delivered, no routing rules are defined in the ItemResponseEBS. It is provided for future use.

4.7.4 CreateProductEbizReqABCSImpl

The CreateProductEbizReqABCSImpl is a Business Process Execution Language (BPEL) process that is responsible for calling the Oracle EBS Product web service, based on the event payload, to get the Oracle EBS Product ABM, and for transforming the Oracle EBS Product ABM messages into the appropriate Item EBM format and invoking the SyncItem EBS operation. By default, an orderable product associated with the OE:Item Validation Org is synchronized to Siebel CRM. To bypass validation against the OE:Item Validation Org, the configuration property BYPASS_ITEMVALIDATIONORG_FLAG must be set to Y.

This is a single operation service. It accepts an Oracle EBS Product message as a request and does not return a response.

4.7.5 UpdateProductEbizReqABCSImpl

The UpdateProductEbizReqABCSImpl is a BPEL process that is responsible for calling the Oracle EBS Product web service, based on the event payload to get the Oracle EBS Product ABM and transforming the Oracle EBS Product ABM messages into the appropriate Item EBM format and invoking the SyncItemList EBS operation. By default, an Orderable Product associated with the OE:Item validation organization is synchronized to Siebel CRM. To bypass validation against the OE:Item Validation Org, the configuration property BYPASS_ITEMVALIDATIONORG_FLAG must be set to Y.

This is a single operation service. It accepts an Oracle EBS Product message as a request and does not return a response.

4.7.6 BulkLoadProductEbizReqABCSImpl

The BulkLoadProductEbizReqABCSImpl is a BPEL process that is responsible for calling the Oracle EBS Product web service, based on the event payload, to get the Oracle EBS Product ABM and transforming the Oracle EBS Product ABM messages into the appropriate Item EBM format and invoking the SyncItemList EBS operation. By default, an orderable product associated with the OE:Item Validation Org is synchronized to Siebel CRM. To bypass validation against OE:Item Validation Org, the configuration property BYPASS_ITEMVALIDATIONORG_FLAG must be set to Y.

This is a single operation service. It accepts an Oracle EBS Product message as a request and does not return a response.

4.7.7 SyncProductSiebelProvABCSImpl

The SyncProductSiebelProvABCSImpl is a BPEL process that receives the ItemEBM and transforms it into a Siebel Product ABM. It invokes the Siebel Product web service to synchronize the same into Siebel. The Model and Option class item is synchronized to Siebel CRM as a customizable product that does not get released, whereas a standard item is synchronized to Siebel CRM as a bundle product and is released as part of the synchronize process.

The configuration property controls the released product in Siebel CRM:

  • SIMPLE_PRODUCT_RELEASE_FLAG: Default value Y

  • COMPLEX_PRODUCT_RELEASE_FLAG: Default value N

This is a single operation service. It accepts a SyncItemListEBM Product message as a request.

4.7.8 RequestProductStructureSiebelReqABCSImpl

The RequestProductStructureSiebelReqABCSImpl is a BPEL process that receives the Siebel product message RequestProductStructureABM from the SyncProductStructureSiebelJMSConsumer service and is responsible for transforming the RequestProductStructureABM into the QueryItemCompositionListEBM message and invoking the ItemCompositionOrchestrationEBS.

This asynchronous service accepts the Siebel product message RequestProductStructureABM as a request and does not return a response.

4.7.9 ItemCompositionOrchestrationEBS

The ItemCompositionOrchestrationEBS is a lightweight routing service that routes the request from the RequestProductStructureSiebelReqABCSImpl service to the InterfaceSyncProductStructurelEBF Enterprise Business Flow service. The ItemCompositionOrchestrationEBS does not expose any enterprise operations that can be performed with an Item Composition enterprise object.

The operation ProcessItemComposition is provided by the ItemCompositionOrchestrationEBS enterprise business service for routing purposes.

4.7.10 InterfaceSyncProductStructureEBF

The InterfaceSyncProductStructureEBF enterprise business flow service is an asynchronous BPEL process that queries the Non Orderable (default) or All (based on the configuration property PUBLISH_ALL_PRODUCT) products that are associated with the complex product and synchronizes them to Siebel CRM. This service is invoked from the ItemCompositionOrchestrationEBS service with request message QueryItemCompositionListEBM.

A single operation is available for this service, and the input is an instance of the QueryItemCompositionListEBM message. The Data Area of the message contains only one Product ID, Inventory Location ID, and Business Unit ID. (In the case of multiple product requests from Siebel, the service iterates through the collection in the RequestProductStructureSiebelReqABCSImpl and invokes the InterfaceSyncProductStructureEBF for each complex product.)

4.7.11 QueryItemCompositionListEbizProvABCSImpl

The InterfaceSyncProductStructureEBF invokes the QueryItemCompositionListEbizProvABCSImpl BPEL process through the ItemCompositionEBS. This service is responsible for transforming the QueryItemCompositionListEBM into the EbizQueryMissingItemsInputABM Oracle product message and running Oracle API BOM_STRUCT_SYNC_PUB.EXPLODE_STRUCTURE through Oracle Apps adapter to explode the BOM.

By default, the QueryItemCompositionListEbizProvABCSImpl publishes all nonorderable child components of the BOM and BOM Structure. The configuration property PUBLISH_ALL_PRODUCT controls this function.

This is a single operation service that accepts a QueryItemCompositionListEBM message as a request and returns a QueryItemCompositionListResponseEBM as a response.

4.7.12 ItemCompositionEBS

The ItemCompositionEBS is a lightweight routing service that exposes all of the enterprise operations that can be performed with an ItemComposition EBO.

ItemCompositionEBS provides these operations:

  • QueryItemCompositionList

  • SyncItemCompositionList

4.7.12.1 QueryItemCompositionList

The ItemCompositionEBS calls the QueryItemCompositionListEbizProviderABCSImpl Oracle implementation to get item and item structure. The QueryItemCompositionListEbizProviderABCSImpl runs the following Oracle APIs:

  • BOM_STRUCT_SYNC_PUB.EXPLODE_STRUCTURE to explode the BOM

  • Query Oracle View object EGO_ITEM_SYNC_V, BOM_STRUCTURE_SYNC_V to fetch the Non Orderable Item (default) or All (based on the configuration property PUBLISH_ALL_PRODUCT)

  • BOM_STRUCT_SYNC_PUB.GET_STRUCTURE_PAYLOAD to get the BOM structure

4.7.12.2 SyncItemCompositionList

When a Siebel product administrator requests one or more product structures to be available in the Siebel CRM system, the product and its corresponding product structure are synchronized through the ItemCompositionEBS from Oracle EBS back into Siebel CRM.

The ItemCompositionEBS calls the SyncItemCompositionListSiebelProvABCSImpl Siebel implementation to synchronize the product and corresponding product structure into Siebel CRM.

4.7.13 SyncItemCompositionListSiebelProvABCSImpl

The ItemCompositionEBS invokes the SyncItemCompositionListSiebelProvABCSImpl Siebel implementation. The responsibility of this service is to receive SyncItemCompositionListEBM, transform it into a Siebel Product ABM, and then invoke the Siebel Product web service to synchronize the item structure into Siebel CRM.

Model and Option class items are synchronized to Siebel as customizable products and do not get released, whereas a standard item is synchronized to Siebel as Bundle Product and released as part of synchronization process.

The following configuration properties control the Release Product in Siebel:

  • SIMPLE_PRODUCT_RELEASE_FLAG: Default value Y

  • COMPLEX_PRODUCT_RELEASE_FLAG: Default value N

This is a single operation service that accepts a SyncItemCompositionListEBM Product message as a request and invokes the ItemCompositionResponseEBS with the operation SyncItemCompositionListResponse and the message SyncItemCompositionListResponseEBM to return the response message to the InterfaceSyncProductStructureEBF.

4.7.14 RequestProductStructureSiebelJMSProducer

The RequestProductStructureSiebelJMSProducer is implemented as a BPEL process because it involves JMS Header manipulations.

This service is responsible for enqueueing the Siebel RequestProductStructure ABM event payload into the JMS queue when a Siebel product administrator decides to replicate an existing complex product from the back office in Siebel. The enqueued message can be a list of product IDs with the related inventory location IDs and business unit IDs.

This service has one asynchronous request-only operation: RequestProductStructure

4.7.15 RequestProductStructureSiebelJMSConsumer

The RequestProductStructureSiebelJMSConsumer is implemented as a process with JMS adapter and routing services.

This service is responsible for dequeueing the Siebel RequestProductStructureABM message from the JMS queue AIA_ITEMCOMPJMSQUEUE and invoking the RequestProductStructure operation of the RequestProductStructureSiebelReqABCSImpl.

One service with one operation is available for reading Siebel messages RequestProductStructureMsg from the JMS queue AIA_ITEMCOMPJMSQUEUE. That service is RequestProductStructureJMSConsumer

4.7.16 CreateItemEbizEventConsumer

The CreateItemEbizEventConsumer has an Oracle Apps adapter configured to listen for create business events with routing services.

One service with one operation is available to read the Oracle EBS message EbizSyncProductReqMsg from the Oracle AQ WF_BPEL_Q. That service is CreateItemEbizEventConsumer

This service is implemented as a process with an Oracle Apps adapter for listening to business event and routing services.

4.7.17 UpdateItemEbizEventConsumer

The UpdateItemEbizEventConsumer has an Oracle Apps adapter configured to listen for update business events with routing services.

One service with one operation is available to read the Oracle EBS message EbizSyncProductReqMsg from the Oracle AQ WF_BPEL_Q. That service is UpdateItemEbizEventConsumer

This service is implemented as a process with an Oracle Apps adapter for listening to business events and routing services.

4.7.18 BulkloadItemEbizEventConsumer

The BulkloadItemEbizEventConsumer has an Oracle Apps adapter configured to listen for Bulkload business events with routing services.

One service with one operation is available to read the Oracle EBS message EbizSyncProductReqMsg from the Oracle AQ WF_BPEL_Q. That service is BulkloadItemEbizEventConsumer

This service is implemented as a process with an Oracle Apps adapter for listening to business events and routing services.