Results for “lwr_lmt”

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

Overview

APPS.BEN_CVG_AMT_CALC_MTHD_D is a reporting and integration view in the Oracle EBS Advanced Benefits (BEN) module, exposed in the APPS schema. It presents the effective-dated definition of coverage amount calculation methods — the rules that determine how a benefit coverage amount is derived, incremented, bounded, and rounded during enrollment and plan processing. The view is registered in FND Design Data as BEN.BEN_CVG_AMT_CALC_MTHD_D and carries a VALID status in both 12.1.1 and 12.2.2. Oracle flags the object as Internal Use Only: it is not supported for direct customer access except through standard Oracle Applications programs, and the _D suffix conventionally signals a denormalized, descriptive view that joins base calculation-method rows to their associated plan, option, and option-in-plan descriptive columns.

The view is frequently referenced when analysts search for rounding_code, since ROUNDING_CODE is one of its exposed columns. Together with ROUNDING_RULE, MINIMUM_VALUE, MAXIMUM_VALUE, INCREMENT_VALUE, and the various limit columns, this view provides a single queryable surface for understanding how calculation methods behave across benefit programs.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over the following base synonyms and objects: BEN_COMP_LVL_FCTR, BEN_CVG_AMT_CALC_MTHD_F, BEN_OIPL_F, BEN_OPT_F, BEN_PL_F, FF_FORMULAS_F, FND_USER, HR_API (package), and HR_LOOKUPS (view). The primary driver is BEN_CVG_AMT_CALC_MTHD_F, the _F (full/date-tracked) table holding the effective-dated calculation method definitions. BEN_PL_F, BEN_OPT_F, and BEN_OIPL_F supply plan, option, and option-in-plan descriptive attributes. BEN_COMP_LVL_FCTR provides compensation-level factor reference data. FF_FORMULAS_F supplies the FastFormula definitions referenced by the VALUE_RULE, ROUNDING_RULE, and limit rule columns. FND_USER and HR_API support the standard WHO columns and date-tracked derivation, while HR_LOOKUPS resolves lookup meaning values for the various _CODE and _RULE attributes.

Key Columns

• CVG_AMT_CALC_MTHD_ID — Primary identifier of the calculation method.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Date-tracked validity window for the row.
• COVERAGE_NAME — Descriptive name of the coverage being calculated.
• ROUNDING_CODE and ROUNDING_RULE — The rounding option applied to the computed amount and the FastFormula rule that implements it. These are the columns most relevant to the "rounding_code" search.
• MINIMUM_VALUE, MAXIMUM_VALUE, NO_MINIMUM_VALUE, NO_MAXIMUM_VALUE — Bounds applied to the calculated amount, with flags indicating absence of a bound.
• INCREMENT_VALUE — The step by which the amount is incremented.
• VALUE, VALUE_RULE, VALUE_OVERRIDE_ALLOWED, DEFAULT_VALUE, DEFAULT_FLAG, ENTER_VALUE_AT_ENROLLMENT — The base amount, the formula rule that computes it, and controls governing overrides, defaults, and enrollment entry.
• LOWER_LIMIT_VALUE / UPPER_LIMIT_VALUE and their corresponding _RULE columns — Limit values and the formulas that enforce them.
• UNIT_OF_MEASURE, NONMONETARY, BOUNDARY_PERIOD, BENEFIT_TYPE, COVERAGE_MULTIPLE, RATE_TYPE — Contextual attributes that describe how the amount is expressed and bounded.
• COMPENSATION_LEVEL_FACTOR, OPTION_IN_PLAN_NAME, PLAN_NAME — Descriptive denormalized columns joining the method to its plan/option context.

Common Use Cases and Queries

Typical usage centers on auditing the rounding and bound configuration of coverage calculation methods. A common query retrieves the rounding code and rule for a plan and its options:

SELECT cm.plan_name,
       cm.option_in_plan_name,
       cm.coverage_name,
       cm.rounding_code,
       cm.rounding_rule,
       cm.minimum_value,
       cm.maximum_value,
       cm.increment_value
FROM   apps.ben_cvg_amt_calc_mthd_d cm
WHERE  TRUNC(SYSDATE) BETWEEN cm.effective_start_date
                          AND NVL(cm.effective_end_date, TRUNC(SYSDATE))
ORDER  BY cm.plan_name, cm.option_in_plan_name;

Other scenarios include verifying that a value rule or rounding rule points to a valid FastFormula, confirming that lower and upper limit rules are consistently populated, and extracting method configuration for data migration or benefit reconciliation. Because the object is date-tracked, queries should always filter on the effective dates to return the configuration valid on the reporting date. Direct access remains governed by the Oracle Internal Use Only restriction, so production consumption should occur through supported Oracle Benefits programs.