My Oracle Support Banner

OBPM 14.1 PS 10 :: Creditoraccountid Getting Populated As NULL In OBPM Sanction Request XML (Doc ID 2486746.1)

Last updated on DECEMBER 18, 2020

Applies to:

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

Goal

On : 14.1.0.0.0 version, Implementation Support

OBPM 14.1 PS 10 :: Creditoraccountid getting populated as NULL in OBPM Sanction Request XML

It is observed that the ID tag under CreditorAccount "CdtrAcct" is populated as NULL in the Sanction Request Message by OBPM.
This issue is observed when the Creditor Account Number is not entered for the tranaction.

Simulation Steps:-

1.) Create a Non Urgent Payment through OutBound Low Value (ACH) Payments Transaction Input screen - PADOTONL.
2.) Make sure that under Creditor details, Only Creditor Account IBAN is entered. Creditor Account Number should be left blank.
3.) Save the transaction and it should get saved and authorized successfully.
4.) Launch the "View Queue Action" for the given transaction and check the Sanction Check Queue request message. It is observed that the "ID" tag under "CdtrAcct" node is populated with NULL value.

Expectation :- It is expected that the NULL value should not be populated.
 

Solution

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
Goal
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.