Results for “period_reset_years”

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

Overview

PAY_ALL_PAYROLLS is a date-effective view owned by the APPS schema in Oracle E-Business Suite (documented against 12.1.1 and 12.2.2). It exposes payroll definitions from the PAY product family, presenting one logical row per payroll valid as of the current session's effective date. The view is the query-friendly interface to the underlying payroll definition entity, and it is the object most commonly referenced by reports, concurrent programs, extracts, and integration code that need a payroll's controlling attributes rather than its transaction-level results.

Because the view filters on the session effective date rather than returning every dated row, callers automatically see the version of the payroll that applies to the business date in context. This removes the need for callers to add their own EFFECTIVE_START_DATE / EFFECTIVE_END_DATE predicates, which is the principal reason the view exists alongside its base table.

Underlying Base Objects

The view is defined over a single documented base object, PAY_ALL_PAYROLLS_F (referenced through a SYNONYM), with a supporting reference to FND_SESSIONS. The SELECT list enumerates the full column set of the base table, including the surrogate primary key PAYROLL_ID, the date-effective range columns EFFECTIVE_START_DATE and EFFECTIVE_END_DATE, the descriptive PAYROLL_NAME, and the PRL_INFORMATION1–30 descriptive flexfield context and segment columns.

The date-effectiveness predicate is driven by a subquery against FND_SESSIONS, matching SESSION_ID to USERENV('SESSIONID') and comparing the session EFFECTIVE_DATE to the row's effective range. The view therefore returns the single currently applicable version of each payroll for the running session.

Key Columns

• PAYROLL_ID — surrogate key of the payroll definition; the join key to payroll actions, assignment payrolls, and element entries.
• PAYROLL_NAME — user-visible payroll name.
• BUSINESS_GROUP_ID — the business group (legislative context) that owns the payroll.
• PERIOD_TYPE — the payroll period frequency (for example, weekly, semi-monthly, monthly).
• NUMBER_OF_YEARS — the number of years of payroll periods generated and made available.
• PERIOD_RESET_YEARS — the reset interval, in years, at which the calendar of payroll periods is re-established. This column is directly relevant to the searched term period_reset_years and controls the horizon over which period definitions recur before resetting.
• FIRST_PERIOD_END_DATE — the anchor date from which the payroll calendar is generated.
• PAY_DATE_OFFSET, CUT_OFF_DATE_OFFSET, PAY_ADVICE_DATE_OFFSET, DIRECT_DEPOSIT_DATE_OFFSET, PAYSLIP_VIEW_DATE_OFFSET, MIDPOINT_OFFSET — the relative day offsets that drive payroll run dates, cut-off, advice dates, and related timing behavior.
• DEFAULT_PAYMENT_METHOD_ID, CONSOLIDATION_SET_ID, ORGANIZATION_ID — default payment method and consolidation/organization references.
• COST_ALLOCATION_KEYFLEX_ID, SUSPENSE_ACCOUNT_KEYFLEX_ID, SOFT_CODING_KEYFLEX_ID, GL_SET_OF_BOOKS_ID — accounting and costing defaults.
• NEGATIVE_PAY_ALLOWED_FLAG, ARREARS_FLAG, MULTI_ASSIGNMENTS_FLAG, WORKLOAD_SHIFTING_LEVEL — payroll processing behavior flags.
• PRL_INFORMATION_CATEGORY and PRL_INFORMATION1–30, ATTRIBUTE1–20 — descriptive flexfield context and segments.
• Effective dating, audit, and comment columns — EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, COMMENT_ID, and standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN).

Common Use Cases and Queries

Typical scenarios include populating payroll selection lists in custom forms and OAF pages, driving payroll extracts and third-party interfaces, and validating payroll configuration in audit reports. Because the view is already date-filtered, queries are simple.

To locate payrolls by name and their period reset configuration:

• SELECT payroll_id, payroll_name, period_type, number_of_years, period_reset_years, first_period_end_date FROM pay_all_payrolls WHERE UPPER(payroll_name) LIKE UPPER(:p_name);

To return all payrolls for a business group with their payment and accounting defaults:

• SELECT p.payroll_id, p.payroll_name, p.period_type, p.default_payment_method_id, p.gl_set_of_books_id FROM pay_all_payrolls p WHERE p.business_group_id = :p_bg_id ORDER BY p.payroll_name;

To join payroll definitions to their dated base rows and date-effective relationships:

• SELECT p.payroll_name, f.effective_start_date, f.effective_end_date FROM pay_all_payrolls p, pay_all_payrolls_f f WHERE p.payroll_id = f.payroll_id AND p.business_group_id = :p_bg_id;

In every case the view supplies the currently effective payroll row for the session, so callers should avoid re-applying effective-date predicates on the view itself and should use the _F base table only when historical versions are explicitly required.