Results for “billable_capitalizable_flag”

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

Overview

PA_CAPITAL_EVENT_COSTS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the Projects (PA) product family. It presents expenditure line detail that has been associated with a capital event, exposing the cost components, descriptive attributes, and the billable/capitalizable indicator that users frequently search for as billable_capitalizable_flag. The view is validated and available in both 12.1.1 and 12.2.2.

The view does not store data; it is a query-time projection over the expenditure transactions and their related setup and party information. Its primary role is to support reporting, reconciliation, and integration scenarios where capital event costs must be analyzed alongside task, transaction source, employee, and vendor context. Because the view filters out net-zero adjustments, it returns only economically meaningful expenditure rows.

Underlying Base Objects

The view is defined over the following documented base objects:

• PA_EXPENDITURE_ITEMS_ALL (synonym) — the primary driver, supplying expenditure item detail such as raw cost, burden cost, expenditure item date, and the billable flag aliased as BILLABLE_CAPITALIZABLE_FLAG.
• PA_EXPENDITURES_ALL (synonym) — joined on EXPENDITURE_ID to supply the incurred-by person, vendor, and operating unit (ORG_ID).
• PA_TASKS (synonym) — joined on TASK_ID to resolve TASK_NUMBER.
• PA_TRANSACTION_SOURCES (synonym) — joined with an outer (+) operator on TRANSACTION_SOURCE to supply the user-facing description in USER_TRANSACTION_SOURCE.
• PER_ALL_PEOPLE_F (synonym) — a scalar subquery resolves the full name of the incurring person, using the effective-dated person record valid on the expenditure item date.
• PO_VENDORS (view) — a scalar subquery resolves VENDOR_NAME.

The join structure is an inner join between expenditure items and expenditures, tasks, and the net-zero filter, with an outer join to transaction sources. This means rows are returned only where matching expenditure, task, and expenditure-item records exist and the item is not flagged as a net-zero adjustment.

Key Columns

• EXPENDITURE_ITEM_ID and CAPITAL_EVENT_ID — the transaction identifiers linking the cost to its capitalization context.
• PROJECT_ID, TASK_ID, TASK_NUMBER — the project and task to which the cost belongs.
• EXPENDITURE_TYPE and TRANSACTION_SOURCE — the cost category and source system/code, with USER_TRANSACTION_SOURCE providing the descriptive label.
• EMPLOYEE_ID, EMPLOYEE_NAME, VENDOR_ID, VENDOR_NAME — the incurring party, resolved via effective-dated person and vendor lookups.
• RAW_COST and BURDEN_COST — the unbundened and burdened cost components of the expenditure item.
• EXPENDITURE_ITEM_DATE — the transaction date, also used to control the effective-dated person subquery.
• BILLABLE_CAPITALIZABLE_FLAG — the alias of PA_EXPENDITURE_ITEMS_ALL.BILLABLE_FLAG, indicating whether the cost is billable and therefore relevant for capitalization decisions.
• ORG_ID — the operating unit associated with the expenditure, supporting multi-org reporting.

Common Use Cases and Queries

A frequent requirement is to identify capital-event costs that are flagged billable/capitalizable for a project. Because the underlying column is BILLABLE_FLAG but the view exposes the alias BILLABLE_CAPITALIZABLE_FLAG, queries should reference the alias when selecting from the view:

SELECT expenditure_item_id, capital_event_id, task_number, expenditure_type, raw_cost, burden_cost, billable_capitalizable_flag FROM apps.pa_capital_event_costs_v WHERE project_id = :project_id AND billable_capitalizable_flag = 'Y';

Other scenarios include reconciling capital event expenditure by source or vendor, summarising burdened cost by task, and feeding downstream capitalization or accounting processes. Multi-org reports should constrain on ORG_ID. Because net-zero adjustments are excluded by the view definition, results reflect only live costs and require no additional filter for that purpose.