Skip Headers
Oracle® Application Integration Architecture Oracle Communications Order to Cash Integration Pack Implementation Guide for Siebel CRM, Oracle Communications Order and Service Management, and Oracle Communications Billing and Revenue Management
Release 11.3

Part Number E37675-02
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

10 Understanding the Synchronize Fulfillment Order Billing Account Business Flow

This chapter provides an overview of the Synchronize Fulfillment Order Billing Account business flow and discusses solution assumptions and constraints.

The Synchronize Fulfillment Order Billing Account business flow is enabled by the following Pre-Built Integration option of the Oracle Communications Order to Cash Integration Pack for Siebel customer relationship management (Siebel CRM), Oracle Communications Order and Service Management (OSM), and Oracle Communications Billing and Revenue Management (BRM) (the integration):

Overview of the Synchronize Fulfillment Order Billing Account Business Flow

The Synchronize Fulfillment Order Billing Account business flow lets you create only the customer data necessary for order fulfillment in BRM without overburdening BRM with all of the customer information from Siebel CRM.

This business flow provides the following service:

  • CommsProcessFulfillmentOrderBillingAccountListEBF: creates customer data in Oracle BRM when called as part of the order fulfillment process.

This service takes an order as input and collates order data and then calls other enterprise billing services (from the process integration for Customer Management) to create accounts and their components (such as billing preferences and payment methods) in a BRM instance. This service can be invoked from an order orchestration flow from within OSM, to create customer data in BRM.

See "Expectations from an Order Management System for Billing Integration" for more information about calling this service from an order management system other than OSM.

See "Understanding the Process Integration for Customer Management" for more information about the Customer Management process integration.

Figure 10-1 shows how the integration interfaces orders to create customer data in BRM.

Figure 10-1 Interfacing Customer Data to Billing

This image is described in surrounding text.

The CommsProcessFulfillmentOrderBillingAccountListEBF service processes only lines with the actions of ADD, UPDATE, and MOVE-ADD and ignores the others. This service considers order lines for customer data collation as follows:

  • For lines whose billing type is Service Bundle, Item, Subscription, or Discount, it considers Service Account, Billing Account, and Billing Profile.

  • For lines whose product type is Promotion, it includes only Billing Account.

  • All other lines are ignored.

The result of calling this service is the creation of customer data such as accounts, /billinfo objects, and /payinfo objects in BRM.

Customer creation that occurs in BRM as part of order fulfillment using the InterfaceOrderToCustomerEBF service cannot be undone. The service does not support inactivating or deleting accounts, /billinfos objects, or /payinfo objects in BRM.

Calling the CommsProcessFulfillmentOrderBillingAccountListEBF again with the same input as before has no effect.

When you call the service again with different customer data than before, the service detects the delta and creates just the account, /billinfo objects, and /payinfo objects that do not exist in BRM.

When the service account on a service bundle or account-level product line is different from the bill-to account, the service account is created as a nonpaying subordinate account under the bill-to account in BRM. This creates a paying hierarchy in billing.

A paying hierarchy, when created, cannot be undone by the cancelling the original Siebel CRM order. If the service is called to update an existing paying hierarchy (for example, to set the paying account for a subordinate account to a different paying account), to undo that update (because the Siebel CRM order requesting the change was canceled), the order management system must rework the message such that it is a call to update the hierarchy to a previous state.

See "About the Create/Sync Account Integration Flow" for more information about what Siebel CRM account information is sent to BRM.

If you are using an order management system other than OSM, Table 10-1 summarizes what is expected for the action on the line. OSM and OSM AIA cartridges conform to these expectations.

Table 10-1 Actions on Order Line Expectations Summary

Original Action on Order Line Type of Order (Revision or New) Type of Revision Action Set by Order Management System on Compensation Order Line Comments

ADD

New

Not applicable

ADD

None

ADD

Revision

No changes to service account, billing account, or billing profile

NONE

No changes for customer sync to process.

ADD

Revision

Changes to service account, billing account, or billing profile

UPDATE

The order management system creates customer data in BRM if it does not already exist.

If revisions are made to attributes affecting account hierarchy, the order management system makes the change in BRM.

The order management system indicates which attributes have changed by populating the prior value fields for the changed attributes.

Prior value fields are used in flagging and determining that a paying hierarchy change has occurred.

ADD

Revision

Cancellation. Manifests as a missing line on the revision.

DELETE

This action is ignored.

If the original ADD line added a new account, /billinfo object, and /payinfo object, and the revision cancels the request for the new purchase, the account, /billinfo, and /payinfo are not inactivated or deleted.

If the original ADD line created a paying hierarchy and the revision cancels the request for the new purchase, then the paying hierarchy stays in place.

UPDATE

New

Not applicable

UPDATE

Expects prior value fields to be populated.

UPDATE

Revision

No changes to service account, billing account, or billing profile

NONE

No changes.

UPDATE

Revision

Changes to service account, billing account, or billing profile

UPDATE

The order management system creates customer data in BRM if it does not already exist.

If revisions are made to attributes affecting account hierarchy, the order management system makes the change in BRM.

The order management system indicates which attributes have changed by populating the prior value fields for the changed attributes.

UPDATE

Revision

Cancellation. Manifests as a missing line on the revision or the action changing to a "-" (NONE).

UPDATE

If the original update line created a new account and billing profile in BRM, then it cannot be undone.

For the attributes that have changed on the original line, the order management system flips the values (old, new) on the compensation line. If a hierarchy has been updated, this reverts that update.

MOVE-ADD

New, but can change billing account and billing profile as part of a move-add.

Not Applicable

MOVE-ADD

Expects prior value fields to be populated for values that are changing from an existing asset.

MOVE-ADD

Revision

No changes to service account, billing account, or billing profile

NONE

No changes.

MOVE-ADD

Revision

Changes to billing account or billing profile

MOVE-ADD

The order management system creates customer data in BRM if it does not already exist.

If revisions are made to attributes affecting account hierarchy, the order management system makes the change in BRM.

The order management system indicates which attributes have changed by populating the prior value fields for the changed attributes.

MOVE-ADD

Revision

Manifests as a missing line on the revision or the action changing to a "-"

(The line is canceled).

MOVE-ADD

If the original MOVE-ADD line created a new account and billing profile in BRM, then it cannot be undone.

For the attributes that have changed on the original line, the order management system flips the values (old, new) on the compensation line. If a hierarchy has been updated, this reverts that update.


Caution:

The process integration for billing management (delivered in the Agent Assisted Billing Care pre-built integration) assumes that a given billing profile is synchronized to a single billing system. It does not support the ability to query data for the same billing profile from multiple billing system. For that reason, if that process integration is in use, then the same billing profile must not be used on an order for services that are fulfilled in different billing systems.

See the discussion of billing management in Oracle Application Integration Architecture Siebel CRM Integration Pack for Oracle Communications Billing and Revenue Management: Agent Assisted Billing Care Implementation Guide for more information.

Assumptions and Constraints for the Synchronize Fulfillment Order Billing Account Business Flow

See "Assumptions and Constraints for the Bill Fulfillment Order Business Flow" for information on this business flow.