Results for “last_standard_process_date”

50+ results




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

Overview

HR_ADP_EMPLOYEE_V is a seeded, VALID database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the PER (Human Resources) product family and is documented as an "ADP payroll interface view." Its purpose is to present a single, flattened employee record structured for consumption by the ADP payroll interface, consolidating person, assignment, address, period-of-service, and organization data that would otherwise require numerous joins across the HR schema.

The view is a key component of the HR_ADP extraction architecture. Rather than serving transactional screens, it supplies the row-level dataset that the HR_ADP package and related extract processes read when generating the outbound file transmitted to ADP. Because the columns and the assignment-status derivation logic are embedded in the view definition, the ADP interface mapping is effectively fixed at the view layer, and the returned values drive termination, status, and date-of-death coding in the extract.

For users searching on deceased_flag, the relevant behavior is the derived column defined as DECODE(PP.DATE_OF_DEATH, NULL, 'N', 'Y'). This does not read a stored flag column; it is computed at runtime from PER_ALL_PEOPLE_F.DATE_OF_DEATH. A value of 'Y' indicates a recorded date of death, and 'N' indicates none. This derived value is the view's effective deceased indicator and is the field consumed downstream by the ADP interface.

Underlying Base Objects

The view is defined over the following documented base objects: the HR_ADP, HR_GENERAL, and HR_SECURITY packages; the HR_ADP_EMP_REF_V and HR_ADP_SPOUSE_V views; and synonyms to HR_ALL_ORGANIZATION_UNITS, HR_SOFT_CODING_KEYFLEX, PAY_PEOPLE_GROUPS, PER_ADDRESSES, PER_ALL_ASSIGNMENTS_F, PER_ALL_PEOPLE_F, PER_ASSIGNMENT_STATUS_TYPES, PER_JOBS, PER_PERIODS_OF_SERVICE, and PER_TIME_PERIOD_TYPES.

PER_ALL_PEOPLE_F is the primary driver, supplying person attributes including employee number, name, sex, national identifier, date of birth, date of death, marital status, and original date of hire. PER_ALL_ASSIGNMENTS_F provides assignment context and organization linkage, while PER_PERIODS_OF_SERVICE contributes termination, final-process, and leaving-reason data. PER_ADDRESSES supplies address and telephone information, HR_ALL_ORGANIZATION_UNITS resolves organization names, and HR_SOFT_CODING_KEYFLEX (HS) provides the segment values used for company and location coding. PER_TIME_PERIOD_TYPES supplies the payroll frequency that the view decodes into W, S, B, or M. HR_ADP_EMP_REF_V delivers the company code equivalent, and HR_ADP_SPOUSE_V contributes spouse date of birth. HR_SECURITY is invoked to enforce row-level access, and HR_ADP.GET_ADP_EXTRACT_DATE is called within the assignment-status decode.

Key Columns

Common Use Cases and Queries

The most frequent use is the generation and troubleshooting of the ADP extract, particularly verifying how an employee will be coded for status, termination, or deceased processing. Because the deceased indicator is derived rather than stored, reconciliation and audit queries commonly filter on it.

Identify deceased employees included in the interface:

  • SELECT employee_number, first_name, last_name, date_of_death FROM apps.hr_adp_employee_v WHERE DECODE(date_of_death, NULL, 'N', 'Y') = 'Y';

Count active versus terminated assignments for the extract:

  • SELECT assignment_status, COUNT(*) FROM apps.hr_adp_employee_v GROUP BY assignment_status;

Cross-check deceased persons directly against the base table:

  • SELECT p.employee_number, p.date_of_death FROM apps.per_all_people_f p WHERE p.date_of_death IS NOT NULL AND TRUNC(SYSDATE) BETWEEN p.effective_start_date AND p.effective_end_date;

Additional scenarios include auditing termination dates and leaving reasons before submission, validating company and location coding before file generation, and confirming that HR_SECURITY is returning the expected population. All queries should be executed read-only, as the view is a reporting/integration object rather than a maintenance surface.