Skip Headers
Oracle® Application Integration Architecture Oracle Product Master Data Management Integration Implementation Guide
Release 11.2

Part Number E38142-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

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

-- Rate defined in OPH? Rate sync'd to BRM? Rate sync'd to SBL? Revision defined in OPH? Revision sync'd to BRM? Revision sync'd to Siebel? *1 Effectivity defined in OPH? (absolute + relative) Effectivity sync'd to BRM? (absolute + relative) Absolute effectivity sync'd to Siebel? Relative effectivity sync'd to Siebel? (Applies only to Rates and Balance Impact)

Promotion

No

No

No

Yes

No

Yes

Yes

No

Yes

N/A

Product (Acc level product/SSB only)

Yes

Yes

Yes

Yes

No

Yes

Yes

Yes

Yes

N/A

Bundle

No *2

No

No

Yes

No

Yes

Yes

No

Yes

N/A

Product

Yes

Yes

Yes

Yes

No

Yes

Yes

Yes

Yes

N/A

Tier 1

Yes

Yes

No *3

N/A

N/A

N/A

Yes

Yes

Yes

No

Balance Impact

Yes

Yes

Yes

N/A

N/A

N/A

Yes (Only absolute)

Yes (Only absolute)

N/A *4

No

Tier 2

Yes

Yes

No *3

N/A

N/A

N/A

Yes

Yes

Yes

No

Balance Impact

Yes

Yes

Yes

N/A

N/A

N/A

Yes (Only absolute)

Yes (Only absolute)

N/A*4

No

Discount (Acc level discount only)

N/A *5

N/A

N/A

Yes

No

Yes *6

Yes

Yes

Yes

N/A


There is no one-to-one mapping between revisions of items in OPH and versions of products in Siebel.

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 Communications Order to Cash Integration Pack for Siebel CRM, Oracle Communications Order and Service Management, and Oracle Communications Billing and Revenue Management 11.1 - Implementation Guide.

The rate tier information is not synchronized to Siebel. Only the price specified in the balance impact attribute group (AG) associated with the rate tier is stored 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 OPH and synchronized to BRM. The actual definition is enriched in BRM.

Discounts are synchronized as products to Siebel.