Results for “element_entry_value_id”

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

Overview

HR_PAY_INTERFACE_OAB_VALUE2_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It resides within the PER (Human Resources) product family and is a component of the HR Pay Interface extraction mechanism, which feeds benefits and compensation data from Oracle Advanced Benefits into Oracle Payroll for processing. The view consolidates assignment, element entry, and benefit participation rate information into a single denormalized result set that is consumed by the payroll interface programs.

The name carries the "VALUE2" designation, indicating it is one of several parallel views in a numbered family (for example, VALUE1, VALUE2, and related variants) that extract rate values of different activity types. This view is specifically oriented toward the activity type code ERPYC (Employer Payroll Cost), returning the effective rate value applied to an assignment across a defined time period. Because it is a view rather than a table, it exposes no storage of its own and derives all data at query time.

Underlying Base Objects

The view is defined over a set of synonyms resolving to base tables and one package, all in the APPS schema:

• PER_ALL_ASSIGNMENTS_F — the assignment record providing assignment id, number, person id, and effective dates.
• PAY_ELEMENT_ENTRIES_F — element entry header rows tying an assignment to an element.
• PAY_ELEMENT_ENTRY_VALUES_F — the individual input values for each element entry, supplying SCREEN_ENTRY_VALUE and ELEMENT_ENTRY_VALUE_ID.
• BEN_PRTT_RT_VAL — participant rate values, and the central benefit table in the join; it appears three times (aliased BPRV, BPRV1, BPRV2) to supply the rate start and end dates and the rate value itself.
• BEN_ACTY_BASE_RT_F, BEN_ACTY_RT_PTD_LMT_F, and BEN_PTD_LMT_F — activity base rates, activity-to-period-limit mappings, and period limit definitions, combined in an inline subquery to yield the maximum period limit value.
• HR_PAY_INTERFACE_PKG — the package supplying GET_EXTRACT_DATE, whose return value drives the effective-date filtering throughout the view.

Key Columns

• SCREEN_ENTRY_VALUE — the entered value from the element entry screen.
• ASSIGNMENT_ID / ASSIGNMENT_NUMBER / PERSON_ID — assignment and person identifiers linking the rate to a worker.
• RT_VAL (rate_amount) — the participant rate value, the monetary or numeric amount applied for the activity. This is the column most commonly referenced as the "rate_amount" a user searches for.
• RT_TYP_CD / ACTY_TYP_CD — the rate type and activity type codes; ACTY_TYP_CD is restricted to ERPYC.
• RT_STRT_DT / RT_END_DT — the effective window of the rate value.
• MX_VAL — the maximum period limit value derived from the limit subquery.
• ACTY_REF_PERD_CD — the activity reference period code.
• PRTT_ENRT_RSLT_ID / PRTT_RATE_VAL_ID / PER_IN_LER_ID / ELEMENT_ENTRY_VALUE_ID — surrogate keys linking back to participation enrollment results, rate values, and element entry values.

Common Use Cases and Queries

Typical usage is reconciliation and troubleshooting of payroll interface extractions, particularly when auditing employer payroll cost rates for a given assignment.

SELECT assignment_number,
       person_id,
       rt_val,
       rt_strt_dt,
       rt_end_dt
FROM   apps.hr_pay_interface_oab_value2_v
WHERE  assignment_id = :p_assignment_id
AND    TRUNC(HR_PAY_INTERFACE_PKG.GET_EXTRACT_DATE)
         BETWEEN rt_strt_dt AND rt_end_dt;

A second scenario validates maximum period limits against extracted rates:

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

Because the view joins several large benefit and payroll tables, queries should be filtered by assignment, person, or effective date to avoid full scans on PER_ALL_ASSIGNMENTS_F and BEN_PRTT_RT_VAL.