My Oracle Support Banner

SEPA Payment Reversal Is Using Wrong Reason Id Sometimes (Doc ID 2306609.1)

Last updated on SEPTEMBER 15, 2020

Applies to:

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

Symptoms

On all versions of Oracle Communications Billing and Revenue Management (BRM), when using pin_sepa to process multiple Single Euro Payments Area (SEPA) payment reversal transactions, occasionally invalid Reason IDs and invalid Domain IDs are present in the PCM_OP_BILL_REVERSE opcode input flist.

This is despite the input XML containing multiple transactions and all with the same reason code 'SEPA Payment Reversal'.

The application internally calls PCM_OP_PYMT_PROCESS_SEPA_RESPONSE opcode with valid trans ids and reason codes but internally the opcode is using valid reason id for some transactions and invalid reason ids for some transactions.

Sample input flist for PCM_OP_PYMT_PROCESS_SEPA_RESPONSE opcode:

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!


In this Document
Symptoms
Changes
Cause
Solution
References


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