Results for “maximum_value”

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

Overview

The APPS.BEN_PTD_LMT_D view is a denormalized reporting object within the Oracle Advanced Benefits (BEN) module. It presents period-to-date (PTD) limit definitions configured for compensation and benefit plan processing along with their resolved descriptive attributes. The view consolidates the base limit definition record from BEN_PTD_LMT_F with the lookup meaning of the limit determination rule, the compensation level factor name, the balance type name, the formula name associated with the period-to-date limit calculation, and the identity of the user who last updated the row. Because it resolves foreign key identifiers into human-readable names, BEN_PTD_LMT_D is intended for reporting, data extraction, and integration scenarios where descriptive context is required rather than for transactional data entry.

Underlying Base Objects

The view is defined as an outer join across several documented base objects. The primary driving table is BEN_PTD_LMT_F, aliased PDL, which supplies the effective-dated period-to-date limit definition and provides the PTD_LMT_ID, effective dates, name, and limit attribute columns. FND_USER_VIEW is outer-joined on USER_ID to resolve the LAST_UPDATED_BY value into a user name. BEN_COMP_LVL_FCTR is outer-joined on COMP_LVL_FCTR_ID to return the compensation level factor name. PAY_BALANCE_TYPES is outer-joined on BALANCE_TYPE_ID to return the balance name. HR_LOOKUPS is outer-joined on LMT_DET_CD with LOOKUP_TYPE restricted to 'BEN_LMT_DET' to yield the limit determination meaning. FF_FORMULAS_F is outer-joined on PTD_LMT_CALC_RL and additionally constrained so that the limit's effective start date falls between the formula's effective start and end dates, returning the formula name for the period-to-date limit calculation rule. ETRM metadata also lists FND_USER_VIEW as a referenced view and HR_API package, HR_LOOKUPS view, and the synonyms for the remaining base tables.

Key Columns

• ROW_ID – the ROWID of the underlying BEN_PTD_LMT_F row, exposed to support direct row addressing.
• PTD_LMT_ID – the primary identifier of the period-to-date limit definition.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE – the date range during which the limit definition is active.
• NAME – the user-defined name of the period-to-date limit.
• MAX_PAY_TO_CONSIDER – the maximum compensation amount eligible for consideration under the limit.
• MAXIMUM_VALUE – the absolute monetary ceiling the limit imposes.
• MAXIMUM_PERCENT – the percentage-based ceiling, expressed as a percentage of the relevant compensation measure.
• RULE – the name of the fast formula used to calculate the period-to-date limit.
• LIMIT_DETERMINATION – the decoded lookup meaning indicating how the limit is determined.
• COMPENSATION_LEVEL_FACTOR – the name of the compensation level factor associated with the limit, corresponding to the searched term "compensation_level_factor."
• BALANCE_TYPE – the balance name referenced by the limit, where applicable.
• LAST_UPDATE_DATE, LAST_UPDATED_BY – audit columns recording when and by whom the row was last modified.

Common Use Cases and Queries

Typical use cases include reporting on active period-to-date limits and their governing formulas, auditing which compensation level factors are attached to specific limits, and extracting limit configuration for integration or data migration. A representative query for currently active limits associated with a compensation level factor is:

• SELECT ptd_lmt_id, name, effective_start_date, effective_end_date, compensation_level_factor, maximum_value, maximum_percent, limit_determination, rule FROM apps.ben_ptd_lmt_d WHERE TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date ORDER BY name;
• SELECT name, rule, limit_determination, balance_type FROM apps.ben_ptd_lmt_d WHERE compensation_level_factor = :p_factor AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;

Because the view applies outer joins, rows lacking a matching compensation level factor, balance type, lookup, or formula still appear with null descriptive values, which makes it suitable for completeness audits of limit configuration.