Search Results ben_cm_dlvry_mthd_typ




Overview

BEN.BEN_CM_DLVRY_MTHD_TYP is a configuration (setup) table within the Oracle Advanced Benefits (BEN) module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It holds the definition of communication delivery method types — the configurable categories that govern how benefits-related communications (enrollment notices, confirmation statements, plan documents, and similar correspondence) are delivered to participants and dependents. Records in this table act as the parent classification layer above the individual delivery media, so a delivery method type can be associated with one or more concrete media definitions.

From a Data Vault modeling perspective, the metadata classifies this object as hub-leaning. The table carries a single-column surrogate primary key and serves primarily as a stable, referenceable list of business concepts rather than a transactional or event record. A Data Vault design would therefore most naturally treat BEN_CM_DLVRY_MTHD_TYP as a hub, with descriptive attributes such as the default and required flags modelled as a satellite on that hub. Because the documented foreign keys show other tables referencing this one (and no outbound business foreign keys other than CM_TYP_ID), there is little evidence of link-role behaviour.

Key Information Stored

The table is documented with 43 physical columns. The most significant are:

  • CM_DLVRY_MTHD_TYP_ID — the surrogate primary key, enforced by unique index BEN_CM_DLVRY_MTHD_TYP_PK. This is the value referenced by child tables and is the only documented unique business-key candidate; there is no separate natural-key unique index recorded.
  • CM_DLVRY_MTHD_TYP_CD — the user-visible code identifying the delivery method type; this is the practical lookup value used in setup and reporting.
  • BUSINESS_GROUP_ID — the operating unit / business group that owns the setup row, enabling multi-tenant style partitioning of benefits configuration.
  • DFLT_FLAG — indicates whether the delivery method type is used as the default when no explicit selection is made.
  • RQD_FLAG — indicates whether the method is mandatory for the associated communication.
  • CM_TYP_ID — the communication type this delivery method type belongs to, linking the row to the broader communication taxonomy.
  • CMT_ATTRIBUTE_CATEGORY and CMT_ATTRIBUTE1 through CMT_ATTRIBUTE30 — the descriptive flexfield (DFF) context and segment columns, providing customer-extensible attributes.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle who-column audit set.
  • OBJECT_VERSION_NUMBER — the optimistic locking column used by the Oracle Application Framework (OAF) / BC4J stack to detect concurrent updates.

Common Use Cases and Queries

Typical uses centre on setup validation, communication configuration reporting, and integration extracts.

  • Listing all delivery method types for a business group, with their default and required behaviour:
SELECT CM_DLVRY_MTHD_TYP_ID, CM_DLVRY_MTHD_TYP_CD, DFLT_FLAG, RQD_FLAG
FROM   BEN.BEN_CM_DLVRY_MTHD_TYP
WHERE  BUSINESS_GROUP_ID = :p_bg_id
ORDER  BY CM_DLVRY_MTHD_TYP_CD;
  • Resolving the delivery media attached to each delivery method type (joining the child table):
SELECT t.CM_DLVRY_MTHD_TYP_CD, m.CM_DLVRY_MED_TYP_ID
FROM   BEN.BEN_CM_DLVRY_MTHD_TYP t,
       BEN.BEN_CM_DLVRY_MED_TYP m
WHERE  m.CM_DLVRY_MTHD_TYP_ID = t.CM_DLVRY_MTHD_TYP_ID
AND    t.BUSINESS_GROUP_ID = :p_bg_id;
  • Identifying the default method for a given communication type for use in enrollment processing logic.
  • Extracting setup rows for a data warehouse or data vault staging load, keyed on CM_DLVRY_MTHD_TYP_ID and carrying the DFF attributes as satellite context.

Related Objects

  • BEN.BEN_CM_DLVRY_MED_TYP — the primary dependent table. Its CM_DLVRY_MTHD_TYP_ID column carries the foreign key to BEN_CM_DLVRY_MTHD_TYP_PK, so this table defines the media types available under each delivery method type.
  • CM_TYP_ID references the communication type definition within the Advanced Benefits communication setup, establishing the parent classification of each delivery method type.
  • The Advanced Benefits communication configuration (the BEN_CM_* family) depends on this row set when resolving how a given communication is delivered to a participant.
  • Standard EBS concurrent programs and OAF-based Benefits setup pages that maintain communication delivery configuration read and write this table, observing OBJECT_VERSION_NUMBER for concurrency control.
  • Reporting and integration extracts that publish benefits communication setup typically join BEN_CM_DLVRY_MTHD_TYP to BEN_CM_DLVRY_MED_TYP and to the communication type table to produce a complete delivery routing view.