Search Results pay_run_types_pk

Overview

PAY_RUN_TYPES_F is the core definition table for payroll run types in Oracle E-Business Suite Payroll (PAY). Owned by the HR schema, it stores the different categories of payroll run processing that an enterprise can initiate, such as regular payroll runs, supplemental runs, prepayments, reversals, and quick pays. Each row represents a date-tracked (datetracked) definition of a run type, meaning the table is an effective-dated entity: the same logical run type can exist as multiple rows partitioned by EFFECTIVE_START_DATE and EFFECTIVE_END_DATE, allowing historical and future-dated changes without losing prior configuration.

From a Data Vault modeling perspective, the mined heuristic classification is standalone, suggesting this object behaves as an independent reference/satellite construct rather than a link resolving many-to-many relationships. In practice it functions as a reference data hub-with-history: the run type identity is stable, while date-effective attributes form its temporal satellite content.

The table is central to the payroll processing cycle. When a payroll administrator submits a run, the application reads the corresponding run type definition to determine processing behavior, parameters, and reporting characteristics. It is therefore foundational to both transactional payroll execution and downstream reporting.

Key Information Stored

The table contains 47 documented columns, of which the most operationally significant are:

• RUN_TYPE_ID — surrogate identifier for the run type; part of the primary key PAY_RUN_TYPES_PK.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the datetrack columns that bound each version of the definition; both are also primary key members.
• RUN_TYPE_NAME — the user-visible name of the run type; a business-key component in PAY_RUN_TYPES_UK1.
• RUN_METHOD — the processing method associated with the run type (for example, whether it is a regular or a special run).
• BUSINESS_GROUP_ID — the enterprise grouping that owns the run type; a uniqueness component.
• LEGISLATION_CODE — the legislation under which the run type is valid; a uniqueness component.
• SHORTNAME — an abbreviated identifier for the run type; part of the unique index.
• SRS_FLAG — indicates characteristics related to reporting or submission behavior.
• RUN_INFORMATION_CATEGORY and RUN_INFORMATION1 through RUN_INFORMATION30 — a flexible descriptive-flexfield style block used to store run type specific attributes and parameters.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns for change tracking.
• OBJECT_VERSION_NUMBER — optimistic locking and row versioning support.

The primary key PAY_RUN_TYPES_PK (RUN_TYPE_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, and ZD_EDITION_NAME) uses the surrogate identifier combined with datetrack columns. The unique index PAY_RUN_TYPES_UK1 (RUN_TYPE_NAME, EFFECTIVE_START_DATE, BUSINESS_GROUP_ID, LEGISLATION_CODE, SHORTNAME, EFFECTIVE_END_DATE, ZD_EDITION_NAME) represents the business-key candidate that enforces naming uniqueness within a business group and legislation.

Common Use Cases and Queries

Typical uses center on identifying available run types and interpreting their configuration.

• Listing currently active run types for a business group:

SELECT run_type_id, run_type_name, shortname, legislation_code
FROM   pay_run_types_f
WHERE  business_group_id = :p_bg_id
AND    TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;

• Looking up the run method for a submitted payroll process to determine processing behavior.
• Driving reporting on which run types were used across payroll periods, joined to the payroll action and assignment action tables.
• Migrating or auditing configuration by comparing date-effective versions of the same run type.

Related Objects

The metadata classifies this table as standalone, but functionally it is referenced by payroll transaction and action tables. Significant related objects include:

• PAY_RUN_TYPES (view) — exposes the effective-dated rows for application queries.
• PAY_PAYROLL_ACTIONS — links a payroll action to the run type used.
• PAY_ASSIGNMENT_ACTIONS — assignment-level results for a given run type.
• PAY_RUN_RESULTS / PAY_RUN_RESULT_VALUES — payroll calculation output associated with a run type.
• PAY_PAYROLLS_F — defines the payroll to which run types are applied.
• PAY_ELEMENT_TYPES_F — elements processed within the run.

These joins are driven through RUN_TYPE_ID and the associated datetrack columns.