GL Posting Does Not Support Backdating
Last updated on SEPTEMBER 26, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 7.4.0]
Information in this document applies to any platform.
***Checked for relevance on 11-12-2013***
Once the GL has been posted via pin_ledger_report -mode export, 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 we want to be able to use the posting solution in BRM, 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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms