Search Results ben_ler_extra_info_pk

Overview

BEN_LER_EXTRA_INFO is a table within the BEN (Advanced Benefits) product schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description is "Life Event Reasons Extra Information," indicating that it stores supplemental, flexfield-based attribute data associated with Life Event Reasons (LER) defined in Oracle Advanced Benefits. Life Event Reasons are the configurable business triggers — marriage, birth, termination, transfer, and similar — that drive eligibility and enrollment processing in Benefits. The table exists to hold descriptive detail that does not fit the standard columns of the parent Life Event Reason entity.

The object is owned by the BEN schema, holds VALID status, and is documented with 65 columns in the ETRM 12.2.2 physical schema. Its heuristic Data Vault classification, mined from the foreign-key structure, is standalone; under a Data Vault modeling approach this suggests the table behaves as a satellite-style extension record rather than a true hub or link, since it is not itself the target of dependent foreign keys. The only unique index documented is the primary key constraint.

Key Information Stored

The most significant columns fall into several functional groups:

• LER_EXTRA_INFO_ID — the surrogate primary key, enforced by BEN_LER_EXTRA_INFO_PK. This is the only documented unique index and therefore the sole business-key candidate in the metadata.
• LER_ID — the foreign reference to the parent Life Event Reason record, tying each extra-information row to its owning LER.
• INFORMATION_TYPE — classifies the type of extra information being recorded.
• LRI_ATTRIBUTE_CATEGORY and LRI_ATTRIBUTE1 through LRI_ATTRIBUTE20 — a descriptive flexfield segment set used to capture context-sensitive attribute values for the LER.
• LRI_INFORMATION_CATEGORY and LRI_INFORMATION1 through LRI_INFORMATION30 — a second, larger flexfield group providing thirty generic information segments for extensible storage.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context columns used to trace which batch process created or last updated the row.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, OBJECT_VERSION_NUMBER — the standard WHO audit and optimistic-locking columns present on most EBS transactional tables.

Common Use Cases and Queries

Typical usage centers on joining extra information back to the parent Life Event Reason so that reporting and configuration extracts can present the full definition of an LER. A representative query retrieves all extra-information rows for a given reason:

SELECT ler_extra_info_id, ler_id, information_type,
       lri_attribute_category, lri_attribute1,
       lri_information_category, lri_information1
FROM   ben.ben_ler_extra_info
WHERE  ler_id = :p_ler_id;

Because the table carries both ATTRIBUTE and INFORMATION flexfield groups, developers frequently query the FND_DESCR_FLEX_COL_USAGE and FND_FLEX_VALUES views to translate the category and segment values into user-facing labels. Audit and reconciliation reports commonly filter on LAST_UPDATE_DATE or PROGRAM_UPDATE_DATE to isolate rows touched by a specific concurrent request, and legacy data-migration scripts use REQUEST_ID to identify records loaded by a given batch.

Related Objects

• BEN_LER — the parent Life Event Reason table; join on BEN_LER_EXTRA_INFO.LER_ID = BEN_LER.LER_ID.
• BEN_LER_EXTRA_INFO_PK — the primary key constraint on LER_EXTRA_INFO_ID.
• BEN_LER_F — the descriptive flexfield definition associated with Life Event Reasons.
• FND_FLEX_VALUES / FND_FLEX_VALUES_TL — flexfield value lookups used to decode the ATTRIBUTE and INFORMATION segments.
• FND_DESCR_FLEX_COL_USAGE — conveys which columns in this table are flexfield-enabled and their prompt labels.
• FND_CONCURRENT_REQUESTS — resolves REQUEST_ID to the concurrent program that populated the row.

The table is best treated as a dependent satellite of BEN_LER; any delete or purge of a Life Event Reason must account for its extra-information rows to avoid orphaned data.