Info On Pin_fld_actg_last_t For Billinfo Modify Events Published To Pipeline (Doc ID 754846.1)

Last updated on NOVEMBER 27, 2011

Applies to:

Oracle Communications Billing and Revenue Management - Version: 7.2.1.0.0 and later   [Release: 7.2.1 and later ]
Information in this document applies to any platform.
***Checked for relevance on 27-Nov-2011***

Goal

Why PIN_FLD_ACTG_LAST_T in the new billinfo data for events
"/event/customer/billinfo/create" and "/event/customer/billinfo/modify"  published to integrate is
being changed with PIN_FLD_END_T ?



Below is the policy code in fm_ifw_sync_pol_publish_event.c which set the PIN_FLD_ACTG_LAST_T to PIN_FLD_END_T.


if ((!strcmp(PIN_POID_GET_TYPE(poidp), "/event/customer/billinfo/create")) ||
(!strcmp(PIN_POID_GET_TYPE(poidp),
"/event/customer/billinfo/modify"))) {
process_billinfo(connp, in_flistp, flags, out_flistpp, ebufp);
}

static void
process_billinfo(
cm_nap_connection_t *connp,
pin_flist_t *in_flistp,
int32 flags,
pin_flist_t **out_flistpp,
pin_errbuf_t *ebufp)
{
time_t *tp = NULL;
pin_flist_t *fp1 = NULL;

/* copy PIN_FLD_END_T to PIN_FLD_ACTG_LAST_T */
tp = PIN_FLIST_FLD_GET(in_flistp, PIN_FLD_END_T, 0, ebufp);
fp1 = PIN_FLIST_ELEM_GET(in_flistp, PIN_FLD_BILLINFO, 1, 0, ebufp);
PIN_FLIST_FLD_SET(fp1, PIN_FLD_ACTG_LAST_T, tp, ebufp);
}



Sample event:

0 PIN_FLD_POID POID [0] 0.0.0.9 /event/customer/billinfo/modify 248876665683011309 0
0 PIN_FLD_CREATED_T TSTAMP [0] (1222358136) Thu Sep 25 09:55:36 2008
0 PIN_FLD_ACCOUNT_OBJ POID [0] 0.0.0.9 /account 28921126 1344
0 PIN_FLD_END_T TSTAMP [0] (1222358136) Thu Sep 25 09:55:36 2008
0 PIN_FLD_FLAGS INT [0] 0
0 PIN_FLD_ITEM_OBJ POID [0] 0.0.0.0 0 0
0 PIN_FLD_NAME STR [0] "Customer Mngmt. Event Log"
0 PIN_FLD_PROGRAM_NAME STR [0] "Customer Center"
0 PIN_FLD_SERVICE_OBJ POID [0] 0.0.0.0 0 0
0 PIN_FLD_START_T TSTAMP [0] (1222358136) Thu Sep 25 09:55:36 2008
0 PIN_FLD_SYS_DESCR STR [0] "Set Billing Info"
0 PIN_FLD_TIMEZONE_ADJ_END_T TSTAMP [0] (1222358136) Thu Sep 25 09:55:36 2008
0 PIN_FLD_TIMEZONE_ADJ_START_T TSTAMP [0] (1222358136) Thu Sep 25 09:55:36 2008
0 PIN_FLD_BILLINFO ARRAY [0] allocated 20, used 11
1 PIN_FLD_ACTG_CYCLE_DOM INT [0] 23
1 PIN_FLD_ACTG_FUTURE_T TSTAMP [0] (1227420000) Sun Nov 23 00:00:00 2008
1 PIN_FLD_ACTG_LAST_T TSTAMP [0] (1222149600) Tue Sep 23 00:00:00 2008
1 PIN_FLD_ACTG_NEXT_T TSTAMP [0] (1224741600) Thu Oct 23 00:00:00 2008
1 PIN_FLD_BILLINFO_OBJ POID [0] 0.0.0.0 0 0
1 PIN_FLD_BILL_ACTGCYCLES_LEFT INT [0] 1
1 PIN_FLD_BILL_WHEN INT [0] 1
1 PIN_FLD_CURRENCY INT [0] 124
1 PIN_FLD_NEXT_BILL_T TSTAMP [0] (1224741600) Thu Oct 23 00:00:00 2008
1 PIN_FLD_PARENT_BILLINFO_OBJ POID [0] 0.0.0.0 0 0
1 PIN_FLD_PAY_TYPE ENUM [0] 10001
0 PIN_FLD_BILLINFO ARRAY [1] allocated 20, used 11
1 PIN_FLD_ACTG_CYCLE_DOM INT [0] 23
1 PIN_FLD_ACTG_FUTURE_T TSTAMP [0] (1227420000) Sun Nov 23 00:00:00 2008
1 PIN_FLD_ACTG_LAST_T TSTAMP [0] (1222149600) Tue Sep 23 00:00:00 2008
1 PIN_FLD_ACTG_NEXT_T TSTAMP [0] (1224741600) Thu Oct 23 00:00:00 2008
1 PIN_FLD_BILLINFO_OBJ POID [0] 0.0.0.9 /billinfo 7064297098 71
1 PIN_FLD_BILL_ACTGCYCLES_LEFT INT [0] 0
1 PIN_FLD_BILL_WHEN INT [0] 1
1 PIN_FLD_CURRENCY INT [0] 0
1 PIN_FLD_NEXT_BILL_T TSTAMP [0] (1224741600) Thu Oct 23 00:00:00 2008
1 PIN_FLD_PARENT_BILLINFO_OBJ POID [0] 0.0.0.0 / 0 0
1 PIN_FLD_PAY_TYPE ENUM [0] 10003


In the above example, PIN_FLD_ACTG_LAST_T in PIN_FLD_BILLINFO ARRAY [1] gets replaced with "(1222358136) Thu Sep 25 09:55:36 2008"



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