Results for “pji_exp_categories_v”

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

Overview

PJI_EXPENDITURE_CATEGORIES_V (commonly referenced through searches for pa_expenditure_categories) is a database view owned by the APPS schema and defined within the PJI – Project Intelligence product module. Oracle's ETRM documentation classifies it explicitly as an "internal summarization view." Its purpose is narrow and deliberate: it exposes the pair of columns that identify and describe expenditure categories so that Project Intelligence reporting and integration logic can reference category values without carrying the full PA_EXPENDITURE_CATEGORIES record. The view is documented with a status of VALID and appears in both the 12.1.1 and 12.2.2 object reference sets, indicating that its definition and stability have been maintained across the two release lines.

Because the view is intended for internal summarization rather than direct end-user reporting, it is typically consumed by PJI dashboards, Oracle Business Intelligence extracts, and dependent views or PL/SQL packages that need a lightweight category dimension. Its existence allows the Project Intelligence layer to decouple its reporting structures from the transactional expenditure category table.

Underlying Base Objects

The view text documented in the ETRM metadata is a single-source SELECT over one base object:

• PA_EXPENDITURE_CATEGORIES — the expenditure category definition table that stores the complete set of expenditure categories used across grants, projects, and costing. The ETRM metadata states the view is derived from this object; no other referenced base objects are documented.

The projection is a one-to-one mapping with no joins, unions, or aggregations. In practice, this makes PJI_EXPENDITURE_CATEGORIES_V a thin, denormalized lens on PA_EXPENDITURE_CATEGORIES, restricted to the identifying and descriptive columns. Because the view text references PA_EXPENDITURE_CATEGORIES directly, any row-level security, category enablement, or organizational classification configured on the base table remains the authoritative source of truth; the view adds no filtering logic of its own.

Key Columns

The ETRM metadata documents two exposed columns:

• EXPENDITURE_CATEGORY_ID — the surrogate key of the expenditure category. This is the primary identifier carried through project transactions, budgets, and cost distributions, and it is the column most commonly used to join the view to fact-level PJI objects.
• EXPENDITURE_CATEGORY — the user-facing category name. This is the descriptive label that appears on expenditure category definition forms and in project reporting, and it is the value typically displayed in summaries or used as a grouping label.

No additional columns, aliases, or calculated fields are documented in the ETRM metadata. Consumers requiring attributes such as the category's expenditure type class, cost book assignments, or start and end dates must join back to PA_EXPENDITURE_CATEGORIES, since those attributes are not surfaced by this view.

Common Use Cases and Queries

The view is most often used where a concise ID-to-name lookup for expenditure categories is required within a PJI reporting query, rather than for exhaustive category maintenance reporting. Typical scenarios include joining category names to project expenditure facts, building parameter lists for concurrent requests, and populating LOV-style structures in project intelligence extracts. A representative query is:

• SELECT expenditure_category_id, expenditure_category FROM pji_exp_categories_v ORDER BY expenditure_category;
• SELECT v.expenditure_category FROM pji_exp_categories_v v WHERE v.expenditure_category_id = :category_id;

When further detail is needed — for example, the associated expenditure type class or the category's effective dates — the view should be joined to its base table on EXPENDITURE_CATEGORY_ID. Given its designation as an internal summarization view, direct custom development against it should be treated cautiously, and any dependency should be validated against the base PA_EXPENDITURE_CATEGORIES table during upgrade testing between 12.1.1 and 12.2.2.