Results for “expenditure_category_id”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
PA_EXPEND_CATEGORIES_RES_V is an Oracle E-Business Suite view owned by the APPS schema in the Projects (PA) product family. Its name follows Oracle's resource-view naming convention: RES_V denotes a resource view used by the Oracle Projects resource list mechanism, the same framework that drives the expenditure type, expenditure category, and organization LOVs throughout the Projects application. The documented description states "10Sc Only," indicating the view is scoped to a single responsibility context rather than exposed as a general-purpose reporting entity. It is catalogued as VALID and is available in both EBS 12.1.1 and 12.2.2.
Functionally, the view presents expenditure categories filtered and flagged according to whether they are treated as labor. It splits the result set into two logical groups and unions them together, producing a normalized list suitable for LOV and resource-selection processing.
Underlying Base Objects
The ETRM metadata documents the following referenced objects:
- PA_EXPENDITURE_CATEGORIES (SYNONYM) — the primary source of
EXPENDITURE_CATEGORY_ID,EXPENDITURE_CATEGORY,DESCRIPTION, and the active date range columnsSTART_DATE_ACTIVEandEND_DATE_ACTIVE. - PA_EXPENDITURE_TYPES_RES_V (VIEW) — used in correlated EXISTS / NOT EXISTS subqueries to determine whether any expenditure type linked to the category carries
TRACK_AS_LABOR_FLAG = 'Y'. - PA_GET_RESOURCE (PACKAGE) — supplies
PA_GET_RESOURCE.INCLUDE_INACTIVE_RESOURCES, which governs date filtering behavior.
The date predicate applies a DECODE that returns START_DATE_ACTIVE when inactive resources are included, otherwise TRUNC(SYSDATE), and tests it against the range from START_DATE_ACTIVE to NVL(END_DATE_ACTIVE, TRUNC(SYSDATE)). This ensures only currently effective categories are returned unless the session is configured to include inactive ones.
Key Columns
- EXPENDITURE_CATEGORY_ID — surrogate key from
PA_EXPENDITURE_CATEGORIES; used as the resource identifier. - EXPENDITURE_CATEGORY — the category name visible in LOVs.
- DESCRIPTION — descriptive text for the category.
- TRACK_AS_LABOR_FLAG — derived flag; hard-coded 'N' in the first branch (no labor-tracking expenditure type) and 'Y' in the second.
- UNIT_OF_MEASURE — NULL in the non-labor branch, 'HOURS' in the labor branch.
- ROLLUP_QUANTITY_FLAG — hard-coded 'N' for non-labor, 'Y' for labor.
Common Use Cases and Queries
This view is typically consumed indirectly by resource LOVs, but can be queried directly for diagnostics and reporting on labor versus non-labor expenditure categories.
- List all labor categories:
SELECT EXPENDITURE_CATEGORY FROM PA_EXPEND_CATEGORIES_RES_V WHERE TRACK_AS_LABOR_FLAG = 'Y'; - Find non-labor categories with their descriptions:
SELECT EXPENDITURE_CATEGORY_ID, EXPENDITURE_CATEGORY, DESCRIPTION FROM PA_EXPEND_CATEGORIES_RES_V WHERE TRACK_AS_LABOR_FLAG = 'N'; - Validate LOV contents by joining to
PA_EXPENDITURE_CATEGORIESonEXPENDITURE_CATEGORY_ID.
Because the "10Sc Only" designation limits its exposure, direct use for custom reporting should be validated against the specific responsibility context in which the resource list is invoked.
-
10Sc Only
APPS.PA_EXPEND_CATEGORIES_RES_V·↳ PA_EXPENDITURE_CATEGORIES·↳ PA_EXPENDITURE_TYPES_RES_V·↳ PA_GET_RESOURCE·Explore PA module →
-
10Sc Only
APPS.PA_EXPEND_CATEGORIES_RES_V·↳ PA_EXPENDITURE_CATEGORIES·↳ PA_EXPENDITURE_TYPES_RES_V·↳ PA_GET_RESOURCE·Explore PA module →
-
This table stores the RBS element information and the parent-child relationship.
-
Implementation-defined groupings of expenditure types by type of cost
-
Implementation-defined groupings of expenditure types by type of cost
-
This table stores the resource attribute combinations which are used for resource breakdown structure mapping
-
This table stores the resource attribute combinations which are used for resource breakdown structure mapping
-
This table stores the RBS element information and the parent-child relationship.
-
This intermediate table is used for the first aggregation of PJP data by periods.
-
This intermediate table is used for the first aggregation of PJP data by periods.
-
VIEW: PA.PA_RBS_ELEMENTS# 12.2.2
-
View: PJI_EXP_TYPES_V 12.2.2
This is an internal summarization view.
Not implemented in this database·Explore PJI module →
-
VIEW: PJI.PJI_FM_AGGR_FIN6# 12.2.2
-
View: PJI_EXP_CATEGORIES_V 12.2.2
This is an internal summarization view.
Not implemented in this database·Explore PJI module →
-
VIEW: PA.PA_RBS_ELEMENTS# 12.2.2
-
VIEW: APPS.PJI_EXP_TYPES_V 12.1.1
-
View: PJI_EXP_CATEGORIES_V 12.1.1
This is an internal summarization view.
APPS.PJI_EXP_CATEGORIES_V·↳ PA_EXPENDITURE_CATEGORIES·Explore PJI module →
-
View: PJI_EXP_TYPES_V 12.1.1
This is an internal summarization view.
APPS.PJI_EXP_TYPES_V·↳ PA_EXPENDITURE_CATEGORIES·↳ PA_EXPENDITURE_TYPES·Explore PJI module →
-
TABLE: PA.PA_RBS_MAP_TMP3 12.1.1
-
TABLE: PA.PA_RBS_MAP_TMP9 12.1.1
-
TABLE: PA.PA_RBS_MAP_TMP12 12.1.1
-
TABLE: PA.PA_RBS_MAP_TMP10 12.2.2
-
TABLE: PA.PA_RBS_MAP_TMP11 12.1.1
-
TABLE: PA.PA_RBS_MAP_TMP4 12.1.1
-
TABLE: PA.PA_RBS_MAP_TMP13 12.1.1
-
TABLE: PA.PA_RBS_MAP_TMP6 12.1.1
-
TABLE: PA.PA_RBS_MAP_TMP8 12.2.2
-
TABLE: PA.PA_RBS_MAP_TMP9 12.2.2
-
TABLE: PA.PA_RBS_MAP_TMP2 12.2.2
-
TABLE: PA.PA_RBS_MAP_TMP2 12.1.1
-
TABLE: PA.PA_RBS_MAP_TMP3 12.2.2
-
TABLE: PA.PA_RBS_MAP_TMP1 12.2.2
-
TABLE: PA.PA_RBS_MAP_TMP5 12.2.2
-
TABLE: PA.PA_RBS_MAP_TMP13 12.2.2
-
TABLE: PA.PA_RBS_MAP_TMP7 12.2.2