My Oracle Support Banner

Input Flist For Opcode Fm_pymt_pol_pre_refund Changed From PS19 (Doc ID 2356505.1)

Last updated on FEBRUARY 15, 2018

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.19.0 and later
Information in this document applies to any platform.

Symptoms

On : 7.5.0.19.0 version, Payments

ACTUAL BEHAVIOR
---------------
User is observing change in Input to fm_pymt_pol_pre_refund after PS19 upgrade.

This Opcode is called by pin_refund which is OOB code.
NOTE: "per_batch" is set to 1 in pin_refund's pin.conf

EXPECTED BEHAVIOR
-----------------------
Same behavior like PS15

STEPS
-----------------------
The issue can be reproduced at will with the following steps:


Set the following in pin_billd/pin.conf
- pin_billd loglevel 3
- pin_refund per_batch 1
- pin_deposit per_batch 1


1.Create a subscriber with credit card payment method and purchase a plan
2.Move 1 month ahead and run billing.
3. Do over payment/event adjustment.
4.Refund account with below flist:
  #PCM_OP_BILL_ITEM_REFUND
  0 PIN_FLD_POID           POID [0] 0.0.0.1 /account 625158 25
  0 PIN_FLD_PROGRAM_NAME    STR [0] "Customer Center"
  0 PIN_FLD_BILL_OBJ POID [0] 0.0.0.1 /bill 624902 5
5, Then run pin_refund -pay_type 10003 -active -vendor fusa -verbose from apps/pin_billd
Alternatively,move 1 month ahead and run billing which will internally call refund opcode to issue the refunds.

Check the cm.pinlog for input to fm_pymt_pol_pre_refund.



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!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.