Billing Care: Selected Reason Code Not Passed in PAYMENT_REASONS Array
Last updated on JANUARY 30, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
On : 22.214.171.124.0 version, Billing Care
In Billing Care UI, when an amount is distributed to an account from Suspense, the selected reason code did not get passed in the PAYMENT_REASONS within the CHARGES array for the account on which it is allocated.
1. open suspended payment
2. add account which has 0 bill due
3. add amount
4. click on auto allocate button
5. continue warning message will appear
6. click continue button
The expectation is the allocation should route the Payment to account and move it to GL ID selected. But since the PIN_FLD_PAYMENT_REASONS is not populated with the selected reason code, it is not able to do that. And GLID remains "0" too.
Notes : The opcode PCM_OP_PYMT_RECYCLE_PAYMENT is called when a single payment or a list of distributed payments is transferred between the payment suspense account and one or more customer accounts. The issue lies in the
input flist of the opcode, wherein, array PIN_FLD_PAYMENT_REASONS does not have any reason_code fields associated with it. See below snippet of the input flist. The Billing Care UI is responsible for building the input flist and correctly populating the reason codes :
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