Results for “payroll_type”

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

Overview

PAY_PAYROLLS_F is a secure, date-tracked (datetracked) view owned by the APPS schema in Oracle E-Business Suite, belonging to the PAY (Payroll) product. It presents payroll definition data — the master records that govern how payroll runs are processed, costed, and paid — as maintained in the Oracle HRMS Payroll module. The "_F" suffix conventionally denotes a view whose rows carry effective start and end dates, enabling the date-effective (datetrack) behavior that Oracle HRMS uses to preserve a full history of changes to a payroll definition over time. As its documented description states, PAY_PAYROLLS_F is a secure view based on the corresponding _ALL_ table, meaning it filters the underlying payroll data according to the responsibility's security profile and business group, so a user or concurrent program only sees the payrolls they are authorized to access. This makes it the standard presentation-layer object for reporting, integrations, and APIs that need to read payroll definitions without querying the base table directly.

Underlying Base Objects

According to the ETRM metadata for 12.2.2, the view is defined over the following referenced objects: the synonym PAY_ALL_PAYROLLS_F, and the packages HR_SECURITY and HR_GENERAL. In the view text, PAY_ALL_PAYROLLS_F is aliased as PAP and is the true source of payroll rows; PAY_PAYROLLS_F is therefore a filtered projection of that _ALL_ table, not of a physical base table. The security filtering is performed by two DECODE expressions. The first calls HR_SECURITY.SHOW_RECORD('PAY_ALL_PAYROLLS_F', PAP.PAYROLL_ID), which returns TRUE only when the current user's security profile grants access to the specific payroll; the shortcut HR_SECURITY.VIEW_ALL = 'Y' bypasses this per-row check for users with unrestricted access. The second expression uses HR_GENERAL.GET_XBG_PROFILE and HR_GENERAL.G... to restrict rows to the user's current business group, ensuring payrolls from other business groups are not exposed. Together these packages enforce row-level security at the view layer.

Key Columns

The view exposes the full set of payroll attributes, including the primary key PAYROLL_ID and the datetrack columns EFFECTIVE_START_DATE and EFFECTIVE_END_DATE. Identification and grouping columns include BUSINESS_GROUP_ID and PAYROLL_NAME. Financial and costing attributes include DEFAULT_PAYMENT_METHOD_ID, CONSOLIDATION_SET_ID, COST_ALLOCATION_KEYFLEX_ID, SUSPENSE_ACCOUNT_KEYFLEX_ID, GL_SET_OF_BOOKS_ID, SOFT_CODING_KEYFLEX_ID, and ORGANIZATION_ID. Scheduling and payment columns include PERIOD_TYPE, CUT_OFF_DATE_OFFSET, DIRECT_DEPOSIT_DATE_OFFSET, FIRST_PERIOD_END_DATE, PAY_ADVICE_DATE_OFFSET, PAY_DATE_OFFSET, PAYSLIP_VIEW_DATE_OFFSET, MIDPOINT_OFFSET, and NUMBER_OF_YEARS. Behavioral flags include NEGATIVE_PAY_ALLOWED_FLAG, ARREARS_FLAG, MULTI_ASSIGNMENTS_FLAG, and WORKLOAD_SHIFTING_LEVEL. The view also carries COMMENT_ID, PAYROLL_TYPE, PERIOD_RESET_YEARS, the ATTRIBUTE1–20 descriptive flexfield columns, the PRL_INFORMATION1–30 context columns, and the standard WHO audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE).

Common Use Cases and Queries

Typical uses include validating payroll setup during configuration, driving integrations that must honor security, and reporting on payroll definitions by business group. A simple query lists payrolls visible to the current responsibility:

• SELECT payroll_id, payroll_name, period_type, payroll_type FROM pay_payrolls_f WHERE TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;
• SELECT payroll_id, payroll_name, gl_set_of_books_id, consolidation_set_id FROM pay_payrolls_f WHERE business_group_id = :p_bg_id;
• SELECT payroll_name, negative_pay_allowed_flag, arrears_flag, multi_assignments_flag FROM pay_payrolls_f WHERE payroll_type = 'R';

Because the view is secure, results automatically reflect the caller's security profile and business group, eliminating the need to replicate HR_SECURITY logic in application code. For unrestricted administrative extracts, querying PAY_ALL_PAYROLLS_F directly may be appropriate, but PAY_PAYROLLS_F remains the recommended, security-compliant interface for standard reporting and integration.