AR_GROSS_AMT Fields Populated for Discount When Ledger Is Running
(Doc ID 869823.1)
Last updated on MARCH 27, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
The expected system behavior when the pin_ledger_report is executed would be for the discount amount to be populated either CR_AR_GROSS_AMT and DB_OFF_GROSS_AMT only, or DB_AR_GROSS_AMT and CR_OFF_GROSS_AMT only in the LEDGER_REPORT_ACCTS_T table.
Steps To Reproduce:
- A normal discount of 5% is tied to a monthly recurring product (with CYCLE_FEE event charged at $50 per month).
The discount is tied to a GLID but the recurring event is not tied to a GLID.
- An account is created, and the plan is purchased.
- The account is billed, and pin_ledger_report ('Billed') is run:
$pin_ledger_report -start 08/18/2011 -end 09/19/2011 -type billed -detail -report abc.txt
- The amount given by the discount is logged in the LEDGER_REPORT_ACCTS_T table, but with all four fields populated:
CR_AR_GROSS_AMT, DB_AR_GROSS_AMT, CR_OFF_GROSS_AMT, DB_OFF_GROSS_AMT
And the ledger report will be generated as below (part of the report is displayed here):
DEBIT ACCOUNT DEBIT CREDIT CREDIT ACCOUNT DEBIT CREDIT
GROSS monthly.debit 5.0000000 5.0000000 monthly.credit 5.0000000 5.0000000
NET monthly.debit 0.0000000 5.0000000 monthly.credit 5.0000000 0.0000000
DISC monthly.credit 5.0000000 0.0000000 monthly.debit 0.0000000 5.0000000
TAX -- N/A -- 0.0000000 0.0000000 -- N/A -- 0.0000000 0.0000000
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