Search Results default_payment_method_id




Overview
Explore in AI Chat

Overview

PAY_PAYROLLS_X is a date-effective (datetracked) view owned by the APPS schema in Oracle E-Business Suite, belonging to the PAY – Payroll product. It presents the currently active payroll definitions for an enterprise as of the system date. The view is defined over the PAY_PAYROLLS_F base table, applying an effective-date filter so that only rows where the current date falls between EFFECTIVE_START_DATE and EFFECTIVE_END_DATE are returned. In Oracle EBS 12.1.1 and 12.2.2, this pattern mirrors the standard date-tracked object convention: the "_F" object stores all versioned rows, while the "_X" view exposes the single active version for transactional and reporting use. Because the view filters on TRUNC(SYSDATE), it always returns a consistent, point-in-time snapshot of valid payroll records without requiring the caller to supply date parameters. This makes it the preferred source for concurrent programs, reports, and integrations that must reference a payroll's current configuration.

Underlying Base Objects

The documented base object is PAY_PAYROLLS_F (VIEW), from which all columns are inherited. The ETRM metadata lists HR_GENERAL (PACKAGE) and HR_SECURITY (PACKAGE) as supporting references associated with the object. HR_SECURITY is significant because date-effective HR/payroll views commonly embed business-group security predicates at runtime, ensuring the querying session only sees payrolls for organizations it is authorized to access. The view text itself is a direct projection of PAY_PAYROLLS_F columns with the effective-date WHERE clause appended, and no joins are performed within the view definition. In Oracle EBS releases, PAY_PAYROLLS_F provides the versioned data and is conventionally paired with a corresponding _X date-effective view.

Key Columns

The view exposes the full payroll attribute set. The primary key column PAYROLL_ID uniquely identifies each payroll. EFFECTIVE_START_DATE and EFFECTIVE_END_DATE delimit the version's validity window. BUSINESS_GROUP_ID and ORGANIZATION_ID establish ownership and legislative context. The column most relevant to the search term, SUSPENSE_ACCOUNT_KEYFLEX_ID, stores the key flexfield combination identifier for the suspense account to which unresolved payroll entries are posted. Closely related accounting columns include COST_ALLOCATION_KEYFLEX_ID, SOFT_CODING_KEYFLEX_ID, and GL_SET_OF_BOOKS_ID, which govern costing, soft coding, and general ledger mapping. Payment and scheduling behavior is controlled by DEFAULT_PAYMENT_METHOD_ID, CONSOLIDATION_SET_ID, PERIOD_TYPE, CUT_OFF_DATE_OFFSET, PAY_DATE_OFFSET, PAY_ADVICE_DATE_OFFSET, DIRECT_DEPOSIT_DATE_OFFSET, FIRST_PERIOD_END_DATE, MIDPOINT_OFFSET, and NUMBER_OF_YEARS. Flags such as NEGATIVE_PAY_ALLOWED_FLAG, ARREARS_FLAG, and MULTI_ASSIGNMENTS_FLAG control validation rules. Descriptive and audit columns include PAYROLL_NAME, COMMENT_ID, ATTRIBUTE_CATEGORY, ATTRIBUTE1–20, PRL_INFORMATION_CATEGORY, PRL_INFORMATION1–30, and the standard WHO audit columns.

Common Use Cases and Queries

The view is typically used to list active payrolls, retrieve configuration for a specific payroll, or resolve the suspense account flexfield for accounting integrations. A representative query retrieving the suspense account keyflex for all active payrolls is:

  • SELECT PAYROLL_ID, PAYROLL_NAME, SUSPENSE_ACCOUNT_KEYFLEX_ID, GL_SET_OF_BOOKS_ID FROM APPS.PAY_PAYROLLS_X WHERE BUSINESS_GROUP_ID = :p_business_group_id;
  • SELECT PAYROLL_ID, PAYROLL_NAME, PERIOD_TYPE, PAY_DATE_OFFSET, CUT_OFF_DATE_OFFSET FROM APPS.PAY_PAYROLLS_X ORDER BY PAYROLL_NAME;
  • SELECT PAYROLL_ID, COST_ALLOCATION_KEYFLEX_ID, SOFT_CODING_KEYFLEX_ID FROM APPS.PAY_PAYROLLS_X WHERE PAYROLL_ID = :p_payroll_id;

Because the view draws exclusively from PAY_PAYROLLS_F, it is read-only and intended for querying rather than DML. For historical or future-dated versions of a payroll, query PAY_PAYROLLS_F directly with the appropriate date range.