Results for “opt_attribute_category”

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

Overview

BEN_OPT_X is a public synonym and view in the APPS schema belonging to the BEN — Advanced Benefits product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The view exposes a single row per currently effective option record, where an option represents a selectable plan or program element offered to participants within a benefits program. Its defining characteristic is the effective-dated date filter applied in its WHERE clause: the view returns only rows from BEN_OPT_F whose effective start and end dates straddle the current system date (TRUNC(SYSDATE)). This makes BEN_OPT_X a convenient "current only" projection of the underlying date-tracked table, sparing report developers and integration writers from having to code the effective-date predicate themselves.

The view is read-only in intent and is typically used in benefits extracts, eligibility debugging, self-service data queries, and downstream interfaces that must reflect the option configuration in force on the current business day.

Underlying Base Objects

The view is defined over a single documented base object: the synonym BEN_OPT_F, which resolves to the APPS-owned date-tracked table BEN_OPT_F. This table stores the full history of option definitions using the standard Oracle HRMS effective-dating model of EFFECTIVE_START_DATE and EFFECTIVE_END_DATE pairs. Because BEN_OPT_F is a "_F" (date-tracked/translated) table, multiple versions of the same OPT_ID can exist over time; the view resolves this by restricting output to the row set valid as of the current date. No joins to other tables are present in the documented view text, so every column projected by BEN_OPT_X originates directly from BEN_OPT_F.

Key Columns

• OPT_ID — Primary identifier of the option; the surrogate key carried across all effective-dated versions.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — The date boundary columns used to isolate the currently active version.
• NAME, SHORT_NAME, SHORT_CODE — User-facing and shorthand identifiers for the option.
• CMBN_PTIP_OPT_ID — Reference to a combined plan-type/option linkage, relevant where the option is offered through a combined plan configuration.
• BUSINESS_GROUP_ID — Owning business group; essential for multi-organization and security-aware queries.
• GROUP_OPT_ID — The identifier associating the option with its parent option group; this is the column most frequently targeted by users searching the term "group_opt_id".
• COMPONENT_REASON — Descriptive reason code attached to the option component.
• LEGISLATION_CODE / LEGISLATION_SUBGROUP — Localization context governing the option's behavior.
• MAPPING_TABLE_NAME / MAPPING_TABLE_PK_ID — External mapping reference and primary key used for integration hand-offs.
• INVK_WV_OPT_FLAG — Flag indicating option invocation or waiver handling behavior.
• RQD_PERD_ENRT_NENRT_UOM / _VAL / _RL — Unit of measure, value, and rule controlling required-period enrollment versus non-enrollment.
• OPT_ATTRIBUTE_CATEGORY and OPT_ATTRIBUTE1 … OPT_ATTRIBUTE30 — Descriptive flexfield context and segment columns for customer-defined extensions.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit and concurrency columns.

Common Use Cases and Queries

Typical scenarios include retrieving the set of currently active options for a business group, resolving the parent group assignment of an option via GROUP_OPT_ID, and feeding option metadata to external systems using the mapping columns.

List all active options for a business group:

SELECT opt_id, name, short_name, group_opt_id
FROM apps.ben_opt_x
WHERE business_group_id = :p_bg_id
ORDER BY name;

Resolve options belonging to a specific option group:

SELECT opt_id, name, short_code
FROM apps.ben_opt_x
WHERE group_opt_id = :p_group_opt_id;

Inspect integration mapping information:

SELECT opt_id, name, mapping_table_name, mapping_table_pk_id
FROM apps.ben_opt_x
WHERE mapping_table_name IS NOT NULL;

Because the view already applies the TRUNC(SYSDATE) effective-date filter, callers must not add their own date predicate unless they intend to bypass the view and query BEN_OPT_F directly for historical or future-dated analysis.