Results for “cst_proj_exp_types_val_v”

46 results




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

Overview

CST_PROJ_EXP_TYPES_VAL_V is an APPS-owned database view in Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It is catalogued under the BOM (Bills of Material) product family but functionally serves the Cost Management and Projects integration space. The view exposes expenditure types that are associated with cost elements through system linkage definitions, providing a consolidated, validated list of expenditure types that are eligible for system-generated cost transactions.

The view is the standard reference used to resolve an expenditure type into its governing cost element and to confirm whether that expenditure type is actively linked to a source system such as Inventory, Work in Process, Buy-to-Collect, or Standard costing. It is a read-only validation view rather than a transactional object, and it is commonly consumed by costing, manufacturing, and project costing reports, concurrent programs, and integration extracts.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through APPS synonyms:

  • PA_EXPENDITURE_TYPES — the master repository of expenditure types, supplying the type name, description, unit of measure, and the effective start and end dates of the expenditure type itself.
  • PA_EXPEND_TYP_SYS_LINKS — the linkage table that maps expenditure types to system linkage functions and to cost elements, supplying the system linkage function and the effective dates of the linkage.

The two tables are joined on EXPENDITURE_TYPE. The view body is a UNION of two SELECT statements that filter PA_EXPEND_TYP_SYS_LINKS on SYSTEM_LINKAGE_FUNCTION values of INV, WIP, BTC, and ST. A DECODE converts the system linkage function into a numeric COST_ELEMENT_ID: INV maps to 1, BTC to 2, WIP to 4, and ST to 5, with a default of 3 for unmatched rows. The second branch of the UNION captures WIP and BTC linkages that produce the higher cost element identifiers. This structure explains the user search term pa_expend_typ_sys_links, since that table is the primary driver of the view's content.

Key Columns

  • EXPENDITURE_TYPE — the expenditure type name, used as the join key across both base tables.
  • EXPENDITURE_TYPE_ID — the surrogate primary key of the expenditure type in PA_EXPENDITURE_TYPES.
  • DESCRIPTION — the descriptive text of the expenditure type.
  • COST_ELEMENT_ID — a derived numeric identifier produced by the DECODE on SYSTEM_LINKAGE_FUNCTION, indicating the cost element associated with the linkage.
  • SYS_LINK_START_DATE / SYS_LINK_END_DATE — the effective date range of the system linkage record in PA_EXPEND_TYP_SYS_LINKS.
  • EXP_TYPE_START_DATE / EXP_TYPE_END_DATE — the effective date range of the expenditure type itself.
  • UNIT_OF_MEASURE — the unit of measure assigned to the expenditure type.

Common Use Cases and Queries

The view is typically used to validate that an expenditure type is linked to a system before allowing it on a cost transaction, and to determine the cost element that a transaction will roll up into. A representative query listing all active linkages is:

  • SELECT expenditure_type, expenditure_type_id, cost_element_id, unit_of_measure FROM cst_proj_exp_types_val_v WHERE SYSDATE BETWEEN sys_link_start_date AND NVL(sys_link_end_date, SYSDATE) ORDER BY expenditure_type;
  • SELECT expenditure_type, description FROM cst_proj_exp_types_val_v WHERE cost_element_id = 4; — isolates expenditure types linked to the WIP cost element.
  • SELECT expenditure_type FROM cst_proj_exp_types_val_v WHERE SYSDATE BETWEEN exp_type_start_date AND NVL(exp_type_end_date, SYSDATE) AND cost_element_id IN (1,2); — active Inventory and Buy-to-Collect types.

Because the view is read-only and derived entirely from the two PA tables, it can be safely queried for reconciliation and audit purposes without risk to transactional data.