My Oracle Support Banner

OBPM | PXDOTONL Charge Bearer BEN - Charge Account Invalid - Repair Q (Doc ID 3045141.1)

Last updated on SEPTEMBER 05, 2024

Applies to:

Oracle Banking Payments - Version 14.7.0.0.0 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
---------------
While creating an outbound cross border Customer transfer with the Charge bearer as BEN(MT) in the PXDOTONL screen, upon saving, the system displayed an error messages as "Invalid Charge Account. Charge Account must belong to debit customer." and the transaction went to repair Queue.

EXPECTED BEHAVIOR
-----------------------
we are expecting that the system should allow us to post the transaction with the charge bearer as BEN/ PXDOTONL

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Launch PXDOTONL
2. Capture the mandatory details
3. Charge Bearer : BEN
4. Enrich
5. Validate the charges
6. Save
7. System showing the error message and the transaction moved to repair Queue


Changes

 Validations were present for the charge account. Code changes done to remove charge account validation.

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.