My Oracle Support Banner

REST Service For Loan Repayment Fails with error "Record Already Locked" (Doc ID 2899456.1)

Last updated on OCTOBER 07, 2022

Applies to:

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

Symptoms

On : 14.5.0.0.0 version, Production Support-SET

ACTUAL BEHAVIOR
---------------
Account lock is not removed when Loan repayment is posted through REST API


EXPECTED BEHAVIOR
-----------------------
Account lock should be released from CSTB_ADV_LOCK when Loan repayment is posted through REST API

 

STEPS
-----------------------
1) Perform a payment (negative test case) via REST and user ID is SYSTEM. Payment rejected as expected (refer Request1_SYSTEM.txt)
2) Perform a payment for same loan account with different user ID “MOBILEAPP”. System returns error message “record already locked”. Refer Reques2_MOBILEAPPUSER


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot post repayment through API

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


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