Skip Headers
Oracle® Application Integration Architecture Oracle Financial Management Integration Pack Implementation Guide for Oracle Transportation Management and Oracle E-Business Suite
Release 3.1

Part Number E23563-07
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

7 Process Integration for Customer Synchronization

This chapter provides an overview of the process integration for customer synchronization and discusses business process flows, assumptions and constraints, Oracle E-Business Suite (Oracle EBS) and Oracle Transportation Management (OTM) interfaces, core Oracle Application Integration Architecture (Oracle AIA) components, and integration services.

This chapter includes the following sections:

7.1 Overview

The customer synchronization integration supports these operations and corresponding synchronization of customer records from Oracle EBS to OTM:

7.2 Business Process Flows

Figure 7-1 is a flow diagram that shows the customer flow synchronization.

Figure 7-1 Customer Flow - Sync Operation

This image is described in surrounding text.

Figure 7-2 is a flow diagram that shows the customer flow for merge party:

Figure 7-2 Customer Flow - Merge Party Operation

This images is described in surrounding text.

Figure 7-3 is a flow diagram that shows the customer flow for merge account:

Figure 7-3 Customer Flow - Merge Account Operation

This image is described in surrouding text.

Figure 7-4 is a sequence diagram that shows the incremental changes in the customer party synchronization:

Figure 7-4 Incremental Changes - Customer Party Sync

This image is described un surrounding text.

Figure 7-5 is a sequence diagram that shows the incremental changes in the customer party synchronization:

Figure 7-5 Incremental Changes - Customer Party Sync

This image is described un surrounding text.

Figure 7-6 is a sequence diagram that shows the incremental changes in customer party merge:

Figure 7-6 Incremental Changes - Customer Party Merge

This image is described in surrounding text.

Figure 7-7 is a sequence diagram that shows the incremental changes in the customer account merge:

Figure 7-7 Incremental Changes - Account Merge

This image is described in surrounding text.

7.2.1 Order to Cash Integration Services

These services from Order to Cash (O2C) are available:

  • SyncCustomerPartyListEbizEventConsumer

  • MergeAccountEbizEventConsumer

  • SyncCustomerPartyListEbizReqABCSImpl

  • CustomerPartyEBSV2

  • SyncCustomerPartyListLogisticsProvABCSImpl

  • MergeAccountEbizReqABCSImpl

  • MergePartyEbizReqABCSImpl

  • MergeCustomerPartyListLogisticsProvABCSImpl

  • CreatePayableInvoiceLogisticsReqABCSImpl

  • QueryCustomerPartyListEbizCreateAdapter

  • QueryCustomerPartyListEbizUpdateAdapter

  • QueryCustomerPartyEbizAdapter

  • MergeAccountEbizEventConsumer

  • MergePartyEbizEventConsumer

  • MergeAccountEbizReqABCSImpl

  • MergePartyEbizReqABCSImpl

  • TransformAppContextEbizService

  • QueryMergeAccountEbizAdapter

  • QueryPartyMergeEbizAdapter

  • QueryMergeOrgCustEbizAdapter

  • QueryRelatedOrgCustEbizAdapter

7.3 Assumptions and Constraints

These are the assumptions and constraints:

7.4 Oracle EBS Interfaces

For more information about Oracle EBS web services definition language (WSDL) and schema definition, see Oracle Customer Master Data Management Integration documentation.

For more information about Oracle EBS 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 EBS documentation for R12.1.3 and beyond, see this library: http://download.oracle.com/docs/cd/E18727_01/index.htm.

7.5 OTM Interfaces

The OTM provides an interface through a web service to connect to its application. This connectivity is established as a partner link in the provider service. When the logistics web service is called it returns an acknowledgment with a transmission number. Once the processing is complete, it then sends a transmission report back indicating the success or the failure.

For more information about the logistics service, see Oracle Transportation Management Integration Guide.

7.6 Core Oracle AIA Components

The integration flow uses these components:

The core enterprise business object (EBO) and enterprise business message (EBM) XSD files can be located by EBO within the $AIA_HOME/AIAMetaData/AIAComponents/EnterpriseObjectLibrary/Core/EBO/ parent folder.

The core enterprise business services (EBS) web services definition language (WSDL) files can be located by EBO within the $AIA_HOME/AIAMetaData/AIAComponents/EnterpriseBusinessServiceLibrary/Core/EBO/ parent folder.

For detailed documentation of individual EBOs and EBMs, click AIA Reference Doc link on EBO and EBM detail pages in the 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 remain intact after a patch or an upgrade.

For more information, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Extensibility for AIA Artifacts".

7.7 Integration Services

These are the services delivered with this integration:

7.7.1 CustomerPartyEBSV2

CustomerPartyEBSV2 is the Enterprise Business Service to route all location related actions such as create customer, update customer, delete customer, and synchronize customer. The mediator service routes to SyncCustomerPartyListLogisticsProvABCSImpl in case of create and update operations of customer. The mediator service routes to MergeCustomerPartyListLogisticsProvABCSImpl in case of merge operations of customer. The mediator service routes to Composite Application Validation System (CAVS) based on the filter condition and operation.

7.7.2 CustomerPartyResponseEBSV2

CustomerPartyResponseEBSV2 is the Enterprise Business Service to route all customer related actions such as create customer, update customer, delete customer, and synchronize customer.

The mediator service routes the response message to MergeAccountEbizReqABCSImpl in case of merge of customer accounts. The mediator service routes to CAVS based on the filter condition and operation.

7.7.3 MergeCustomerPartyListLogisticsProvABCSImpl

MergeCustomerPartyListLogisticsProvABCSImpl is a Business Process Execution Language (BPEL) Process which receives SyncCustomerPartyListEBM as input from CustomerPartyEBSV2. This message is transformed to LogisticsABM. Cross-reference values are populated here. SyncCustomerPartyListEBM is transformed into CustomerPartyLogisticsABM and then the LogisticsWebService is invoked with this transformed application business message (ABM). This instance asynchronously waits for TransmissionReport from OTM. If the transaction is successful, the cross-reference values are populated; else, AIAAsyncErrorHandlingBPELProcess is invoked with an error message.