Unexpected Addition of AUTHID CURRENT_USER Clause in Custom Packages

Custom PL/SQL packages created under the APPS schema may automatically include the clause AUTHID CURRENT_USER in their package specification — even if it wasn’t originally defined.

Reason:

If the package contains the word ‘Header’ in its definition, AD utilities (like adadmin) treat it as a system-managed object and automatically inject the AUTHID CURRENT_USER clause during compilation.

Recommended Solution:

Replace the word ‘Header’ in your package definition with a neutral alternative — such as ‘Version’ or any other non-reserved term.
Recompile the APPS schema using adadmin.
Confirm that the AUTHID CURRENT_USER clause is no longer added automatically.

Why This Matters:

The AUTHID CURRENT_USER clause changes the execution context of the package — potentially affecting privileges, data access, and behavior. Ensuring it’s only present when explicitly intended helps maintain predictable and secure application logic.