Results for “pay_grade_rules”

50+ results




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

Overview

PAY_GRADE_RULES is a date-effective database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the PAY (Payroll) product family and exposes grade rule and grade rate configuration data used by Oracle Payroll, Oracle Human Resources, and related compensation processes. As a date-effective (datetracked) view, it does not store data itself; instead, it presents only those rows from its underlying table that are valid as of the effective date held in the user's current FND session. This behavior allows applications and reports to query grade rules "as of today" without embedding date predicates in every statement.

The view is documented in the ETRM repository with status VALID, confirming it is a supported, compiled object in the APPS schema. It is commonly referenced in custom reporting, data extraction, and integration routines that need grade rule and rate information for a given business group.

Underlying Base Objects

The view is defined over a single base table, PAY_GRADE_RULES_F, which stores the full dated and non-dated attribute set for grade rules. The view applies a session-based effective date filter using the FND_SESSIONS table. Specifically, rows are returned only where EFFECTIVE_START_DATE is less than or equal to the session effective date and EFFECTIVE_END_DATE is greater than or equal to that same session effective date, both resolved through USERENV('SESSIONID').

The documented referenced base objects are FND_SESSIONS (SYNONYM) and PAY_GRADE_RULES_F (SYNONYM). FND_SESSIONS supplies the effective date for the current user session, while PAY_GRADE_RULES_F provides the underlying grade rule data. This design is the standard Oracle EBS "datetrack" pattern: the _F table holds all dated rows, and the date-effective view returns the single current row per logical record for the session's effective date. Because the view inherits the base table's column set, it is read-only in practice for configuration purposes.

Key Columns

Common Use Cases and Queries

Typical scenarios include validating grade rate boundaries during salary proposals, reporting current grade rules by business group, and feeding compensation data into custom extracts. Because the view already filters by session effective date, queries are simplified.

Example: list current grade rules for a business group

  • SELECT gr.GRADE_RULE_ID, gr.BUSINESS_GROUP_ID, gr.RATE_ID, gr.GRADE_OR_SPINAL_POINT_ID, gr.RATE_TYPE, gr.MINIMUM, gr.MID_VALUE, gr.MAXIMUM, gr.CURRENCY_CODE FROM APPS.PAY_GRADE_RULES gr WHERE gr.BUSINESS_GROUP_ID = :p_business_group_id ORDER BY gr.RATE_ID, gr.SEQUENCE;

Example: join to grade rates for descriptive reporting

  • SELECT gr.GRADE_RULE_ID, gr.RATE_ID, gr.MINIMUM, gr.MAXIMUM, gr.CURRENCY_CODE FROM APPS.PAY_GRADE_RULES gr WHERE gr.EFFECTIVE_START_DATE <= SYSDATE AND gr.EFFECTIVE_END_DATE >= SYSDATE;

For historical or future-dated analysis, query PAY_GRADE_RULES_F directly with explicit effective date predicates, since the view always returns the session-effective row. Integrations should respect the business group and currency context to avoid ambiguous rate interpretation.