My Oracle Support Banner

Application Update WS Call Does Not Allow to Update Tracking Attribute of Length more than 30 char (Doc ID 2975168.1)

Last updated on SEPTEMBER 20, 2023

Applies to:

Oracle Financial Services Lending and Leasing Cloud Service - Version 14.12.0.0.0 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
---------------
Application Update WS call does not allow to update tracking attribute for length > 30.

User unable to update Tracking attribute of length > 30 by using Application Update WS call. Also, WS does not allow to update value of tracking attribute if the value already exist in tracking attribute parameter. Gives error 400 Bad Request "No data found for the given Parameter and Table for Attribute name APT_LOAN_001 Table name. "

EXPECTED BEHAVIOR
-----------------------
Application Update WS Call should allow user to update tracking attribute for length > 30 and it should not throw error 400 bad request during update of value of tracking attribute if the value already exist in tracking attribute parameter.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create application via Simple Application Entry WS call.
2. Use Application Update WS call and pass the Tracking attribute for length > 30 characters. As observed system display error "Invalid value", even though database and App entry web service allow to update tracking attribute of length max 80 characters.
3. However proceed for updating tracking attribute (e.g., APT_LOAN_001) for Length up to 30 characters.
4. Invoke Application Update WS call to again update same tracking attribute value / or another tracking attribute value however system displays below error -
"No data found for the given Parameter and Table for Attribute name APT_LOAN_001 Table name. "

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot update tracking attribute for length > 30 and update of value of tracking attribute if the value already exist in tracking attribute parameter.

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.