All AR_GROSS_AMT Fields Are Populated For Discount When Ledger Is Run (Doc ID 869823.1)

Last updated on SEPTEMBER 15, 2016

Applies to:

Goal

The expected system behavior when the pin_ledger_report is executed would be for the discount amount to populate 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: 

1. 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.
2. An account is created, and the plan is purchased.
3. 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
4. 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):

Solution

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