My Oracle Support Banner

AMOUNT_DEFERRED Is Incorrectly Derived During Manual Re-Rating Using Pin_event_extract And Backout Pipeline (Doc ID 1148633.1)

Last updated on MARCH 13, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version to [Release 7.3.0]
Information in this document applies to any platform.
***Checked for relevance on 28-Oct-2013***


Re-rated events have incorrect amount_deferred attribute set within their balance impacts for events with deferred taxation.
Balance impacts for re-rating events, which were identified as a shadow adjustment have incorrect sign for the amount_deferred attribute (adding the charge to the total sum instead of subtracting it).

Selected balance impact from the original event

Consider another scenario reported with the same issue :

Scenario :

Test case 1

Jun 15th : account creation (bdom = 15)
Jul 16th : accounting + billing
Jul 17th : rating usages worth total amount 0.833
Jul 17th : cancelling all the usages using Backout pipeline
Jul 18th : rating usages again worth total amount 0.833
Aug 18th : accounting + billing

Test case 2

Jun 15th : account creation (bdom = 15)
Jul 16th : accounting + billing
Jul 18th : rating usage worth amount 0.833
Aug 18th : accounting + billing

Question :

What is the reason for the above behavior and how can one get the correct tax calculation in Test case 1 ?


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.