Search Results holiday_code

Overview

The APPS.HR_CERIDIAN_EMPLOYEE_ONLY_V view is a seeded database object within the Oracle E-Business Suite PER (Human Resources) product module. Its documented purpose is to serve as a Ceridian Source 100 payroll interface view, presenting a flattened, denormalized projection of employee, assignment, address, and payroll element data intended for extraction by the Ceridian Source 100 third-party payroll application. It is therefore an integration surface rather than a transactional or data-entry object.

The view is registered with a status of VALID and is owned by the APPS schema, consistent with the standard Oracle EBS convention in which seeded reporting and interface views reside in APPS while the underlying base tables remain in the PER, PAY, and HR schemas. In releases 12.1.1 and 12.2.2 the definition of this view is essentially unchanged; the metadata supplied for 12.2.2 lists the same referenced objects.

A user searching for the term vacation_code in connection with this view is typically attempting to locate a leave, absence, or accrual attribute exposed for downstream payroll transmission. It should be noted that vacation_code is not a documented column of HR_CERIDIAN_EMPLOYEE_ONLY_V; the view instead surfaces element entry values generically through the SCREEN_ENTRY_VALUE columns sourced from PAY_ELEMENT_ENTRY_VALUES_F. Any vacation, leave, or accrual code configured as an element input value would be delivered through those generic columns rather than through a specifically named VACATION_CODE column.

Underlying Base Objects

The view is constructed from a multi-table join across the PER, PAY, and HR schemas, filtered so that only employee-type assignments are returned (PJ.ASSIGNMENT_TYPE = 'E'). The documented base objects are:

• PER_ALL_PEOPLE_F (synonym) — the primary person record supplying name, national identifier, sex, date of birth, and attributes.
• PER_ALL_ASSIGNMENTS_F (synonym) — assignment and job context, filtered to employee assignments.
• PER_PERIODS_OF_SERVICE (synonym) — start date, final process date, and adjusted service date.
• PER_ADDRESSES (synonym) — address line 1 and 2, town or city, region, and postal code.
• HR_CERIDIAN_SPOUSE_V (view) — spouse date of birth, outer-joined to the person.
• PAY_ELEMENT_ENTRIES_F, PAY_ELEMENT_ENTRY_VALUES_F, and PAY_INPUT_VALUES_F (synonyms) — element entry and input value data, aliased three times (PV1/PV2/PV3 and PIV1/PIV2/PIV3) to project up to three screen entry values.
• PAY_ELEMENT_TYPES_X and PAY_ELEMENT_LINKS_X (views) — element configuration used to constrain the linked entries.
• HR_ORGANIZATION_UNITS (view) and HR_SOFT_CODING_KEYFLEX (synonym) — organization and soft-coding key flexfield data.
• HR_CERIDIAN, HR_GENERAL, HR_SECURITY, and FND_PROFILE (packages) — security and profile-option logic invoked by the view, notably FND_PROFILE.VALUE('PER_OAB_NEW_BENEFITS_MODEL'), which conditionally derives the smoker flag and adjusted service date.

Key Columns

• EMPLOYEE_NUMBER, LAST_NAME, FIRST_NAME, MIDDLE_NAMES, SUFFIX — core identifying attributes of the person.
• NATIONAL_IDENTIFIER, SEX, DATE_OF_BIRTH — statutory personal data required by the payroll interface.
• SPOUSE_DATE_OF_BIRTH — dependent information from HR_CERIDIAN_SPOUSE_V.
• ADDRESS_LINE1, ADDRESS_LINE2, TOWN_OR_CITY, REGION_2, POSTAL_CODE — mailing address elements.
• DATE_START, FINAL_PROCESS_DATE, ADJUSTED_SERVICE_DATE — service and payroll cut-off dates; the adjusted service date is derived from PPS.ADJUSTED_SVC_DATE or from PP.ATTRIBUTE3 depending on the benefits model profile.
• SCREEN_ENTRY_VALUE (PV1, PV2, PV3) — the generic element entry value slots through which codes such as leave or vacation categories are transmitted.
• SMOKER_FLAG — derived from PP.USES_TOBACCO_FLAG or PP.ATTRIBUTE2.
• BUSINESS_GROUP_ID, PERSON_ID, JOB_ID — surrogate keys supporting downstream reconciliation.
• Five trailing GREATEST(NVL(...)) expressions — computed last-update timestamps used for change detection and incremental extraction.

Common Use Cases and Queries

Typical usage is an incremental extract that feeds Ceridian. A representative query selecting employee identity alongside the generic element value columns is:

• SELECT employee_number, last_name, first_name, screen_entry_value, business_group_id, person_id FROM apps.hr_ceridian_employee_only_v WHERE person_id = :p_person_id;
• SELECT person_id, employee_number, date_start, final_process_date FROM apps.hr_ceridian_employee_only_v WHERE business_group_id = :p_bg_id ORDER BY employee_number;

Where a search for vacation_code is the objective, the correct approach is to join the view's PERSON_ID back to PAY_ELEMENT_ENTRY_VALUES_F and PAY_INPUT_VALUES_F, filtering on the input value name associated with the vacation element, since the view itself exposes no column bearing that name. All queries should be run as the APPS schema or a responsibility with the appropriate HR security profile, because the view invokes HR_SECURITY and therefore enforces row-level access restrictions.