Results for “pay_status_processing_rules_f”

50+ results




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

Overview

PAY_STATUS_PROCESSING_RULES_F is a Payroll (PAY) module table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the assignment status rules that govern how specific payroll elements are processed. In practice, the table acts as a configuration repository that links an element type to an assignment status type and defines the rule by which processing should proceed — for example, whether an element is processed, skipped, or handled conditionally based on the employee's assignment status at the time of the payroll run.

Because the table carries EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns and a _F suffix, it is date-tracked (datetracked) and functions as the "F" (final/current) table in the standard EBS date-tracked table pattern. Its heuristic Data Vault classification, mined from the foreign-key structure, is satellite-leaning. This suggests that, in a dimensional or Data Vault model, the object is best treated as a descriptive satellite attached to a business key comprised of element type, assignment status type, business group, and legislation, rather than as a standalone hub or a many-to-many link.

Key Information Stored

The table contains 18 documented columns. The most important are summarized below, distinguishing the surrogate primary key from the business-key candidates defined by unique indexes.

The primary key isolates a single physical row, while PAY_STATUS_PROCESSING_RULE_UK2 — spanning element type, assignment status type, business group, legislation, dates, and processing rule — defines the logical business key that prevents duplicate rule definitions.

Common Use Cases and Queries

Typical uses include auditing which assignment statuses drive or suppress element processing, troubleshooting payroll run outcomes where an element unexpectedly did not process, and reporting configuration for a given legislation or business group.

  • Rules for a given element and business group:
    SELECT p.ELEMENT_TYPE_ID, p.ASSIGNMENT_STATUS_TYPE_ID,
           p.PROCESSING_RULE, p.EFFECTIVE_START_DATE, p.EFFECTIVE_END_DATE
    FROM   HR.PAY_STATUS_PROCESSING_RULES_F p
    WHERE  p.ELEMENT_TYPE_ID = :element_type_id
    AND    p.BUSINESS_GROUP_ID = :business_group_id
    AND    TRUNC(SYSDATE) BETWEEN p.EFFECTIVE_START_DATE AND p.EFFECTIVE_END_DATE;
    
  • Rules effective as of a payroll run date: filter on the date window using the run's effective date rather than SYSDATE.
  • Join to status and element lookups to render readable reports, translating IDs into names.
  • Integration / data migration: extract current rows to replicate payroll configuration across environments.

Related Objects

  • PER_ASSIGNMENT_STATUS_TYPES — referenced by PAY_STATUS_PROCESSING_RULES_F.ASSIGNMENT_STATUS_TYPE_ID; the FK target that resolves the assignment status definition.
  • PAY_ELEMENT_TYPES_F — the element type referenced by ELEMENT_TYPE_ID, supplying element names and classifications.
  • FF_FORMULAS_F — resolves FORMULA_ID into the underlying payroll formula.
  • FND_DOCUMENTS / comment objects — resolve COMMENT_ID into descriptive text.
  • HR_ALL_ORGANIZATION_UNITS — provides business group context via BUSINESS_GROUP_ID.
  • PAY_STATUS_PROCESSING_RULES_TL / _VL — associated translated and view layers that expose this base table for reporting.
  • Payroll run/batch objects (e.g., PAY_PAYROLL_ACTIONS) — consume these rules indirectly during processing to determine element behavior per assignment status.