Results for “personnel_attached_flag”

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

Overview

IGW_BUDGET_EXPENDITURES_V is a reporting view historically shipped within the Oracle E-Business Suite Grants Proposal module (product code IGW). The ETRM metadata classifies this object as obsolete and annotates it with the description "10SC Only," indicating that it was implemented in a limited set of legacy references and is not available in standard 12.1.1 or 12.2.2 installations. The metadata record explicitly states "Not implemented in this database," confirming that the view is absent from current seeded schemas and is not referenced by supported application flows.

The view presents a consolidated list of budget expenditure values, merging expenditure categories and expenditure types into a single denormalized structure. It was designed to feed grants budgeting screens and integration points where a unified choice list of budget lines was required. Because the object remains catalogued, technical consultants frequently encounter it during impact analysis, custom code audits, and upgrade remediation exercises.

Underlying Base Objects

Per the documented view text, IGW_BUDGET_EXPENDITURES_V is defined as a UNION of two component views: IGW_EXPENDITURE_CATEGORIES_V and IGW_EXPENDITURE_TYPES_V. No base tables are documented against the view itself, and the ETRM record lists no referenced base objects. This reflects the layering convention in the IGW schema, where the _V objects wrap the underlying Grants tables and expose filtered, effective-dated rows.

The first branch of the UNION selects from IGW_EXPENDITURE_CATEGORIES_V and produces budget expenditure rows at the category level, with a null PARENT_CATEGORY and the literal flag 'Y' in EXPENDITURE_CATEGORY_FLAG. The second branch joins IGW_EXPENDITURE_TYPES_V to IGW_EXPENDITURE_CATEGORIES_V on EXPENDITURE_CATEGORY, producing type-level rows that carry the parent category value and the flag 'N'. The join therefore depends on the category view to supply the parent relationship, the budget category code, and the personnel-attached indicator for each expenditure type.

Key Columns

• BUDGET_EXPENDITURE — The primary display value; sourced from EXPENDITURE_CATEGORY in the first branch and from EXPENDITURE_TYPE in the second.
• DESCRIPTION — The descriptive text of the category or type.
• BUDGET_CATEGORY_CODE — The budget category classification, always taken from the category view.
• EXPENDITURE_CATEGORY — The governing category for the row; populated for both categories and types.
• PARENT_CATEGORY — Null for category rows, and equal to EXPENDITURE_CATEGORY for type rows, enabling hierarchical rendering.
• PERSONNEL_ATTACHED_FLAG — Indicates whether personnel costs are attached to the category, used to control personnel budgeting behavior.
• EXPENDITURE_CATEGORY_FLAG — Distinguishes category rows ('Y') from expenditure type rows ('N').
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effective dating inherited from the source category and type views.

Common Use Cases and Queries

The principal historical use case was populating budget line selection lists in the Grants Proposal budgeting pages, where a single query returns both categories and their child expenditure types. Downstream reporting against awards and proposals could similarly consume the view to reconcile budgeted amounts with expenditure classifications.

Because the object is obsolete and not implemented, any query executed on a current 12.1.1 or 12.2.2 instance will fail with an ORA-00942 invalid table error. Verification queries should therefore confirm object existence before attempting to reference it:

• SELECT object_name, object_type, status FROM all_objects WHERE object_name = 'IGW_BUDGET_EXPENDITURES_V';
• SELECT * FROM igw_budget_expenditures_v WHERE expenditure_category_flag = 'N' ORDER BY expenditure_category, budget_expenditure;
• SELECT budget_expenditure, description, parent_category FROM igw_budget_expenditures_v WHERE personnel_attached_flag = 'Y';

Where equivalent functionality is required today, the supported replacement is to query the corresponding expenditure category and expenditure type views directly, or to use the Oracle Grants Management (GMS) budget inquiry objects that superseded the IGW Proposal module. Legacy customizations referencing this view should be retired or repointed during upgrade remediation.