Search Results ldap_event




Overview
Explore in AI Chat

Overview

The LBACSYS.OLS_DIP_NTFY package is a component of Oracle Label Security (OLS), which is shipped as part of the Oracle Database and is used by Oracle E-Business Suite 12.1.1 and 12.2.2 to enforce row-level data classification and access mediation. The package name references DIP, the Directory Integration Platform, and NTFY, denoting notification handling. Its function is to support event-driven notification processing that links the Oracle Label Security infrastructure to directory integration events, so that label policy changes, user provisioning actions, and synchronization events originating from an external directory can be communicated and acknowledged within the database tier.

The package is owned by the LBACSYS schema, the dedicated schema that holds Oracle Label Security administrative objects. The ETRM record lists the package status as VALID and classifies it under the generic OTHER API classification, indicating it is an internal infrastructure package rather than a supported application-facing API. E-Business Suite deployments that implement OLS policies for sensitive data, such as human resources or financial records, inherit this package as part of the database option.

Key Procedures and Functions

The documented ETRM metadata for this object records zero exposed procedures or functions. No parameter lists are published, and none should be assumed. Based on its dependency footprint, the package behaves as an internal notification and event-listener handler rather than a callable business API. Its logic is invoked as a side effect of directory integration activity rather than through direct calls from application code.

Consistent with the naming convention and dependency set, the package is understood to process notification records that describe LDAP directory events and to reconcile event status between the directory integration layer and the Oracle Label Security repository. Because the procedures are not documented as public entry points, they are considered private implementation details subject to change with database patch levels.

Tables Accessed

Two objects are documented as referenced by LBACSYS.OLS_DIP_NTFY: LDAP_EVENT and LDAP_EVENT_STATUS. These serve as the event queue and event lifecycle tracking tables respectively. LDAP_EVENT holds directory-originated events requiring processing, while LDAP_EVENT_STATUS records the processing state of each event, allowing the notification handler to determine which events remain outstanding and which have completed.

The dependency list also shows references to the SYS.STANDARD package, the default PL/SQL package providing base datatypes and built-in functions. The APPS-synonym table reference to PLITBLM is additionally recorded. PLITBLM is a standard Oracle E-Business Suite table used in the PL/SQL profiler and instrumentation infrastructure, suggesting the package participates in or is instrumented by EBS-level PL/SQL tracing.

Usage Notes

OLS_DIP_NTFY is not intended for direct invocation from E-Business Suite forms, concurrent programs, or custom code. It is executed internally by the Oracle Label Security and directory integration runtime when LDAP events are raised against the database. Administrators encounter this object only during dependency analysis, invalid-object investigation, or Oracle Support-driven diagnostics.

Two operational points are relevant. First, both the package and its body are referenced by the package itself and by PUBLIC, so grants are broad and the object appears in cross-schema dependency reports frequently. Second, because the object resides in LBACSYS, it must never be modified or recompiled outside Oracle-supplied patches; changes to OLS system objects can invalidate the label security policy engine. When troubleshooting invalid objects in EBS after database upgrades, verify that LBACSYS.OLS_DIP_NTFY reports VALID before concluding that dependent application packages require remediation.