My Oracle Support Banner

FND_GLOBAL.INITIALIZE Procedure Does Not Handle FND_INIT_SQL Correctly After Applying RUP5 (Doc ID 452713.1)

Last updated on MAY 06, 2024

Applies to:

Oracle Application Object Library - Version 11.5.10.2 to 11.5.10.2 [Release 11.5]
Information in this document applies to any platform.
AFSCGBLB.pls 115.108
 


Symptoms

After applying <Patch 5473858> 11i.ATG_PF.H.RUP5, Initialization SQL Statement - Custom profile option value (FND_INIT_SQL) no longer executes for context changes.
When you switch the responsibility, the SQL statement in Initialization SQL Statement - Custom profile option will not be executed, like it was before applying the patch.

The issue can be reproduced at will with the following steps:
1. Set Initialization SQL Statement - Custom (FND_INIT_SQL) profile option to execute a custom SQL.
2. Login E Business and choose a responsibility.
3. Change the responsibility to a different one - the SQL statement is not executed anymore.

Changes

You applied <Patch 5473858> 11i.ATG_PF.H.RUP5.

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
References

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