Results for “time_period_name”

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

Overview

HXT_EMP_TIME_INFO_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite Time and Labor (HXT) product family. It is shipped with a VALID status in both Oracle EBS 12.1.1 and 12.2.2 and is documented in the E-Business Suite Technical Reference Manual (ETRM). The view exposes timecard header information joined to the employee's business group and the corresponding time period definition, allowing consumers to resolve a timecard to the person it belongs to and the period over which it accrues.

Because it is a view rather than a table, HXT_EMP_TIME_INFO_V introduces no storage of its own. Its role is to consolidate three disparate entities — timecards, time periods, and people — into a single denormalized row per timecard, which simplifies downstream reporting, integrations, and concurrent program logic that would otherwise require repeated joins. It is a common dependency for Time and Labor extracts, payroll cost distribution reporting, and custom OAF or Forms-based inquiries. Users frequently encounter this object when searching for "per_people," since PER_PEOPLE is one of its primary referenced objects.

Underlying Base Objects

The documented view text defines HXT_EMP_TIME_INFO_V over three principal sources: HXT_TIMECARDS (itself a view), PER_TIME_PERIODS (exposed as a synonym), and PER_PEOPLE (a view). The joins are inner-join style: timecards link to periods on TIME_PERIOD_ID, and to people on FOR_PERSON_ID = PER.PERSON_ID.

The ETRM 12.2.2 metadata further enumerates referenced base objects including the packages HR_GENERAL, HR_PERSON_NAME, HR_PERSON_TYPE_USAGE_INFO, and HR_SECURITY. These packages are surfaced because PER_PEOPLE and HXT_TIMECARDS select through them — HR_SECURITY supplies row-level access control, while HR_PERSON_NAME and HR_PERSON_TYPE_USAGE_INFO drive name formatting and person-type categorization. HR_GENERAL supplies common HR utility logic. Consequently, query results are filtered by the security profile of the querying user, and the effective name displayed derives from the HR name format configuration.

Key Columns

• TIM_ID — Primary identifier of the timecard header from HXT_TIMECARDS. Joins to timecard detail lines.
• FOR_PERSON_ID — The person for whom the timecard is recorded; foreign key to PER_PEOPLE.PERSON_ID.
• TIME_PERIOD_ID — Identifier of the time period the timecard falls within.
• TIME_PERIOD_START_DATE and TIME_PERIOD_END_DATE — The begin and end dates of that period from PER_TIME_PERIODS.
• TIME_PERIOD_NAME and TIME_PERIOD_NUM — The descriptive period name (e.g., a payroll period label) and its numeric sequence.
• BUSINESS_GROUP_ID — The business group of the person, sourced from PER_PEOPLE; essential for multi-organization filtering and security partitioning.

Common Use Cases and Queries

Typical scenarios include reconciling timecard activity to periods, building absence and overtime trend reports, and feeding downstream interfaces that need person and period context. A simple listing by person and period:

• SELECT tim_id, for_person_id, time_period_name, time_period_start_date, time_period_end_date, business_group_id FROM apps.hxt_emp_time_info_v WHERE for_person_id = :p_person_id ORDER BY time_period_start_date;
• SELECT business_group_id, time_period_name, COUNT(*) FROM apps.hxt_emp_time_info_v GROUP BY business_group_id, time_period_name;

Because HR_SECURITY is referenced, queries return only persons within the caller's security profile — a key consideration when designing reports or interfaces. Standard practice is to filter on FOR_PERSON_ID or BUSINESS_GROUP_ID and to join to PER_PEOPLE_VIEW or HXT_TIMECARD_DETAILS for full reporting detail.