Results for “ben_pc_kit”

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

Overview

APPS.BENBV_CM_TYP_V is a read-only reporting view in the Oracle E-Business Suite Benefits (BEN) module. It presents configuration data for "Communication Types," which govern the correspondence, notifications, and letters generated during benefits enrollment and life-event processing. The view flattens the underlying communication-type entity together with its translated name and a series of lookup-decoded descriptions, yielding a single consumable row per communication type per effective date. Because the view is defined WITH READ ONLY and conforms to the ETRM business-view naming convention (BENBV_), it is intended for reporting, extracts, and integration rather than for transactional maintenance. The user search term "ben_rcpent" corresponds directly to the RCPENT_CD column of this view, which designates the recipient of a communication.

Underlying Base Objects

The view is defined over the following documented objects in the APPS schema: BEN_CM_TYP_F (SYNONYM), the base ("_F") table holding communication-type definitions; BEN_CM_TYP_F_TL (SYNONYM), its translation table supplying language-specific NAME values; and the HR_BIS package, used solely through the BIS_DECODE_LOOKUP function to translate coded values. The join is on CM_TYP_ID and EFFECTIVE_START_DATE between the base and translation tables, restricted by TL.LANGUAGE = USERENV('LANG'), so each query returns names in the session's current language. A descriptive flexfield reference ('_DF:BEN:BEN_CM_TYP_F:CCT') is embedded to expose the DFF context. All three referenced objects are documented in ETRM 12.2.2; the same definition is applicable to 12.1.1.

Key Columns

• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Date-effective range for each communication-type record.
• NAME, DESC_TXT, SHRT_NAME — Translated display name, description, and short name from the TL table.
• CM_TYP_ID, BUSINESS_GROUP_ID, PARNT_CM_TYP_ID — Primary identifier, business group, and parent communication type (for hierarchies).
• RCPENT_CD — Recipient code, decoded via lookup 'BEN_RCPENT'; the exposed value behind the "ben_rcpent" lookup the user searched for.
• TO_BE_SENT_DT_CD — Timing code for when the communication is sent, decoded via 'BEN_TO_BE_SENT_DT'.
• CM_USG_CD — Communication usage code, decoded via 'BEN_CM_USG'.
• PC_KIT_CD — Plan/kit association code, decoded via 'BEN_PC_KIT'.
• WHNVR_TRGRD_FLAG, TRK_MLG_FLAG, INSPN_RQD_FLAG — Yes/No indicator flags decoded through the 'YES_NO' lookup (whenever triggered, track mailing, inspection required).
• CM_TYP_RL, MX_NUM_AVLBL_VAL, INSPN_RQD_RL, TO_BE_SENT_DT_RL — Rule and numeric control attributes.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE — Standard WHO audit columns.

Common Use Cases and Queries

Typical applications include listing all communication types and their recipients for a business group, validating lookup configuration, and feeding external correspondence or letter-generation processes. The following query filters by recipient code and returns the decoded description:

• SELECT cm_typ_id, name, rcpent_cd, desc_txt FROM apps.benbv_cm_typ_v WHERE rcpent_cd = 'ben_rcpent' AND business_group_id = :p_bg_id ORDER BY name;
• SELECT name, shrt_name, cm_usg_cd, whnvr_trgrd_flag FROM apps.benbv_cm_typ_v WHERE TRUNC(SYSDATE) BETWEEN effective_start_date AND NVL(effective_end_date, SYSDATE+1);

Because the view resolves lookups at runtime and returns only translated names, it is well suited to ad-hoc reporting and interfaces where code-to-meaning translation is required without direct joining to lookup tables.