Results for “ben_cm_typ_usg_x”

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

Overview

BEN_CM_TYP_USG_X is a date-effective (X) view in the APPS schema that exposes current, active rows from the ben_cm_typ_usg_f table in Oracle Advanced Benefits (BEN). The view is part of the BEN module's standard "X" view pattern, in which a "_X" suffix denotes a runtime view that filters a "_F" (full) table by the effective date range using TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE. Its object status is VALID, and it is owned by APPS. The view is commonly used by concurrent programs, PL/SQL APIs, and ad-hoc reporting in both Oracle EBS 12.1.1 and 12.2.2 where only currently effective configuration records are relevant.

Underlying Base Objects

The view is defined over a single documented base object: BEN_CM_TYP_USG_F, referenced through a synonym. The full table stores all effective-dated rows, including historical and future versions of each record; the view restricts this to rows effective as of the current system date. The primary key of the underlying table is CM_TYP_USG_ID, and the effective-date pair EFFECTIVE_START_DATE / EFFECTIVE_END_DATE governs row validity. Because the view applies SYSDATE filtering, it never returns multi-versioned history per record — only the active version at query time.

Key Columns

The view projects the full column list of BEN_CM_TYP_USG_F, including:

• CM_TYP_USG_ID — primary identifier for the communication type usage record.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-effective window controlling visibility.
• ALL_R_ANY_CD — code indicating whether the usage applies to all or any of the associated relationships.
• CM_USG_RL — the usage rule governing communication type usage.
• CM_TYP_ID — foreign reference to the communication type.
• PGM_ID, PL_ID, PL_TYP_ID, ENRT_PERD_ID, ACTN_TYP_ID, LER_ID — foreign references to program, plan, plan type, enrollment period, action type, and legal entity/rule context.
• BUSINESS_GROUP_ID — HR business group owning the row.
• CTU_ATTRIBUTE_CATEGORY and CTU_ATTRIBUTE1 … CTU_ATTRIBUTE30 — the DFF (Descriptive Flexfield) context and attribute columns. The user's search term, CTU_ATTRIBUTE30, is one of these thirty generic segment columns, available for customer-defined data captured through the CTU_ATTRIBUTE_CATEGORY flexfield context.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER.

Common Use Cases and Queries

The most frequent use is retrieving currently effective communication type usage rules for a given plan, program, or communication type, including any DFF values stored in CTU_ATTRIBUTE30:

• Lookup by plan or program: SELECT cm_typ_usg_id, cm_typ_id, pl_id, pl_typ_id, cm_usg_rl FROM ben_cm_typ_usg_x WHERE pl_id = :p_plan_id;
• Filter on descriptive flexfield: SELECT cm_typ_usg_id, ctu_attribute30 FROM apps.ben_cm_typ_usg_x WHERE ctu_attribute_category = 'My_Context' AND ctu_attribute30 = 'VALUE';
• Reporting join to communication type and plan: join CM_TYP_ID to ben_cm_typ_f and PL_ID to ben_pl_f (both filtered to SYSDATE) to produce a current configuration report for the business group.

Because the view already restricts rows to the current effective date, users should not add redundant effective-date predicates when a "current configuration" result is intended. For historical or future-dated analysis, query the base table BEN_CM_TYP_USG_F directly.