E Examples of Changing the Paying Parent on Subordinate Accounts

This appendix gives examples of changing the paying parent on subordinate accounts. When service-level balance groups are enabled, there are different options for changing the paying parent than when service-level balance groups are disabled. The examples illustrate these options.

About the Examples

The examples show Siebel customer relationship management (Siebel CRM) orders and illustrations of the conceptual arrangement of services, billing profiles, balance groups, and bill units resulting from sending the orders to Oracle Communications Billing and Revenue Management (BRM).

The first order in each example is the base order that purchases services for a subordinate account under a paying parent account. When the service account on an order is different from the billing account, BRM creates the service account with a dummy /billinfo object as a subordinate account under the billing account. The integration points the dummy /billinfo object to the billing profile of the paying parent account.

The subsequent orders in each example are change orders that transfer the services purchased in the first order to new paying parent accounts. When the services are transferred, the integration moves the subordinate account under the new paying parent account in BRM. The integration also creates new balance groups and dummy /billinfo objects for the services in the subordinate account pointing to the paying parent account's chosen billing profile.

Because of the automatic naming conventions for balance groups, the new balance groups for transferred services have the same name as the old balance groups. The examples show a different number in the balance group name to illustrate that these are different balance groups. In reality the balance groups would be identical.

Because BRM does not support subordinate accounts with more than one paying parent, the change orders must transfer all services for the subordinate account at once.

Table E-1 defines the abbreviations used in the examples.

Table E-1 Abbreviations Used in the Examples

Abbreviation	Description
S	Service: a Siebel CRM service bundle that represents a service instance in BRM
SA	Service account: the subordinate account
BA	Billing account: the parent account
BG	Balance group: the BRM balance group in which each service is tracked
BP	Billing profile: the billing profile on the parent account
DBP	Dummy /billinfo object: a /billinfo object created for a subordinate account that the integration points to the parent account's billing profile

Examples when Service-Level Balance Groups Are Enabled

This section gives examples of changing the paying parent on subordinate accounts when service-level balance groups are enabled.

Changing the Paying Parent for a Subordinate Account with Separate Billing Profiles

This example shows:

A base order that purchases two services with separate billing profiles for a subordinate account
Change orders that change the paying parent for the subordinate account and all of its services

Table E-2 shows the base order. A separate billing profile is assigned to each service.

Table E-2 Base Order for Services with Separate Billing Profiles

Action	Service Number	Service Account	Billing Account	Billing Profile
ADD	S1	SA1	BA1	BA1-BP1
ADD	S2	SA1	BA1	BA1-BP2

Figure E-1 shows the result of sending the base order to billing. The services are tracked in separate balance groups that point to separate dummy /billinfo objects.

Figure E-1 Result of Base Order for Services with Separate Billing Profiles

Description of "Figure E-1 Result of Base Order for Services with Separate Billing Profiles"

Table E-3 shows the change order to change the paying parent for the subordinate account while maintaining separate billing profiles for the services.

Table E-3 Order to Change the Paying Parent with Separate Billing Profiles

Action	Service Number	Service Account	Billing Account	Billing Profile
UPDATE	S1	SA1	BA2	BA2-BP3
UPDATE	S2	SA1	BA2	BA2-BP4

Figure E-2 shows the result of sending the change order to billing.

Figure E-2 Result of Change Order to Change the Paying Parent with Separate Billing Profiles

Description of "Figure E-2 Result of Change Order to Change the Paying Parent with Separate Billing Profiles"

Alternatively, the change order can change the paying parent for the subordinate account and assign the same billing profile to both services. Table E-4 shows this alternative order.

Table E-4 Alternative Change Order to Change the Paying Parent with a Single Billing Profile

Action	Service Number	Service Account	Billing Account	Billing Profile
UPDATE	S1	SA1	BA2	BA2-BP3
UPDATE	S2	SA1	BA2	BA2-BP3

Figure E-3 shows the results of sending the alternative order to billing.

Figure E-3 Result of Alternative Change Order to Change the Paying Parent with a Single BIlling Profile

Description of "Figure E-3 Result of Alternative Change Order to Change the Paying Parent with a Single BIlling Profile"

Changing the Paying Parent for a Subordinate Account with a Single Billing Profile

This example shows:

A base order that purchases two services with a single billing profile for a subordinate account
Change orders that change the paying parent for the subordinate account and all of its services

Table E-5 shows the base order. The same billing profile is assigned to both services.

Table E-5 Base Order for Services with a Single Billing Profile

Action	Service Number	Service Account	Billing Account	Billing Profile
ADD	S1	SA1	BA1	BA1-BP1
ADD	S2	SA1	BA1	BA1-BP1

Figure E-4 shows the result of sending the base order to billing. The services are tracked in separate balance groups that point to the same dummy /billinfo object.

Figure E-4 Result of Base Order for Services with a Single Billing Profile

Description of "Figure E-4 Result of Base Order for Services with a Single Billing Profile"

Table E-6 shows the change order to change the paying parent for the subordinate account while maintaining a single billing profile for the services.

Table E-6 Order to Change the Paying Parent with a Single Billing Profile

Action	Service Number	Service Account	Billing Account	Billing Profile
UPDATE	S1	SA1	BA2	BA2-BP2
UPDATE	S2	SA1	BA2	BA2-BP2

Figure E-5 shows the result of sending the change order to billing.

Figure E-5 Result of Order to Change the Paying Parent with a Single Billing Profile

Description of "Figure E-5 Result of Order to Change the Paying Parent with a Single Billing Profile"

Alternatively, the change order can change the paying parent for the subordinate account and assign separate billing profiles to the services. Table E-7 shows this alternative order.

Table E-7 Alternative Order to Change the Paying Parent with Multiple Billing Profiles

Action	Service Number	Service Account	Billing Account	Billing Profile
UPDATE	S1	SA1	BA2	BA2-BP2
UPDATE	S2	SA1	BA2	BA2-BP3

Figure E-6 shows the results of sending the alternative order to billing.

Figure E-6 Result of Alternative Order to Change the Paying Parent with Multiple Billing Profiles

Description of "Figure E-6 Result of Alternative Order to Change the Paying Parent with Multiple Billing Profiles"

Changing the Paying Parent for Multiple Subordinate Accounts

This example shows:

A base order that purchases one service each for two subordinate accounts
A change order that changes the paying parent for both subordinate accounts and all their services

Table E-8 shows the base order. A separate billing profile is assigned to each service.

Table E-8 Base Order for Services in Multiple Subordinate Accounts

Action	Service Number	Service Account	Billing Account	Billing Profile
ADD	S1	SA1	BA1	BA1-BP1
ADD	S2	SA2	BA1	BA1-BP2

Figure E-7 shows the results of sending the base order to billing. The services are tracked in separate balance groups that point to separate dummy /billinfo objects.

Figure E-7 Result of Base Order for Services in Multiple Subordinate Accounts

Description of "Figure E-7 Result of Base Order for Services in Multiple Subordinate Accounts"

Table E-9 shows the change order to change the paying parent for both subordinate accounts at once while maintaining separate billing profiles.

Table E-9 Order to Change the Paying Parent for Multiple Subordinate Accounts with Multiple Billing Profiles

Action	Service Number	Service Account	Billing Account	Billing Profile
UPDATE	S1	SA1	BA2	BA2-BP3
UPDATE	S2	SA2	BA2	BA2-BP4

Figure E-8 shows the results of sending the change order to billing.

Figure E-8 Result of Order to Change the Paying Parent for Multiple Subordinate Accounts with Multiple Billing Profiles

Description of "Figure E-8 Result of Order to Change the Paying Parent for Multiple Subordinate Accounts with Multiple Billing Profiles"

Alternatively, the change order can change the paying parent for the subordinate accounts and assign the same billing profile to the services. Table E-10 shows this alternative order.

Table E-10 Alternative Order to Change the Paying Parent for Multiple Subordinate Accounts with a Single Billing Profile

Action	Service Number	Service Account	Billing Account	Billing Profile
UPDATE	S1	SA1	BA2	BA2-BP3
UPDATE	S2	SA2	BA2	BA2-BP3

Figure E-9 shows the result of sending the alternative order to billing.

Figure E-9 Result of Alternative Order to Change the Paying Parent for Multiple Subordinate Accounts with a Single Billing Profile

Description of "Figure E-9 Result of Alternative Order to Change the Paying Parent for Multiple Subordinate Accounts with a Single Billing Profile"

Examples when Service-Level Balance Groups Are Disabled

This section gives examples of changing the paying parent on subordinate accounts when service-level balance groups are disabled.

Changing the Paying Parent for a Subordinate Account

This example shows:

A base order that purchases two services for a subordinate account
A change order that changes the paying parent for the subordinate account and its services

Table E-11 shows the base order. The same billing profile is assigned to both services.

Table E-11 Base Order for Services in a Subordinate Account

Action	Service Number	Service Account	Billing Account	Billing Profile
ADD	S1	SA1	BA1	BA1-BP1
ADD	S2	SA1	BA1	BA1-BP1

Figure E-10 shows the result of sending the base order to billing. The services are tracked together under the default account-level balance group.

Figure E-10 Result of Base Order for Services in a Subordinate Account

This image is described in surrounding text.

Description of "Figure E-10 Result of Base Order for Services in a Subordinate Account"

Table E-12 shows the change order to change the paying parent for the subordinate account.

Table E-12 Order to Change the Paying Parent for a Subordinate Account

Action	Service Number	Service Account	Billing Account	Billing Profile
UPDATE	S1	SA1	BA2	BA2-BP2
UPDATE	S2	SA1	BA2	BA2-BP2

Figure E-11 shows the result of sending the change order to billing.

Figure E-11 Result of Order to Change the Paying Parent for a Subordinate Account

Graphic is described in the following text.

Description of "Figure E-11 Result of Order to Change the Paying Parent for a Subordinate Account"

Changing the Paying Parent for Multiple Subordinate Accounts with Separate Billing Profiles

This example shows:

A base order that purchases one service each for two subordinate accounts
A change order that changes the paying parent for both accounts and all their services

Table E-13 shows the base order. A separate billing profile is assigned to each subordinate account.

Note:

When service-level balance groups are disabled, a parent account can only use multiple billing profiles to pay for services under separate subordinate accounts. A single subordinate account cannot have multiple billing profiles. See "Problems When Integrating Separate Billing Profiles on the Same Account" for an example of this restriction.

Table E-13 Base Order for Multiple Subordinate Accounts

Action	Service Number	Service Account	Billing Account	Billing Profile
ADD	S1	BA1	BA1	BA1-BP1
ADD	S2	SA1	BA1	BA1-BP2
ADD	S3	SA2	BA1	BA1-BP3

Figure E-12 shows the result of sending the base order to billing. Each service is tracked under the default account-level balance group for its account.

Figure E-12 Result of Base Order for Multiple Subordinate Accounts

Description of "Figure E-12 Result of Base Order for Multiple Subordinate Accounts"

Note:

The account -level balance group for the parent account (BA1) references the first billing profile that is created for that account (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-14 shows the change order to change the paying parent for both subordinate accounts using one billing profile under the new parent.

Table E-14 Order to Change the Paying Parent for Multiple Subordinate Accounts

Action	Service Number	Service Account	Billing Account	Billing Profile
UPDATE	S2	SA1	BA2	BA2-BP4
UPDATE	S3	SA2	BA2	BA2-BP4

Figure E-13 shows the result of sending the change order to billing.

Figure E-13 Result of Changing the Paying Parent for Multiple Subordinate Accounts

Description of "Figure E-13 Result of Changing the Paying Parent for Multiple Subordinate Accounts"

Because S1 was purchased directly under the parent account, it was not included in the update order and remains unchanged.

Alternatively, the order could maintain separate billing profiles for the subordinate accounts.

When service-level balance groups are disabled, you cannot transfer subordinate accounts to new billing profiles on the same paying parent account.

Problems When Integrating Separate Billing Profiles on the Same Account

This example shows:

A base order that purchases two services with separate billing profiles for one subordinate account
A resubmitted version of the order to correct errors

Table E-15 shows the base order. Each service is assigned a separate billing profile.

Table E-15 Base Order for Services with Separate Billing Profiles

Action	Service Number	Service Account	Billing Account	Billing Profile
ADD	S1	SA1	BA1	BA1-BP1
ADD	S2	SA1	BA1	BA1-BP2

When the order is sent to billing, the integration creates two dummy /billinfo objects in BRM:

DBP1 under the subordinate account (SA1) pointing the primary billing profile (BP1) on the parent account (BA1)
DBP2 under SA1 pointing to a separate billing profile (BP2) on BA1

The default account-level balance group points to the primary billing profile (BP1) on BA1.

If both services are purchased on a single order, as in Table E-15, the integration uses billing account and billing profile on the first service purchased for all the remaining services on the order. The billing account and billing profile specified on the second service are ignored. The result of sending the order to billing is the same as in Figure E-10, "Result of Base Order for Services in a Subordinate Account".

Though the order is processed successfully, it results in a mismatch in the billing profile in Siebel CRM and the /billinfo object in BRM. To prevent this mismatch, ensure that orders in Siebel CRM use a single billing profile for all services purchased for one account when service-level balance groups are disabled.

If the services are purchased on two separate orders, the order for S1 succeeds but the order for S2 fails.

The integration fails to process S2 because it is attempting to point the dummy /billinfo object for S2 to a billing profile different than the default account-level billing profile.

Table E-16 shows the revision order to resolve the failure or data mismatch by assigning S2 to BP1.

Table E-16 Resubmitted Order

Action	Service Number	Service Account	Billing Account	Billing Profile
ADD	S1	SA1	BA1	BA1-BP1
ADD	S2	SA1	BA1	BA1-BP1

After the order is processed to billing, the result is the same as in Figure E-10, "Result of Base Order for Services in a Subordinate Account".

Though the revised order is processed successfully, the dummy /billinfo object for S2 (DBP2) remains in BRM under SA1. A change order to transfer SA1 to a new parent account will fail integration. BRM requires all services of a subordinate account to be paid by the same parent, so all services of a subordinate must be transferred to the new parent together. Because DBP2 is not used by any service it will not be transferred to a new parent, causing order failure.

To resolve the failure you must manually move SA1 under the new parent in BRM so that BRM can repoint all of the dummy /billinfo objects and resubmit the change order.