Search Results ben_dlvry_med




Overview
Explore in AI Chat

Overview

APPS.BENBV_CM_DLVRY_MED_TYP_V is a read-only Oracle EBS view belonging to the Advanced Benefits (BEN) module, specifically the Communications (CM) functional area. It presents delivery medium type definitions — the configurable media (for example, print, email, or electronic distribution) through which benefit communications such as enrollment notices, confirmation statements, and plan materials are delivered to participants. Because the view is defined WITH READ ONLY, it is intended strictly for query, reporting, and integration consumption rather than for application-level data maintenance, which continues to occur against the underlying base table through the BEN forms and APIs.

Objects prefixed with BENBV in Oracle EBS are business views that combine the persistent columns of a base table with decoded, user-facing values and descriptive flexfield context information. This view performs that role for the delivery medium type entity, exposing both raw code values and human-readable descriptions in a single projection, and it is therefore useful for SOA/BPEL integrations, Oracle Business Intelligence (OBIEE) or Discoverer reports, and custom concurrent programs that must present benefit communication configuration in a readable form.

Underlying Base Objects

The view is defined over two documented objects referenced in the ETRM metadata:

The FROM clause reads exclusively from BEN_CM_DLVRY_MED_TYP. The HR_BIS.BIS_DECODE_LOOKUP calls translate stored lookup codes into their display meanings, while HR_BIS.GET_SEC_PROFILE_BG_ID enforces Business Group security: the WHERE clause restricts rows to the Business Group returned by the security profile, defaulting to the row's own BUSINESS_GROUP_ID when the function returns null. This security predicate is central to the view's behavior in multi-Business-Group installations.

Key Columns

  • CM_DLVRY_MED_TYP_ID — Primary identifier for the delivery medium type record.
  • CM_DLVRY_MED_TYP_CD — The stored code for the delivery medium type.
  • BIS_DECODE_LOOKUP('BEN_DLVRY_MED', CM_DLVRY_MED_TYP_CD) — Decoded, user-facing description of the delivery medium, resolving the code against the BEN_DLVRY_MED lookup type. This column is the direct answer to searches for "ben_dlvry_med".
  • RQD_FLAG and its decoded form via BIS_DECODE_LOOKUP('YES_NO', RQD_FLAG) — Indicates whether the delivery medium type is required.
  • DFLT_FLAG and its decoded form via BIS_DECODE_LOOKUP('YES_NO', DFLT_FLAG) — Indicates whether the medium type is the default.
  • BUSINESS_GROUP_ID — The Business Group owning the record; also used for the security filter.
  • CM_DLVRY_MTHD_TYP_ID — Foreign key to the related communication delivery method type, linking the medium to its delivery method.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE — Standard WHO audit columns.
  • '_DF:BEN:BEN_CM_DLVRY_MED_TYP:CMD' — A literal descriptive flexfield context token, conventionally consumed by the BEN forms framework to identify the DFF block context for this entity.

Common Use Cases and Queries

Typical uses include validating configured delivery media prior to running a communication batch, building reference reports of available media per Business Group, and joining the view to delivery method and communication setup tables in custom extracts.

To list all configured delivery medium types with decoded values:

SELECT cm_dlvry_med_typ_id,
       cm_dlvry_med_typ_cd,
       business_group_id,
       cm_dlvry_mthd_typ_id,
       dflt_flg,
       rqd_flg
FROM   apps.benbv_cm_dlvry_med_typ_v;

To identify the default medium types available within the secured Business Group:

SELECT cm_dlvry_med_typ_cd, cm_dlvry_mthd_typ_id
FROM   apps.benbv_cm_dl_vry_med_typ_v
WHERE  dflt_flag = 'Y';

Because the view is prefixed BENBV and grants no DML capability, all references should be read-only. The BIS_DECODE_LOOKUP invocations can introduce per-row function call overhead on large result sets, so queries filtering on CM_DLVRY_MTHD_TYP_ID or BUSINESS_GROUP_ID will perform best when those predicates are pushed to the base table.