Results for “hxt_tasks_v”

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

Overview

HXT_TASKS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the HXT (Time and Labor) product family. It exposes a curated subset of project task attributes sourced from the Oracle Projects task layer, providing Time and Labor consumers with a stable, denormalized interface to task and project identifiers without requiring direct access to the underlying Projects tables. The view is documented as VALID in both EBS 12.1.1 and 12.2.2 and appears in ETRM under "View: HXT_TASKS_V."

The view matters because Time and Labor frequently needs to associate reported time entries with project tasks for costing, billing, and approval routing. Rather than querying Projects tables directly, HXT code and extensions reference this view, which insulates them from changes in the Projects data model.

Underlying Base Objects

The documented ETRM metadata restricts the reference base to a single view: PA_ONLINE_TASKS_V. The view text is effectively a pass-through projection:

SELECT TASK.TASK_ID, TASK.PROJECT_ID, TASK.TASK_NAME, TASK.TASK_NUMBER, TASK.START_DATE, TASK.COMPLETION_DATE FROM PA_ONLINE_TASKS_V TASK

PA_ONLINE_TASKS_V is the Online Tasks view in Oracle Projects, itself built over PA_TASKS and related Projects structures. The ETRM 12.2.2 metadata also lists FND_PROFILE (PACKAGE) and PA_TASK_UTILS (PACKAGE) as referenced base objects, confirming that HXT_TASKS_V participates in security and utility logic that governs which tasks are visible to a given user, based on profile options and Projects task utilities.

Key Columns

• TASK_ID — Unique identifier for the project task; primary correlation key used in Time and Labor.
• PROJECT_ID — Identifier of the owning project; links the task to project-level attributes.
• TASK_NAME — User-facing name of the task.
• TASK_NUMBER — Short task number, typically used in reporting and reference displays.
• START_DATE — Effective start date of the task.
• COMPLETION_DATE — Date the task was completed, if applicable.

Common Use Cases and Queries

Typical scenarios include LOV validations, task-based reporting, and integration payloads for time entry. A basic listing:

SELECT task_id, project_id, task_name, task_number, start_date, completion_date FROM apps.hxt_tasks_v WHERE project_id = :p_project_id;

Restricting to active tasks by date uses the date columns:

SELECT task_id, task_name FROM apps.hxt_tasks_v WHERE project_id = :p_project_id AND start_date <= SYSDATE AND (completion_date IS NULL OR completion_date >= SYSDATE);

Joining to time entry or project tables keyed on TASK_ID or PROJECT_ID supports costing and reconciliation reporting. Because access to tasks is governed by FND_PROFILE and PA_TASK_UTILS, query results reflect the requesting user's Projects security context, which should be considered when designing reports and integrations.