Results for “change_reason_meaning”

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

Overview

The HR_ADP_ASSIGNMENT_V view is an APPS-owned database view within the Oracle E-Business Suite Human Resources (PER) product. It is documented in ETRM as an "ADP payroll interface view," indicating that its purpose is to expose assignment-level payroll data in a flat structure suitable for extraction by Automatic Data Processing (ADP) or similar third-party payroll processing interfaces. The view consolidates information drawn from core HR person, assignment, pay proposal, element entry, and organization objects into a single denormalized projection, allowing external payroll systems or interface programs to consume the data with minimal joining.

The view is marked VALID and resides in the APPS schema, and its definition incorporates a substantial amount of business logic, including DECODE-based translations, NVL-based defaulting, and calls to the HR_ADP and HR_GENERAL packages. This embedded logic means the view is not a simple join; it applies payroll-specific rules such as deriving a weekly/semi-monthly/bi-weekly/monthly period indicator from PER_TIME_PERIOD_TYPES.NUMBER_PER_FISCAL_YEAR, resolving the payroll status, and computing last-update timestamps using GREATEST across multiple source records. Because the search term supplied was "payroll_status," it is relevant to note that the view constructs a PAYROLL_STATUS column using nested DECODE and NVL expressions that resolve a status code from PER_ASS_STATUS_TYPE_AMENDS and PER_ASSIGNMENT_STATUS_TYPES, adjusted by a comparison against HR_ADP.GET_ADP_EXTRACT_DATE.

Underlying Base Objects

The documented base objects referenced by HR_ADP_ASSIGNMENT_V include both tables (via synonyms) and supporting views and packages. The principal person and assignment sources are PER_ALL_PEOPLE_F and PER_ALL_ASSIGNMENTS_F. Organization and location context is supplied by HR_ALL_ORGANIZATION_UNITS and HR_LOCATIONS_ALL, with soft coding values drawn from HR_SOFT_CODING_KEYFLEX. Job and pay basis details come from PER_JOBS and PER_PAY_BASES, while salary and proposal history is sourced from PER_PAY_PROPOSALS and PER_PERIODS_OF_SERVICE. Payroll element data is obtained from PAY_ELEMENT_TYPES_F, PAY_ELEMENT_LINKS_F, PAY_ELEMENT_LINKS_X, PAY_ELEMENT_ENTRIES_F, PAY_ELEMENT_ENTRY_VALUES_F, and PAY_INPUT_VALUES_F.

Status derivation relies on PER_ASSIGNMENT_STATUS_TYPES and PER_ASS_STATUS_TYPE_AMENDS, and period definitions are taken from PER_TIME_PERIOD_TYPES. The view also references HR_ADP (PACKAGE), HR_GENERAL (PACKAGE), HR_SECURITY (PACKAGE), and HR_ADP_EMP_REF_V (VIEW). HR_SECURITY in particular indicates that row-level security may be applied to the underlying person and assignment records, which is significant for controlled extraction.

Key Columns

• PAYROLL_STATUS — Derived status code combining assignment status and amendment data, with a special value ('D') returned when the assignment effective end date matches the truncated ADP extract date.
• COMPANY_CODE_EQUIVALENT — Company identifier from the employee reference view, used for payroll company mapping.
• PERSON_ID / EMPLOYEE_NUMBER / BUSINESS_GROUP_ID — Core person identifiers from PER_ALL_PEOPLE_F.
• ASSIGNMENT_ID / ASSIGNMENT_NUMBER / PRIMARY_FLAG — Assignment identifiers; PRIMARY_FLAG is decorrelated so that primary assignments receive a zero sequence.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Date-tracked validity of the assignment.
• NORMAL_HOURS — Standard working hours for the assignment.
• PAY_BASIS indicator — A single-character code (P, H, M, A) derived from PER_PAY_BASES.PAY_BASIS.
• Period type indicator — Weekly (W), Semi-monthly (S), Bi-weekly (B), or Monthly (M) based on NUMBER_PER_FISCAL_YEAR.
• Location and organization names/LOCATION_CODE — From HR_LOCATIONS_ALL and HR_ALL_ORGANIZATION_UNITS.
• LAST_CHANGE_DATE / NEXT_SAL_REVIEW_DATE / FINAL_PROCESS_DATE — Key payroll and salary milestone dates.
• Update timestamps — GREATEST expressions tracking the latest change across person, assignment, proposal, and proposal-period records.

Common Use Cases and Queries

This view is typically queried by ADP extract programs, custom payroll interfaces, and reconciliation reports. A frequent pattern is filtering on PAYROLL_STATUS to identify active versus terminated assignments for a given extract run.

SELECT person_id,
       employee_number,
       assignment_id,
       payroll_status,
       pay_basis_indicator,
       effective_start_date,
       effective_end_date
FROM   apps.hr_adp_assignment_v
WHERE  payroll_status = 'A'
AND    SYSDATE BETWEEN effective_start_date AND effective_end_date;

Analysts can also use the view to reconcile salary review schedules or confirm pay basis mapping before transmitting data to ADP. Because the view embeds HR_SECURITY logic, users must ensure their responsibility and security profile grant access to the underlying records. Customizations should not modify the view, since it is a seeded APPS object; instead, wrap it in a custom view or query to add site-specific filters.