Results for “ben_cm_typ_usg_d”

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

Overview

BEN_CM_TYP_USG_D is a reporting view owned by the APPS schema within the Oracle Advanced Benefits (BEN) product. It presents configuration data describing how a particular communication type is used within a benefits program. In the Oracle EBS data model, the suffix "_D" on a BEN view conventionally denotes the date-tracked (datetrack) reporting layer over a corresponding "_F" base table. Accordingly, BEN_CM_TYP_USG_D exposes the rows of BEN_CM_TYP_USG_F and is the object that reporting tools, concurrent programs, and integrations should query rather than the base table directly.

The view is significant because it carries the ALL_R_ANY_CD column, which is the column most frequently associated with the search term "all_r_any_cd". This column encodes whether the usage rule defined by a given row applies to all persons or only to any (some) qualifying persons, and it is therefore central to interpreting eligibility and communication targeting logic.

Underlying Base Objects

The documented view definition selects exclusively from BEN_CM_TYP_USG_F, aliased as CTU, and exposes every column from that base table without joins, filters, or transformation. Consequently, BEN_CM_TYP_USG_D is a straight projection of its base object. The documented referenced objects list BEN_CM_TYP_USG_F and FND_USER, both accessed through synonyms; FND_USER is referenced indirectly through the standard WHO columns (LAST_UPDATED_BY, CREATED_BY) that carry user identifiers into the reporting layer. Because the view adds no business logic, any row visible in the base table appears identically in the view, subject to the user's read privileges on the APPS schema objects.

Key Columns

• CM_TYP_USG_ID — Primary identifier for the communication type usage record.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Datetrack boundaries defining the period during which the configuration row is valid.
• ALL_R_ANY_CD — Indicates whether the usage applies to all persons or any qualifying person; the primary focus of "all_r_any_cd" lookups.
• CM_USG_RL — The usage rule governing how the communication type may be applied.
• DESCR_TEXT — Descriptive text associated with the usage definition.
• PGM_ID / PL_ID / PL_TYP_ID — Foreign keys to the benefit program, plan, and plan type to which the usage is tied.
• ENRT_PERD_ID / ACTN_TYP_ID — References to the enrollment period and action type context.
• CM_TYP_ID — The communication type being used.
• LER_ID / BUSINESS_GROUP_ID — Legislative data group reference and the business group (operating unit) owning the row.
• CTU_ATTRIBUTE_CATEGORY and CTU_ATTRIBUTE1–10 — Descriptive flexfield segments for customer-defined extensions.
• WHO Columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, and OBJECT_VERSION_NUMBER, the standard audit and locking columns.

Common Use Cases and Queries

Typical uses include reporting the communication types configured for a benefits program, auditing which usages are flagged as applying to all versus any persons, and joining to plan and program tables to resolve names for extract or interface files. A representative query filtering on the search term column follows:

SELECT ctu.cm_typ_usg_id, ctu.all_r_any_cd, ctu.cm_typ_id, ctu.pgm_id, ctu.pl_id, ctu.effective_start_date, ctu.effective_end_date FROM apps.ben_cm_typ_usg_d ctu WHERE ctu.all_r_any_cd = :p_all_r_any_cd AND TRUNC(SYSDATE) BETWEEN ctu.effective_start_date AND ctu.effective_end_date ORDER BY ctu.pgm_id, ctu.cm_typ_id;

To resolve the owning user for audit purposes, the view may be joined to FND_USER on LAST_UPDATED_BY = USER_ID. Date-effective filtering against EFFECTIVE_START_DATE and EFFECTIVE_END_DATE should accompany nearly every query, since the underlying table is datetrack-enabled and historical rows remain present. All queries must be schema-qualified with APPS unless a synonym is created in the executing schema.