Search Results cm_typ




Overview
Explore in AI Chat

Overview

APPS.BEN_CM_TYP_TRGR_D is a reporting and inquiry view within the Oracle E-Business Suite Advanced Benefits (BEN) module. The suffix "_D" indicates that the object is a denormalized descriptive view; its purpose is to present the effective-dated rows of the BEN_CM_TYP_TRGR_F base table alongside the human-readable names, descriptions, and formula identifiers that reside in adjacent reference tables. In release 12.1.1 and 12.2.2, this view is used wherever a user-facing list of communication type triggers is required, such as in the Compensation and Communication setup pages, in concurrent program extract queries, and in custom reports or integrations that must resolve surrogate identifiers to descriptive text.

The view exposes the surrogate primary key CM_TYP_TRGR_ID together with the effective date range, the resolved formula name, the communication trigger description, and the communication type name. Because it is defined over the "_F" (date-tracked) table, only the currently effective row for a given primary key is returned for the effective date in context, and audit columns tracking the last updater are also surfaced.

Underlying Base Objects

The view is owned by APPS and is defined over the following documented objects:

All joins to the descriptive tables are outer joins (indicated by the (+) operator), so a row in BEN_CM_TYP_TRGR_F is returned even when the corresponding communication type, trigger, formula, or user row cannot be resolved. The effective-date joins additionally correlate the trigger transaction date range against the effective ranges of the communication type and formula, ensuring that the descriptive name reflects the definition in force at that time.

Key Columns

  • ROW_ID — the ROWID of the underlying BEN_CM_TYP_TRGR_F row.
  • CM_TYP_TRGR_ID — primary key of the communication type/trigger intersection.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-tracked validity window.
  • FORMULA_NAME — the Fast Formula name backing the trigger rule.
  • DESC_TXT — descriptive text for the communication trigger from BEN_CM_TRGR.
  • NAME — the communication type name from BEN_CM_TYP_F.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY — audit information, with the user ID resolved through FND_USER.

Common Use Cases and Queries

The view is typically queried to produce configuration extracts, to validate that communication types are correctly associated with their triggers, and to display descriptive values in custom OLTP or reporting pages.

SELECT cm_typ_trgr_id, name, desc_txt, formula_name,
       effective_start_date, effective_end_date
  FROM apps.ben_cm_typ_trgr_d
 WHERE TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date
 ORDER BY name, desc_txt;

A second common pattern resolves the audit trail for a specific configuration row:

SELECT cm_typ_trgr_id, last_updated_by, last_update_date
  FROM apps.ben_cm_typ_trgr_d
 WHERE cm_typ_trgr_id = :p_id;

Because all reference joins are outer joins, consumers should be prepared for NULL values in NAME, DESC_TXT, or FORMULA_NAME where the underlying setup row is missing or dates fall outside the correlated effective ranges. Filtering on the effective dates is strongly recommended for point-in-time reporting.