| 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-03 |
|
|
PDF · Mobi · ePub |
This appendix provides information about the Move, Add, Change, Disconnect (MACD) line actions that are supported by the order lifecycle management (OLM) Bill Fulfillment Order process integration for a given product type. Also discussed is how OLM Bill Fulfillment Order communicates changes to billing for attributes on change orders (action of UPDATE (for service bundle and its components)) for a given product type.
This appendix contains the following sections:
OLM Bill Fulfillment Order process integration supports the MACD line actions listed in Table D-1 for a given product type.
| Product Type | Add | Delete | Suspend | Resume | Update | Move-Add | Move-Delete |
|---|---|---|---|---|---|---|---|
|
-- |
-- |
-- |
-- |
-- |
-- |
See Table B for a list of attributes |
-- |
|
Marketing Bundle ('Promotion' in Siebel, no representation in Oracle Communications Billing and Revenue Management (Oracle BRM) |
Yes |
Yes |
Not Applicable. Does not affect purchased bundle in Oracle BRM. |
Not Applicable. Does not affect purchased bundle in Oracle BRM. |
Yes |
Xref updated to reflect new Siebel Customer Relationship Management (Siebel CRM) asset. |
Ignored other than to determine original Oracle BRM asset. |
|
Service Bundle |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes. Same as UPDATE with communicating changes to line attributes. |
Ignored other than to determine original Oracle BRM asset. |
|
Service Bundle Component - Billing Subscription product (applies to service) |
Yes. Can communicate price/discount override as part of this action. |
Yes |
Not supported by either Siebel or Oracle BRM, hence ignored by Billing Integration. |
Not supported by either Siebel or Oracle BRM, hence ignored by Billing Integration. |
Yes |
Yes. Same as UPDATE with communicating changes to line attributes. |
Ignored other than to determine original Oracle BRM asset. |
|
Service Bundle Component - Billing Discount product (applies to service) |
Yes |
Yes |
Not supported by either Siebel or Oracle BRM, hence ignored by Billing Integration. |
Not supported by either Siebel or Oracle BRM, hence ignored by Billing Integration. |
Yes. Same as UPDATE with communicating changes to line attributes. |
Yes |
Ignored other than to determine original Oracle BRM asset. |
|
Service Bundle Component - Billing Item product (applies to service). Example: One-Time charge |
Yes. Can communicate price/discount override as part of this action. |
Not Applicable, because no asset or purchased product instance is created. |
Not Applicable, because no asset or purchased product instance is created. |
Not Applicable, because no asset or purchased product instance is created. |
*Not Applicable, because no asset or purchased product instance is created. |
Not Applicable, because no asset or purchased product instance is created. |
Not Applicable, because no asset or purchased product instance is created. |
|
Billing Subscription product (applies to account) |
Yes. Can communicate price/discount override as part of this action. |
Yes |
Yes |
Yes |
Yes |
Ignored |
Ignored |
|
Billing Discount (applies to account) |
Yes |
Yes |
Yes |
Yes |
Yes |
Ignored |
Ignored |
|
Billing Item product (applies to an account). Example: Penalty charge. |
Yes. Can communicate price/discount override as part of this action. |
Not Applicable, because no asset or purchased product instance is created. |
Not Applicable, because no asset or purchased product instance is created. |
Not Applicable, because no asset or purchased product instance is created. |
*Not Applicable, because no asset or purchased product instance is created. |
Ignored |
Ignored |
Note:
* If a line is billing-initiated and a revision is processed for a service-level product of type Item, then pricing information and billing dates can change. If a line is billing-initiated and a revision is processed for an account-level product of type Item, then Billing Account, Bill Profile, Promotion Reference, Pricing Information, and Billing Dates can change.
OLM Bill Fulfillment Order process integration communicates changes to billing for the attributes on change orders (action of UPDATE (for service bundle and its components)) for a given product type, as shown in Table D-2.
Note:
Attributes may be updated on a revision and a change order, unless comments indicate otherwise.
| Product Type | Service Acct (transfer) | Billing Account and Billing Profile | Pricing Info | Promotion Ref | Service ID | F&F List Ref | Billing Dates and End Date | Comments |
|---|---|---|---|---|---|---|---|---|
|
Marketing Bundle (Promotion in Siebel, no representation in Oracle BRM |
NA |
Yes For Billing Account, see note 4 |
NA See note 1 |
NA |
NA |
NA |
Yes See note 3 |
The billing interface creates purchased bundle instances under billing accounts in Oracle BRM based on promotion lines. The purchase date on promotion lines is used as the start effective date for the bundle instance. When a billing account on a promotion line is updated to a different one, the purchased bundle instance is repointed to the new billing account. Billing Profile is irrelevant for promotions. Updates to a billing account on a revision or a change order result in the bundle instance being repointed to the new billing account. Updates to a purchase date on a revision result in the start effective date on the bundle instance being reset |
|
Service Bundle |
NA See note 2 |
Yes |
NA |
NA |
Yes |
NA |
NA |
No pricing on service bundle itself. Pricing is on service bundle components. A service can be transferred from one account to another provided it is the only service in a balance group and that balance group is not an account-level default balance group. Because this release supports only account-level balance groups, service transfers fail. |
|
Service Bundle Component - Billing Subscription product (applies to service) |
NA |
NA |
Yes |
Yes |
NA |
NA |
Yes |
When subscription product is bundled in a service bundle. Service Acct, Billing Acct/Billing Profile, & Service Identifier - Integration looks only at service bundle line for these attributes. Promotion reference changes is communicated to billing. The purchased product instance is repointed to the new bundle instance in billing. Billing Dates - Cannot be reset using change orders. Cycle Start and Usage Start dates can be reset using revisions on billing initiation, if the dates that were previously set are not current. In two-phase billing, when Cycle Start and Usage Start dates have been set using billing initiation, they can be reset using billing fulfillment if the dates that were previously set are not current. End dates can be updated by change orders (promotion upgrade/downgrades) that change duration for products/discounts. |
|
Service Bundle Component - Billing Discount product (applies to service) |
NA |
NA |
NA |
Yes |
NA |
NA |
Yes |
When discount is bundled in a service bundle. Discount products are not priced. Service Acct, Billing Acct/Billing Profile and Service Identifier - Integration looks only at Service bundle line for these attributes. Promotion reference changing is communicated to billing. The purchased discount instance is repointed to the new bundle instance in billing. Billing Dates cannot be reset using change orders. Cycle Start and Usage Start dates can be reset using revisions on billing initiation if the dates that were previously set are not current. In two-phase billing, when cycle start and usage start dates have been set using billing initiation, they can be reset using billing fulfillment if the dates that were previously set are not current. End dates can be updated by change orders (promotion upgrade and downgrades) that change duration for products and discounts. |
|
Service Bundle Component - Billing Item product (applies to service). |
NA |
NA |
Yes |
NA |
NA |
NA |
Yes |
Example: Onetime Charge. No purchased product instance, hence no change orders. Pricing information, Promotion, and Quantity can be updated only on new purchase revisions. Billing dates or end date - Cannot be reset using change orders. In two-phase billing, when billing dates have been set using billing initiation, they can be reset using billing fulfillment if the dates that were previously set are not current. |
|
Service Bundle Component - Special Rating product (applies to service). |
NA |
NA |
NA |
NA |
NA |
Yes |
NA |
On a change order, change in list reference results in list values being updated to new values from new F&F list. As delivered, the integration does not check for changes to the Special Rating List reference on revision orders when the list product has been billing-initiated. The assumption is that for wireless services (that F&F is targeted toward) no fulfillment latency exists between provisioning and billing and therefore they do not undergo two-phase billing. For more information, see Section 3.3.12, "Supporting Friends and Family." |
|
Billing Subscription product (applies to account) |
NA See comments |
Yes |
Yes |
Yes |
NA |
NA |
Yes |
Subscription product that is not bundled into a service bundle. Service Acct - Oracle BRM does not support transferring account-level product from one account to another. Siebel CRM disallows this change. Promotion reference changing is communicated to billing. The purchased product instance is repointed to the new bundle instance in billing. Billing Dates - Cannot be reset using change orders. Cycle Start and Usage Start dates can be reset using revisions on billing initiation if the dates that were previously set are not current. In two-phase billing, when Cycle Start and Usage Start dates have been set using billing initiation, they can be reset using billing fulfillment if the dates that were previously set are not current. End dates can be updated by change orders (promotion upgrade and downgrades) that change duration for products and discounts. |
|
Billing Discount (applies to an account) |
NA See Comments |
Yes |
NA |
Yes |
NA |
NA |
Yes |
When discount is not bundled in a service bundle. Discount products are not priced. Service Acct - Oracle BRM does not support transferring account-level products from one account to another. Siebel CRM disallows this change. Promotion reference changing is communicated to billing. The purchased discount instance is repointed to the new bundle instance in billing. Billing dates - Cannot be reset using change orders. Cycle Start and Usage Start dates can be reset using revisions on billing initiation if the dates that were previously set are not current. In two-phase billing, when Cycle Start and Usage Start dates have been set using billing initiation, they can be reset using billing fulfillment if the dates that were previously set are not current. End dates can be updated by change orders (promotion upgrade/downgrades) that change duration for products/discounts. |
|
Billing Item product (applies to an account). |
NA |
Yes |
Yes |
NA |
NA |
NA |
Yes |
Example: Penalty. No purchased product instance, hence no MACD. Billing Acct/Profile, Pricing info, Promotion reference, can be changed on revisions. Service Acct - Oracle BRM does not support transferring account-level products from one account to another. Siebel CRM disallows this change. Billing dates or end date - Cannot be reset using change orders. Cycle Start and Usage Start dates can be reset using revisions on billing initiation, if the dates that were previously set are not current. In two-phase billing, when Cycle Start and Usage Start dates have been set using billing initiation, can be reset using billing fulfillment if the dates that were previously set are not current. |
Pricing information: This includes selling price, pricing commit type, dynamic discount method, discount amount, and discount percent.
Because this release supports only account-level balance groups, and Oracle BRM disallows transferring a service pointing to the account-level balance group. This fails.
Billing dates: This refers to purchase date, cycle start date, and usage start date.
With Oracle BRM 7.4: Billing profile change alone, which results in the balance group being repointed to a different bill-info, is not supported. In the case of a nonpaying subordinate account, changing the paying parent (billing account and billing profile) is supported.
|
 Copyright © 2001, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
