GL Does Not Pick Items Which Backdate More Than One Accounting Cycle
(Doc ID 1403854.1)
Last updated on OCTOBER 17, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
If one backdates a purchase for more than one accounting cycle, it is currently setting item effective_t to the next Billing Day of Month (DOM) (from the backdated date).
The item effective_t should be set to posted_t of the ledger report (DATA_LEDGER_REPORT_T.POSTED_T). Otherwise, these backdated items will not be picked up by General Ledger (GL) reporting.
Steps to Reproduce:
1) On Nov 3, run pin_ledger_report export.
2) On Nov 3, create account and backdate purchase a one-time purchase fee on Sep 6.
Expect: The backdated item effective_t be set to Nov 3.
Actual: The backdated item effective_t being set to Oct 3.
3) On Nov 4, run pin_ledger_report export.
Expect: The backdated item be picked up in GL.
Actual: The backdated item does not show up in the GL.
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 |
Cause |
Solution |
References |