B Support for Rate Tiers and Effectivity

Table B-1 depicts the support for rate tiers and effectivity.

Table B-1 Support for Rate Tiers and Effectivity

Feature Promotion Account Product Bundle Product Tier 1 Balance Impact Tier 2 Account Discount

Rate defined in Oracle Product Hub?

No

Yes

No*2

Yes

Yes

Yes

Yes

NA*5

Rate sync'd to Billing and Revenue Management?

No

Yes

No

Yes

Yes

Yes

Yes

NA

Rate sync'd to Siebel CRM?

No

Yes

No

Yes

No*3

Yes

No*3

NA

Revision defined in Oracle Product Hub?

Yes

Yes

Yes

Yes

NA

NA

NA

Yes

Revision sync'd to Billing and Revenue Management?

No

No

No

No

NA

NA

NA

No

Revision sync'd to Siebel CRM?*1

Yes

Yes

Yes

Yes

NA

NA

NA

Yes*6

Effectivity defined in Oracle Product Hub (absolute + relative)

Yes

Yes

Yes

Yes

Yes

Yes (Only absolute)

Yes

Yes

Effectivity sync'd to Billing and Revenue Management (absolute + relative)

No

Yes

No

Yes

Yes

Yes (Only absolute)

Yes

Yes

Absolute effectivity sync'd to Siebel CRM

No

Yes

Yes

Yes

Yes

NA*4

Yes

Yes

Relative effectivity sync'd to Siebel CRM (Only Rates and Balance Impact)

NA

NA

NA

NA

No

No

No

NA


There is no one-to-one mapping between revisions of items in Oracle Product Hub and versions of products in Siebel CRM.

The pricing for the bundles is calculated as the sum of the charges for the component products. If you decide not to use the recommended Communications Product Definition methodology on bundles, the pricing can be specified on the item that represents the bundle.

For more information about the communications-product-definition methodology, see the Oracle Application Integration Architecture Oracle Communications Order to Cash Integration Pack Implementation Guide.

The rate tier information is not synchronized to Siebel CRM. The rate tier only stores the price specified in the balance impact attribute group (AG) associated with the rate tier as the list price on the pricelist line.

The balance impact effectivity is defined only for non-currency resources and it is relative to the purchased product date.

Only discount models can be associated for discount. Only the name of the discount model is associated to the discount in Oracle Product Hub and synchronized to Billing and Revenue Management (BRM). The actual definition is enriched in BRM.

Discounts are synchronized as products to Siebel CRM.