Results for “hrfv_accrual_values”

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

Overview

The APPS.HRFV_ACCRUAL_VALUES view is a business view template in Oracle E-Business Suite, owned by the APPS schema and belonging to the PER (Human Resources) product family. As its ETRM description states, it is the "business view template from which the flexfield view is generated." It consolidates accrual plan participation, assignment details, and time-period eligibility into a single reporting surface that resolves an employee's accrued or net accrual balance as of the current system date (TRUNC(SYSDATE)). Because the view is defined in the APPS schema and exposed through standard synonyms, it can be queried directly by reporting tools, extracts, and integrations across both 12.1.1 and 12.2.2 releases. The view carries a duplicate DUMMY union (types 1 and 2) that produces separate rows for gross accrued and net entitlement components, each labeled and ordered via HR_BIS.BIS_DECODE_LOOKUP.

Underlying Base Objects

The view is constructed over a mix of TL (_TL) tables, _X (_X) views, and PL/SQL packages. Documented references include HR_ALL_ORGANIZATION_UNITS_TL, PAY_ACCRUAL_PLANS, PAY_ELEMENT_TYPES_X (with PAY_ELEMENT_TYPES_F and PAY_ELEMENT_TYPES_F_TL), PAY_ELEMENT_LINKS_X, PAY_ELEMENT_ENTRIES_X (with PAY_ELEMENT_ENTRIES_F), PER_ASSIGNMENTS_X, PER_PEOPLE_X, PER_TIME_PERIODS, PAY_INPUT_VALUES_X, PAY_NET_CALCULATION_RULES, and DUAL. It also references the packages HR_BIS, HR_GENERAL, HR_PERSON_NAME, HR_SECURITY, and PER_VIEWS_PKG. The core join chain links an accrual plan to its element type, element links, and element entries, then to the assignment and person, and finally to the business group. A correlated subquery against PER_TIME_PERIODS and PAY_ELEMENT_ENTRIES_F filters rows to those whose earliest payroll time period start date is on or before the current date. Business group security is enforced through HR_BIS.GET_SEC_PROFILE_BG_ID.

Key Columns

• ACCRUAL_PLAN_ID — the identifier of the accrual plan, sourced from PAY_ACCRUAL_PLANS; it is the join key into PAY_ELEMENT_TYPES via ACCRUAL_PLAN_ELEMENT_TYPE_ID.
• ACCRUAL_PLAN_NAME — the descriptive name of the accrual plan.
• ACCRUAL_VALUE — the resolved balance, computed by PER_VIEWS_PKG.PER_GET_NET_ACCRUAL or PER_VIEWS_PKG.PER_GET_ACCRUAL depending on DUMMY.TYPE, evaluated at the current date for a given assignment and accrual plan.
• ACCRUAL_UNITS — decoded from ACCRUAL_UNITS_OF_MEASURE via the HOURS_OR_DAYS lookup.
• ACCRUAL_COMPONENT — the translated entitlement name (net entitlement or accrued) via NAME_TRANSLATIONS.
• PERSON_NAME, BUSINESS_GROUP_NAME, ASSIGNMENT_NUMBER, BUSINESS_GROUP_ID, ASSIGNMENT_ID — descriptive and security/join context.
• ORDER_NUMBER — controls row ordering of the two unioned components.

Common Use Cases and Queries

Typical uses include absence and accrual balance reporting, accrual reconciliation alongside payroll, and feeding accrual balances into a custom OAF page or concurrent program. A basic query filtered on the searched acccrual_plan_id might read:

• SELECT person_name, assignment_number, accrual_plan_name, accrual_value, accrual_units, accrual_component FROM apps.hrfv_accrual_values WHERE accrual_plan_id = :p_plan_id;
• SELECT business_group_name, accrual_plan_name, SUM(accrual_value) FROM apps.hrfv_accrual_values GROUP BY business_group_name, accrual_plan_name;
• SELECT * FROM apps.hrfv_accrual_values WHERE person_name = :p_name ORDER BY person_name, order_number;

Because ACCRUAL_PLAN_ID drives the plan-to-element-type join and is returned in every row, it is the standard filter for isolating a single plan's accruals. Note that the view computes balances at runtime using SYSDATE, so results reflect the current point-in-time position and are not historic snapshots.