My Oracle Support Banner

Cache Issue Is Observed Upon Modification Of Account Name From STDCRACC Screen In OBPM (Doc ID 2678982.1)

Last updated on JUNE 10, 2020

Applies to:

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

Symptoms

On : 14.3.0.0.0 version, Implementation Support

ACTUAL BEHAVIOR
---------------
Cache issue is observed upon modification of account name from STDCRACC screen


EXPECTED BEHAVIOR
-----------------------
System should have inerted the latest data maintained for the account in STDCRACC screen.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1) Inject a payment via single payment service in OBPM such that it creates a book transfer transaction with credit account
2) System inserts details into PBTB_TXN table and CR_NAME gets populated as the account name maintained in STDCRACC account.
3) User modifies and changes the account name from STDCRACC screen.
4) Inject another payment via SPS service in OBPM such that it creates a book transfer transaction
5) System inserts details into PBTB_TXN table and CR_NAME still populates as the old account name maintained in STDCRACC

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, incorrect details are being sent for scanning.

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
Cause
Solution


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