My Oracle Support Banner

Incorrect START_T In Notification XML From Pipeline (Doc ID 1542530.1)

Last updated on SEPTEMBER 21, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version to [Release 7.4.0]
Oracle Solaris on SPARC (64-bit)


Issue: Incorrect START_T in Notification XML from pipeline

Configure the pipeline so that the balance-breach notification xml gets generated when a non-currency balance breach occurs. Check the generated xml for the fields: START_T and END_T.

END_T is coming same as START_T in Notification xml.

Both the fields have the same value which is equal to CHARGING END TIMESTAMP in unix seconds.

Sample Notification XML generated by Pipeline:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<POID> /account 38096895511 0</POID>
<POID> /event/notification/threshold -1 0</POID>
<NAME> Credit Threshold Notification </NAME>
<ACCOUNT_OBJ> /account 38021398785 0</ACCOUNT_OBJ>
<PROGRAM_NAME> Load Notification Event </PROGRAM_NAME>
<START_T>1349423053</START_T>     ****** Here is the issue. ******
   <BALANCES elem="1">
    <BAL_GRP_OBJ> /balance_group 38021398785 0</BAL_GRP_OBJ>
  <THRESHOLDS elem="0">
  <THRESHOLDS elem="1">


To view full details, 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 a vibrant support community of peers and Oracle experts.