Results for “pji_exp_types_v”

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

Overview

PJI_EXP_TYPES_V is a database view historically shipped within the Oracle E-Business Suite Project Intelligence (PJI) product family. In Oracle EBS 12.1.1 and 12.2.2, PJI is classified as an obsolete module, meaning the product is no longer actively developed, though legacy objects may still persist in upgraded environments where the schema was never cleansed. The view is documented as an internal summarization view, a designation that distinguishes it from end-user-facing reporting objects. Its purpose is to present a concise, denormalized projection of expenditure type data by joining expenditure types to their parent expenditure categories. This allows dependent code or legacy reports to resolve the category context of an expenditure type without issuing a separate lookup against the category table.

Because the object is described as internal, it was never intended as a supported public interface. Its presence in the data dictionary is largely a byproduct of PJI's internal processing logic. Users searching on the identifier expenditure_type_id will encounter this view when tracing where that key is exposed across the EBS schema.

Underlying Base Objects

The view text, as documented in the ETRM metadata, reveals its dependency on two base tables in the Oracle Projects (PA) schema:

• PA_EXPENDITURE_TYPES (alias PET) — the master table defining expenditure types, keyed by EXPENDITURE_TYPE_ID.
• PA_EXPENDITURE_CATEGORIES (alias PEC) — the reference table defining expenditure categories.

The two tables are joined on the EXPENDITURE_CATEGORY column, which is the shared category identifier carried on each expenditure type row. Notably, the ETRM metadata states the view is "Not implemented in this database" and lists no documented referenced base objects at the metadata layer, indicating it may be absent from many 12.2.2 instances. Where it does exist, it is a simple two-table equijoin with no aggregation, filters, or outer joins.

Key Columns

• EXPENDITURE_TYPE_ID — the primary key of PA_EXPENDITURE_TYPES, uniquely identifying each expenditure type. This is the column users most commonly search for, as it is the foreign key referenced throughout Oracle Projects transactions.
• EXPENDITURE_TYPE — the descriptive name of the expenditure type, carried from PA_EXPENDITURE_TYPES.
• EXPENDITURE_CATEGORY_ID — the category identifier sourced from PA_EXPENDITURE_CATEGORIES, providing the denormalized category context.
• EXPENDITURE_CATEGORY — the join key present in both base tables, used to link types to their categories.

Common Use Cases and Queries

The principal use case is resolving an expenditure_type_id to its human-readable name and category in a single lookup. Because the underlying tables are the authoritative source, equivalent queries can be written directly against them if the view is not implemented.

Example query against the view:

• SELECT expenditure_type_id, expenditure_type, expenditure_category_id FROM pji_exp_types_v WHERE expenditure_type_id = :p_id;

If the view is absent, the same result is obtained directly:

• SELECT pet.expenditure_type_id, pet.expenditure_type, pec.expenditure_category_id FROM pa_expenditure_types pet, pa_expenditure_categories pec WHERE pet.expenditure_category = pec.expenditure_category AND pet.expenditure_type_id = :p_id;

Given its obsolete status and the documented note that it is not implemented in the database, developers should treat PJI_EXP_TYPES_V as non-authoritative and prefer PA_EXPENDITURE_TYPES joined to PA_EXPENDITURE_CATEGORIES for all new reporting and integration work.