Events are Not Created if Parent Event Creation is Skipped after Upgrading to BRM 7.5 PS14 (Doc ID 2147156.1)

Last updated on JUNE 14, 2017

Applies to:

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

Goal

On Oracle Communications Billing and Revenue Management(BRM), 7.5.0.14.0 version, the below scenario is observed where events are not created if parent event creation is skipped after upgrading to PS14.

Scenario:

pin_event_record_map contains the events which will not be recorded into Infranet, when they occur.
pin_event_record_map contains "/event/billing/suppression: 0 "
in PS10, PCM_OP_BILL_RECORD_EVENT does not create "/event/billing/suppression" if it occurs.
in PS14, PCM_OP_BILL_RECORD_EVENT does not create "/event/billing/suppression" and all sub-classes "/event/billing/suppression/*" if they occur.

Steps to reproduce:

1. Add "/event/billing/suppression: 0" in pin_event_record_map file.
2. Run “load_pin_event_record_map -v pin_event_record_map”.
3. Restart cm.
4. Call PCM_OP_BILL_RECORD_EVENT opcode using the following flist.

0 PIN_FLD_SUPPRESSION_INFO SUBSTRUCT [0] allocated 20, used 2
1 PIN_FLD_REASON ENUM [0] 0
1 PIN_FLD_EXCEPTION ENUM [0] 5
0 PIN_FLD_POID POID [0] 0.0.0.1 /event/billing/suppression/exception -1 0
0 PIN_FLD_NAME STR [0] "Suppression Exception Event"
0 PIN_FLD_USERID POID [0] 0.0.0.1 /service/pcm_client 1 29
0 PIN_FLD_SESSION_OBJ POID [0] 0.0.0.1 /event/session 0 0
0 PIN_FLD_ACCOUNT_OBJ POID [0] 0.0.0.1 /account 152269 0
0 PIN_FLD_PROGRAM_NAME STR [0] "Automatic Bill Suppression opcode"
0 PIN_FLD_START_T TSTAMP [0] (1465964133) Wed Jun 15 00:15:33 2016
0 PIN_FLD_END_T TSTAMP [0] (1465964133) Wed Jun 15 00:15:33 2016
0 PIN_FLD_SYS_DESCR STR [0] "Suppression Exception Event"

Expected Results:
Given pin_event_record_map doesn’t contain configuration for ‘/event/billing/suppression/exception’, PCM_OP_BILL_RECORD_EVENT will creates /event/billing/suppression/exception event

Actual Result:
PCM_OP_BILL_RECORD_EVENT didn’t create any event.


Question: Is the reported behavior a bug or a new feature? Is there a way to suppress the parent class, but still create a child class event by using a different configuration?

Solution

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