INVOICE_DATA Field for Rerated Batch Usage Events Sometimes Incorrect

(Doc ID 2112633.1)

Last updated on JULY 27, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version to [Release 7.5.0]
Information in this document applies to any platform.


On : version, Rerating/Rebilling

The INVOICE_DATA field for rerated batch usage events were sometimes incorrect when the limit of 4000 bytes got exceeded which caused these rerated batch usage events not to be properly displayed on the invoice.          

The INVOICE_DATA field for these rerated batch usage events that were not properly displayed on the invoice started with "@INTEGRATE", while for other rerated batch usage events that are properly displayed on the invoice, it usually did not start with "@INTEGRATE".




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