Search Results accrual_band_id




Overview
Explore in AI Chat

Overview

The HR.PAY_ACCRUAL_BANDS table is a core configuration table within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 Human Resources (HR) and Payroll modules. It defines the service-based accrual tiers for paid time off (PTO) plans. Each row in this table represents a specific length-of-service band within an accrual plan, detailing the accrual rate and associated limits that apply to employees whose tenure falls within that band. This table is fundamental to the automated calculation of vacation, sick leave, and other time-off entitlements, enabling complex, tiered accrual policies based on an employee's years of service.

Key Information Stored

The table stores the parameters that govern accrual calculations for each service band. The system-generated primary key, ACCRUAL_BAND_ID, uniquely identifies each band record. Each band is linked to a specific ACCRUAL_PLAN_ID and BUSINESS_GROUP_ID for data security and multi-org support. The core business logic is defined by the LOWER_LIMIT and UPPER_LIMIT columns, which establish the service duration range (e.g., 0 to 5 years) for the band. The ANNUAL_RATE specifies the amount of time off accrued per year within this band. Control over entitlement accumulation is managed by the CEILING (maximum total balance allowed) and MAX_CARRY_OVER (maximum unused balance transferable to the next period) columns. Standard "Who" columns (CREATED_BY, LAST_UPDATE_DATE, etc.) track row history.

Common Use Cases and Queries

Primary use cases include the setup and maintenance of accrual plans, auditing plan configurations, and troubleshooting accrual calculation issues. A common reporting requirement is to list all bands for a specific accrual plan to verify tiered rates. For example, to audit the "US Vacation" plan (ID: 1001), a query would be:

  • SELECT accrual_plan_id, lower_limit, upper_limit, annual_rate, ceiling, max_carry_over FROM hr.pay_accrual_bands WHERE accrual_plan_id = 1001 ORDER BY lower_limit;

Another critical scenario involves identifying which service band applies to a given employee based on their hire date. This requires joining with service calculation logic, often via the PAY_ACCRUAL_PLANS and PER_ALL_PEOPLE_F tables. Support and development tasks frequently reference this table when debugging why an employee is receiving an unexpected accrual amount, typically by verifying the active band limits against the employee's length of service.

Related Objects

PAY_ACCRUAL_BANDS has defined relationships with several key EBS objects, primarily through foreign key constraints. It is a child table of PAY_ACCRUAL_PLANS, linked via the ACCRUAL_PLAN_ID column. This relationship is essential as all bands must belong to a parent plan. It also references HR_ALL_ORGANIZATION_UNITS via BUSINESS_GROUP_ID for security and multi-org partitioning. The table is central to the accrual engine; therefore, key PL/SQL APIs in the PAY_ACCRUAL_FUNCTIONS package and accrual calculation processes will read from this table to determine applicable rates. Reports and forms for managing accrual plans, such as those in the "Absence" and "Accrual Plan" setups, directly interact with data in this table.