Incorrect Value Is Added Into PIN_FLD_AR_ITEM_OBJ When ‘deferred_tax_journaling’ Is Enabled
(Doc ID 2827909.1)
Last updated on JANUARY 31, 2022
Applies to:
Oracle Communications Billing and Revenue Management - Version 12.0.0.3.0 and laterInformation in this document applies to any platform.
Symptoms
Following behavior is observed post-migration from BRM7.5 PS15 to BRM12 PS3:
With the 'deferred tax journaling' parameter set to 2 (enabled), when a usage event is inserted, it creates a new /item object which has the wrong value in PIN_FLD_AR_ITEM_OBJ field.
Example:
Because the AR_ITEM_OBJ_TYPE field is not null, billing does not use this event to calculate taxes.
If the PIN_FLD_AR_ITEM_OBJ is updated to null:
update item_t set ar_item_obj_db = 0, ar_item_obj_type = null where poid_id0 = 2600544765;
Then the billing takes this event to calculate the taxes correctly. The problem is in the REL procedure in the database.
With the parameter 'deferred tax journaling' setting to 0 (disabled), the taxes are calculated correctly.
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 |
Cause |
Solution |
References |