Search Results getcreatebase_template

Overview

FND_OID_PLUG is an internal Oracle E-Business Suite package that implements the Oracle Internet Directory (OID) / LDAP plug-in layer used by Oracle EBS user and realm resolution. Its central purpose is to map an EBS user identity to directory-side configuration: the realm distinguished name (DN), the user repository created in the directory, the relative distinguished name (RDN), the search base, the search filter, and the attribute used for nicknames. The package header carries the AFSCOPGS header identifier and defines two plug-in models: G_STATIC (0), where the realm and user create base are fixed, and G_DYNAMIC (1), where the realm and user create base depend on the specific user being resolved. This distinction is exposed through the pluginType and setPlugin entry points, allowing the directory integration to operate either against a single fixed directory container or against per-user containers.

The source comment explicitly documents that plug-ins must implement a Realm(username) and UserRepository(username) contract, meaning FND_OID_PLUG acts as the abstraction bridge between generic EBS directory integration code and a specific directory layout convention. The getRealmDN function is the primary accessor associated with the search term "get_realm_dn," returning the directory DN of the realm for a given user.

Key Procedures and Functions

• SETPLUGIN / SETPLUGIN_OLD — Initializes the active plug-in context (default realm, default user repository, and plug-in name), establishing the configuration the package uses for subsequent resolution calls. SETPLUGIN_OLD provides backward compatibility.
• GET_REALM_DN / GETREALMDN — Return the distinguished name of the realm resolved for a user; GET_REALMDN corresponds to the internal getRealmDN declaration. This is the entry point returned for the "get_realm_dn" query.
• GET_DEFAULT_REALM, GET_DEFAULTREALM_TEMPLATE, GETREALM_TEMPLATE, GETDEFAULTREALM_TEMPLATE — Resolve and provide templated values for the default realm, supporting both direct lookup and template substitution patterns.
• GETREALMLIST — Enumerates the realms available in the directory configuration.
• GETCREATEBASE_TEMPLATE, GETDEFAULTCREATEBASE_TEMPLATE — Supply the template and default values for the user create base (repository) in which new directory entries are placed.
• GETRDN_TEMPLATE — Provides the template used to construct the relative distinguished name of a directory entry.
• GETREALM_FROM_USER_DN — Derives the realm identity from a supplied user DN, supporting reverse resolution.
• GETNICKNAMEATTR — Returns the directory attribute designated for nicknames, used during identity matching.
• COUNT_ATTRIBUTES — Counts the attributes present in an LDAP attribute collection, used to determine whether a returned entry set is populated.
• COMPLETEFORCREATE, FIXUPLDAPUSER — Post-processing and repair routines used when directory users are created or must be reconciled/corrected against EBS user definitions. FIXUPLDAPUSER_TEMPLATE provides a templated variant of this repair logic.
• HELPER_NEWEMPTYCOLLECTION — Constructs an empty LDAP attribute collection used as the working structure for subsequent attribute assignment during directory operations.

Tables Accessed

• FND_USER — The core EBS user table; read to identify the user being resolved and to synchronize directory identity attributes.
• DBMS_LDAP — The Oracle-supplied LDAP PL/SQL API used to bind, search, and retrieve entries from the directory.
• DBMS_DESCRIBE / DBMS_SQL — Dynamic SQL utilities used for runtime introspection and execution of dynamic statements against the directory configuration.
• DBA_OBJECTS / USER_OBJECTS — Data dictionary views queried to determine the existence and status of package objects and dependent definitions.
• PLITBLM — The PL/SQL table type used for attribute and collection handling.

Usage Notes

FND_OID_PLUG is not a public API. It is invoked indirectly by EBS directory integration and user-management flows that require OID/LDAP synchronization, including user creation, login-time identity resolution, and maintenance of the relationship between FND_USER records and their directory counterparts. The package is referenced by five other packages within the EBS schema, indicating that it functions as a shared internal service rather than a standalone callable interface. Customizations should not call it directly; instead, the supported EBS user and directory integration APIs should be used. Where extension is required, the documented plug-in contract (Realm and UserRepository implementations) is the intended customization point, since the source comments state that plug-ins must implement these functions.