Search Results run_method




Overview
Explore in AI Chat

Overview

The PAY_RUN_TYPES view is a date-effective reporting object in the Oracle E-Business Suite Payroll (PAY) product, owned by the APPS schema. In Oracle EBS 12.1.1 and 12.2.2, it exposes payroll run type definitions that are valid as of the current application session's effective date. A "run type" defines the category of a payroll run — for example a regular payroll run, a supplemental run, a reversal, or a quick pay — and controls how the payroll engine processes that run. The view shields consumers from the underlying date-tracked table by automatically filtering rows to those whose effective start and end dates bracket the session effective date, returning only the single currently valid version of each run type.

Because it is a view and not a table, PAY_RUN_TYPES is read-only. It is intended for enquiry, reporting, and integration rather than for data maintenance; inserts and updates must be directed at the underlying _F table through the supported payroll APIs. The object holds a VALID status in the APPS schema and is available wherever the Payroll product is licensed.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through APPS synonyms:

The view text selects from PAY_RUN_TYPES_F aliased as RT and applies two correlated sub-queries against FND_SESSIONS using USERENV('SESSIONID'). A row is returned only when its EFFECTIVE_START_DATE is less than or equal to the session effective date and its EFFECTIVE_END_DATE is greater than or equal to that same date. This pattern is the standard Oracle HRMS/Payroll date-effective view construct and guarantees that a query returns exactly one effective row per run type for the session context.

Key Columns

  • RUN_TYPE_ID — the primary identifier of the run type; the join key to other payroll run tables.
  • RUN_TYPE_NAME — the user-visible name of the run type.
  • RUN_METHOD — indicates the processing method associated with the run type (for example, whether the run processes a standard range of assignments). This is a key attribute governing payroll behaviour.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-effective bounds controlling row visibility.
  • BUSINESS_GROUP_ID — the legislative business group to which the run type belongs; important for multi-organization filtering in HRMS queries.
  • LEGISLATION_CODE — the legislation (country) under which the run type is defined, used to isolate country-specific run types.
  • SHORTNAME — an abbreviated identifier for the run type.
  • OBJECT_VERSION_NUMBER — the optimistic-locking version stamp used by the underlying table's DML.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE provide standard who-column auditing.

Common Use Cases and Queries

The view is typically queried to list the run types available to a paying business group, to look up a run type name from a RUN_TYPE_ID encountered on a payroll action, or to drive validation and reporting logic. A representative query is shown below.

  • Listing effective run types for a business group and legislation.
  • Resolving RUN_TYPE_ID values returned by payroll run or assignment action queries.
  • Feeding LOVs and integration extracts that require the current run type definition.

Sample SQL:

SELECT rt.run_type_id, rt.run_type_name, rt.run_method, rt.shortname, rt.legislation_code
FROM apps.pay_run_types rt
WHERE rt.business_group_id = :p_business_group_id
ORDER BY rt.run_type_name;

Note that because filtering depends on FND_SESSIONS, results reflect the effective date of the session in which the query executes; applications that must report on a historic or future date must query the base table PAY_RUN_TYPES_F directly with explicit date predicates rather than relying on this view.