Pin_apply_bulk_adjustment Assigning GLID As 0
(Doc ID 1614060.1)
Last updated on MARCH 20, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 7.3.0]
Information in this document applies to any platform.
On Oracle Communications Billing and Revenue Management(BRM), 126.96.36.199.0 version, 'pin_apply_bulk_adjustment' utility is assigning GLID as 0, when wrong combination of version_id and reason_id are passed.
What is Oracle's suggestion to handle the scenario in which the requirement is to define a GLID (say 1234567) to be used in case wrong version & reason_id is sent in adjustment.
Can it be handled through some configuration or some code change is required?
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