Data Share Discount Being Mis-recorded in Journal_t Impacting Revenue Reporting
(Doc ID 2228976.1)
Last updated on MARCH 15, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On : 220.127.116.11.0 version, General Ledger (GL) - GL
In Production, Revenue Management team indicated that revenue for GLID (Data) dropped in December by approx. $330,000. It should have remained the same or increased, when compared to November. Since data sharing was launched to consumers around this time frame, the user started looking at Journal T entries for Data Share customers.
The Discount Amount applied to a service, to give the customer their data free, has been recorded in Journal_T in the "Db Ar Disc Amt" field, while the offsetting charge that the discount is going against is not recorded anywhere, for Resource ID 124. As a result, all of the Discounts being applied to Data Share customers have the potential to make Revenue appear lower than normal.
1) Performed plan change from non-shared plan to shared plan
2) Authorized the data for 50MB
3) Reauthorized additional 50MB
4) Performed stop accounting for total 100MB
Rating was successful and currency charged was zero as it was consumed from shared bucket.
5) Verified /journal entries for this /item/st_data for currency resource and found $3 in "Db Ar Disc Amt"
It was missing $3 charge in any other column.
And, the /journal entry for currency resource with GLID 0 contained all zero's in all the columns, it was not clear about the purpose of having this entry.
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
|Questions and Answers|
|Why revenue reports were showing low revenue from above scenario result?|