Search Results hxt_all_projects_v




Overview
Explore in AI Chat

Overview

HXT_ALL_PROJECTS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the HXT (Time and Labor) product family. In EBS 12.1.1 and 12.2.2, the view is documented as VALID and is exposed as a simple projection over Oracle Projects project master data. Its purpose is to provide the Time and Labor module with a stable, denormalized list of projects that can be referenced by time-entry validation, preference configuration, and reporting logic without requiring HXT code to join directly to the full PA_PROJECTS_ALL structure.

The view presents one row per project defined in Oracle Projects, carrying the project identifier, descriptive attributes, owning organization, and project lifecycle dates. Because it is a thin selection layer rather than a transformation or aggregation, it inherits the row cardinality, security behavior, and multi-organization characteristics of its base object. Applications and reports that need the set of projects available for timecard entry commonly resolve them through this view rather than through the base table, keeping HXT-dependent SQL insulated from column-level changes in PA_PROJECTS_ALL.

Underlying Base Objects

The documented definition of HXT_ALL_PROJECTS_V references a single base object: PA_PROJECTS_ALL, accessed through the APPS schema synonym. The view text is a straightforward SELECT that projects six columns from that table, with no joins, unions, filters, or aggregations applied. Consequently, the view returns all projects present in PA_PROJECTS_ALL, including projects across all operating units and organizations represented in that table.

PA_PROJECTS_ALL is the Oracle Projects implementation of the _ALL table pattern, meaning it stores project definitions across multiple organizations without an operating unit column restriction at the table level. Filters based on organization or business group are typically applied by the caller or by the Oracle Projects security model rather than by this view. Because the view is defined over an APPS synonym, the base table must be accessible in the APPS schema for the view to compile and remain VALID, which the ETRM metadata confirms for 12.2.2.

Key Columns

  • PROJECT_ID — The unique primary key of the project. This is the value time-entry and preference records store as the project reference, and the column most frequently used in joins to other HXT and PA tables.
  • PROJECT_NAME — The descriptive project name, sourced from PPA.NAME. Used for user-facing display and lookup lists.
  • PROJECT_NUMBER — The user-assigned project number, sourced from PPA.SEGMENT1. This is the primary searchable business identifier for the project.
  • CARRYING_OUT_ORGANIZATION_ID — The organization responsible for carrying out the project, used in organizational filtering and reporting by owning entity.
  • START_DATE — The project start date, used to determine whether a project is active during a given timecard period.
  • COMPLETION_DATE — The project completion date, used to exclude closed or completed projects from active selection lists.

Common Use Cases and Queries

Typical usage includes populating project selection lists, validating that a timecard line references an active project, and driving Time and Labor preference or rule configuration. A basic lookup by project number is shown below.

SELECT project_id, project_name, project_number, start_date, completion_date FROM hxt_all_projects_v WHERE project_number = :project_number;

To retrieve only projects active on a given date, callers apply a date predicate, since the view itself imposes none:

SELECT project_id, project_name, project_number FROM hxt_all_projects_v WHERE start_date <= :as_of_date AND (completion_date IS NULL OR completion_date >= :as_of_date) ORDER BY project_number;

For joins, PROJECT_ID is the natural key, for example linking the view to timecard project references to resolve the project number and name for a time entry, or to CARrying_out_organization_id for organization-level reporting. Because the view carries all rows from PA_PROJECTS_ALL, consumers that require a restricted set should always include explicit date, organization, or project-status criteria in the calling SQL.

As a documented, VALID view in both 12.1.1 and 12.2.2, HXT_ALL_PROJECTS_V should be treated as a supported read-only interface. It exposes no columns beyond those listed in the ETRM metadata, and any extension beyond project identification, naming, ownership, and lifecycle dating must be obtained from the base Oracle Projects tables.