Incorrect Response Codes Assigned In Case Of BRM Initiated Payments.

(Doc ID 1501522.1)

Last updated on DECEMBER 05, 2012

Applies to:

Oracle Communications Billing and Revenue Management - Version to [Release 7.4.0]
Information in this document applies to any platform.


Incorrect response codes assigned in case of BRM-initiated payments. 

Example :

Create two successful AUTH and then run pin_deposit where the first AUTH VC302 and second is returning VC100. In dm_fusa will set incorrect VC302 to the second transactions instead of VC100.

Steps to verify: 

1) Go to $PIN_HOME/apps/fusa_server/pin.conf
    enabled the below entry,
    - answer simulation_level 1
    commented the existing ones and added below entries to the pin.conf
    - answer_b v_code 100
    - answer_b v_code_4387xxxxxxxxx 401
    - answer_b v_code_3714xxxxxxxxxxx 401
    - answer_b v_code_6011xxxxxxxxxxxx 501
    - answer_b v_code_5442xxxxxxxxxxxx302

2) Go to $PIN_HOME/sys/dm_fusa enabled the below entry,
    - dm_fusa sd_descriptor_flag 1
    Restart all the services

3) Create 3 credit card accounts with the credit card numbers: 6011xxxxxxxxxxxx, 5442xxxxxxxxxxxx, and 4441xxxxxxxxxxx
4) move pvt 7days ahead and run pin_deposit
    pin_deposit -pay_type 10003 -vendor fusa

5) Verify in cm.pinlog dm search output flist and op_pymt_charge_cc result flist should have the correct vendors code for the correct credit card number
    For example:
    for 6011xxxxxxxxxxxx :

    for 5442xxxxxxxxxxxx : 

    for 4441xxxxxxxxxxx :



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