Results for “project_currency_code”

50+ results




Overview
Explore in AI Chat

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

Overview

GMS_PQH_PROJECTS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the GMS – Grants Accounting product family. Its name associates it with the Project Quick Header (PQH) presentation layer, and its role is to expose a narrow, denormalized projection of project header data for grants-related inquiry, reporting, and integration consumers. Rather than returning the full set of project attributes maintained in the Projects foundation tables, the view restricts output to four columns: PROJECT_NUMBER, PROJECT_NAME, PROJECT_ID, and PROJECT_CURRENCY_CODE.

In EBS 12.1.1 and 12.2.2 the object retains VALID status and remains an APPS-owned, read-only construct. Because it is a view rather than a table, it carries no storage of its own and inherits its access and row-level behavior from the underlying definitions. This makes it appropriate for lightweight lookups and for join paths where only project identity and currency context are required, while avoiding the performance cost of querying the full project header structures.

Underlying Base Objects

The ETRM definition shows the view text as a direct projection over GMS_PROJECTS_V:

  • GMS_PROJECTS_V (VIEW) — the immediate parent object supplying all four exposed columns. GMS_PQH_PROJECTS_V performs no joins, filters, or expressions of its own; it is a column-subset wrapper. The documented base objects of the parent view are FND_PROFILE (PACKAGE), PA_CROSS_BUSINESS_GRP (PACKAGE), and PA_PROJECT_UTILS (PACKAGE).
  • FND_PROFILE (PACKAGE) — supplies profile-option values, most notably the operating unit and business group context that governs which projects are visible.
  • PA_CROSS_BUSINESS_GRP (PACKAGE) — provides cross-business-group security logic, determining project visibility across organizations.
  • PA_PROJECT_UTILS (PACKAGE) — contributes Projects-related utility logic, including currency and structural derivations used by the parent view.

Consequently, querying GMS_PQH_PROJECTS_V indirectly invokes Projects security and profile resolution. Access is therefore subject to the same MO: Operating Unit and business group constraints applied to the parent view, and results should be interpreted accordingly.

Key Columns

  • PROJECT_ID — the surrogate primary key of the project. This is the column to use for joins to PA_PROJECTS_ALL, PA_TASKS, PA_EXPENDITURES, grants award tables, and other Projects objects.
  • PROJECT_NUMBER — the user-visible project number, typically the value users enter when searching for a project in the Grants Accounting forms and reports.
  • PROJECT_NAME — the descriptive project name, suitable for list-of-values displays and report headings.
  • PROJECT_CURRENCY_CODE — the project's currency, as returned by the parent view's currency derivation. This is the column matched by the search term the user supplied. In Grants Accounting it identifies the currency in which project budgets, costs, and award amounts are denominated, and is essential for any multi-currency reporting or reconciliation.

Common Use Cases and Queries

The view is most often used as a compact project reference for grants reporting, extracts, and interface validation. A typical inquiry retrieves project identifiers and their currency:

  • Selecting projects by number or name for an LOV-style display.
  • Joining PROJECT_ID to transactional tables to enrich expenditure or budget extracts with PROJECT_NUMBER, PROJECT_NAME, and PROJECT_CURRENCY_CODE.
  • Filtering projects by PROJECT_CURRENCY_CODE to isolate awards or projects denominated in a specific currency for financial reporting.

Sample SQL:

  • SELECT project_id, project_number, project_name, project_currency_code FROM apps.gms_pqh_projects_v WHERE project_currency_code = 'USD';
  • SELECT p.project_number, p.project_name, p.project_currency_code FROM apps.gms_pqh_projects_v p, apps.pa_tasks t WHERE p.project_id = t.project_id AND t.task_number = :task_number;

Because the view is defined over a secured parent and profile-driven packages, results reflect the operating unit context of the session. Integrations should therefore set the correct MO: Operating Unit before querying, and should not assume the view returns projects across all business groups.