Results for “pa_expenditure_types_res_v”

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

Overview

PA_EXPENDITURE_TYPES_RES_V is an Oracle Projects (PA) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes a filtered, effective-dated list of expenditure types that are valid for resource-related processing. The view presents the expenditure type name, description, expenditure category, revenue category, unit of measure, a labor-tracking indicator, and a rollup quantity flag, and is intended to answer the question "which expenditure types may currently be selected as resources?" The ETRM documentation classifies the object as a view with status VALID and notes the description "10Sc Only," indicating it was originally introduced to support specific resource and cost functionality rather than as a general-purpose catalog.

Because the view joins expenditure types to system linkage information and applies an active-date filter through a PL/SQL function, it behaves differently from a plain query on PA_EXPENDITURE_TYPES. Consumers receive only currently active rows (or all rows when inactive resources are explicitly included), which makes it suitable for list-of-values and integration lookups where inactive expenditure types must not be presented. It is a read-only interface; no data manipulation is performed through the view.

Underlying Base Objects

The view text is defined over two synonyms and one package:

• PA_EXPENDITURE_TYPES (synonym to the APPS base table) — supplies EXPENDITURE_TYPE, DESCRIPTION, EXPENDITURE_CATEGORY, REVENUE_CATEGORY_CODE, UNIT_OF_MEASURE, START_DATE_ACTIVE, and END_DATE_ACTIVE.
• PA_EXPEND_TYP_SYS_LINKS (synonym) — outer-joined on EXPENDITURE_TYPE and SYSTEM_LINKAGE_FUNCTION = 'ST' to derive the TRACK_AS_LABOR_FLAG.
• PA_GET_RESOURCE (package) — referenced through the public variable INCLUDE_INACTIVE_RESOURCES, which drives the effective-date predicate.

The join to PA_EXPEND_TYP_SYS_LINKS is an outer join (denoted by the (+) operator), so expenditure types lacking a 'ST' system linkage are still returned, with the labor flag resolving to 'N' via DECODE. The date predicate compares either EXPENDITURE_TYPES.START_DATE_ACTIVE (when PA_GET_RESOURCE.INCLUDE_INACTIVE_RESOURCES = 'Y') or TRUNC(SYSDATE) against the range START_DATE_ACTIVE to NVL(END_DATE_ACTIVE, TRUNC(SYSDATE)). This means a row is excluded once its end date has passed, unless the session variable opts into inactive rows.

Key Columns

• EXPENDITURE_TYPE — the expenditure type identifier/name; the principal lookup key.
• DESCRIPTION — descriptive text for the expenditure type.
• EXPENDITURE_CATEGORY — the cost category used in costing and reporting, such as labor or expense groupings.
• REVENUE_CATEGORY_CODE — the revenue category used to derive revenue amounts for the type.
• TRACK_AS_LABOR_FLAG — 'Y' or 'N', derived by DECODE from the presence of an 'ST' row in PA_EXPEND_TYP_SYS_LINKS; 'Y' indicates the type participates in labor tracking.
• UNIT_OF_MEASURE — the unit associated with quantity-bearing expenditure types.
• ROLLUP_QUANTITY_FLAG — a constant 'Y' in the view text, indicating quantities are eligible for rollup.

Common Use Cases and Queries

Typical scenarios include populating expenditure type list-of-values in resource-oriented screens, validating imported expenditure types before they are posted, and building reporting joins to expenditure or cost distributions. A basic query returning all active resource-eligible types is:

• SELECT expenditure_type, description, expenditure_category FROM pa_expenditure_types_res_v;
• SELECT expenditure_type, track_as_labor_flag FROM pa_expenditure_types_res_v WHERE track_as_labor_flag = 'Y';
• SELECT r.expenditure_type, r.description, r.revenue_category_code FROM pa_expenditure_types_res_v r WHERE r.expenditure_category = 'LABOR';

Note that filtering results depends on the current value of PA_GET_RESOURCE.INCLUDE_INACTIVE_RESOURCES; callers requiring inactive rows must set that variable before querying. Because the view is a Projects-owned object, reporting queries should reference the APPS synonym and be used read-only.