My Oracle Support Banner

Change Of GL's In STDCUSAC Screen Not Updating The CUST_ACC_BREAKUP GL's Columns And Not Initiating Balance Movement To New GL's (Doc ID 2807463.1)

Last updated on JANUARY 24, 2022

Applies to:

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

Symptoms

ACTUAL BEHAVIOR
---------------
When user perform change in GL lines in STDCUSAC screen, only DR_GL in gltb_cust_acc_breakup is getting updated and CR_GL still holds old GL value, even though both debit and credit GL values reflects new values in STDCUSAC screen.

Update of the sttm_cust_account table to check whether the trigger STTR_GL_CODE_UPDATE will update debit and credit GL's, is failing as only debit GL is updating and credit GL still holds the old GL value.

EXPECTED BEHAVIOR
-----------------------
Change is GL's in STDCUSAC screen should update the respective columns in gltb_cust_acc_breakup table and initiate the balance movement.

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

1. Perform Debit, Credit GL's change in STDCUSAC screen, SAVE and AUTHORIZE.

2. Check for GL details in gltb_cust_acc_breakup and balance movement to new GL's


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, accruals are posted to wrong GL's.

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
References


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