Results for “document_line_number”

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

Overview

PA_EXPENDITURE_ITEMS_V is a Projects (PA) module view owned by the APPS schema. The ETRM documentation marks its description as "10SC Only," indicating that the view is associated with a specific localized or specialized deployment context rather than the general global product baseline. In Oracle EBS 12.1.1 and 12.2.2, the view presents expenditure item detail — the transaction-level records that make up project costs and revenue — enriched with descriptive attributes drawn from tasks, projects, expenditure groups, expenditure types, organizations, and purchasing documents. Because expenditure items carry the granular financial facts that feed cost distribution, revenue accrual, billing, and forecasting, this view serves as a convenient reporting and integration surface. It denormalizes foreign-key identifiers into human-readable names and numbers, which makes it well suited for concurrent-program extract logic, Discoverer or BI Publisher data models, and third-party interfaces that must read project transaction detail without directly joining the base tables.

The view is read-only by nature and inherits the security behavior of the objects beneath it. The presence of HR_SECURITY, HR_GENERAL, and HR_ORG_UNITS_NO_JOIN in its definition confirms that organization-level access is resolved at query time, so results are filtered according to the operating unit and organization hierarchy of the session.

Underlying Base Objects

The view resolves against several APPS synonyms and views, notably PA_EXPENDITURE_ITEMS, PA_EXPENDITURES, PA_EXPENDITURE_COMMENTS, PA_EXPENDITURE_TYPES, PA_PROJECTS_ALL, PA_TASKS, PA_TRANSACTION_SOURCES, PA_LOOKUPS, FND_LOOKUPS, PA_RBS_ELEMENTS, PO_HEADERS_ALL, and PO_LINES_ALL. Organization names are obtained from HR_ALL_ORGANIZATION_UNITS_TL via HR_ORG_UNITS_NO_JOIN, while FND_GLOBAL, HR_GENERAL, HR_SECURITY, and PA_UTILS4 supply session context and utility logic. The principal driver is PA_EXPENDITURE_ITEMS (aliased E), joined to PA_EXPENDITURES (X) for the expenditure group and status, PA_TASKS (T) and PA_PROJECTS_ALL (P) for project and task descriptions, PA_EXPENDITURE_COMMENTS (C) for remarks, and lookup views for the unit-of-measure and related meanings. Purchase-order attributes are sourced from PO_HEADERS_ALL and PO_LINES_ALL, and transaction-source text from PA_TRANSACTION_SOURCES (TR). The E.ROWID is exposed as ROW_ID.

Key Columns

• EXPENDITURE_ITEM_ID / EXPENDITURE_ID — Primary identifiers for the item and its parent expenditure batch.
• PROJECT_ID, PROJECT_NUMBER, PROJECT_NAME, TASK_ID, TASK_NUMBER, TASK_NAME — Project and task context resolved from PA_PROJECTS_ALL and PA_TASKS.
• EXPENDITURE_ITEM_DATE, EXPENDITURE_TYPE — The accounting date and classification of the transaction.
• QUANTITY, RAW_COST, RAW_COST_RATE, BURDEN_COST, BURDEN_COST_RATE — Cost amounts and rates.
• BILLABLE_FLAG, BILL_HOLD_FLAG, BILL_RATE, BILL_AMOUNT, ACCRUED_REVENUE, ADJUSTED_REVENUE, FORECAST_REVENUE — Billability and revenue values used in billing and revenue recognition.
• COST_DISTRIBUTED_FLAG, REVENUE_DISTRIBUTED_FLAG, COST_BURDEN_DISTRIBUTED_FLAG — Distribution processing status.
• EXPENDITURE_STATUS_CODE, EXPENDITURE_GROUP — Status and grouping from PA_EXPENDITURES.
• NLR_ORGANIZATION_NAME, ORGANIZATION_ID, OVERRIDE_TO_ORGANIZATION_ID — Non-labor resource and organization context.
• USER_TRANSACTION_SOURCE, TRANSACTION_SOURCE, ORIG_TRANSACTION_REFERENCE — Origin of the transaction.
• ADJUSTED_EXPENDITURE_ITEM_ID, TRANSFERRED_FROM_EXP_ITEM_ID, SOURCE_EXPENDITURE_ITEM_ID — Adjustment and transfer lineage.
• ATTRIBUTE1–ATTRIBUTE10, ATTRIBUTE_CATEGORY — Descriptive flexfield values.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns.

Common Use Cases and Queries

Typical uses include extracting project cost detail for reconciliation to GL, reporting billable versus non-billable expenditure, and feeding interfaces that require project/task names rather than IDs.

SELECT expenditure_item_id, project_number, project_name,
       task_number, expenditure_item_date, expenditure_type,
       raw_cost, burden_cost, billable_flag
FROM   apps.pa_expenditure_items_v
WHERE  project_number = :p_project_number
AND    expenditure_item_date BETWEEN :p_from AND :p_to;

For billing and revenue analysis, restrict on distribution flags and billability:

SELECT expenditure_item_id, bill_rate, bill_amount,
       accrued_revenue, adjusted_revenue, bill_hold_flag
FROM   apps.pa_expenditure_items_v
WHERE  billable_flag = 'Y'
AND    revenue_distributed_flag = 'Y';

Those searching for get_assignment_name typically need the employee or assignment associated with an expenditure item. This view does not expose an assignment-name column directly; assignment and person descriptions are generally obtained through the labor-costing tables that feed PA_EXPENDITURE_ITEMS, or through the HR assignment APIs. In practice, a query on this view should be joined to the HR assignment objects via INCURRED_BY_PERSON_ID and related person identifiers to resolve the assignment name, rather than expecting it as a native column.