Results for “recorded_hours”

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

Overview

HXC_PUBLIC_TEMPLATE_LIST_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, belonging to the HXC (Time and Labor Engine) product family. Its purpose is to expose a consolidated, human-readable listing of public timecard templates defined in the Time and Labor Engine, together with descriptive attributes, the assigned recurring period, the number of recorded hours, and the identities of the users who created and last updated each template.

The view joins template summary data to layout translations, recurring period definitions, and two independent lookups into the people table to resolve creator and updater names. Because it filters on TEMPLATE_TYPE = 'PUBLIC', only templates available for general use are returned; private or user-owned templates are excluded. This makes the view a convenient reporting and integration surface for administrators and downstream processes that need a stable list of shared templates without having to reconstruct the multi-table join themselves.

The view also enforces referential and referential-date constraints implicitly: it restricts the join to people records whose effective date range brackets the current system date, ensuring that only currently valid person rows contribute creator and updater names.

Underlying Base Objects

The view is defined over four documented base objects, accessed through synonyms in the APPS schema:

• HXC_TEMPLATE_SUMMARY — the driving table, supplying template identity, type, business group, recorded hours, recurring period reference, layout reference, start/stop times, and the resource IDs for the creator and last updater.
• HXC_LAYOUTS_TL — the translated layouts table, supplying the display layout name. The join is restricted by LANGUAGE = USERENV('LANG') so that the layout name is returned in the session's current language.
• HXC_RECURRING_PERIODS — supplies the recurring period name associated with each template.
• PER_ALL_PEOPLE_F — joined twice, once against the resource identifier of the creator and once against the last-updated resource identifier, to resolve full names. Both joins include effective-date predicates against SYSDATE.

The join conditions are driven by RECURRING_PERIOD_ID, LAYOUT_ID, RESOURCE_ID, and LAST_UPDATED_BY_RESOURCE_ID, with the public-template filter applied on the summary table.

Key Columns

• TEMPLATE_ID — primary identifier of the timecard template; the principal join key for downstream queries.
• TEMPLATE_NAME and DESCRIPTION — the template's user-facing label and descriptive text.
• DISPLAY_LAYOUT_NAME — the translated layout name assigned to the template.
• RECURRING_PERIOD_NAME — the recurring period definition governing the template's schedule.
• RECORDED_HOURS — the total recorded hours associated with the template, the attribute most commonly sought when users search for this view.
• CREATED_BY_NAME and LAST_UPDATE_BY_NAME — full names of the creating and most recent updating persons.
• BUSINESS_GROUP_ID — the business group context for the template.
• START_TIME and STOP_TIME — the operational window bounds for the template.

Common Use Cases and Queries

The view is typically used to list available public templates, verify ownership and layout assignment, and aggregate or filter on recorded hours. A representative query follows:

• SELECT template_id, template_name, recorded_hours, recurring_period_name FROM hxc_public_template_list_v ORDER BY template_name; — a baseline listing of public templates and their recorded hours.
• SELECT template_id, template_name, display_layout_name, last_update_by_name FROM hxc_public_template_list_v WHERE business_group_id = :p_bg_id; — restricted reporting for a specific business group.
• SELECT SUM(recorded_hours) FROM hxc_public_template_list_v WHERE start_time >= :p_from AND stop_time <= :p_to; — aggregation across a time window for analysis.

Because the view resolves person names and translated layout names at query time, it is well suited to read-only reporting and lightweight integration, while remaining subject to the effective-date and language predicates embedded in its definition.