Results for “hxt_projects_v”

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

Overview

HXT_PROJECTS_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. The view presents a filtered, security-aware projection of project information sourced from the underlying PA (Projects) application, exposing project identity attributes such as project identifier, name, number, owning organization, and lifecycle dates. In Oracle EBS 12.1.1 and 12.2.2, HXT_PROJECTS_V serves as the sanctioned interface through which Time and Labor components, concurrent programs, and custom extensions retrieve the list of projects that may be referenced by timecard entry, project-related validation, or downstream reporting. Because it is a view rather than a table, it inherits the business group and security enforcement logic defined in the Projects schemas, while retaining a stable, simplified column set for consumers within the HXT module.

Underlying Base Objects

The documented view text defines HXT_PROJECTS_V as a straightforward selection over PA_ONLINE_PROJECTS_V, an existing Projects view used for online validation of project values:

• PA_ONLINE_PROJECTS_V (VIEW) — The sole source of the projected columns; HXT_PROJECTS_V selects PROJECT_ID, PROJECT_NAME, PROJECT_NUMBER, CARRYING_OUT_ORGANIZATION_ID, START_DATE, and COMPLETION_DATE from it without additional joins or filters in the view text.
• PA_PROJECT_UTILS (PACKAGE) — Referenced by the view's dependency chain; supplies project-related utility logic used within the Projects validation stack.
• PA_CROSS_BUSINESS_GRP (PACKAGE) and HR_SECURITY (PACKAGE) — Provide the business group and security profile enforcement that determines which projects are visible to the querying responsibility or user.
• HR_GENERAL (PACKAGE) — Supplements user and session context retrieval used throughout the HR/Projects security model.
• FND_PROFILE (PACKAGE) — Resolves profile option values, including MO (Operating Unit) and security-related settings, that influence filtered visibility.

In practice, the view therefore inherits the full dependency stack of PA_ONLINE_PROJECTS_V rather than introducing new base tables of its own.

Key Columns

• PROJECT_ID — The unique numeric identifier of the project; this is the primary key value used in foreign-key references from time and labor transaction tables.
• PROJECT_NAME — The user-facing project name displayed in list of values and reports.
• PROJECT_NUMBER — The alphanumeric project number, typically used for cross-referencing with external systems or user-entered searches.
• CARRYING_OUT_ORGANIZATION_ID — The organization responsible for executing the project; used in organization-aware filtering and reporting.
• START_DATE — The date on which the project begins, relevant for date-based validation of timecard entries.
• COMPLETION_DATE — The date on which the project is expected or actual to complete, used to constrain chargeable periods.

Common Use Cases and Queries

HXT_PROJECTS_V is typically queried to populate project list-of-values, to validate that a submitted timecard references an active project, and to drive extracts of project master data for reporting in Time and Labor. A basic retrieval of all visible projects follows:

• SELECT project_id, project_number, project_name, carrying_out_organization_id, start_date, completion_date FROM hxt_projects_v ORDER BY project_name;
• SELECT project_id, project_number, project_name FROM hxt_projects_v WHERE project_number = :p_number;
• SELECT p.project_id, p.project_name, p.start_date, p.completion_date FROM hxt_projects_v p WHERE TRUNC(SYSDATE) BETWEEN p.start_date AND NVL(p.completion_date, TRUNC(SYSDATE));

Because visibility is governed by HR security and profile settings through the underlying packages, results returned to a given user or responsibility may differ from those of another. Development and integration efforts should therefore treat the view as the authoritative, security-consistent entry point for project data within HXT rather than querying PA base tables directly.