Search Results dpnt_person

Overview

APPS.BEN_PER_CM_D is a reporting and integration view within the Oracle E-Business Suite Advanced Benefits (Oracle Benefits) module. It exposes communication records associated with benefit participants, presenting a denormalized, human-readable projection of the underlying BEN_PER_CM_F transactional table and its related lookups. The view resolves surrogate foreign keys into descriptive names — participant full names, communication type names, life event reason names, and the application user who last updated the record — so that downstream reports, extracts, and interfaces do not need to perform those joins themselves.

The "_D" suffix is a common Oracle naming convention indicating a "descriptive" or denormalized view. In the ETRM 12.2.2 metadata the view is owned by APPS and is documented with the title VIEW: APPS.BEN_PER_CM_D. It is primarily consumed for participant communication tracking, correspondence auditing, and Benefits self-service reporting.

Underlying Base Objects

The view is defined over the following documented base objects:

• BEN_PER_CM_F (synonym) — the primary driving table, holding person communication records. It supplies PER_CM_ID, dates, and foreign keys.
• BEN_PER_IN_LER (synonym) — the person-in-life-event-reason intersection, joined on PER_IN_LER_ID and BUSINESS_GROUP_ID. A filter excludes rows whose PER_IN_LER_STAT_CD is 'VOIDD' or 'BCKDT'.
• BEN_LER_F (synonym) — the life event reason, providing LER.NAME.
• BEN_CM_TYP_F (synonym) — the communication type, providing CM_TYP.NAME.
• PER_ALL_PEOPLE_F (synonym, referenced twice) — joined once as BNF_PERSON for the beneficiary and once as DPNT_PERSON for the dependent, each contributing FULL_NAME.
• FND_USER_VIEW (view) — resolves the LAST_UPDATED_BY numeric user ID to a USER_NAME.

All joins are outer joins (denoted by the "(+)" operator), meaning a communication row survives even when its life event reason, participant, communication type, or updating user is absent. Notably, the join to BEN_PER_IN_LER includes a business group offset (PCM.BUSINESS_GROUP_ID+0), reflecting the multi-tenant business group partitioning applied in Benefits.

Key Columns

• ROW_ID — the ROWID of the base BEN_PER_CM_F row; used for direct row access.
• PER_CM_ID — primary key of the person communication record.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — date-tracked validity of the communication.
• LF_EVT_OCRD_DT — the date the triggering life event occurred.
• LER_NAME — descriptive name of the life event reason.
• BNF_PERSON_NAME — full name of the beneficiary participant.
• DPNT_PERSON_NAME — full name of the dependent participant, corresponding to the DPNT_PERSON join referenced in the user's search term "dpnt_person".
• CM_TYP_NAME — descriptive name of the communication type.
• RQSTBL_UNTL_DT — the requestable-until date, governing how long the communication remains actionable.
• LAST_UPDATE_DATE and LAST_UPDATED_BY — audit columns; the latter is resolved to the FND user name.

Common Use Cases and Queries

Typical scenarios include auditing generated participant communications, reconciling dependent and beneficiary correspondence, and extracting data for regulatory or HR reporting. A representative query follows:

SELECT per_cm_id, bnf_person_name, dpnt_person_name, cm_typ_name, ler_name, lf_evt_ocrd_dt, rqstbl_untl_dt, last_updated_by FROM apps.ben_per_cm_d WHERE effective_start_date BETWEEN :p_start AND :p_end AND (dpnt_person_name IS NOT NULL OR bnf_person_name = :p_person);

Because the view already resolves participant names and communication types, it eliminates the need to join BEN_PER_CM_F to PER_ALL_PEOPLE_F and BEN_CM_TYP_F in ad-hoc reporting. Analysts should note that the outer joins can produce NULL descriptive fields when reference data is missing, and that the business group offset on BEN_PER_IN_LER is essential to correct multi-tenant behavior.