Results for “parnt_cm_typ”

4 results




Overview
Explore in AI Chat

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

Overview

APPS.BEN_CM_TYP_D is a reporting view in the Oracle E-Business Suite Benefits (BEN) module. It exposes the descriptive and translated attributes of "communication types" (CM_TYP) — the configurable categories used to classify communications such as enrollment notices, confirmation statements, and benefit plan correspondence. The view consolidates both the DFF-free base record and the meaning/name derivations (lookup meanings such as INSPN_RQD_MEANING) so that concurrent programs, Oracle Reports, and custom extracts can retrieve fully resolved values in a single select.

The object is a view (not a table), owned by APPS with FND Design Data reference BEN.BEN_CM_TYP_D, and is marked VALID. A warning in the ETRM metadata states it is for Oracle Internal Use Only and is not supported for direct customer access except from standard Oracle Applications programs. Developers should therefore treat it as a read-only integration and reporting surface.

The user search term "inspn_rqd_meaning" maps directly to the INSPN_RQD_MEANING column of this view, which returns the human-readable lookup meaning indicating whether an inspection is required for the communication type.

Underlying Base Objects

The view depends on the following documented objects:

No database object is documented as referencing this view, confirming its role as a terminal reporting layer rather than a data-entry path.

Key Columns

  • ROW_ID / CM_TYP_ID — ROWID locator and the numeric communication-type identifier.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — date-tracked validity window inherited from the _F table.
  • NAME / CM_TYP_NAME / SHRT_NAME / DESC_TXT — display name, translated name, short name, and long description.
  • CM_USG_MEANING — lookup meaning for the communication usage (for example, the context in which the type is applied).
  • INSPN_RQD_MEANING / INSPN_RQD_NAME — meaning and name indicating inspection requirement, the columns targeted by the user's search.
  • WHNVR_TRGRD_MEANING — whether the communication is triggered on an event.
  • PC_KIT_MEANING, TRK_MLG_MEANING, RCPENT_MEANING — flags for printed kit, mileage tracking, and recipient handling.
  • MX_NUM_AVLBL_VAL — maximum numeric value associated with the type.
  • PARNT_CM_TYP_NAME — parent communication type for hierarchical relationships.
  • LAST_UPDATE_DATE / LAST_UPDATED_BY — standard Who columns for audit and concurrency tracking.

Common Use Cases and Queries

Typical scenarios include reporting on active communication types, filtering by inspection requirement, and embedding the view in Oracle Reports or BI Publisher extracts for Benefits enrollment packs. Oracle advises sourcing it only from standard programs, so custom SQL should be used for read-only extraction.

Sample query — current inspection-relevant communication types:

  • SELECT cm_typ_id, cm_typ_name, inspn_rqd_meaning, cm_usg_meaning, effective_start_date, effective_end_date FROM apps.ben_cm_typ_d WHERE TRUNC(SYSDATE) BETWEEN effective_start_date AND NVL(effective_end_date, SYSDATE) AND inspn_rqd_meaning = 'Yes';

Sample query — audit of last-modified communication types:

  • SELECT cm_typ_id, name, last_updated_by, last_update_date FROM apps.ben_cm_typ_d ORDER BY last_update_date DESC;

Sample query — parent/child hierarchy:

  • SELECT cm_typ_name, parnt_cm_typ_name, shrT_name FROM apps.ben_cm_typ_d WHERE parnt_cm_typ_name IS NOT NULL;

Because the view is unsupported for direct modification and is not referenced by other database objects, it is best treated as a stable read-only window into Benefits communication-type configuration for 12.1.1 and 12.2.2.