Results for “pay_status_processing_rules_x”

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

Overview

The PAY_STATUS_PROCESSING_RULES_X view is a date-effective (informational) view owned by the APPS schema within the Oracle E-Business Suite Payroll (PAY) product. Its primary function is to present the currently effective rows from the underlying PAY_STATUS_PROCESSING_RULES_F table by applying a system-date filter. It is classified as a "Date-effective view," which is a standard Oracle EBS design pattern for exposing datetracked configuration data to reports, concurrent programs, and integrations without requiring callers to construct their own effective-date predicates.

The view is documented as VALID in both ETRM 12.1.1 and 12.2.2 environments. Status processing rules drive how assignment statuses are handled during payroll processing — for example, whether an assignment should be processed, skipped, or calculated based on its current status. The view therefore plays an important role in reporting and integration scenarios where only the rule that is active "as of today" is relevant.

Underlying Base Objects

The view is defined over a single referenced base object, PAY_STATUS_PROCESSING_RULES_F, which is exposed through a synonym in the APPS schema. The ETRM metadata records the following definition:

• Base object: PAY_STATUS_PROCESSING_RULES_F (accessed via synonym)
• Filter predicate: TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE

Because the definition applies TRUNC(SYSDATE), the view always returns the single effective version of each status processing rule valid on the current system date. Historical or future-dated rule versions stored in the _F table are excluded. This mirrors the behavior of Oracle's standard _X views (for example, those used across HRMS datetracked entities) and means the view is read-only and intended for query and reporting rather than maintenance.

Key Columns

The view exposes the full column set from the underlying _F table, including both business attributes and standard WHO (audit) columns. Significant columns include:

• STATUS_PROCESSING_RULE_ID — Primary key identifying each status processing rule record.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — The datetrack effective range of the rule version.
• BUSINESS_GROUP_ID — Business group context for the rule.
• LEGISLATION_CODE — Payroll legislation (for example, US, GB) to which the rule applies.
• LEGISLATION_SUBGROUP — Further legislative subdivision where relevant.
• ELEMENT_TYPE_ID — Element type associated with the rule, if rule behaviour is element-specific.
• ASSIGNMENT_STATUS_TYPE_ID — The assignment status type that the processing rule governs.
• FORMULA_ID — Optional formula referenced when the rule requires formula-based processing.
• PROCESSING_RULE — The rule value/indicator defining how the status is treated during processing.
• COMMENT_ID — Reference to supporting comment/note text.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard audit columns.

Common Use Cases and Queries

Typical uses include validating payroll configuration during implementation, troubleshooting why certain assignments were processed or skipped, and driving integrations that need the currently effective rule set. Because the view already filters by TRUNC(SYSDATE), queries do not normally need their own date predicate.

Example 1 — list all currently effective rules for a legislation:

• SELECT status_processing_rule_id, assignment_status_type_id, element_type_id, processing_rule, formula_id
•   FROM apps.pay_status_processing_rules_x
•  WHERE legislation_code = 'US';

Example 2 — join to assignment status type to present readable rule output:

• SELECT p.processing_rule, ast.user_status, p.legislation_code
•   FROM apps.pay_status_processing_rules_x p,
•        apps.pay_assignment_status_types ast
•  WHERE p.assignment_status_type_id = ast.assignment_status_type_id;

Example 3 — count effective rules per business group to audit configuration coverage:

• SELECT business_group_id, COUNT(*)
•   FROM apps.pay_status_processing_rules_x
•  GROUP BY business_group_id;

Where historical or future-dated rules must be examined, query the underlying PAY_STATUS_PROCESSING_RULES_F table directly, as the _X view intentionally limits output to the effective-dated slice for the current date.