Results for “typ_cd”

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

Overview

BEN_STARTUP_LERS is a seeded configuration table in the BEN (Advanced Benefits) product schema of Oracle E-Business Suite. Its documented purpose is to hold seeded life event reasons — the predefined catalog of qualifying life events (for example, marriage, birth of a child, divorce, change of address, or change of employment status) that Oracle ships as delivered reference data and that drive benefits eligibility, enrollment window opening, and rate recalculation processing.

The table functions as a startup or seed reference object: its rows are inserted by Oracle during product installation or upgrade rather than maintained by end users during normal operations, and customers typically consume the seeded values through the benefits life event setup and self-service enrollment flows. In Oracle EBS 12.1.1 and 12.2.2 the table physically resides in the BEN schema, is marked VALID, and is protected by the primary key constraint BEN_STARTUP_LERS_PK.

Based on the heuristic Data Vault classification mined from its foreign key structure, BEN_STARTUP_LERS is modelled as a standalone object. In Data Vault terms this suggests it is best treated as a reference or code table rather than as a hub, link, or satellite, since it carries no documented outbound foreign key relationships to other business entities. Practitioners designing an ETRM or analytics layer should therefore map it as a small, slowly changing reference dimension keyed on its type code.

Key Information Stored

The documented physical schema contains eight columns. The most significant are:

• TYP_CD — The type code identifying a seeded life event reason. This is the business key of the table and the leading column of the primary key.
• NAME — The descriptive name of the seeded life event reason, used for display and selection in benefits setup and self-service pages.
• LAST_UPDATE_DATE — Standard EBS audit column recording when the row was last modified.
• LAST_UPDATED_BY — The application user or seed process that last modified the row.
• LAST_UPDATE_LOGIN — The login identifier associated with the last update, supporting audit and session tracing.
• CREATED_BY — The user or process that created the seed row.
• CREATION_DATE — The date the seed row was inserted.
• ZD_EDITION_NAME — The editioning column used by EBS 12.2's Online Patching (Edition-Based Redefinition) architecture, distinguishing seed rows per edition.

The surrogate primary key is BEN_STARTUP_LERS_PK. The documented unique index candidate for the business key is BEN_STARTUP_LERS_PK (TYP_CD, ZD_EDITION_NAME), which confirms that TYP_CD alone is the logical business key and that ZD_EDITION_NAME qualifies uniqueness per edition in the 12.2.2 patching model. Note that the metadata lists the primary key as BEN_STARTUP_LERS_PK (TYP_CD) while the unique index includes ZD_EDITION_NAME; this reflects the editioning overlay applied in later 12.2 releases.

Common Use Cases and Queries

Typical usage centers on reference lookups, validation of life event codes, and reporting on benefits eligibility events. A common pattern joins the seed table to life event processing tables on TYP_CD to resolve a meaningful NAME for reporting.

• Listing all seeded life event reasons: SELECT TYP_CD, NAME FROM BEN.BEN_STARTUP_LERS ORDER BY TYP_CD;
• Validating that a given code exists before enrollment: SELECT 1 FROM BEN.BEN_STARTUP_LERS WHERE TYP_CD = :p_typ_cd;
• Audit of when seed data was last refreshed: SELECT TYP_CD, NAME, LAST_UPDATE_DATE, LAST_UPDATED_BY FROM BEN.BEN_STARTUP_LERS;
• Joining to life event enrollment or eligibility tables via TYP_CD to display event descriptions on benefits reports.

Because the object is a seeded code table, reporting queries are usually simple key lookups rather than aggregation workloads.

Related Objects

The metadata classifies BEN_STARTUP_LERS as standalone, meaning no outbound foreign keys are documented. Related objects are those that reference it by TYP_CD, primarily life event and benefits processing tables within the BEN schema.

• BEN_PL_LER_F — Plan-level life event reason assignments, joined on TYP_CD.
• BEN_LER_F — Core life event reason definition table, joined on TYP_CD.
• BEN_LER_RLTNSHP_F — Life event reason relationships, referencing event reason codes.
• BEN_PTIP_LER_F — Participation type life event reason mappings.
• BEN_ELIG_LER_F — Eligibility life event reason definitions.
• BEN_LER_OPT_F — Life event reason option configurations keyed to event types.
• Benefits self-service enrollment views and life event registration forms in the BEN module that consume seeded reason codes.

These join relationships, while not enforced by declared foreign keys in the documented metadata, are established logically on TYP_CD and should be confirmed against the delivered data model before use in any integration or extraction logic.