Search Results cnredf_event_trig_pkg

Overview

APPS.CNREDF_EVENT_TRIG_PKG is a PL/SQL package that forms part of the Oracle E-Business Suite Event Triggers and Event Types infrastructure, historically associated with the Oracle Contracts (CN) and the former Oracle Sales for Handhelds/Field Sales application family. The "CNREDF" prefix indicates that the object originated within the Contracts event definition framework, where "REDF" reflects the internal event definition naming convention used by the application. In Oracle EBS 12.1.1 and 12.2.2, the package is deployed in the APPS schema with a status of VALID and is classified in the ETRM repository as an "OTHER" API, meaning it is a supporting package rather than a formally published public API.

The package provides the low-level data access layer for the event trigger definition entity. An event trigger record associates a business event with the actions or subscriptions that should fire when the event is raised. The package encapsulates the standard CRUD (create, read, update, delete) and concurrency-control operations required by the maintenance forms and internal processes that manage these trigger definitions.

Key Procedures and Functions

The ETRM metadata documents five procedures or functions within the package:

• SELECT_COLUMNS — Retrieves the columns of an event trigger definition row. This routine supplies the query-side logic used by the maintenance form to populate the trigger definition block with the stored attribute values for a given trigger.
• INSERT_ROW — Creates a new event trigger definition record. It writes the supplied trigger attributes into the underlying base table as part of the form's insert processing.
• DELETE_ROW — Removes an existing event trigger definition record. It is invoked when a user or process deletes a trigger definition from the maintenance form.
• LOCK_ROW — Acquires a row-level lock on the trigger definition. This supports Oracle Forms' optimistic locking model, ensuring that a record cannot be modified concurrently by another session without detection.
• GET_TRIGGER_ID_DEFAULTS — Returns default attribute values for a new trigger definition, typically including the next trigger identifier. It is used when the form initializes a blank record so that required key and default columns are pre-populated before the user commits the row.

No parameter lists are documented in the ETRM extract, and none should be assumed. The names and the CRUD pattern indicate that the procedures are intended to be called by the owning application's forms and internal logic rather than by external integrations.

Tables Accessed

The ETRM metadata records no tables accessed via APPS synonyms for this package. This is consistent with the package being a thin data-access wrapper that references its base objects directly (or through private, package-level constructs) rather than through public synonyms. The underlying storage is the Contracts event trigger definition table within the CN/REDF schema family. Because the metadata does not enumerate the tables, the specific base table names cannot be confirmed from the documentation alone.

Usage Notes

CNREDF_EVENT_TRIG_PKG is referenced by no other packages according to the ETRM dependency report, which indicates it is a leaf-level utility invoked directly by the application's maintenance forms — most likely the Contracts event trigger setup form — and by internal routines that manage event trigger definitions. The dependency listing shows the package depending on SYS.STANDARD and being self-referenced, a typical profile for a Forms-support package.

Because the package is classified as "OTHER" rather than as a public API, custom code should not invoke it as a supported integration point. Any direct calls risk breaking when the package body changes. Integrations that need to manage event triggers should instead use the supported Contracts event APIs or the standard event system interfaces. When troubleshooting form-level errors on the event trigger setup screen, this package is a likely candidate for inspection at the database level.