GL Posting Does Not Support Backdating
(Doc ID 1292858.1)
Last updated on FEBRUARY 07, 2024
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 to 7.4.0.0.0 [Release 7.4.0]Information in this document applies to any platform.
Symptoms
Once the General Ledger (GL) has been posted via pin_ledger_report -mode export, Billing and Revenue Management (BRM) does not accept purchases that are backdated earlier than the posted_date.
In an enterprise solution where Siebel is taking the original order, there can be any number of reasons for backdating including latency. Backdating is an important feature in these cases. At the same time, the posting solution in BRM is desired, these should not be mutually exclusive. Currently internal BRM code is refusing to rate a purchase if the purchase is backdated earlier than the posted_t date. BRM could alleviate the issue by making that logic configurable.
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 |