Search Results ben_cm_typ




Overview
Explore in AI Chat

Overview

BEN_CM_TYP is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the BEN (Advanced Benefits) product family. The view exposes the effective-dated definition of communication types configured for the Benefits module. Communication types are the classified templates and delivery mechanisms — for example, enrollment notices, confirmation statements, and election summaries — that Advanced Benefits uses to generate participant-facing communications. The view provides the descriptive, control, and extensibility attributes required to drive those processes without requiring reporting or integration code to address the underlying table directly.

Because the object is a view rather than a table, it presents a single, filtered row per communication type version, resolving the date-effective record that is valid for the current user session. This makes it suitable for operational reporting, concurrent program logic, and interface extraction in both Oracle EBS 12.1.1 and 12.2.2, where the same APPS-owned definition is retained.

Underlying Base Objects

The documented definition of BEN_CM_TYP selects exclusively from BEN_CM_TYP_F, accessed through a synonym. All columns exposed by the view are inherited from that base table, with no joins, unions, or computed expressions other than the effective-date predicate. The view therefore functions as a thin, session-aware wrapper around the dated table.

A second referenced object, the synonym FND_SESSIONS, appears in the WHERE clause rather than the FROM clause. It supplies the session effective date used to restrict the result set:

The consequence is that the view always returns the row that is effective as of the session date, so callers never need to write their own date-range logic. The dependency on FND_SESSIONS also means results vary with the effective date assigned to the current session.

Key Columns

The view publishes the full column list of BEN_CM_TYP_F. Notable columns include:

Common Use Cases and Queries

Typical usage centers on reporting the active communication types for a business group, populating validation lists, and extracting configuration for interfaces.

  • List active communication types: 
    SELECT cm_typ_id,
       name,
       shrt_name,
       cm_usg_cd,
       whnvr_trgrd_flag
FROM   apps.ben_cm_typ
WHERE  business_group_id = :p_business_group_id
ORDER  BY name;
  • Retrieve a single type by identifier: 
    SELECT name, desc_txt, cm_usg_cd, to_be_sent_dt_cd
FROM   apps.ben_cm_typ
WHERE  cm_typ_id = :p_cm_typ_id;
  • Locate trigger-driven communications: 
    SELECT cm_typ_id, name
FROM   apps.ben_cm_typ
WHERE  whnvr_trgrd_flag = 'Y';
  • Resolve parent/child relationships: 
    SELECT child.name AS child_type,
       parent.name AS parent_type
FROM   apps.ben_cm_typ child,
       apps.ben_cm_typ parent
WHERE  child.parnt_cm_typ_id = parent.cm_typ_id;

Because the effective-date filter is applied internally, no additional date predicates are normally required. If historical perspective is needed, callers must query BEN_CM_TYP_F directly or set the session effective date via FND_SESSIONS. All queries should remain schema-qualified against APPS in 12.1.1 and 12.2.2.