My Oracle Support Banner

BRM to Be Able to Decode Information in PIN_FLD_INVOICE_DATA When Contains Values With Special Characters Without Escape Character (Doc ID 2796033.1)

Last updated on APRIL 10, 2023

Applies to:

Oracle Communications Billing and Revenue Management - Version and later
Information in this document applies to any platform.


In complex enterprise environment, CDR's received by Billing and Revenue Management (BRM) include some data which contains special characters (# < > | / ).
Some of these fields are part of INVOICE_DATA which is stored in event_t table, hence when running invoicing it is failing in decoding the INVOICE_DATA because of special characters.
In order to prevent invoicing failure, an escape character can be used "\" .

However, it is not feasible to control the other fulfilment systems and restrict from sending special characters.
Also, there is a preference to avoid a supplementary customization in BRM to add escape character before loading the data in event_t .

Expectation is that BRM will be able to decode information in PIN_FLD_INVOICE_DATA also when contains values with special characters (/,#,<,>) without escape character.

Is it possible to enhance the product as such?


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.