pin_ledger_report Is Generating Blank XMLs in Multischema Environment
(Doc ID 2915095.1)
Last updated on DECEMBER 16, 2022
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
In a multischema environment, pin_ledger_report tool is generating blank XML reports for pin02 to pinXX schema, post Billing and Revenue Management (BRM) 12 upgraded from 7.5 PatchSet (PS) 21.
On each schema, the user is running the following command:
$pin_ledger_report -mode export -segment .postpaid -verbose
While pin_ledger_report is executed on secondary schemas, for instance pin02/0.0.0.2, it generates the /process_audit/export_gl & /ledger_report objects in pin02/0.0.0.2. Next, for generating the XML file, it calls "gl.get_gl_accts_data" stored procedure to get the /ledger_report objects that were just generated. But instead of doing that in pin02/0.0.0.2, it uses the primary pin01/0.0.0.1.
From pin_ledger_report log, the POID is wrongly set to 0.0.0.1 instead of 0.0.0.2:
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