Skip Headers
Oracle® Application Integration Architecture Oracle Customer Master Data Management Integration Implementation Guide
Release 11.1

Part Number E23082-04
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

5 Oracle Customer Master Data Management Integration Option for Oracle Communications BRM

This chapter provides an overview of the integration option for Oracle Communications Billing and Revenue Management (BRM), and discusses the interfaces, and integration services.

This chapter contains the following sections:

5.1 Overview

There is no process flow from Oracle BRM to Oracle Customer Hub (OCH).

For OCH to Oracle BRM flows, see Chapter 2, "Oracle Customer Master Data Management Integration Base Pack".

Note:

The status of any entity is special compared to other fields of that entity. Account status or Contact status changes from valid to invalid or from active to inactive, have implications in various systems such as billing or CRM or ERP.

If customers need to update status in systems other than OCH, ensure the survivorship rules are defined properly in OCH so that this status update is not rejected by OCH. If survivorship rules are not configured properly, then OCH will reject the update and reverse the status back in CRM (or any other source application). This is true for any updates to an account or a contact.

When the Oracle Communications Order To Cash Siebel CRM and BRM options are deployed along with the Customer MDM Base Pack and BRM options, and the account status sync is enabled (in Comms O2C), then there is a chance that by the time OCH rejects the update from CRM, BRM may already have been updated with the status information from CRM directly.

To avoid this mismatch between Siebel CRM and BRM, if OCH is the master for account status, Oracle recommends that customers put business process controls in place to disallow changes to account status in Siebel CRM.

Alternatively, if status needs to be updated in any source system, then customers can make sure that survivorship rules are configured in OCH to allow updates from any source system to be accepted by OCH.

For more information about the implications of enabling status sync to BRM see the Oracle Communications Order to Cash Integration Pack for Siebel CRM, Oracle Communications Order and Service Management, and Oracle Communications Billing and Revenue Management Implementation Guide, section "18.4.2.1 Account Status Synchronization Methodology."

5.2 Oracle BRM Interfaces

The SyncCustomerPartyListBRMCommsProvABCSImpl is the only service that directly calls Oracle BRM. A new configuration property is added for this ABCS called StatusUpdateRequired. This property is used to indicate the status whether the account in Siebel needs to be communicated to Oracle BRM or not. In addition, there are appropriate configuration properties added supporting extensibility.

5.3 Oracle BRM Integration Services

These are the integration services for Oracle BRM spoke.

5.3.1 Core2CommsCustomerPartyBridge

The Core2CommsCustomerPartyBridge routes messages from the core CustomerPartyEBSV2 to the CommunicationsCustomerPartyEBSV2.

For more information about Communications-specific services or flows, see the Oracle Communications Order to Cash Integration Pack for Siebel CRM, Oracle Communications Order and Service Management, and Oracle Communications Billing and Revenue Management Implementation Guide, or the Siebel CRM Integration Pack for Oracle Communications Billing and Revenue Management: Agent Assisted Billing Care Implementation Guide.

5.3.2 CommunicationsCustomerPartyEBSV2

CommunicationsCustomerPartyEBSV2 is used to route the CustomerPartyEnterpriseObjects for creating a new customer or updating the customer in Oracle BRM. This enterprise business service routes the messages from Siebel and OCH to Oracle BRM.

If the incoming message is from Siebel, the message is routed through the SyncCustomerPartyListBRMCommsJMSProducer to a topic; then to the SyncCustomerPartyListBRM_01CommsJMSConsumer; and finally to the SyncCustomerPartyListBRMProvABCSImpl, which synchronizes the data to Oracle BRM.

If the incoming message is from OCH, the message is stamped with the actionCode value as Update because it is an updated message and then sent to the SyncCustomerPartyListBRMProvABCSImpl, which in turn synchronizes the data to Oracle BRM.

If the incoming message is from Siebel Order then this service routes the message to SyncCustomerPartyListBRMProvABCSImpl, which in turn synchronizes the data to Oracle BRM.

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."

For more information about Communications-specific services or flows, see the Oracle Communications Order to Cash Integration Pack for Siebel CRM, Oracle Communications Order and Service Management, and Oracle Communications Billing and Revenue Management Implementation Guide, or the Siebel CRM Integration Pack for Oracle Communications Billing and Revenue Management: Agent Assisted Billing Care Implementation Guide.

5.3.3 SyncCustomerPartyListBRMCommsProvABCSImpl

The SyncCustomerPartyListBRMCommsProvABCSImpl service is invoked by CommsProcessBillingAccountListEBF or SyncAccountSiebelReqABCSImpl or SyncOrganizationUCMReqABCSImpl service when the routing rules determine that Oracle BRM is to be the service provider of the SyncCustomerPartyList operation of the CommunicationsCustomerPartyEBSV2.

This either occurs during the integration flow that is initiated by the account-synchronization-processing portion of the order flow or during the account update flow.

For more information about Communications-specific services or flows, see the Oracle Communications Order to Cash Integration Pack for Siebel CRM, Oracle Communications Order and Service Management, and Oracle Communications Billing and Revenue Management Implementation Guide, or the Siebel CRM Integration Pack for Oracle Communications Billing and Revenue Management: Agent Assisted Billing Care Implementation Guide.

5.3.4 CommunicationsCustomerPartyResponseEBSV2

CommunicationsCustomerPartyResponseEBSV2 is used for routing the CustomerPartyResponse EnterpriseObjects to synchronize the status back to the caller.

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."

For more information about Communications-specific services or flows, see the Oracle Communications Order to Cash Integration Pack for Siebel CRM, Oracle Communications Order and Service Management, and Oracle Communications Billing and Revenue Management Implementation Guide, or the Siebel CRM Integration Pack for Oracle Communications Billing and Revenue Management: Agent Assisted Billing Care Implementation Guide.

5.3.5 SyncCustomerPartyListBRMCommsJMSProducer

This process enqueues the customer messages from the communication customer party EBS to a topic, and routes the message to the SyncCustomerPartyListBRMProvABCSImpl.

For more information about Communications-specific services or flows, see the Oracle Communications Order to Cash Integration Pack for Siebel CRM, Oracle Communications Order and Service Management, and Oracle Communications Billing and Revenue Management Implementation Guide, or the Siebel CRM Integration Pack for Oracle Communications Billing and Revenue Management: Agent Assisted Billing Care Implementation Guide.

5.3.6 SyncCustomerPartyListBRM_01CommsJMSConsumer

This process consumes the topic messages. For every billing instance, one such consumer must be deployed. It checks with the cross-reference data to ensure that the customer belongs to the corresponding instance. If the data belongs to the corresponding Oracle BRM instance, this process stamps the appropriate target system identifiers in EBM and routes the message to the provider.

For more information about Communications-specific services or flows, see the Oracle Communications Order to Cash Integration Pack for Siebel CRM, Oracle Communications Order and Service Management, and Oracle Communications Billing and Revenue Management Implementation Guide, or the Siebel CRM Integration Pack for Oracle Communications Billing and Revenue Management: Agent Assisted Billing Care Implementation Guide.