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

Part Number E26501-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

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

E OLM - Examples of Changing the Paying Parent on Subordinate Accounts

This appendix describes three example scenarios for changing the paying parent on subordinate accounts.

This appendix contains the following sections:

Table E-1 provides descriptions for the abbreviations used in the example scenarios.

Table E-1 Legend

Abbreviation Description

S

Service

SA

Service Account

BA

Billing Account

BG

Balance Group

BP

Billing Profile

DBP

Dummy Bill Info


E.1 Scenario One - Supported

Table E-2 is the base scenario.

Table E-2 Base scenario

Action #
SA BA BP

ADD

S1

SA1

BA1

BA1-BP1

ADD

S2

SA1

BA1

BA1-BP1


Figure E-1 shows the scenario results after the order is processed to billing.

Figure E-1 Base Scenario Results

This image is described in surrounding text.

Table E-3 shows reparenting the subordinate to a different parent.

Table E-3 Reparenting subordinate to a different parent - Example 1

Action #
SA BA BP

UPD

S1

SA1

BA2

BA2-BP2

UPD

S2

SA1

BA2

BA2-BP2


This works even if S2 is not included on the order. However, to keep Siebel Customer Relationship Management (Siebel CRM) assets synchronized, S2 should also be updated. Or as shown in Table E-4.

Table E-4 Reparenting subordinate to a different parent - Example 2

Action #
SA BA BP

UPD

S1

SA1

BA2

BA2-BP2

UPD

S2

SA1

BA2

BA2-BP2

ADD

S3

SA1

BA2

BA2-BP2


Figure E-2 shows the results for the preceding scenario.

Figure E-2 Reparenting Subordinate to a Different Parent - Example 2 Results

This image is described in surrounding text.

E.2 Scenario Two - Supported

Table E-5 is the base scenario:

A parent using different billing profiles to pay for their account and not each of the child accounts.

Note:

A parent cannot use multiple billing profile to pay for services of the same child account because the child account can have only one balance group, which can point to only one bill-info.

Table E-5 Base scenario

Action #
SA BA BP

ADD

S1

BA1

BA1

BA1-BP1

ADD

S2

SA1

BA1

BA1-BP2

ADD

S3

SA2

BA1

BA1-BP3


Figure E-3 shows the scenario results after the order is processed to billing.:

Figure E-3 Base Scenario Results

This image is described in surrounding text.

Note:

The account-level balance group for the parent account (BA1) references the first billing profile that is created for that account. In the previous scenario it is BP1. If the ADD line for the service purchase for the parent account (BA1) is not the first line on the order, then the account-level balance group references billing profile BP2, and the purchase of S1 fails because it is using BP1.

Table E-6 shows that the change order is processed, which reparents both the subordinate accounts to a new parent, and the same billing profile under the new parent.

Table E-6 Change order processed

Action #
SA BA BP

UPDATE

S1

SA1

BA2

BA2-BP4

UPDATE

S2

SA2

BA2

BA2-BP4


Figure E-4 shows what is visible in Oracle Communications Billing and Revenue Management (Oracle BRM):

Figure E-4 Outcome in Oracle BRM

This image is described in surrounding text.

The repointing of the dummy bill-infos to the new billing profile is handled by the services that interface customer data to billing.

Alternates:

Figure E-5 shows how S1 remains unchanged.

Figure E-5 Service 1 (S1)

This image is described in surrounding text.

E.3 Scenario Three - Supported (with caveats)

Table E-7 is the base scenario.

Table E-7 Base scenario

Action #
SA BA BP

ADD

S1

SA1

BA1

BA1-BP1

ADD

S2

SA1

BA1

BA1-BP2


After customer sync, the integration creates two dummy bill-infos:

The default account-level balance group points to BA1-BP1. (It points to the billing profile referenced on the first line on the order).

However, depending on which lines are sent for processing, the order billing integration behaves in one of two ways: