Results for “hr_pay_interface_oab_value1_v”

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

Overview

The HR_PAY_INTERFACE_OAB_VALUE1_V view is an Oracle E-Business Suite dictionary object owned by the APPS schema and classified under the PER (Human Resources) product family. It is a VALID view in both EBS 12.1.1 and 12.2.2 and is used as part of the HR-to-Payroll interface extraction logic. The view consolidates assignment, element entry, and benefits rate information into a single denormalized result set, exposing a rate value (RT_VAL) alongside the assignment identifier and element entry value context needed to feed the payroll interface processes.

Its role is primarily integrative: it is not an end-user form-driven object but a technical construct referenced by HR/Payroll interface routines that must reconcile assignment-level element entries with benefit participation rate values and period-to-date limits. The view draws its "as of" filtering logic from the HR_PAY_INTERFACE_PKG.GET_EXTRACT_DATE function, meaning the result set is date-effective against the current extract date rather than a fixed point in time.

Underlying Base Objects

The view is defined over a mixture of HR, Payroll, and Benefits synonyms, joined with a package function call:

• PER_ALL_ASSIGNMENTS_F — assignment details including assignment ID, number, and effective dates.
• PAY_ELEMENT_ENTRIES_F and PAY_ELEMENT_ENTRY_VALUES_F — element entry and entry value records, joined via ELEMENT_ENTRY_VALUE_ID.
• BEN_PRTT_RT_VAL (aliased BPRV, BPRV1, BPRV2) — participant rate values, supplying RT_VAL, RT_STRT_DT, RT_END_DT, and the activity type code.
• BEN_PTD_LMT_F, BEN_ACTY_RT_PTD_LMT_F, and BEN_ACTY_BASE_RT_F — combined in an inline subquery (aliased PTD_LIMIT) to derive the maximum period-to-date limit value (MX_VAL).
• HR_PAY_INTERFACE_PKG — the package supplying GET_EXTRACT_DATE, used to restrict all effective-dated rows.

The join is anchored on the activity type code 'EEPYC', and each of the three BEN_PRTT_RT_VAL aliases is filtered on this code, indicating the view targets pre-tax or employee-participation contributions of that specific activity category.

Key Columns

• SCREEN_ENTRY_VALUE — the entry value captured on the element entry screen.
• ACTY_TYP_CD — activity type code (filtered to 'EEPYC').
• ASSIGNMENT_ID, ASSIGNMENT_NUMBER, PERSON_ID — assignment and person identifiers.
• RT_VAL — the rate value; the primary numeric interest for the "rate_amount" search context.
• RT_STRT_DT, RT_END_DT — effective start and end dates of the rate.
• RT_TYP_CD — rate type classification.
• MX_VAL — the maximum period-to-date limit derived from the PTD_LIMIT subquery.
• ACTY_REF_PERD_CD — activity reference period code.
• PRTT_ENRT_RSLT_ID, PRTT_RT_VAL_ID, ELEMENT_ENTRY_VALUE_ID, PER_IN_LER_ID — surrogate keys linking to participation results, rate values, and element entry values.
• EFFECTIVE_START_DATE, EFFECTIVE_END_DATE — datetracked boundaries on assignments and element entries.

Common Use Cases and Queries

Typical usage involves validating the rate amount fed into the payroll interface for a given assignment and element entry value, and reconciling it against the applicable period-to-date limit. Report developers query the view to surface rate values alongside assignment and person context without manually joining the underlying HR, Payroll, and Benefits tables.

• Rate amount lookup: SELECT ASSIGNMENT_NUMBER, PERSON_ID, RT_VAL, RT_TYP_CD FROM HR_PAY_INTERFACE_OAB_VALUE1_V WHERE ASSIGNMENT_ID = :p_assignment_id;
• Element entry reconciliation: SELECT ELEMENT_ENTRY_VALUE_ID, SCREEN_ENTRY_VALUE, RT_VAL, MX_VAL FROM HR_PAY_INTERFACE_OAB_VALUE1_V WHERE ELEMENT_ENTRY_VALUE_ID = :p_eev_id;
• Extract-date rate analysis: SELECT PERSON_ID, ASSIGNMENT_NUMBER, RT_VAL, RT_STRT_DT, RT_END_DT FROM HR_PAY_INTERFACE_OAB_VALUE1_V ORDER BY PERSON_ID, RT_STRT_DT;

Because extraction is governed by HR_PAY_INTERFACE_PKG.GET_EXTRACT_DATE, results vary with the extract date context set for the session; queries intended for point-in-time reporting should account for this behavior.