Search Results smoker_flag




Overview
Explore in AI Chat

Overview

The APPS.HR_CERIDIAN_500_EMPLOYEE_V view is a seeded Oracle E-Business Suite database object owned by the APPS schema and delivered under the PER (Human Resources) product family. It functions as the employee-level extract interface for Ceridian Source 500 payroll processing, presenting both personal and assignment-related attributes of an employee in a single, denormalized row suitable for outbound third-party payroll feeds. The view carries a VALID status in ETRM 12.2.2 and performs no DML; it exists purely as a read-only projection.

Because Ceridian Source 500 relies on flat, fixed-format employee records, the view resolves foreign keys, effective-dated row selection, and profile-driven switching of the adjustment logic on behalf of the integration, shielding the payroll vendor from the normalized PER schemas.

Underlying Base Objects

The view is defined over the following documented base objects:

The joins make the view a composite of person, address, assignment, and service data keyed by PERSON_ID and BUSINESS_GROUP_ID.

Key Columns

The columns most relevant to payroll extraction include:

  • EMPLOYEE_NUMBER, LAST_NAME, FIRST_NAME, MIDDLE_NAMES, SUFFIX — the identity payload delivered to Ceridian.
  • NATIONAL_IDENTIFIER, SEX, DATE_OF_BIRTH, SPOUSE_DATE_OF_BIRTH — statutory and benefit eligibility data.
  • ADJUSTED_SERVICE_DATE — the user’s search term. It is derived conditionally: when PER_OAB_NEW_BENEFITS_MODEL is ‘Y’, the view returns PPS.ADJUSTED_SVC_DATE; otherwise it converts PP.ATTRIBUTE3 using the ‘YYYY/MM/DD HH24:MI:SS’ format. This dual path is the reason the column is often cited in customization and troubleshooting queries.
  • SMOKER_FLAG — likewise profile-controlled, mapped to PP.ATTRIBUTE2 when the new benefits model is enabled, otherwise to USES_TOBACCO_FLAG.
  • DATE_START, FINAL_PROCESS_DATE — hire and termination/processing markers.
  • DATE_FROM / DATE_TO (address) — effective dating, with DATE_TO nullified once the extract date is reached.
  • BUSINESS_GROUP_ID, PERSON_ID — keys for downstream joins and reconciliation.

Common Use Cases and Queries

Typical scenarios include verifying the adjusted service date used for benefit calculations before a Ceridian extract run, and reconciling employee demographic data across HR and payroll.

SELECT employee_number,
       last_name,
       first_name,
       adjusted_service_date
FROM   apps.hr_ceridian_500_employee_v
WHERE  adjusted_service_date IS NOT NULL;
SELECT employee_number,
       date_start,
       final_process_date,
       smoker_flag
FROM   apps.hr_ceridian_500_employee_v
WHERE  business_group_id = :p_business_group_id;

Because the view reads through HR_CERIDIAN.GET_CER_EXTRACT_DATE, results are sensitive to session context and extracted profile values; extraction jobs should therefore execute under the standard concurrent manager session rather than ad hoc SQL.