Search Results ben_per_cm_f_n1

Overview

BEN.BEN_PER_CM_F is a date-tracked (effective-dated) transactional table in the Oracle E-Business Suite Benefits (BEN) schema. It records the intersection of a person and a communication type, capturing communications that are generated as the result of a communication trigger being fired for the applicable usage for that person. In ETRM terms, the table acts as a bridge between the workforce population (PER_ALL_PEOPLE_F) and the communication configuration model (BEN_CM_TYP_F). It is registered as a valid object under FND Design Data BEN.BEN_PER_CM_F and physically resides in the APPS_TS_TX_DATA tablespace, while its indexes are held in APPS_TS_TX_IDX.

Heuristic Data Vault classification mined from the foreign key structure suggests a satellite-leaning role. The table is keyed by a surrogate identifier with a date range, and it carries descriptive attribute columns (PCM_ATTRIBUTE_CATEGORY through PCM_ATTRIBUTE30) plus who-columns such as CREATED_BY and LAST_UPDATED_BY. This pattern is characteristic of a satellite attached to a business key, rather than a pure hub or link, though the presence of several person-role foreign keys also gives it link-like breadth across relationships.

Key Information Stored

The surrogate primary key is defined by the unique index BEN_PER_CM_F_PK over PER_CM_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE. PER_CM_ID is the system-generated key, while the effective date pair establishes the temporal validity window of the row and therefore functions as the documented business-key candidate. Among the 54 columns, the following are the most operationally significant:

• PER_CM_ID — system-generated primary key column.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — effective start and end dates defining the dated range.
• PERSON_ID — foreign key to PER_PEOPLE_F, identifying the person associated with the communication.
• CM_TYP_ID — foreign key to BEN_CM_TYP_F, identifying the communication type.
• BUSINESS_GROUP_ID — foreign key to HR_ORGANIZATION_UNITS, scoping the record to a business group.
• RQSTBL_UNTL_DT — requestable-until date controlling how long the communication remains requestable.
• PCM_ATTRIBUTE_CATEGORY and the PCM_ATTRIBUTE1–PCM_ATTRIBUTE30 columns — descriptive flexfield structure and segment columns for customer-defined information.
• LER_ID / PER_IN_LER_ID — life event and participant context, linking the communication to a qualifying life event.
• BNF_PERSON_ID and DPNT_PERSON_ID — beneficiary and dependent person references used to bind communications to covered family members.
• PRTT_ENRT_ACTN_ID — identifier tying the row to a particip/enrollment action.
• Standard who-columns (LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE, REQUEST_ID, PROGRAM_ID) and OBJECT_VERSION_NUMBER for concurrency control.

Common Use Cases and Queries

The most frequent access path is by person, which is exactly what the ad-hoc index BEN_PER_CM_F_N1 on PERSON_ID supports. Reporting queries typically filter to current effective rows and join upward to the communication type lookup:

• List all communications for an employee as of a date — filter on PERSON_ID and SYSDATE BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE.
• Audit which communication triggers fired for a given communication type, using the BEN_PER_CM_F_N7 index on CM_TYP_ID.
• Reconcile beneficiary and dependent communications via BNF_PERSON_ID / DPNT_PERSON_ID for open enrollment reporting.
• Identify records pending action using RQSTBL_UNTL_DT, and trace the event and enrollment context via LER_ID and PRTT_ENRT_ACTN_ID.
• Extract descriptive flexfield content for regulatory or carrier feeds via PCM_ATTRIBUTE_CATEGORY and the segment columns.

Related Objects

The following objects are the most significant dependencies and join targets:

• BEN.BEN_CM_TYP_F — communication type definition; joined on CM_TYP_ID (documented as the intersection partner).
• PER.PER_ALL_PEOPLE_F — person master; joined on PERSON_ID for the primary person, and via BNF_PERSON_ID / DPNT_PERSON_ID for family members.
• BEN.BEN_PER_IN_LER — referenced by the documented foreign key from PER_IN_LER_ID (index BEN_PER_CM_F_FK2), carrying the life-event participation context.
• HR.HR_ORGANIZATION_UNITS — business group validation, joined on BUSINESS_GROUP_ID (index BEN_PER_CM_F_FK1).
• BEN.BEN_PER_LER_F / life-event tables — related through LER_ID (index BEN_PER_CM_F_N3) to associate the communication with the originating event.
• BEN.BEN_PRTT_ENRT_ACTN_F — participation and enrollment action referenced through PRTT_ENRT_ACTN_ID (index BEN_PER_CM_F_N6).

Because the table is effective-dated and carries the standard OBJECT_VERSION_NUMBER, all integration and reporting access should be performed through dated joins rather than on the raw key alone.