Search Results get_user_guid_and_count

Overview

APPS.FND_LDAP_USER is the Oracle E-Business Suite package that mediates user account operations against an external LDAP directory, typically Oracle Internet Directory (OID), and reconciles those operations with the local FND_USER repository. In EBS 12.1.1 and 12.2.2, this package supports Oracle Single Sign-On and integrated directory deployments by providing programmatic control over password changes, user name changes, account creation, account linking, and directory attribute manipulation. It is classified as an FND internal API (API classification OTHER), meaning it is intended for use by Oracle's own application code and by carefully controlled extensions rather than as a general-purpose public interface.

The package declares a global record type, ldap_user_type, which is the object most often located through searches for the term "ldap_user_type". This record bundles the attributes needed to represent a directory user inside PL/SQL: the user name, GUID, user ID, RDN attribute name and value, nickname attribute name, parent DN, realm DN, distinguished name, and a collection of directory attribute values (FND_LDAP_UTIL.ldap_record_values). It acts as the in-memory carrier for user identity information between LDAP lookups and EBS-side processing.

Key Procedures and Functions

The package exposes 24 documented procedures and functions. They fall into several functional groups.

• Password and identity maintenance: CHANGE_PASSWORD (modifies an OID password for a user identified by GUID or user name, with an option to expire the password on next login), CHANGE_USER_NAME, and VALIDATE_LOGIN.
• Account lifecycle: CREATE_USER, UPDATE_USER, DELETE_USER, USER_EXISTS, LINK_USER, and UNLINK_USER (the latter two associate and dissociate an EBS user with a directory user).
• GUID and lookup utilities: GET_USER_GUID_AND_COUNT, GET_USERNAME_FROM_GUID, and SEARCHUSER.
• Attribute manipulation: GET_ATTRIBUTE_VALUE, SETATTRIBUTE, DELETEATTRIBUTE, GETATTRIBUTE, ATTRIBUTEPRESENT, FIRSTVALUE, NEXTVALUE, and GETNICKNAMEATTR.

Parameter lists are not reproduced here; the documentation describes purpose only. Collectively these routines allow EBS to provision, query, and synchronize directory accounts while preserving the mapping between the directory GUID and the local FND_USER record.

Tables Accessed

The package references three documented objects through APPS synonyms.

• FND_USER — the local EBS user repository. It supplies and receives user_name, user_guid, and user_id, and is the anchor for the LINK_USER, UNLINK_USER, and lookup routines.
• DBMS_LDAP — the Oracle-supplied PL/SQL LDAP client library used to bind, search, add, modify, and delete entries in the directory.
• PLITBLM — a supporting table used by the PL/SQL dictionary-managed parse environment.

The ldap_user_type record structure reflects this access pattern, carrying FND_USER key values alongside directory-specific fields such as dn, parent_DN, and realmDN.

Usage Notes

FND_LDAP_USER is most commonly invoked indirectly. It is referenced by two other packages and is called from EBS user-management forms, the FND user maintenance flows, and SSO/OID integration processes when a user password, name, or directory linkage must be updated. In deployments integrated with OID, it executes during user creation, password reset, and profile-driven directory synchronization. Custom code should use it only where the standard user-management APIs do not suffice, because the package is FND internal and its contract may change between releases. The presence of the ldap_user_type global indicates the package is also a useful reference for developers inspecting how EBS models directory user identity.