My Oracle Support Banner

Pin_ledger_report Generates Output Having Different/Incorrect File Format (Doc ID 2488717.1)

Last updated on MARCH 17, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.21.0 and later
Information in this document applies to any platform.

Symptoms

On : 7.5.0.21.0 version, General Ledger (GL)

ACTUAL BEHAVIOR
--------------------
Observed that pin_ledger_report binary is updated in PS21. After upgrading BRM from PS17 to PS21, pin_ledger_report utility is generating output files having different file format in PS21 as compared to PS17. In PS21, the output file does not contain important information like the schema details which is essential for customization (in multi db architecture) to identify to which schema the output file belongs.

Issue is with output FILE NAME generated getting generated for each revenue type.

PS17 output file Name format: GL_report_be_20181201_20181101_0.0.0.x-123456789-1.xml
PS21 output file Name format: GL_report_be_20181201_20181101_1.xml

One can clearly see difference in OOTB file NAMES generated upon execution of pin_ledger_report with -export mode in PS17 and PS21 environments.

PS17: “GL_report_be_20181201_20181101” + ”_” + ”0.0.0.x-123456789-1” + ”.xml”
PS21: “GL_report_be_20181201_20181101” + ”_”1” + ”.xml”

This complete string ”0.0.0.x-123456789-1” (Database_Number-Sequence_id-File_number) are missing in PS21 output files and just replaced with “1” (file_number).

EXPECTED BEHAVIOR
-----------------------
“GL_report_be_20181201_20181101” + ”_” + ”0.0.0.x-123456789-1” + ”.xml”

Steps
--------
pin_ledger_report -mode export -segment .postpaid -verbose

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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