For BRM Initiated Payments, MANUAL_ALLOC Or ALLOCATION_DEFERRED Flags Do Not Stop Auto Allocation (Doc ID 2021496.1)

Last updated on JANUARY 05, 2017

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

On : 7.5.0.10.0 version, Payments

ISSUES

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.


For BRM initiated payments, MANUAL_ALLOC or ALLOCATION_DEFERRED flags do not stop auto allocation.

Customer collects the credit card payments by running pin_collect application.
For certain specific accounts they want the collected amount to remain unallocated. This amount would later be allocated manually.

In BRM 7.5 documentation, we can see a field in the opcode PCM_OP_PYMT_POL_PRE_COLLECT, called PIN_FLD_SELECT_STATUS to which we can assign certain flag values.

PCM_OP_PYMT_POL_PRE_COLLECT opcode return flist specification in BRM 7.5 documentation has following values for the field PIN_FLD_SELECT_STATUS:


Flag values from pin_pymt.h


Based on this, Customer 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 flist.

But the amount still gets allocated automatically.


EXPECTATIONS

The amount should remain unallocated when these flags are used.


STEPS

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.


BUSINESS IMPACT

The issue has the following business impact:
Due to this issue, users cannot allocate the payment amount manually. Amount is getting auto-allocated.

Cause

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