Search Results cn_obj_triggers_v

Overview

CNREDF_EVENT_TRIG_PKG is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM metadata as an "OTHER" API type. Its name and its dependency on the cn_obj_triggers_v view indicate that it belongs to the Oracle EBS object-versioning and trigger-management layer associated with the CN (Change Management / object definitions) product family. The package encapsulates the persistence and query logic required to associate an event definition with a database trigger registered in the EBS metadata repository. In practical terms, it provides the procedural back end that a maintenance form or internal routine uses to read trigger metadata, bind an event to a trigger, release that binding, and serialize concurrent edits through an explicit row lock. All five documented procedures were created on 28-DEC-1993 by Paul Mitchell, as recorded in the embedded history headers, making this a legacy but still referenced component of the EBS dictionary. The package declares no package-level state or initialization section; each routine is stateless and operates directly against the underlying view.

Key Procedures and Functions

• SELECT_COLUMNS — Resolves a trigger identifier into its descriptive attributes, returning the trigger name and the name of the table on which the trigger is defined. It is the lookup routine used to populate display fields when a user or caller supplies only a trigger ID.
• DELETE_ROW — Removes the event association from a trigger by nulling the event identifier for the supplied trigger. It does not delete the trigger itself; it clears the linkage.
• INSERT_ROW — Establishes the association between a trigger and an event by setting the event identifier on the trigger record. Despite the naming convention, the operation is implemented as an update of the event column.
• LOCK_ROW — Acquires a row-level lock on the trigger record using SELECT ... FOR UPDATE OF the event column, serializing concurrent modification attempts. It is intended to be invoked before an insert or delete operation.
• GET_TRIGGER_ID_DEFAULTS — Returns the default table identifier and table name associated with a given trigger, supporting form defaulting logic when a new event-to-trigger association is created.

Tables Accessed

The package operates exclusively through two APPS synonyms that expose dictionary views: cn_obj_triggers_v and cn_obj_tables_v. The trigger view supplies the trigger name, trigger ID, table ID, and event ID columns that the package reads and writes. The tables view supplies the table name used for display and defaulting. Both views are joined on the table identifier in SELECT_COLUMNS and GET_TRIGGER_ID_DEFAULTS, while DELETE_ROW, INSERT_ROW, and LOCK_ROW act on the trigger view alone. The absence of documented base tables reflects that these are dictionary-backed views rather than application data tables.

Usage Notes

Given its age and its inclusion in the APPS schema, CNREDF_EVENT_TRIG_PKG is most likely invoked from an Oracle Forms module within the CN product family that maintains the event-to-trigger mapping, or from custom code that manipulates the same dictionary records. The ETRM metadata records zero packages referencing it, so no internal EBS API calls it transitively; callers are therefore forms or bespoke extensions. Typical usage follows the sequence LOCK_ROW, then INSERT_ROW or DELETE_ROW to commit a change, with SELECT_COLUMNS and GET_TRIGGER_ID_DEFAULTS used for query and defaulting. Because the routine writing the event identifier is named INSERT_ROW but performs an UPDATE, integrators should treat the name as a historical artifact rather than a description of DML behavior. This package is compatible with both Oracle EBS 12.1.1 and 12.2.2, though its 1993 vintage and dependence on dictionary views mean it should be exercised with caution and validated against the target instance before use in extensions.