DueDateAdjustment Parameter Specified In PinBillRunControl.xml Not Working As Expected
(Doc ID 1640887.1)
Last updated on AUGUST 14, 2024
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
Scenario:
Create bills by passing the parameter DuedateAdjustment with value of 20.
After bill run, the due date shows 1month + 20days specified. In OOB, it seems to calculate the due date as bill_run_date + 1 month + 20days (duedateadjustment) .
Expectation is bill_run_date + 20days.
Test:
- Create two Accounts - TEST_ACC_1 and TEST_ACC_2 .
- Now create a payment id and set the payment id 1001 to the payinfo/invoice of the account as below :
Change fm_bill_pol_calc_pymt_due_t.c by adding below section :
- Restart CM
- Goto $PIN_HOME/apps/pin_billd directory and change the BillRunConfiguration in PinBillRunControl.xml
- Actual result:
After Billing, the Bill payment due date is :
1. Accounts without Payment Term -- Billrundate + 1 month days (Oct 31 for example)
2. Accounts with Payment Term -- Billrundate + 1 month + <dueDateAdjustment> days (November 10 for example) - Expected Result :
After Billing, the Bill payment due date is :
1. Accounts without Payment Term -- Billrundate + 1 month + <dueDateAdjustment> days (Nov 5 for example)
2. Accounts with Payment Term -- Billrundate + <dueDateAdjustment> days (This is based on customization done) (October 10 for example)
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 |
Cause |
Solution |
References |