RUMs Corrupted During Transformation To BRM
(Doc ID 2056019.1)
Last updated on AUGUST 13, 2024
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.0.0 [Release 7.5.0]Oracle Communications Pricing Design Center - Version 11.1.0.7.0 to 11.1.0.7.0 [Release 11.1.0]
Information in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------------------
* Ratable Usage Metric (RUM) are corrupted during transformation to Billing and Revenue Management (BRM).
* The following service-event map is defined in Pricing Design Center (PDC):
Account:
Event: EventBillingProductFeeCancel
RUM: OCCURRENCE
Event: EventBillingProductFeeCycle_forward_monthly
RUM: OCCURRENCE
Event: EventBillingProductFeePurchase
RUM: OCCURRENCE
TelcoGsm:
Event: EventDelayedSessionTelcoDcbData
RUM: TOTAL_VOLUME
* When load_config processes the output file, the /event/billing/product/fee/cycle/cycle_forward_monthly goes missing in the /config/rum object and gets replaced by /event/delayed/session/telco/dcb/data in the Database (DB), i.e.:
* This is due to 2 WRITE_FLDS writing the 2 different RUMs separately, but each write starting with ELEM_ID = 0.
EXPECTED BEHAVIOR
-----------------------
RUMs should get stored correctly in the BRM DB.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create the mentioned service-event maps in PDC UI
2. Submit it to Transformation Engine OR run ImportExportPricing Utility with -config object parameter
3. Check BRM DB.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |