Results for “proc_cd”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BEN_CM_TRGR is a table in the BEN (Advanced Benefits) schema of Oracle E-Business Suite, documented as VALID in both 12.1.1 and 12.2.2. Its documented description is "Communication trigger," identifying it as the definitional entity that governs when a benefits communication event is fired. In Advanced Benefits, communications (enrollment notices, confirmation statements, life-event reminders, and similar outputs) are not generated ad hoc; they are driven by trigger definitions that determine the condition, source, and processing behavior for the communication. BEN_CM_TRGR stores those trigger definitions.

The table is referenced by two intersection tables, BEN_CM_TYP_TRGR_F and BEN_PER_CM_TRGR_F, which associate triggers with communication types and with persons or programs respectively. Because other tables carry the CM_TRGR_ID foreign key toward BEN_CM_TRGR, the object functions as an authoritative parent record. Heuristically, the mined FK topology classifies BEN_CM_TRGR as hub-leaning: a stable, low-cardinality keyed entity whose descriptive attributes are referenced by dependent relationship rows.

Key Information Stored

The documented physical schema contains 10 columns. The primary key, BEN_CM_TRGR_PK, is defined on the single surrogate column CM_TRGR_ID, which uniquely identifies each trigger definition and is the column propagated into the dependent foreign-key tables.

• CM_TRGR_ID — surrogate primary key and sole unique index; the join column for all dependent relationships.
• CM_TRGR_SRC_CD — source code indicating the origin or category from which the trigger is evaluated.
• CM_TRGR_TYP_CD — trigger type code classifying the kind of event that causes the communication to be issued.
• PROC_CD — processing code controlling how the trigger is handled during communication generation.
• DESC_TXT — descriptive text providing the user-facing name or description of the trigger.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard Oracle EBS WHO columns providing audit and concurrency tracking.

Note that no separate business-key unique index beyond the surrogate primary key is documented. CM_TRGR_ID therefore serves simultaneously as surrogate key and as the effective business identifier for downstream associations.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include enumerating the triggers available for a communication type, auditing who created or last modified a trigger definition, and verifying which triggers are wired into person-level or type-level communication configuration.

SELECT t.cm_trgr_id,
       t.cm_trgr_src_cd,
       t.cm_trgr_typ_cd,
       t.proc_cd,
       t.desc_txt
FROM   ben.ben_cm_trgr t
ORDER  BY t.cm_trgr_src_cd, t.cm_trgr_typ_cd;

To inspect trigger-to-communication-type wiring:

SELECT t.cm_trgr_id,
       t.desc_txt,
       f.cm_typ_id
FROM   ben.ben_cm_trgr t,
       ben.ben_cm_typ_trgr_f f
WHERE  t.cm_trgr_id = f.cm_trgr_id;

Audit queries against the WHO columns support SOX-style change tracking and troubleshooting of unexpected communication generation.

Related Objects

• BEN_CM_TYP_TRGR_F — associates triggers with communication types; join on CM_TRGR_ID.
• BEN_PER_CM_TRGR_F — associates triggers with persons or program-level communication configuration; join on CM_TRGR_ID.
• BEN_CM_TRGR_PK — the unique index enforcing the primary key on CM_TRGR_ID.

These two intersection tables are the only FK relationships documented in the ETRM metadata, and they establish BEN_CM_TRGR as the hub from which communication trigger membership is derived.