Results for “ben_acty_rt_ptd_lmt_x”

18 results




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

Overview

BEN_ACTY_RT_PTD_LMT_X is a read-only database view owned by the APPS schema in Oracle E-Business Suite, belonging to the Advanced Benefits (BEN) product family. It presents data related to activity rate period-to-date limits, associating an activity base rate with a period-to-date limit identifier. The "_X" suffix identifies this as a dated, non-hr (party-independent) view exposed for external consumption, as opposed to the "_F" base table that stores the complete rowset. The view is retrofitted across both EBS 12.1.1 and 12.2.2, meaning its defining logic and column footprint are consistent between the two releases even though the surrounding multi-org access model differs.

The view's principal reporting role is to expose only the currently effective configuration rows. Unlike many BEN views that rely on a session-based effective date, this view hard-codes the filter TRUNC(SYSDATE) BETWEEN APL.EFFECTIVE_START_DATE AND APL.EFFECTIVE_END_DATE, so it always returns the record set that is valid as of the current system date. This makes it convenient for operational validation and point-in-time integration extracts, but unsuitable for historical or future-dated analysis.

Underlying Base Objects

The view is defined over a single documented base object: the synonym BEN_ACTY_RT_PTD_LMT_F, which resolves to the physical table in the APPS schema. The query aliases that base object as APL and selects one column for every column defined on the underlying table, applying only the date-range restriction. There is no join, aggregation, or column-level transformation, so the view is a filtered projection of BEN_ACTY_RT_PTD_LMT_F rather than a denormalized or derived structure.

Because the view depends on the "_F" table and its synonym, any DDL or data change to the base table is immediately reflected in the view. The view carries no independent storage and therefore cannot be updated directly; DML must be performed against the base table or through the corresponding concurrent program and Oracle Forms interfaces provided by Advanced Benefits.

Key Columns

Common Use Cases and Queries

Typical uses include extracting the active period-to-date limit configuration for a given activity base rate, verifying that the correct limit is applied to a rate calculation, and reporting on DFF segment values. The following query lists the currently effective limits together with their first descriptive flexfield segment:

  • SELECT apl.acty_rt_ptd_lmt_id, apl.acty_base_rt_id, apl.ptd_lmt_id, apl.apl_attribute_category, apl.apl_attribute1
  • FROM  apps.ben_acty_rt_ptd_lmt_x apl
  • WHERE apl.apl_attribute1 = :p_attribute1
  • ORDER BY apl.acty_base_rt_id;

To review DFF usage across segment columns, a query can select apl_attribute1 through apl_attribute30 with NVL2 checks to identify populated segments. Because the view is date-filtered internally, no additional SYSDATE predicate is required; callers needing historical rows must query BEN_ACTY_RT_PTD_LMT_F directly with an explicit effective date range.