Search Results ldap_attr_list




Overview
Explore in AI Chat

Overview

FND_LDAP_MAPPER is a PL/SQL package owned by the APPS schema that provides the mapping and translation layer between Oracle E-Business Suite user records and an external LDAP or Oracle Internet Directory (OID) installation. Its core business function is to reconcile the attribute model used by EBS (native FND_USER columns and the WF_ATTRIBUTE_CACHE attribute-value store) with the schema and event model used by the directory server. In Oracle EBS 12.1.1 and 12.2.2 deployments that integrate with Oracle Internet Directory, this package is a foundational component of user provisioning and single sign-on, translating directory-side events into EBS-side updates and vice versa. The ETRM record classifies this object with an API classification of OTHER and records a VALID status with six documented program units. Because the package manipulates user identity data, it is invoked primarily by other Oracle-owned subscription and utility packages rather than by end users directly.

Key Procedures and Functions

The documented program units in FND_LDAP_MAPPER are:

  • MAP_SSO_USER_PROFILES — Maps SSO-related user profile values between the EBS user record and the corresponding directory attributes, supporting single sign-on configuration for the user.
  • MAP_ENTITY_CHANGES_REC — Processes a Workflow entity-changes record, mapping the change event into directory-relevant form so that EBS-side modifications propagate correctly.
  • MAP_LDAP_ATTR_LIST — Maps the LDAP attribute list, translating between the LDAP_ATTR_LIST structure and the EBS attribute representation.
  • MAP_LDAP_MESSAGE — Processes an inbound LDAP message, mapping its contents to the corresponding EBS user and attribute data.
  • MAP_OID_EVENT — Maps an OID event for processing, forming part of the event-driven synchronization path between the directory and EBS.

The metadata lists a total of six documented procedures and functions; MAP_OID_EVENT and the mapping routines above constitute the public surface used by the subscription and utility packages that depend on this package.

Tables Accessed

Access is performed through APPS synonyms. The package references FND_USER, the core EBS application user table, as the primary target for user attribute updates. It also accesses the Workflow attribute and event infrastructure: WF_ATTRIBUTE_CACHE, WF_EVENT_T, WF_ENTITY_CHANGES, and WF_ENTITY_CHANGES_S. These tables provide the cached attribute values, event payloads, and entity-change records that drive the mapping logic. DUAL, PLITBLM, and UTL_RAW are referenced for utility and raw-data conversion purposes. The presence of the Workflow entity-change and event tables confirms that synchronization is event-driven, with attribute changes captured and translated rather than polled directly.

Usage Notes

FND_LDAP_MAPPER is not typically invoked directly from a form. It is referenced by FND_LDAP_MAPPER itself (recursive/internal calls), FND_OID_SUBSCRIPTIONS, FND_OID_UTIL, and WF_OID, and it in turn depends on FND_OID_UTIL, FND_USER, LDAP_ATTR_LIST, LDAP_EVENT, WF_ATTRIBUTE_CACHE, and WF_EVENT_T. The reference to FND_OID_UTIL is significant given the search term "fnd_oid_util": FND_OID_UTIL both calls into and is called by FND_LDAP_MAPPER, so the two packages form a mutually dependent pair in the OID integration stack. In practice, the package is executed as part of OID subscription processing, SSO user provisioning, and Workflow-driven user synchronization events. Customizations should not call its internal mapping routines directly; integrators should work through the subscription and utility packages that Oracle provides.