Search Results benbv_cm_dlvry_med_typ_v




Overview
Explore in AI Chat

Overview

The BENBV_CM_DLVRY_MED_TYP_V view is a descriptive flexfield-enabled, business-group-secured database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the BEN — Advanced Benefits product family and identifies the material or medium used to create a communication. In the Benefits configuration model, a communication delivery method (for example, print, email, or web) is further qualified by the delivery medium type, which distinguishes the physical or electronic carrier used to render and transmit the communication.

The view does not store data itself. It is a reporting and integration facade over the underlying delivery-medium-type table, exposing decoded, user-facing values alongside their raw code values and surrogate identifiers. Because the view is defined with the WITH READ ONLY clause, it is intended strictly for query and extraction purposes and cannot be used as a DML target. This makes it suitable for concurrent programs, BI Publisher data templates, OAF/ADF lookups, and integration extracts that must respect Oracle EBS security conventions.

Underlying Base Objects

According to the documented ETRM metadata, the view is defined over the following referenced base objects:

  • BEN_CM_DLVRY_MED_TYP (SYNONYM) — the base Advanced Benefits table holding delivery medium type definitions, referenced in the view text through the alias CMD.
  • HR_BIS (PACKAGE) — the HR Business Intelligence/security package supplying the BIS_DECODE_LOOKUP function used for code-to-meaning decoding, and GET_SEC_PROFILE_BG_ID used for business group security filtering.

The view joins the base table to the HR_BIS package functions to translate stored lookup codes into descriptive meanings. A security predicate restricts rows to the business group returned by HR_BIS.GET_SEC_PROFILE_BG_ID; when that function returns no value, the NVL expression falls back to the row's own BUSINESS_GROUP_ID.

Key Columns

Common Use Cases and Queries

Typical scenarios include validating available medium types, populating LOVs, and extracting communication setup for audit or migration. A representative query retrieving active medium types for the current security context:

  • SELECT CM_DLVRY_MED_TYP_CD, CM_DLVRY_MED_TYP_CD_M, RQD_FLAG_M, DFLT_FLAG_M FROM BENBV_CM_DLVRY_MED_TYP_V;
  • SELECT CM_DLVRY_MED_TYP_ID, CM_DLVRY_MED_TYP_CD, DFLT_FLAG FROM BENBV_CM_DLVRY_MED_TYP_V WHERE RQD_FLAG = 'Y' ORDER BY CM_DLVRY_MED_TYP_CD;
  • Joining the view to delivery method definitions via CM_DLVRY_MTHD_TYP_ID to report the medium types associated with each communication method.

Because the view enforces read-only access and business group security, it is the recommended access path for reporting on delivery medium types rather than querying BEN_CM_DLVRY_MED_TYP directly.