Search Results is_present

Overview

FND_LDAP_WRAPPER is the Oracle E-Business Suite PL/SQL package body that provides the application-facing interface between EBS user maintenance logic and an external LDAP directory, typically Oracle Internet Directory (OID) or Oracle Unified Directory in a single sign-on deployment. In releases 12.1.1 and 12.2.2 it isolates all directory-server interaction behind a stable PL/SQL API so that user provisioning, password changes, name changes, and login validation can be synchronized without the calling forms or concurrent programs embedding directory-specific calls.

The package maintains a set of package globals (initreg, init, ssoenabled, registered, and registration) that cache SSO registration state for the duration of a session, avoiding repeated lookups against the directory and the APPS_SSO_LDAP_SYNC profile option. The header comment identifies the source as AFSCOLWB.pls and the module source string used for FND_LOG diagnostics is fnd.plsql.oid.fnd_ldap_wrapper.

Key Procedures and Functions

The package exposes nineteen documented program units. Functions GET_LDAP_USER_NAME, GET_ORCLAPPNAME, and GET_REALM_DN resolve directory-side identifiers, mapping an EBS user name to its LDAP equivalent and returning the realm distinguished name used in DN construction. GET_REGISTRATION reports the current SSO registration state cached in the package global.

User lifecycle is handled by CREATE_USER, UPDATE_USER, DELETE_USER, CHANGE_USER_NAME, and CHANGE_PASSWORD, which propagate EBS-side changes to the directory. LINK_USER, UNLINK_USER, and UNLINK_EBIZ_USER manage the association between an existing EBS account and an existing directory entry, supporting both direction of linkage and controlled removal. SYNCH_USER_FROM_LDAP performs the inbound direction, pulling attribute data from the directory into FND_USER.

The remaining units provide validation and gating. USER_EXISTS and IS_PRESENT are boolean-style existence checks — the latter is the member most commonly referenced when diagnosing directory-presence questions. VALIDATE_LOGIN supports credential verification against the directory, IS_OPERATION_ALLOWED enforces whether a given directory operation is permitted under the current configuration, and OID_SYNCHRONIZATION_ENABLED reports whether outbound synchronization is active.

Tables Accessed

The package reads FND_USER through the APPS synonym to resolve USER_GUID for a supplied user name and to read and write account attributes during synchronization. ALL_OBJECTS is queried to test for the existence or validity of dependent database objects before invoking directory operations. DUAL is used for scalar and profile-based evaluations where no table access is required.

Usage Notes

FND_LDAP_WRAPPER is not intended for direct invocation by end users. It is called by the EBS user maintenance forms, by SSO-enabled login processing, and by concurrent programs performing bulk user synchronization. The ETRM metadata records six dependent packages that reference it, indicating that Oracle-delivered SSO and user-management modules rely on it as the sole supported entry point to LDAP operations. Custom code should call the documented procedures rather than manipulating directory entries directly, and should respect the APPS_SSO_LDAP_SYNC profile option, which the package checks before permitting synchronization.