Results for “pay_grade_rules_x”
28 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
PAY_GRADE_RULES_X is a public, date-effective view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2, delivered under the PAY (Payroll) product family. Its documented description is simply "Date-effective view," and it is reported as VALID in the ETRM repository. The view presents the currently effective rows of grade rule definitions used by Oracle Payroll and related HR compensation functionality. Grade rules determine how values such as minimum, mid-value and maximum are derived for a grade or spinal point, including the rate source used in the calculation. The "_X" suffix follows the standard Oracle EBS convention for a date-tracked (datetrack) view: the "_F" base table stores all dated versions of a row, while the "_X" view filters that table to the rows whose effective date range includes the current system date. Because it exposes only currently effective data, the view is intended for operational queries, reports, and integrations that must reflect today's active configuration. For the user searching on "rate_id," this view is directly relevant: RATE_ID is one of its documented columns, identifying the rate referenced by the grade rule.
Underlying Base Objects
The view is defined over a single documented base object, the synonym PAY_GRADE_RULES_F, which resolves to the underlying APPS date-tracked table. The view text confirms this relationship and defines the date-effectiveness logic explicitly:
- SELECT list: the view projects the full set of columns from the base table, including GRADE_RULE_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, BUSINESS_GROUP_ID, RATE_ID, GRADE_OR_SPINAL_POINT_ID, RATE_TYPE, MAXIMUM, MID_VALUE, MINIMUM, SEQUENCE, VALUE, and the standard WHO/audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, OBJECT_VERSION_NUMBER).
- Filter predicate:
WHERE TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE. This restricts output to rows effective on the current date, applying TRUNC to SYSDATE so that time-of-day does not affect the result.
Consequences for consumers: historical and future-dated rows present in PAY_GRADE_RULES_F are not returned. Because the filter is evaluated at query time, results change automatically as date ranges expire or begin. No database link or external object is involved; the view is local to APPS.
Key Columns
- GRADE_RULE_ID — Primary identifier for the grade rule row.
- EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Boundaries of the date-effective range that qualifies the row for inclusion.
- BUSINESS_GROUP_ID — Business group (operating unit) that owns the rule; the standard partitioning key for HR and Payroll data.
- RATE_ID — Identifies the rate associated with the grade rule; the documented column most often used to join to rate definitions.
- GRADE_OR_SPINAL_POINT_ID — References the grade or spinal point to which the rule applies.
- RATE_TYPE — Classifies the rate, for example a fixed or derived value type.
- MAXIMUM, MID_VALUE, MINIMUM — Monetary or numeric bounds defined by the rule.
- SEQUENCE, VALUE — Ordering and computed value elements of the rule definition.
- WHO and audit columns — REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, OBJECT_VERSION_NUMBER, supporting concurrent program traceability and optimistic locking.
Common Use Cases and Queries
Typical scenarios include validating currently effective grade rules before a payroll run, reporting rate assignments by business group, and integration extracts that must not pick up expired or future-dated definitions. The following samples illustrate common access patterns; all rely on the date-effectiveness already applied by the view.
- List all currently effective rules for a business group:
SELECT grade_rule_id, grade_or_spinal_point_id, rate_type,
minimum, mid_value, maximum, rate_id
FROM apps.pay_grade_rules_x
WHERE business_group_id = :p_business_group_id
ORDER BY sequence;
- Resolve the rate referenced by a rule, using the RATE_ID column:
SELECT g.grade_rule_id, g.rate_id, g.rate_type FROM apps.pay_grade_rules_x g WHERE g.rate_id = :p_rate_id;
- Audit which concurrent program last touched effective rules:
SELECT grade_rule_id, last_update_date, last_updated_by,
program_id, request_id
FROM apps.pay_grade_rules_x
WHERE last_update_date >= TRUNC(SYSDATE) - 30;
When historical or future-dated rows are required, query PAY_GRADE_RULES_F directly with an explicit date predicate on EFFECTIVE_START_DATE and EFFECTIVE_END_DATE, since PAY_GRADE_RULES_X deliberately returns only the row effective today.
-
View: PAY_GRADE_RULES_X 12.2.2
Date-effective view.
APPS.PAY_GRADE_RULES_X·↳ PAY_GRADE_RULES_F·Explore PAY module →
-
View: PAY_GRADE_RULES_X 12.1.1
Date-effective view.
APPS.PAY_GRADE_RULES_X·↳ PAY_GRADE_RULES_F·Explore PAY module →
-
VIEW: APPS.PAY_GRADE_RULES_X 12.1.1
-
VIEW: APPS.PAY_GRADE_RULES_X 12.2.2
-
Business view template from which the flexfield view is generated.
APPS.HRFV_GRD_PLACEMNT_PROG_PT_VALS·↳ HR_ALL_ORGANIZATION_UNITS_TL·↳ HR_BIS·↳ HR_GENERAL·Explore PER module →
-
Business view template from which the flexfield view is generated.
APPS.HRFV_GRD_PLACEMNT_PROG_PT_VALS·↳ HR_ALL_ORGANIZATION_UNITS_TL·↳ HR_BIS·↳ HR_GENERAL·Explore PER module →
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
eTRM - PAY Tables and Views 12.1.1
Temporary table used to hold invalid location addresses.
-
12.1.1 DBA Data 12.1.1
-
eTRM - PAY Tables and Views 12.2.2
Temporary table used to hold invalid location addresses.
-
eTRM - PER Tables and Views 12.2.2
Table to store NQF Training info for a person
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person
-
eTRM - PAY Tables and Views 12.1.1
Temporary table used to hold invalid location addresses.
-
eTRM - PAY Tables and Views 12.2.2
Temporary table used to hold invalid location addresses.
-
eTRM - PER Tables and Views 12.2.2
Table to store NQF Training info for a person
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person