Last updated on SEPTEMBER 26, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 7.4.0]
Information in this document applies to any platform.
It was known that MOD_T is the BRM system column which gets modified (with latest timestamp) whenever the BRM object is added/modified. Based on this assumption, a custom ETL (Extraction) tools was designed, which pulls data from BRM to Datawarehouse using the mod_t value. However, the assumption doesn't seem to be correct, as many records getting modified without changing the mod_t specially /bill object. Because of this there are data discrepancies between BRM and Datawarehouse.
Scenario: If bill gets created on 12/26, and received the check payment and allocated to bill on 1/10 then one would expect the /bill object mod_t to be 1/10. But in reality, the /bill object mod_t still is shown as 12/26, while the /item mod_t is updated as 1/10.
So one would doubt that whether there could be other cases as well where BRM OOB doesn't update the mod_t.
1. On 12/26, create invoice account, purchase a product and create a bill of $108.38.
2. Read /bill object details
3. Read /item/cycle_forward object details
4. On 1/10, submit a payment check of $100.
5. Allocate the $100 payment to the bill.
6. Read the same /bill object and /item_cycle_forward object.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms