Results for “ben_lmt_det”

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

Overview

APPS.BEN_PTD_LMT_D is a read-only internal database view in the Oracle E-Business Suite Advanced Benefits (BEN) module, owned by the APPS schema and carrying FND Design Data reference BEN.BEN_PTD_LMT_D. The object is documented as VALID and classified as an internal view, which places it under Oracle's standard caution that it is intended for use only by standard Oracle Applications programs rather than for direct customer access. Despite this restriction, the view is widely referenced in reporting and integration scenarios because it exposes the effective-dated definitions of period-to-date (PTD) limits used in compensation and benefits processing.

The presence of a COMPENSATION_LEVEL_FACTOR column, which the user searched for, indicates that this view is a primary access path for configuration data linking PTD limits to compensation level factors. In Oracle Advanced Benefits, compensation level factors drive how compensation is measured and interpreted when evaluating eligibility, limits, and benefit calculations. This view therefore serves as a convenient denormalized read model over the transactional limit tables, joining derived names and lookup meanings for use by downstream benefit engines and reporting tools.

Underlying Base Objects

The view is defined over several documented base objects: BEN_COMP_LVL_FCTR, BEN_PTD_LMT_F, FF_FORMULAS_F, FND_USER_VIEW, HR_API, HR_LOOKUPS, and PAY_BALANCE_TYPES. BEN_PTD_LMT_F is the primary base table holding PTD limit definitions, with the "_F" suffix denoting the date-tracked (effective-dated) entity. BEN_COMP_LVL_FCTR supplies compensation level factor data, providing the source for the COMPENSATION_LEVEL_FACTOR attribute. FF_FORMULAS_F resolves the formula-based rule definitions, while HR_LOOKUPS decodes lookup values for fields such as RULE and LIMIT_DETERMINATION. PAY_BALANCE_TYPES provides the balance type context for BALANCE_TYPE, and FND_USER_VIEW supplies the standard who-column user information. HR_API is invoked for business-group and security context resolution.

Key Columns

The view exposes the following documented columns:

• ROW_ID – the row identifier (ROWID type) for the underlying record.
• PTD_LMT_ID – the primary numeric key of the PTD limit entity.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE – the effective dating window for the limit definition, essential for point-in-time queries.
• NAME – the descriptive name of the period-to-date limit.
• MAX_PAY_TO_CONSIDER – the maximum compensation amount considered when applying the limit.
• MAXIMUM_VALUE / MAXIMUM_PERCENT – numeric thresholds expressing the limit as an absolute value or a percentage.
• RULE – the rule identifier governing limit application, typically decoded via HR_LOOKUPS.
• LIMIT_DETERMINATION – the determination method for the limit.
• COMPENSATION_LEVEL_FACTOR – the factor applied at the compensation level, central to this view's relevance for compensation searches.
• BALANCE_TYPE – the balance type against which the limit is evaluated.
• LAST_UPDATE_DATE / LAST_UPDATED_BY – standard who columns recording the last modification.

Common Use Cases and Queries

Typical uses include auditing benefit limit configuration, verifying which compensation level factors attach to a PTD limit, and supporting data migration or reconciliation. A basic query is:

SELECT PTD_LMT_ID, NAME, MAX_PAY_TO_CONSIDER, MAXIMUM_VALUE, MAXIMUM_PERCENT, COMPENSATION_LEVEL_FACTOR, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE FROM APPS.BEN_PTD_LMT_D WHERE COMPENSATION_LEVEL_FACTOR IS NOT NULL AND SYSDATE BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE;

Because the view is flagged Oracle Internal Use Only, direct customer access is unsupported; queries should be confined to diagnostic or reporting contexts and validated against the base tables. Where the view proves insufficient, joining to BEN_PTD_LMT_F directly provides the authoritative effective-dated source.