Search Results update_no_reuse_function

Overview

APPS.FND_USER_PKG_WRP is a wrapper package body in the Oracle E-Business Suite Applications (APPS) schema whose purpose is to expose a controlled, stable interface to the underlying user-management logic implemented in FND_USER_PKG. Rather than duplicating business rules, the wrapper delegates each operation to its counterpart in FND_USER_PKG, normalizing the calling conventions so that forms, concurrent programs, and external integrations can invoke user lifecycle operations through a single, well-known entry point. The "WRP" suffix denotes its role as a wrapper layer, and the header comment block confirms each routine is explicitly described as a wrapper for the corresponding FND_USER_PKG member. This pattern is characteristic of EBS releases in the 12.1.1 and 12.2.2 code lines, where the wrapper shields callers from internal signature changes and centralizes validation, user synchronization, and password-handling logic. The p_username/p_user_name parameter appears throughout the package because the FND_USER record — keyed by user name — is the primary subject of virtually every operation the package performs.

Key Procedures and Functions

The ETRM metadata documents ten callable units. The package includes both procedures (which perform an action and return no value, sometimes raising exceptions) and functions (which compute and return a result). In each case the implementation is a thin delegation to FND_USER_PKG.

• USER_SYNCH — Procedure that synchronizes a single user account, taking the user name as input. Used to reconcile FND_USER state with dependent entities such as person or party records.
• DERIVE_PERSON_PARTY_ID — Function returning a numeric identifier. It resolves the person/party association for a given user name, using customer and employee identifiers as inputs, and accepts a logging-exception flag to control error capture behavior.
• SET_OLD_USER_NAME — Function returning a numeric status that records a prior user name, supporting user-name change operations while preserving history.
• VALIDATE_USER_NAME — Procedure that validates a supplied user name against the application's naming rules, raising an error when the name is invalid.
• ISPASSWORDCHANGEABLE — Function returning a Boolean indicating whether the password for the specified user may be changed under current policy (for example, when password controls or external authentication settings apply).
• LDAP_WRAPPER_CREATE_USER — Procedure that creates a user and propagates the account to the directory (LDAP) tier, accepting the user name, an unencrypted password, and a start date.
• LDAP_WRAPPER_UPDATE_USER — Procedure that updates an existing directory-linked user account.
• LDAP_WRAPPER_CHANGE_USER_NAME — Procedure that performs a user-name change and reflects it in the directory.
• FORMS_VALIDATE_PASSWORD — Procedure invoked by the Oracle Forms UI to validate a supplied password during user maintenance.
• FORMS_CHANGE_USER_PWD — Procedure used by the Forms interface to change a user's password.

Tables Accessed

The ETRM metadata records no directly referenced base tables for this wrapper body; the documented implementation delegates entirely to FND_USER_PKG, and no table access appears in the package source itself. In practice, the underlying FND_USER_PKG performs the data manipulation against the FND_USER entity and its dependents, but this wrapper neither issues nor embeds SQL. This separation is by design: it insulates the wrapper's public contract from table-level changes in the base package. Callers requiring table-level detail should consult FND_USER_PKG documentation rather than this wrapper.

Usage Notes

The package is classified as OTHER in the ETRM API classification scheme, and no other packages reference it, indicating it is invoked as a top-level entry point rather than as a shared internal dependency. Typical invocation contexts include the Oracle Forms-based user maintenance screens (notably through the FORMS_VALIDATE_PASSWORD and FORMS_CHANGE_USER_PWD entry points), directory-integration flows that create, update, or rename users in LDAP, and custom or third-party code that prefers the wrapper's stable signatures. Because two of the documented routines exist specifically as Forms-facing wrappers, any refactoring of the underlying FND_USER_PKG should preserve these signatures to avoid breaking user administration forms. All operations are scoped to a single user identified by the p_user_name parameter, so callers processing users in bulk must invoke the wrapper once per account rather than relying on set-based behavior.