Results for “ordr_to_aply_num”

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

Overview

BEN_PRTN_ELIGY_RL_D is a reporting view owned by the APPS schema within the Oracle Advanced Benefits (BEN) product module. In Oracle EBS 12.1.1 and 12.2.2, it presents descriptive, denormalized data for participation eligibility rules configured against a program or plan. The "_D" suffix follows the Oracle EBS convention for a descriptive view that resolves internal foreign-key identifiers and lookup codes into user-facing names, thereby simplifying reporting and integration queries that would otherwise require multiple joins to base tables.

The view is documented in ETRM as VALID and carries the annotation "Retrofitted," indicating that it was introduced or adapted to align with the revised BEN data model used across the 12.1.1 and 12.2.2 releases. The view is principally consumed by concurrent programs, BI Publisher reports, and custom SQL extracts that need to display eligibility rule details without navigating the full BEN entity hierarchy.

Underlying Base Objects

The view is defined over the following documented base objects, most of which are referenced through APPS synonyms:

• BEN_PRTN_ELIGY_RL_F – the primary participation eligibility rule table, supplying rule identifiers, effective dates, ordering, and flag columns.
• BEN_PRTN_ELIG_F – the parent participation eligibility definition, providing the eligibility name and the waiting period unit of measure.
• FF_FORMULAS_F – the Oracle FastFormula repository, supplying the formula name associated with the rule.
• FND_USER – the application user table, used to resolve the LAST_UPDATED_BY identifier.
• HR_LOOKUPS – the lookup view, referenced twice with the alias DRVBL_FCTR_APLS and MNDTRY, both filtered on LOOKUP_TYPE = 'YES_NO'.
• HR_API – a package referenced for supporting business logic.

All base-table joins are outer joins, so a participation eligibility rule row is returned even when the related formula, lookup, eligibility, or user record is absent. The lookup join is filtered on the YES_NO lookup type, which is why DRVBL_FCTR_APLS and MNDTRY are reported as separate columns with their own aliases in the view text.

Key Columns

• ROW_ID – the ROWID of the underlying rule record, useful for DML or precise row identification.
• PRTN_ELIGY_RL_ID – the surrogate primary key of the participation eligibility rule.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE – the date-effective range during which the rule is active.
• PRTN_ELIG_NAME – the descriptive name of the parent participation eligibility definition.
• FORMULA_NAME – the name of the FastFormula attached to the rule.
• DRVBL_FCTR_APLS_MEANING – the decoded YES/NO meaning indicating whether a derivable factor applies.
• MNDTRY_MEANING – the decoded YES/NO meaning indicating whether the rule is mandatory.
• ORDR_TO_APLY_NUM – the numeric sequence in which the rule is applied relative to other rules.
• LAST_UPDATE_DATE / LAST_UPDATED_BY – the audit columns for the most recent modification.

The column DRVBL_FCTR_APLS_MEANING is the resolved form of the DRVBL_FCTR_APLS_FLAG stored in BEN_PRTN_ELIGY_RL_F, which is why the underlying lookup alias DRVBL_FCTR_APLS is central to the view's descriptive purpose.

Common Use Cases and Queries

This view is typically used to report on eligibility rule configuration, to audit FastFormula assignments, and to feed downstream integration extracts. A representative query follows:

• Filter by PRTN_ELIGY_RL_ID or PRTN_ELIG_NAME to inspect the rule set for a specific program or plan.
• Filter DRVBL_FCTR_APLS_MEANING = 'Y' to isolate rules where a derivable factor applies.
• Filter MNDTRY_MEANING = 'Y' to identify mandatory eligibility rules.
• Order by ORDR_TO_APLY_NUM to reproduce the rule application sequence.

Example:

SELECT prtn_eligy_rl_id, prtn_elig_name, formula_name,
       drvbl_fctr_apls_meaning, mndtry_meaning,
       ordr_to_aply_num, effective_start_date, effective_end_date
FROM   apps.ben_prtn_eligy_rl_d
WHERE  drvbl_fctr_apls_meaning = 'Y'
AND    TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date
ORDER  BY prtn_elig_name, ordr_to_aply_num;

Because all joins are outer joins, consumers should anticipate null values in FORMULA_NAME, PRTN_ELIG_NAME, and the decoded meanings when the corresponding source records are missing or end-dated. Date-effective logic should be applied explicitly, as the view does not restrict rows by the current effective date.