For BRM Initiated Payments, MANUAL_ALLOC Or ALLOCATION_DEFERRED Flags Do Not Stop Auto Allocation
(Doc ID 2021496.1)
Last updated on SEPTEMBER 21, 2020
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.5.0]
Information in this document applies to any platform.
1. The PCM_OP_PYMT_POL_PRE_COLLECT opcode is not working as specified.
User tried to set the value for PIN_FLD_SELECT_STATUS as PIN_SELECT_STATUS_MANUAL_ALLOC and also to PIN_SELECT_STATUS_ALLOCATION_DEFERRED in the PCM_OP_PYMT_POL_PRE_COLLECT opcode return flis, but the amount still gets allocated automatically.
Needs a flag that can be used to selectively prevent auto allocation for specific accounts.
2. Wrong PCM_OP_PYMT_POL_PRE_COLLECT opcode specification in the documentation.
In the output specification the field PIN_FLD_SELECT_STATUS is shown at level 0 in the opcode return flist. However, the field is actually present under the PIN_FLD_CHARGES array in PCM_OP_PYMT_POL_PRE_COLLECT opcode return flist.
When collects the credit card payments by running pin_collect application, for certain specific accounts that want the collected amount to remain unallocated so this amount would later be allocated manually.
In Billing and Revenue Management (BRM) 7.5 documentation, it shows a field in the opcode PCM_OP_PYMT_POL_PRE_COLLECT, called PIN_FLD_SELECT_STATUS to which it can be assigned certain flag values as below:
Flag values from pin_pymt.h
- #define PIN_SELECT_STATUS_EXACT_MATCH 0x1
- #define PIN_SELECT_STATUS_UNDER_PAYMENT 0x2
- #define PIN_SELECT_STATUS_OVER_PAYMENT 0x4
- #define PIN_SELECT_STATUS_MANUAL_ALLOC 0x8
- #define PIN_SELECT_STATUS_ALLOCATION_DEFERRED 0x10
- #define PIN_SELECT_STATUS_MBI_DISTRIBUTED 0x20
Based on the above, the user sets the value for PIN_FLD_SELECT_STATUS as PIN_SELECT_STATUS_MANUAL_ALLOC and also to PIN_SELECT_STATUS_ALLOCATION_DEFERRED in the PCM_OP_PYMT_POL_PRE_COLLECT opcode return flist.
But the amount still gets allocated automatically.
The amount should remain unallocated when these flags are used.
The issue can be reproduced at will with the following steps:
1. Create an account.
2. Change payment type to credit card.
3. Purchase a subscription and perform bill-now.
4. run pin_collect to collect payment.
The issue has the following business impact:
Due to this issue, users cannot allocate the payment amount manually. Amount is getting auto-allocated.
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