Effective Date For Reversal Not Saved
Last updated on SEPTEMBER 19, 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.
An issue of reversing MBI payments from Payment Tool has been fixed with the patch 13974738.
A side issue exists when effective date of reversal (changeback date) is set in Payment tool, is not stored in BRM on the tables mentioned above. It turns out that this value is not stored in BRM (neither in table EVENT_BILLING_REVERSAL_WTRAN_T nor EVENT_BILLING_REVERSAL_CASH_T).
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