Discounting IMPACT_TYPE Changed For Positive Discount
(Doc ID 2396197.1)
Last updated on OCTOBER 02, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On : 18.104.22.168.0 version, Account Migration Manager
For the events ,which have (+) ve discounted impact through Discounting, IMPACT_TYPE gets populate as 1 (PIN_IMPACT_TYPE_RATED) instead of 128 (PIN_IMPACT_TYPE_DISCOUNT).
This feature is introduced in Post 7.5 PS6 . ( Support Article is: Wrong IMPACT_TYPE For Discount Balance Impacts After 7.5 PS16 Upgrade (Doc ID 2352776.1))
In 7.4 PS7, due to IMPACT_TYPE set as 128, following were the fields set in /journal object for a specific Use case:
Since there is a need to match the GL amount across 2 systems, thinking to update the IMPACT_TYPE back to 128 in Realtime pipeline post discounting (since events impacted are /event/billing/cycle/discount for us), But while doing the changes observed that FCT_Discount is not writing IMPACT_TYPE in discount packet container field.
Question: Is there a way to change IMPACT_TYPE of Balance impact for positive discount back to 128 Or is there any solution for IMPACT_TYPE gets populated in discount packet post FCT_Discount in realtime pipeline?
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