My Oracle Support Banner

Incorrect Field 72 Validation For The Codewords (Doc ID 2857905.1)

Last updated on MARCH 27, 2022

Applies to:

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

Symptoms

On : 14.5.0.0.0 version,

Incorrect field 72 validation for the codewords

Existing SIs are failing and the transactions are going to repair after the fix was deployed :
33869164 HOOK REQUEST TO MODIFY ACTIVATION DATE, DR AND CR VALUE DATE OF FUTURE VALUE DATED TRANSACTION
as the class file XborderOutTxnValidator.class included hard coded values for the codewords in method populateTempRepairFieldsForSndrRcvr

 if (codeword != null && (
  "C".equals(transferType) ||
  "B".equals(transferType)) &&
  !"ACC".equals(codeword) &&
  !"INS".equals(codeword) && !"BNF".equals(codeword) &&
  !"INT".equals(codeword) &&
  !"REC".equals(codeword)) {
  dbg(new Object[] { "Codeword incorrect.." });
  addErrorMessage("PX-SV-050");
  invalidFields.add(fieldName);
  repairFieldRequest.setMessage(new Message("PX-SV-050"));
  }

But the codewords can also be bilaterally agreed between the banks and the payments should not fail because of this validation. Kindly check this urgently.

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.