Results for “rate_amount”

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

Overview

HR_PAY_INTERFACE_OAB_VALUE_V is a payroll interface toolkit view owned by the APPS schema in Oracle E-Business Suite (documented for 12.1.1 and 12.2.2, Product: PER – Human Resources). Its documented purpose is to expose payroll interface data for elements that feed external payroll processing or third-party payroll providers. In particular, the view surfaces the "value" information attached to element entry records and enriches it with rates, activity type context, and period-to-date limits derived from Oracle Advanced Benefits (BEN) base rate structures. The view returns a distinct set of element entry values joined to assignment and rate-of-pay data, making it suitable for extracting the actual numeric values that the payroll interface package HR_PAY_INTERFACE_PKG passes to the receiving payroll system. Because it is a view and not a table, it reflects the current transactional data at query time and is typically consumed during the interface extraction cycle.

Underlying Base Objects

The view is defined over a set of tables and synonyms that span Oracle Payroll, Oracle Human Resources, and Oracle Advanced Benefits. The documented referenced objects are:

• PER_ALL_ASSIGNMENTS_F — assignment rows supplying assignment ID, assignment number, person ID, and effective dates.
• PAY_ELEMENT_ENTRIES_F — the element entry (assignment-level) records and their effective dates.
• PAY_ELEMENT_ENTRY_VALUES_F — the individual element entry values linked by ELEMENT_ENTRY_VALUE_ID.
• BEN_PRTT_RT_VAL — participant rate values; the view aliases this table three times (BPRV, BPRV1, BPRV2) to capture start and end dates and the rate value itself.
• BEN_ACTY_BASE_RT_F, BEN_ACTY_RT_PTD_LMT_F, BEN_PTD_LMT_F — activity base rate and period-to-date limit tables, used in a derived subquery (aliased PTD_LIMIT) to compute the maximum period limit value.
• HR_PAY_INTERFACE_PKG — the payroll interface package, referenced through GET_EXTRACT_DATE to drive effective-date filtering.

The joins are controlled by the extraction date returned by HR_PAY_INTERFACE_PKG.GET_EXTRACT_DATE, so only rows effective as of that date are exposed.

Key Columns

• SCREEN_ENTRY_VALUE — the element entry value as entered, useful for display and audit.
• ACTY_TYP_CD — activity type code (filtered to 'EEPYC' and 'ERPYC'), indicating employee- or employer-payroll-related activity.
• ASSIGNMENT_ID, ASSIGNMENT_NUMBER, PERSON_ID — assignment and person identifiers.
• RT_VAL — the participant rate value.
• RT_TYP_CD — rate type code.
• RT_STRT_DT / RT_END_DT — rate effective start and end dates (exposed from multiple aliases).
• MX_VAL — the maximum period-to-date limit computed in the PTD_LIMIT subquery.
• PRTT_ENRT_RSLT_ID, PRTT_RT_VAL_ID, PER_IN_LER_ID, ELEMENT_ENTRY_VALUE_ID — primary keys linking to enrollment results, rate values, and element entry values.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — dated-track dates from assignments and element entries.
• ACTY_REF_PERD_CD — activity reference period code.

Common Use Cases and Queries

Typical uses include validating interface extracts, reconciling benefit rates against element entries, and reporting period-to-date limits for a given payroll run. A basic query appears below.

SELECT haov.assignment_number,
       haov.screen_entry_value,
       haov.acty_typ_cd,
       haov.rt_val,
       haov.mx_val
FROM   apps.hr_pay_interface_oab_value_v haov
WHERE  haov.person_id = :p_person_id
AND    haov.acty_typ_cd IN ('EEPYC','ERPYC');

Because the view depends on the current extraction date, results should always be evaluated with that date in mind. Performance can be improved by filtering on PERSON_ID or ASSIGNMENT_ID and restricting the activity type code.