My Oracle Support Banner

OBDX generates reference Number more than 16 digits , How to override OBDX reference number generation logic (Doc ID 2620732.1)

Last updated on JANUARY 07, 2020

Applies to:

Oracle Banking Digital Experience - Version to [Release 11 to 18]
Information in this document applies to any platform.


OBDX  (Oracle Banking Digital Experience )  generates transaction reference number up to 35 length.

Out of box OBDX is qualified with PC (Payments and Collections) module of FCUBS (Oracle FLEXCUBE Universal Banking) for Self, Internal and Domestic which accepts Source reference no up to 35 characters .

If OBDX is implemented to integrate these transfers with FT (Funds transfer) module of Oracle FLEXCUBE Universal Banking then they might fails if reference number length is more than 16 characters.                                                                                                                                         



In payments,when the reference number is generated from OBDX exceeds 16 digits , gives error code : DIGX_PROD_DEF_0000 ones rejected by FCUBS  for processing .




The issue can be reproduced at will with the following steps:

1.Login via Corporate /Retail user

2. Perform a Own / Internal / Domestic payment transaction

3.Observe if any error is populated at confirm screen .



Self , Internal & Domestic Transfers is changed / customized to Send Transaction request to FT (Funds transfer) module of Oracle FLEXCUBE Universal Banking .


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

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