Search Results ben_cm_typ_x

Overview

BEN_CM_TYP_X is a seeded, read-only view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the BEN product family, Oracle Advanced Benefits, and exposes configuration metadata for communication types. A communication type identifies the category of a benefits communication — for example, an enrollment confirmation, a life event notification, or a plan information mailing — and carries the business rules that govern whether and how that communication is produced.

The "_X" suffix follows the standard Oracle EBS convention for a "translated" or date-effective view. Rather than exposing every historical row of the underlying table, BEN_CM_TYP_X applies a date filter so that only rows current as of the query date are returned. This makes it a convenient source for concurrent programs, BI Publisher data models, and custom integrations that need the currently effective definition of each communication type without writing date-effective predicates themselves. Because the view is a stored query over a single base table and is not itself a table, it holds no data and must never be treated as a target for DML.

Underlying Base Objects

The view is defined exclusively over BEN_CM_TYP_F, resolved through an APPS synonym. BEN_CM_TYP_F is the date-effective (datetracked) base table that stores communication type definitions, with EFFECTIVE_START_DATE and EFFECTIVE_END_DATE delimiters on each logical record. The view text selects a fixed column list from this table and filters with TRUNC(SYSDATE) BETWEEN CCT.EFFECTIVE_START_DATE AND CCT.EFFECTIVE_END_DATE, so multiple historical versions of a communication type collapse to the single row effective today. Because the view is a thin projection, it inherits the base table's row-level security and business group partitioning through BUSINESS_GROUP_ID, and it inherits all datetrack behavior from the underlying table — historical or future-dated definitions are not visible through this view.

Key Columns

• CM_TYP_ID — Primary key of the communication type; the value referenced by foreign keys elsewhere in the BEN schema.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Date-effective range of the current row, retained in the view even though the predicate already restricts to the current version.
• NAME / SHRT_NAME / DESC_TXT — User-facing name, short name, and description of the communication type.
• CM_TYP_RL / CM_USG_CD — Rule and usage code controlling when the communication type is applicable.
• WHNVR_TRGRD_FLAG — Indicates whether the communication is triggered whenever the associated event occurs.
• MX_NUM_AVLBL_VAL / TRK_MLG_FLAG / PC_KIT_CD — Maximum available value, tracking flag, and package kit code.
• TO_BE_SENT_DT_CD / TO_BE_SENT_DT_RL — Rules for the date on which the communication should be sent.
• INSPN_RQD_FLAG / INSPN_RQD_RL — Whether inspection is required and the associated rule.
• RCPENT_CD — Recipient code defining the default audience.
• PARNT_CM_TYP_ID — The parent communication type identifier, enabling hierarchical (parent/child) communication type structures. This is the column most directly relevant to the search term parnt_cm_typ_id; it is a self-referencing attribute within the same table.
• BUSINESS_GROUP_ID — Owning business group, the primary partitioning attribute for multi-organization access.
• CCT_ATTRIBUTE_CATEGORY and CCT_ATTRIBUTE1–30 — Descriptive flexfield segments for customer-defined extensions.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, OBJECT_VERSION_NUMBER — Standard WHO columns and optimistic locking column.

Common Use Cases and Queries

The view is typically used to list currently effective communication types, to resolve a parent/child hierarchy, and to drive communication generation logic in reports and interfaces.

• Listing current communication types for a business group:

SELECT cm_typ_id, name, shrt_name, cm_usg_cd
FROM   apps.ben_cm_typ_x
WHERE  business_group_id = :p_bg_id
ORDER  BY name;

• Resolving the parent of a communication type using PARNT_CM_TYP_ID:

SELECT child.cm_typ_id       AS child_id,
       child.name            AS child_name,
       parent.cm_typ_id      AS parent_id,
       parent.name           AS parent_name
FROM   apps.ben_cm_typ_x child,
       apps.ben_cm_typ_x parent
WHERE  child.parnt_cm_typ_id = parent.cm_typ_id
AND    child.business_group_id = :p_bg_id;

• Identifying top-level communication types (those with no parent):

SELECT cm_typ_id, name
FROM   apps.ben_cm_typ_x
WHERE  parnt_cm_typ_id IS NULL
AND    business_group_id = :p_bg_id;

When querying, note that the view already enforces the effective-date predicate; adding additional date conditions on EFFECTIVE_START_DATE or EFFECTIVE_END_DATE is redundant. To inspect historical or future-dated definitions, query BEN_CM_TYP_F directly with explicit datetrack predicates instead of the view. As with all Advanced Benefits setup data, joins to other BEN entities should be constrained on BUSINESS_GROUP_ID to avoid cross-business-group leakage.