6 Oracle Product Master Data Management Integration Option for PDC
This chapter provides an overview of the Oracle Product Master Data Management Integration Pack Option for Oracle Communications Pricing Design Center (PDC), supported features, and assumptions and constraints, and specifically, describes the process flows, interfaces, and integration services required in this integration.
Overview
Oracle Product Hub publishes products, discounts, and sponsorships offerings in batch to various systems, such as Siebel CRM, Pricing Design Center, and Design Studio. The Oracle Application Integration Architecture (Oracle AIA) Product Master Data Management pre-built Integration receives this input, prepares payload for each system, and invokes the appropriate Pricing Design Center services.
Products offerings are synchronized from Oracle Product Hub to Pricing Design Center and auto-promoted to Oracle Communications Billing and Revenue Management (BRM). Once the product is successfully committed to the BRM database, it publishes the message to BRM AQ. The integration then updates the Oracle AIA Cross reference with the BRM Identifier. If the offerings are enriched in Pricing Design Center, then Pricing Design Center administrators manually submit these items from Pricing Design Center to BRM. When these objects are created or updated successfully in BRM, a message is automatically published to indicate successful transaction.
Integration Process Flow
Product offerings are driven by business needs and implemented by product administrators. These offerings are defined in Oracle Product Hub or other third party product master application and synchronized with edge systems, such as Siebel CRM and BRM. Product managers validate each product offering before releasing the products in Pricing Design Center.
Figure 6-1 Process flow from Oracle Product Hub to BRM through Pricing Design Center and Oracle AIA
Description of ''Figure 6-1 Process flow from Oracle Product Hub to BRM through Pricing Design Center and Oracle AIA''
Here is the business process flow from Oracle Product Hub to Pricing Design Center:
-
Product, discounts, and sponsorships are mastered in Oracle Product Hub.
-
Oracle Product Hub batch publishes product, discount, and sponsorship definitions to Oracle AIA.
-
Product Master Data Management Pre-built Integration Pack for Siebel CRM synchronizes product, discount and sponsorship offerings to Siebel CRM and creates Oracle AIA cross-references.
-
A Product Master Data Management Pre-built Integration Pack for Pricing Design Center Oracle AIA connector synchronizes the product, discount and sponsorship offerings to Pricing Design Center and creates Oracle AIA cross-references.
-
Data is enriched in Pricing Design Center using the transformation engine to synchronize the product, discount and sponsorship offerings to BRM.
-
After the product, discount and sponsorship offerings are synchronized in BRM, the BRM identifiers are updated in Oracle AIA cross-references.
Synchronization of Oracle Product Hub and Pricing Design
The Oracle Product Hub to Pricing Design Center synchronization flow lets you create product offerings in Oracle Product Hub and publish them to Pricing Design Center using the Oracle AIA Product Master Data Management pre-built integration.
The Oracle AIA Product Master Data Management pre-built integration receives the published items from Oracle Product Hub and sends them to Pricing Design Center by invoking Pricing Design Center services.
Figure 6-2 shows synchronization between Oracle Product Hub and Pricing Design Center.
Figure 6-2 Oracle Product Hub to Pricing Design Center Synchronization
Description of ''Figure 6-2 Oracle Product Hub to Pricing Design Center Synchronization''
Integration synchronizes items from Oracle Product Hub to Pricing Design Center as follows:
-
Product administrators create or edit products/Discounts/ChargeShares in Oracle Product Hub and publish the batch to Oracle AIA by selecting the target systems.
-
SyncItemListPIMEventConsumer consumes the message and invokes SyncItemListPIMReqABCSImpl
-
SyncItemListPIMReqABCSImpl queries Oracle Product Hub for the list of target systems with which the message needs to be synced using QueryItemListPIMAdapter.
-
After identifying the target system, SyncItemListPIMReqABCSImpl calls Item EBSV2 service to route the message to target systems based on their system IDs.
-
Since the message is intended for Pricing Design Center, ItemEBS routes the message to SyncItemListPDCProvABCSImpl.
-
SyncItemListPDCProvABCSImpl transforms the SyncItemListEBM message into Pricing Design Center PricingObject and sends it to Pricing Design Center.
-
Once successful, SyncItemListPIMReqABCSImpl calls PriceListEBSV2 service to route the message to all the target systems based on their system IDs.
-
Since the message is intended for Pricing Design Center, PriceListEBS routes the message to SyncPriceListPDCProvABCSImpl which updates all the pricing related information such as rate to Pricing Design Center.
-
SyncPriceListPDCProvABCSImpl transforms the SyncPriceListEBM message into Pricing Design Center PricingObject and sends it to Pricing Design Center.
-
Once successful, the success message is sent to SyncItemListPIMReqABCSImpl, which in turn updates Oracle Product Hub with the message status. In case of failure, an error message with all required details is sent back to Oracle Product Hub.
-
Once the product/discount/sponsorship items are synced to Pricing Design Center successfully, they are auto synced to BRM.
-
After the product/discount/sponsorship items are committed to BRM database successfully, BRM send a message to the AQ.
-
Corresponding AQ Consumer picks up the message and populates the Xref (ITEM_ITEMID.xref) with the relevant values.
When a sponsorship object is synced from Oracle Product Hub to Pricing Design Center, Oracle AIA integration creates a dummy sponsorship model (charge share model) in Pricing Design Center which is submitted to BRM automatically. Any enhancements to the sponsorship model is done from Pricing Design Center and submitted to BRM.
Other information such as description, minimum, maximum, and quantity has to be enhanced in Oracle Product Hub. When sponsorship details are changed (other than model), Oracle AIA integration updates Pricing Design Center and BRM.
For information on Pricing Design Center to BRM synchronization see, ”About Pricing Design Center Application Architecture”, Oracle Communications Pricing Design Center User's Guide.
Integration Services
The integration services used by the integration option are the following:
-
SyncItemListPDCProvABCSImpl
-
SyncPriceListPDCProvABCSImpl
-
CreateProductXrefBRMAQ
-
CreateSponsorshipXrefBRMAQ
-
CreateDiscountXrefBRMAQ
SyncItemListPDCProvABCSImpl
This provider ABCS synchronizes item list from Oracle Product Hub to Pricing Design Center.
SyncPriceListPDCProvABCSImpl
This provider ABCS synchronizes pricelist from Oracle Product Hub to Pricing Design Center.
CreateSponsorXrefBRMAQ
This process creates sponsorship items in the cross-reference files. When a sponsorship item is synced from Oracle Product Hub, Pricing Design Center integration spoke creates sponsorship with details. Pricing Design Center provides web service for creating the sponsorship offering object.
Terminology Mapping Between Pricing Design Center and BRM
Table 6-1 lists common terms and description used in Pricing Design Center and BRM:
Table 6-1 Mapping Between BRM and Pricing Design Center Terms
| BRM | Pricing Design Center |
|---|---|
|
ChargeShare Model |
Charge share |
|
ChargeShare |
Charge share offer |
|
Deal |
Bundle |
|
Discount model |
Discount |
|
Discount |
Discount offer |
|
EBal(n) discount expression |
Variable(n) discount expression |
|
EVAL("function_name") discount expression |
Function("function_name") discount expression |
|
Plan |
Package |
|
Plan list |
Package list |
|
Product |
Charge offer |
|
Rate plan |
Charge |
|
Rate plan selector |
Charge selector |
|
Resource |
Balance element |
|
Subscription group |
Service |
Pre-requisites for Multi-BRM Setup
The following are the pre-requisites whenever the multi-BRM setup is used:
-
Only one Pricing Design Center environment can be associated with one BRM. For two BRM environments, set up two Pricing Design Center environments.
-
For integration using two Pricing Design Center environments, enter the values as provide PDC_02 and PDC_03 in the drop down of the destination values on the Destination System Specification page. Similarly, enter the values as PDC_02 and PDC_03 when publishing items.
-
Add PDC_02 and PDC_03 in the systems page in Oracle AIA and restart server.
-
Add the PDC_02 and PDC_03 columns and values in the respective DVMs and cross-references (XREFS) with same values as mentioned in PDC_01.
-
Add the PDC_02 and PDC_03 endpoint URL in AIAConfigurationProperties.xml.
-
In the AIAConfigurationProperties.xml, change the default.BRMID to BRM_02 or BRM_03 as required. For a single BRM instance, use BRM_01.
Since Oracle Product Hub does not send all the discount/ChargeShare model information, the pre-built integration include these values by default (Table 6-2) as they are mandatory columns in Pricing Design Center for creating models.
Table 6-2 Default Discount/ChargeShare Element Values
| Element | Discount | Sponsorship |
|---|---|---|
|
pricingProfileName |
Standard Discount |
ChargeSharing |
|
priceListName |
Default |
Default |
|
Default |
0 |
0 |
|
endDate |
Inf |
Inf |
|
applicableChargeAndQuantity |
REMAINING_CHARGE |
NA |
|
name |
Pricing |
Pricing |
|
distributionMethod |
FROM_BAL_IMPACT |
FROM_BAL_IMPACT |
|
tierBasis |
FALSE |
FALSE |
|
lowerBound |
0.0 |
0.0 |
|
upperBound |
NO_MAX |
NO_MAX |
|
price |
0.0 |
0.0 |
|
unitOfMeasure |
NONE |
NONE |
|
balanceElementNumCode |
840 |
840 |
|
priceType |
GRANT |
GRANT |
|
startValidityMode |
IMMEDIATE |
IMMEDIATE |
|
endValidityMode |
RELATIVE_TO_START |
RELATIVE_TO_START |
|
relativeStartOffset |
-1 |
-1 |
|
relativeEndOffset |
1 |
1 |
|
relativeStartOffsetUnit |
BILLING_CYCLE |
BILLING_CYCLE |
|
relativeEndOffsetUnit |
BILLING_CYCLE |
BILLING_CYCLE |
Assumptions and Constraints
Assumptions and constraints in Oracle Product Hub to Pricing Design Center integration are:
-
Pricing Design Center does not allow creating products with same rate plan name.
-
Unlike BRM integrations, time models are mastered in Pricing Design Center for usage events. Oracle AIA integration does not send objects related to time models.
-
Although, Pricing Design Center provides an alternate method to create and update products, discounts, and sponsorship objects synced from Oracle Product Hub, the recommended method is to use the CreateSubmit and UpdateSubmit APIs to ensure proper updates to BRM.
-
Product item information coming from Oracle Product Hub includes rate plan, rate data, balance impact information. Discount item information coming from Oracle Product Hub include discount, discount model information. Sponsorship item information coming from Oracle Product Hub includes sponsorship, sponsorship model information.
-
Oracle Product Hub week and time ranges are applicable to only usage rate plans in Pricing Design Center.
-
Time model object is applicable only to usage rate plan in Pricing Design Center. While time models are enhanced in the Pricing Design Center, the Oracle AIA integration does not send the day ranges and time ranges to Pricing Design Center. For usage events, all rate plans are mastered in Pricing Design Center. The Oracle AIA integration sends rate plan objects with rate tier and balance impact to Pricing Design Center. Time models need to be enhanced in Pricing Design Center.
-
Even though Oracle Product Hub accepts the same minimum and maximum quantity values for the same rate plan in the balance impact, Pricing Design Center restricts same quantity tiers in the date ranges.
-
As part of master event definition, changes are required on the event details and not for rate plans and rate tiers.
-
Reuse of rate plans is supported by Pricing Design Center. Reuse of existing rate plans in different products is not.
-
Only basic information is synced to Pricing Design Center for usage based rate plan. You need to further enhance the time model part and other information in the rate plan if required. You cannot update the same rate plan information from Oracle Product Hub to Pricing Design Center as any enhancement done for usage rate plans will be lost.
-
While sending payload to Pricing Design Center, rate plan (charge) information is sent as an object to Pricing Design Center in the same payload along with charge offering object. This charge rate plan is unique within the charge offering.
-
Pricing Design Center IDs do not change when products are migrated from one Pricing Design Center environment to another.
-
Pricing Design Center accepts only default price list values in the charge offering and charge rate plans.
-
All offers are subscription profiles. This applies to onetime and recurring charges as well. However, for usage and discounting, you can use different profiles.