Credit Threshold Notification From Pipeline: Impossible to Identify If a Call Belongs to Previous or Next Cycle (Doc ID 1144433.1)

Last updated on SEPTEMBER 26, 2016

Applies to:

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

Symptoms

In the threshold file generated by pipeline, it is impossible to identify if a call belongs to previous cycle (in delayed period), or next cycle to properly manage the credit threshold notification.

For example, a user is getting the following as input flist to the notification policy opcode:

D Tue Aug 10 03:13:29 2010 brmd cm:15830 fm_act_pol_event_notify.c:117 1:brmd:<no_name>:15825:1:163:1274134447:2
    op_act_pol_event_notify input flist
# number of field entries allocated 20, used 7
0 PIN_FLD_POID POID [0] 0.0.0.1 /event/notification/threshold -1 0
0 PIN_FLD_NAME STR [0] " Credit Threshold Notification "
0 PIN_FLD_ACCOUNT_OBJ POID [0] 0.0.0.1 /account 371793 0
0 PIN_FLD_PROGRAM_NAME STR [0] " Load Notification Event "
0 PIN_FLD_START_T TSTAMP [0] (1274134205) Mon May 17 17:10:05 2010
0 PIN_FLD_END_T TSTAMP [0] (1274134205) Mon May 17 17:10:05 2010

0 PIN_FLD_INHERITED_INFO SUBSTRUCT [0] allocated 20, used 2
1    PIN_FLD_BALANCES ARRAY [1] allocated 20, used 10
2       PIN_FLD_AMOUNT DECIMAL [0] 9
2       PIN_FLD_RESOURCE_ID INT [0] 1000401
2       PIN_FLD_BAL_GRP_OBJ POID [0] 0.0.0.1 /balance_group 370001 0
2       PIN_FLD_CREDIT_FLOOR DECIMAL [0] -80
2       PIN_FLD_CREDIT_LIMIT DECIMAL [0] 0
2       PIN_FLD_CREDIT_THRESHOLDS INT [0] 166432
2       PIN_FLD_CREDIT_THRESHOLDS_FIXED STR [0] NULL str ptr
2       PIN_FLD_EVENT_TYPE STR [0] "/event/delayed/session/telco/telephony"
2       PIN_FLD_CALLING_NUMBER STR [0] "811323555"
2       PIN_FLD_CALLED_NUMBER STR [0] "013413239"
1    PIN_FLD_THRESHOLDS ARRAY [0] allocated 20, used 3
2       PIN_FLD_CREDIT_THRESHOLDS INT [0] 50
2       PIN_FLD_ALERT_TYPE ENUM [0] 2
2       PIN_FLD_REASON ENUM [0] 1



As you can see, the system pin_virtual_time is set on Aug 10, 2010.  The call that triggered this notification is from Aug 7, 2010 and this date is not received in any of the date fields on the input flist.  The date set on start_t and end_t are the actual server dates.

So, the user can not identify if the CDRs belongs to the current or next cycle.


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