Search Results entry_delete




Overview
Explore in AI Chat

Overview

APPS.WF_OID is a PL/SQL package within the Oracle E-Business Suite Workflow directory services layer. Its role is to bridge Oracle Workflow with an LDAP-based identity store, most commonly Oracle Internet Directory (OID), so that user, group, subscriber, and subscription activity in EBS remains synchronized with the directory service. The package name reflects that function: WF (Workflow) + OID (Oracle Internet Directory).

The package declares a formal vocabulary of event types — ENTRY_ADD, ENTRY_DELETE, ENTRY_MODIFY, USER_ADD, USER_DELETE, USER_MODIFY, IDENTITY_ADD, IDENTITY_DELETE, IDENTITY_MODIFY, GROUP_ADD, GROUP_DELETE, GROUP_MODIFY, SUBSCRIBER_ADD, SUBSCRIBER_DELETE, SUBSCRIBER_MODIFY, SUBSCRIPTION_ADD, SUBSCRIPTION_DELETE, and SUBSCRIPTION_MODIFY — along with attribute type constants (ATTR_TYPE_STRING, ATTR_TYPE_BINARY, ATTR_TYPE_ENCRYPTED_STRING, ATTR_TYPE_DATE) and modification types (MOD_ADD, MOD_DELETE, MOD_REPLACE). It also defines the event disposition constants EVENT_SUCCESS, EVENT_ERROR, and EVENT_RESEND, plus the return values EVENT_FOUND (0) and EVENT_NOT_FOUND (1403). The error code is documented as zero for success and non-zero for error and resend conditions. In EBS 12.1.1 and 12.2.2 this package is shipped as a noship-tracked source file but is an active part of the Workflow/LDAP integration surface.

Key Procedures and Functions

The ETRM metadata documents seven callable units. Parameter signatures are not exposed here and are deliberately not reproduced.

  • PUTOIDEVENT — places (writes) an event into the directory event stream, using the event type constants above to classify the change being propagated.
  • GETAPPEVENT — retrieves an application-level event for processing. Returns the documented result codes EVENT_FOUND (0) or EVENT_NOT_FOUND (1403).
  • PUTAPPEVENTSTATUS — records the disposition of a processed event, using EVENT_SUCCESS, EVENT_ERROR, or EVENT_RESEND.
  • USER_CHANGE — handles a user-level change and drives the corresponding directory update.
  • GET_OID_SESSION — obtains a session handle against the LDAP directory for subsequent operations.
  • UNBIND — releases the LDAP session established by GET_OID_SESSION.
  • FUTURE_CALLBACK — reserved callback entry point for deferred or future event handling.

Because EVENT_ERROR is one of the package's own constants, it is the value written by PUTAPPEVENTSTATUS to mark an event that failed during directory propagation — the likely context in which a user searches for "event_error" against this object.

Tables Accessed

The documented references are a mixture of EBS tables and PL/SQL-supplied packages:

  • WF_EVENT_T — the Workflow event object type, used to construct and consume the events being propagated.
  • WF_PARAMETER_LIST_T — carries the parameter payload attached to each event.
  • WF_ENTITY_CHANGES — tracks entity-level changes that drive directory synchronization.
  • FND_USER — the EBS user repository, read to resolve user and identity attributes.
  • DBMS_LDAP — the Oracle-supplied LDAP API used to bind, search, and modify entries in OID.
  • PLITBLM — the standard EBS PL/SQL table/index-by table type used for array-style parameter passing.

Usage Notes

WF_OID is invoked indirectly rather than interactively. It is a target of the Workflow LDAP synchronization infrastructure, which fires it in response to user, group, subscriber, and subscription changes originating in EBS forms such as the Users form and Workflow administrator responsibilities. It is not typically called from a standard concurrent program request window.

For troubleshooting, the EVENT_ERROR and EVENT_RESEND dispositions are key diagnostic markers: rows indicating an error mean the EBS-side change did not reach the directory, while a resend indicates the operation should be retried. Because referenced-by metadata shows three dependent packages, customizations should call WF_OID only through its documented procedures and must not assume that OFFSET order or parameter signatures will remain stable across patches. Direct modification of the underlying WF_EVENT_T or WF_ENTITY_CHANGES data is not supported.