DueDateAdjustment Parameter Specified In PinBillRunControl.xml Is Not Being Captured And Sent To PCM_OP_BILL_MAKE BILL
(Doc ID 1625085.1)
Last updated on MARCH 13, 2019
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
"DueDateAdjustment" parameter is used to specify the due date for the bill generated for the subscriber of a service. So when you pass this xml file to pin_bill_day script, we see that the parameter is not picked by PCM_OP_BILL_MAKE BILL.
Input flist for PCM_OP_BILL_MAKE BILL
0 PIN_FLD_ACCOUNT_OBJ POID [0] 0.0.0.1 /account 697666 0
0 PIN_FLD_BILL_NO STR [0] "B1-13"
0 PIN_FLD_END_T TSTAMP [0] (1371052800) Thu Jun 13 00:00:00 2013
0 PIN_FLD_PROGRAM_NAME STR [0] "pin_bill_accts"
0 PIN_FLD_BILLINFO_OBJ POID [0] 0.0.0.1 /billinfo 699202 0
0 PIN_FLD_LAST_BILL_STATE_TO_PROCESS INT [0] 2
Expected to have “PIN_FLD_DUE_DATE_ADJUSTMENTS” but missing in the FLIST.
Steps Implemented:
1. Update the PinBillRunControl.xml File with the DueDateAdjustment value.
<BillRunConfiguration>
<!-- List of adjustment values for this bill run -->
<DueDateAdjustment Length="20">
</DueDateAdjustment>
<!-- List of Billinfo to be billed -->
<BillingList>
<Account>697666</Account>
<Billinfo>699202</Billinfo>
</BillingList>
</BillRunConfiguration>
2. Run the pin_bill_day script as follows:
$ pin_bill_day –verbose –file PinBillRunControl.xml
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |