Search Results ben_css_rltd_per_per_in_ler_f




Overview
Explore in AI Chat

Overview

BEN_CSS_RLTD_PER_PER_IN_LER_F is a table in the BEN schema of Oracle E-Business Suite Advanced Benefits (BEN) module. Its documented description is concise and precise: "Life event causes related person to have a life event." The object therefore models relationships between a triggering life event and the subsequent life event assigned to another person, effectively capturing how a life event experienced by one participant can propagate to a related person. This is a core mechanism used by the Life Event Management and eligibility processing engine when configuring dependent or beneficiary coverage outcomes.

The table is present and valid in both EBS 12.1.1 and 12.2.2. The ETRM 12.2.2 physical schema documents 44 columns, an effective-dated primary key, and a described release-12.2.2 structure. The heuristic Data Vault classification mined from the foreign key structure is standalone; in a Data Vault modeling exercise this would suggest treating it as an independent table rather than as a hub, link, or satellite, since no FK-based parent relationships were inferred. The table does carry effective-dating columns and a surrogate identifier, which are characteristic of EBS date-tracked entities.

Key Information Stored

The primary key is BEN_CSS_RLTD_PER_PER_IN_LE_PK, defined over three columns: CSS_RLTD_PER_PER_IN_LER_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE. The first is the surrogate identifier for the relationship row, while the two date columns provide the effective-dating and date-tracked versioning standard throughout BEN. There is no separate unique index beyond this primary key, so the surrogate ID combined with the effective dates serves as the business-key candidate for identifying a specific version of a relationship.

  • CSS_RLTD_PER_PER_IN_LER_ID — unique surrogate identifier; first component of the primary key.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — effective-dating range controlling which version of the relationship applies.
  • BUSINESS_GROUP_ID — the enterprise business group to which the configuration row belongs; essential for multi-group filtering.
  • LER_ID — the life event reason that acts as the trigger event.
  • RSLTG_LER_ID — the resulting (subsequent) life event reason assigned to the related person.
  • ORDR_TO_PRCS_NUM — processing order sequence used when multiple related-person events apply to the same trigger.
  • CSR_ATTRIBUTE_CATEGORY and CSR_ATTRIBUTE1 through CSR_ATTRIBUTE30 — descriptive flexfield segments used to store customer-specific rules and attributes for the relationship configuration.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, OBJECT_VERSION_NUMBER — standard audit and optimistic-locking columns used by the BEN APIs and concurrent programs.

Together, LER_ID and RSLTG_LER_ID give the table its behavioral meaning: the mapping from a triggering life event to the related person's resulting life event, scoped by business group and ordered for processing.

Common Use Cases and Queries

Administrators and consultants query this table to validate that related-person life event propagation is configured as intended. A representative query retrieves all active mappings for a business group:

  • SELECT LER_ID, RSLTG_LER_ID, ORDR_TO_PRCS_NUM FROM BEN.BEN_CSS_RLTD_PER_PER_IN_LER_F WHERE BUSINESS_GROUP_ID = :p_bg AND SYSDATE BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE ORDER BY ORDR_TO_PRCS_NUM;
  • Reporting scenarios include auditing the number of resulting events per trigger event, identifying duplicate or overlapping effective-dated rows, and verifying that ordering sequences do not conflict.
  • Descriptive flexfield reporting joins CSR_ATTRIBUTE_CATEGORY and the CSR_ATTRIBUTE columns to surface customer-defined attributes alongside the standard LER mappings.
  • Because the table is effective-dated, all reporting must filter on the effective range rather than relying on the surrogate ID alone; historical rows describe what the configuration was on a prior date.

During troubleshooting, comparing an employee's processed life event against this configuration helps explain why a dependent's coverage was or was not triggered.

Related Objects

Given the documented description and column naming, the most significant dependencies are the BEN life event and life event reason tables, plus the standard dependency on the related-person and participant configuration.

  • BEN_LER_F — the life event reason table; LER_ID and RSLTG_LER_ID both resolve to reason definitions here.
  • BEN_LER_ROLE_RL_F — lifecycle-role rules linking life event reasons to participant roles; complements the relationship mapping.
  • BEN_PER_LER_INFO_F — fact/occurrence data for an actual person's life event, used to confirm trigger execution.
  • BEN_PTIP_ELIG_F — participant eligibility derived from the triggering event and its resulting related-person event.
  • BEN_PTIP_F — participant information driving the related person and beneficiary context.
  • FND_DF_FLEXFIELDS / FND_DF_SEGMENTS — define the CSR_ATTRIBUTE_CATEGORY and attribute segments used by this table.

All joins should be scoped by BUSINESS_GROUP_ID and restricted to the effective range; the relation is standalone, so integration is driven by business rules and date ranges rather than declarative foreign keys.