Results for “hr_adp_gtl_v”

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

Overview

HR_ADP_GTL_V is a VALID view owned by the APPS schema within the PER (Human Resources) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to serve as an ADP payroll interface view, exposing a denormalized, ready-for-extract representation of payroll element entries and their associated input values. The view consolidates employee, assignment, element link, input value, and organization data into a single query surface that ADP-facing processes or third-party payroll integrations can consume directly without reimplementing the underlying join logic and hot-default resolution rules.

The name "GTL" reflects its role as a Global Template Layer style extract — a flattened projection intended for downstream transmission rather than interactive maintenance. Critically, the view encapsulates the hot_default_flag input value behavior: rather than returning raw screen entry values, it computes effective values by calling HR_PAY_INTERFACE_PKG.GET_HOT_DEFAULT when a value is null and the hot default flag permits it. This makes the view the authoritative resolution point for hot-default logic within the ADP interface.

Underlying Base Objects

The documented base objects underpinning HR_ADP_GTL_V span payroll configuration, employee/assignment data, and security:

• PER_ALL_PEOPLE_F and PER_ALL_ASSIGNMENTS_F — person and assignment facts supplying employee number, person ID, business group, assignment ID and number.
• PAY_ELEMENT_ENTRIES_F, PAY_ELEMENT_ENTRY_VALUES_F — element entry and entry value facts forming the core payroll data.
• PAY_ELEMENT_LINKS_F, PAY_ELEMENT_TYPES_F, PAY_INPUT_VALUES_F — element link, element type, and input value definitions defining the entry structure and hot-default flags.
• PER_TIME_PERIOD_TYPES — supplying NUMBER_PER_FISCAL_YEAR for period-frequency decoding (W/S/B/M).
• HR_ALL_ORGANIZATION_UNITS and HR_SOFT_CODING_KEYFLEX — organization name and segment1 attributes.
• HR_ADP_EMP_REF_V and HR_ADP — ADP-specific employee reference view and package.
• HR_PAY_INTERFACE_PKG — providing GET_HOT_DEFAULT, and HR_GENERAL / HR_SECURITY for supporting and security logic.

Key Columns

• COMPANY_CODE_EQUIVALENT — company identifier sourced from the ADP employee reference.
• EMPLOYEE_NUMBER, PERSON_ID, BUSINESS_GROUP_ID — person-level identification.
• ASSIGNMENT_ID, ASSIGNMENT_NUMBER, PRIMARY_FLAG — assignment context; PRIMARY_FLAG is decoded so primary assignments yield sequence 0.
• SCREEN_ENTRY_VALUE columns (up to four) — resolved element input values, computed via DECODE on HOT_DEFAULT_FLAG and HR_PAY_INTERFACE_PKG.GET_HOT_DEFAULT.
• NUMBER_PER_FISCAL_YEAR / frequency decode — mapped to 'W', 'S', 'B', or 'M' based on period type.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE (min/max) — element link date bounds.
• LAST_UPDATE-derived GREATEST expressions — audit/currency markers for person, assignment, and element link rows.

Common Use Cases and Queries

The view is typically queried for ADP payroll extracts, hot-default audits, and reconciliation of entry values against element link definitions.

SELECT employee_number,
       assignment_number,
       primary_flag,
       effective_start_date,
       effective_end_date
  FROM apps.hr_adp_gtl_v
 WHERE business_group_id = :p_bg_id
   AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;

To audit hot-default resolution for a specific person:

SELECT employee_number, assignment_number, primary_flag
  FROM apps.hr_adp_gtl_v
 WHERE person_id = :p_person_id;

Because access is mediated by HR_SECURITY, results honor the querying user's security profile. Reporting layers should apply effective-date predicates, as the view carries date-ranged rows.