SQL Mapping Of /event Class Is Obsolete In BRM Documentation (Doc ID 1519111.1)

Last updated on SEPTEMBER 24, 2016

Applies to:

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

Symptoms

SQL mapping of /event class is obsolete in BRM documentation.

It seems that following table names:

EVENT_SUB_BALS_T
EVENT_MONITOR_IMPACTS_T
EVENT_SUB_BAL_IMP_T
EVENT_MONITOR_SUB_BAL_IMP_T
EVENT_MONITOR_SUB_BALS_T

were replaced by one EVENT_ESSENTIALS_T.

E.g. SQL mapping in documentation for /event class is following:

array PIN_FLD_MONITOR_SUB_BAL_IMPACTS event_monitor_sub_bal_imp_t

while it should be (real mapping on DB):

array PIN_FLD_MONITOR_SUB_BAL_IMPACTS event_essentials_t

Discrepancy between documentation and actual mapping on database is confusing.

What can be done about this discrepancy ?

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