Results for “ptd_limit”

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

Overview

APPS.HR_PAY_INTERFACE_OAB_VALUE2_V is an Oracle E-Business Suite 12.1.1 / 12.2.2 view that supports the extraction of benefits-related payroll element entry data used by the Oracle Advanced Benefits (OAB) payroll interface. It consolidates assignment, element entry, element entry value, and benefits rate/period-limit information into a single flat structure that can be consumed by payroll interface processing and downstream reporting.

The view is defined with a DISTINCT projection and is anchored on the extract date returned by HR_PAY_INTERFACE_PKG.GET_EXTRACT_DATE. This packageserves as the analytical anchor for all effective-dating logic in the view: every date-effective join is resolved against the latest row whose effective start date is on or before TRUNC(HR_PAY_INTERFACE_PKG.GET_EXTRACT_DATE).

The user query term "ptd_limit" corresponds directly to an inline subquery alias within this view. That subquery (aliased ptd_limit) resolves period-to-date limits from the benefits tables, exposing the mx_val column as ptd_limit.mx_val in the view's select list.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects, all accessed through APPS synonyms:

• PER_ALL_ASSIGNMENTS_F — assignment header, effective-dated.
• PAY_ELEMENT_ENTRIES_F — element entry definitions for the assignment.
• PAY_ELEMENT_ENTRY_VALUES_F — the individual element input values.
• BEN_PRTT_RT_VAL — participant rate values, joined three times (bprv, bprv1, bprv2) for activity type ERPYC.
• BEN_ACTY_BASE_RT_F — activity base rates.
• BEN_ACTY_RT_PTD_LMT_F — the activity rate-to-period-limit association.
• BEN_PTD_LMT_F — the period-to-date limit master rows (the source of mx_val).
• HR_PAY_INTERFACE_PKG — provides GET_EXTRACT_DATE, used pervasively in the effective-dating subqueries.

The ptd_limit inline subquery joins BEN_PTD_LMT_F to BEN_ACTY_RT_PTD_LMT_F on ptd_lmt_id, then to BEN_ACTY_BASE_RT_F on acty_base_rt_id, and finally to BEN_PRTT_RT_VAL on acty_base_rt_id, restricting BEN_PRTT_RT_VAL rows where prtt_rt_val_stat_cd IS NULL.

Key Columns

• screen_entry_value — from PAY_ELEMENT_ENTRY_VALUES_F; the element input value text.
• assignment_id / assignment_number / person_id — assignment and person identifiers.
• effective_start_date / effective_end_date — appears for the assignment (assg), element entry (pee), and participant rate value (pev) contexts, so the caller can distinguish which date range belongs to which level.
• acty_typ_cd — activity type code; the view populates this from BEN_PRTT_RT_VAL with the constant 'ERPYC'.
• rt_strt_dt / rt_end_dt — rate start and end dates from each of the three BEN_PRTT_RT_VAL aliases.
• rt_val / rt_typ_cd / acty_ref_perd_cd — rate value, rate type code, and activity reference period code.
• mx_val (ptd_limit.mx_val) — the period-to-date limit maximum value resolved by the inline subquery. This is the column relevant to the user's search term.
• prtt_enrt_rslt_id / prtt_rt_val_id / element_entry_value_id / per_in_ler_id — surrogate keys linking back to the benefits and payroll detail tables.

Common Use Cases and Queries

This view is typically used to extract the OAB rate and period-limit data for payroll processing, and to reconcile element entry values against their applicable period limits.

A representative query to retrieve period-limit values for a given person:

• SELECT assignment_number, screen_entry_value, rt_val, acty_ref_perd_cd, mx_val FROM apps.hr_pay_interface_oab_value2_v WHERE person_id = :p_person_id;

To identify entries where the actual rate exceeds the period-to-date limit:

• SELECT assignment_number, person_id, rt_val, mx_val FROM apps.hr_pay_interface_oab_value2_v WHERE rt_val > mx_val;

Because the view uses DISTINCT plus correlated MAX(effective_start_date) subqueries against HR_PAY_INTERFACE_PKG.GET_EXTRACT_DATE, callers should set that extract date (via the package) before querying if deterministic results are required. The view carries no bind parameters of its own; the effective-dating context is entirely driven by the package function.