Pin_apply_bulk_adjustment Assigning GLID As 0 (Doc ID 1614060.1)

Last updated on JUNE 18, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 to 7.3.1.0.0 [Release 7.3.0]
Information in this document applies to any platform.

Goal

On Oracle Communications Billing and Revenue Management(BRM), 7.3.1.0.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?

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms