Search Results process_subscription_add

Overview

FND_OID_UTIL is the Oracle E-Business Suite utility package that brokers communication between EBS and an external Oracle Internet Directory (OID) or compatible LDAP directory. It exists to keep the EBS user repository (FND_USER) synchronized with directory-side identity records, and to translate inbound directory events into the workflow and user-provisioning operations that EBS understands. The package is declared AUTHID CURRENT_USER and resides in the APPS schema, with a header dated 2012 that places it in the 12.1.1 and 12.2.2 code lines. Its classification in ETRM is UTIL, indicating it is a supporting infrastructure package rather than a public application API.

The source declares four PL/SQL record types that define the vocabulary of the interface: LDAP_USER_TYPE and LDAP_MESSAGE_TYPE, which carry the full attribute set used for a directory entry (object name, sn, cn, userPassword, telephoneNumber, street, postalCode, physicalDeliveryOfficeName, st, l, displayName, givenName, homePhone, mail, c, facsimileTelephoneNumber, description, and the Oracle-specific orclisEnabled, orclActiveStartDate, orclActiveEndDate, and orclGUID); LDAP_KEY_TYPE, which carries only the identifying and lifecycle attributes; and APPS_SSO_USER_PROFILES_TYPE, which holds the ldap_sync, local_login, and auto_link profile flags that govern SSO behavior.

Key Procedures and Functions

The twenty-nine documented routines fall into several functional groups.

• Directory connectivity: UNBIND releases the LDAP session established against the directory.
• Attribute and value retrieval: GET_OID_NICKNAME, GET_ORCLAPPNAME, GET_USER_ATTRIBUTES, GET_LDAP_ATTR_STR, GET_LDAP_EVENT_STR, and GET_LDAP_EVENT_STATUS_STR return directory attribute values and human-readable representations of LDAP event codes and statuses. GET_ENTITY_KEY_VALUE and GET_KEY resolve the identifying key for a workflow entity.
• User synchronization: SYNCH_USER_FROM_LDAP and SYNCH_USER_FROM_LDAP_NO_AUTO push directory state into EBS user records; the NO_AUTO variant suppresses automatic linking behavior.
• Provisioning and change capture: ON_DEMAND_USER_CREATE performs user creation on request, while ENTITY_CHANGES records entity-level changes for downstream workflow processing.
• Event processing: PROCESS_IDENTITY_ADD, PROCESS_IDENTITY_MODIFY, and PROCESS_IDENTITY_DELETE handle directory identity lifecycle notifications. PROCESS_SUBSCRIPTION_ADD and PROCESS_SUBSCRIPTION_DELETE manage workflow event subscriptions. PROCESS_NO_SUCCESS_EVENT handles notifications that did not complete successfully.
• Caching: SAVE_TO_CACHE persists intermediate directory data for reuse.

Tables Accessed

The package reads and writes FND_USER, the EBS user repository, as the target of directory synchronization and on-demand creation. Workflow integration is supported through WF_ATTRIBUTE_CACHE, WF_ENTITY_CHANGES, WF_EVENT_SUBSCRIPTIONS, and WF_PARAMETER_LIST_T, which hold cached attribute values, entity change records, subscription definitions, and event parameter payloads respectively. DBMS_LDAP is invoked directly for LDAP protocol operations, and PLITBLM supplies the PL/SQL table type used to pass collections of parameters in and out of the package.

Usage Notes

FND_OID_UTIL is invoked primarily from the Oracle Directory Integration and Provisioning (ODIP) event flow, from SSO/OID configuration screens and concurrent programs that perform bulk user synchronization, and from workflow business event subscriptions that fire on identity add, modify, or delete. Because the package is AUTHID CURRENT_USER, callers must hold the necessary privileges on FND_USER and the workflow objects. Eight other packages reference it, so it sits near the center of the EBS-to-directory synchronization layer. Custom code should call the synchronization and event-processing routines rather than manipulating the LDAP session or cache tables directly, and any change to the LDAP_USER_TYPE or LDAP_MESSAGE_TYPE record layout must be treated as an interface change affecting all dependent packages.