Event Types Are Not Excluded From Being Recorded In The Database (Doc ID 2057438.1)

Last updated on OCTOBER 15, 2015

Applies to:

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

Symptoms

The Oracle BRM utility load_pin_event_record_map that charge the events that do not have to be created, (event_record_map_t), doesn’t work well.
In particular, It was not possible for us to block, at the same time, the “Main Class” and “Sub Classes” events creation.

If we charge the following events, the utility go in error.
/event/audit/customer/payinfo/dd
/event/audit/customer/payinfo/invoice
/event/audit/customer/payinfo/kk
/event/audit/customer/payinfo/pp
/event/audit/customer/payinfo

In the tests it is no possible to charge six rows (Main Class” and “Sub Classes).

Cause

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