Search Results default_payment_method

Overview

PAY_ALL_PAYROLLS_D is a DateTrack history view owned by the APPS schema within the PAY (Payroll) product in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to expose the historical, date-effective record set behind the PAY_ALL_PAYROLLS view, and it is used primarily by the DateTrack History mechanism. In Oracle HRMS terminology, DateTrack enables users to retain multiple effective-dated versions of a record and to view prior or future datetracked rows. The "_D" suffix follows Oracle's convention for the DateTrack history variant of a view, meaning rows reflected here correspond to the full effective dating history rather than only the currently active record.

The view presents payroll definitions joined to consolidation sets, payment methods, organizations, cost allocation flexfields, and soft coding key flexfields, along with decoded lookup meanings. It functions as a reporting and integration access point for payroll configuration data that must be reproduced as of a prior effective date.

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, PAY_ALL_PAYROLLS_D references the following objects in the APPS schema: FND_GLOBAL (PACKAGE), FND_LOOKUPS (VIEW), FND_USER (SYNONYM), HR_ALL_ORGANIZATION_UNITS (SYNONYM), HR_ALL_ORGANIZATION_UNITS_TL (SYNONYM), HR_API (PACKAGE), HR_GENERAL (PACKAGE), HR_LOOKUPS (VIEW), HR_SECURITY (PACKAGE), HR_SOFT_CODING_KEYFLEX (SYNONYM), PAY_CONSOLIDATION_SETS (SYNONYM), PAY_COST_ALLOCATION_KEYFLEX (SYNONYM), PAY_ORG_PAYMENT_METHODS_F (SYNONYM), PAY_ORG_PAYMENT_METHODS_F_TL (SYNONYM), and PAY_PAYROLLS_F (VIEW). The view text joins PAY_PAYROLLS_F to PAY_CONSOLIDATION_SETS, HR_SOFT_CODING_KEYFLEX, PAY_ORG_PAYMENT_METHODS_F and its translation table, HR_ALL_ORGANIZATION_UNITS and its translation table, the cost allocation keyflex, and both HR_LOOKUPS and FND_LOOKUPS for meaning columns.

The standard DateTrack and multilingual translation predicates are applied. Outer joins on the translation tables use the pattern DECODE(key, NULL, '1', language) = DECODE(key, NULL, '1', USERENV('LANG')), and the payment method join is constrained so that the payroll effective date falls between NVL(method effective start date, payroll effective start date) and NVL(method effective end date, payroll effective start date).

Key Columns

• PAYROLL_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE — the primary date-effective keys for the payroll record.
• PAYROLL_NAME — the payroll's descriptive name.
• CONSOLIDATION_SET_NAME — from PAY_CONSOLIDATION_SETS.
• PERIOD_TYPE, FIRST_PERIOD_END_DATE — payroll period definition attributes.
• CUT_OFF_DATE_OFFSET, DIRECT_DEPOSIT_DATE_OFFSET, PAY_ADVICE_DATE_OFFSET, PAY_DATE_OFFSET, MIDPOINT_OFFSET — date offset settings.
• ARREARS_FLAG, MULTI_ASSIGNMENTS_FLAG — payroll configuration flags.
• ORG_PAYMENT_METHOD_NAME and the associated organization NAME (ORGTL.NAME) — the default payment method context, which is the column a user searching for default_payment_method is typically interested in.
• CONCATENATED_SEGMENTS from HR_SOFT_CODING_KEYFLEX and from PAY_COST_ALLOCATION_KEYFLEX (both cost and distribution flexfields).
• MEANING values from HR_LOOKUPS (HR1) and FND_LOOKUPS (FND1).
• LAST_UPDATE_DATE and USER_NAME — audit information from FND_USER.

Common Use Cases and Queries

A frequent requirement is to trace which default payment method was attached to a payroll as of a given effective date, since DEFAULT_PAYMENT_METHOD_ID drives the payment method joined via PAY_ORG_PAYMENT_METHODS_F. The history view allows retrieval of that linkage for any effective date. Report authors and integration developers also use it to reconcile payroll configuration changes over time, audit cost allocation and soft coding assignments, and resolve organization and payment method translations into the session language.

SELECT p.PAYROLL_NAME,
       p.ORG_PAYMENT_METHOD_NAME,
       p.EFFECTIVE_START_DATE,
       p.EFFECTIVE_END_DATE
FROM   APPS.PAY_ALL_PAYROLLS_D p
WHERE  p.EFFECTIVE_START_DATE <= :effective_date
AND   (p.EFFECTIVE_END_DATE IS NULL
       OR p.EFFECTIVE_END_DATE >= :effective_date)
ORDER BY p.PAYROLL_NAME;

Queries against this view should always be bounded by effective date, because an unbounded select returns every historical and future row. Access is typically granted through the standard APPS reporting responsibilities rather than direct schema grants.