Search Results costing_method

Overview

The PA_EXPEND_ITEMS_ADJUST_V view is an Oracle EBS Projects (PA) reporting object owned by the APPS schema. The ETRM documentation classifies its description as "10SC Only," indicating the object is restricted in scope and typically referenced by specific concurrent programs, forms, or diagnostic utilities rather than forming part of the general transactional API surface. Confirmed against Oracle E-Business Suite 12.1.1 and 12.2.2, the view exposes a denormalized, read-only projection of expenditure item data that combines project, task, employee, vendor, organization, and cost attributes within a single queryable structure.

Its role is to serve as a reporting and reconciliation layer over the core expenditure item tables. Because it joins descriptive information from many normalized source tables, it allows inquiry screens, extracts, and adjustment review reports to retrieve fully resolved descriptive context without reimplementing those joins. The view is not a transactional object; it does not participate in posting, distribution, or generation logic.

Underlying Base Objects

The view is defined primarily over PA_EXPENDITURE_ITEMS_ALL (aliased EI), with supporting joins to PA_EXPENDITURES_ALL (X) for header-level attributes such as expenditure group, status, and ending date, and PA_EXPENDITURE_COMMENTS (C) for comment text. Project, task, and type context is obtained from PA_PROJECTS_ALL, PA_PROJECT_TYPES, and PA_TASKS. Cost and currency context draws on PA_COST_DIST_LINES_ALL_BAS, PA_CONVERSION_TYPES_V, and PA_LOOKUPS / FND_LOOKUP_VALUES for meaning columns (for example L1, L2, and L8 lookup meanings). Person and organization data comes from PER_PEOPLE_F, PER_JOBS, HR_ALL_ORGANIZATION_UNITS_TL, HR_PERSON_NAME, HR_GENERAL, and HR_SECURITY. Payroll-related objects include PAY_PAYROLLS_F, PA_PAY_AUDIT_ALL, and PA_PAY_EXTERNAL_PAYROLL. Vendor data comes from PO_VENDORS, and supporting lookups such as PA_SYSTEM_LINKAGES, PA_TRANSACTION_SOURCES, PA_RBS_ELEMENTS, and PA_EXPENDITURE_TYPES supply type, source, and system linkage detail. The HR_GENERAL and HR_SECURITY references indicate the view applies organization-based security filters when resolved at runtime.

Key Columns

• Identifiers: EXPENDITURE_ITEM_ID, EXPENDITURE_ID, PROJECT_ID, TASK_ID, JOB_ID; ROW_ID from the EI rowid.
• Project/Task context: PROJECT_NUMBER, PROJECT_NAME, PROJECT_TYPE, PROJECT_TYPE_CLASS_CODE, PROJECT_CLASS (from lookup L8), TASK_NUMBER, TASK_NAME.
• Who/Where: INCURRED_BY_PERSON_ID, EMPLOYEE_NAME, EMPLOYEE_NUMBER, EXPENDITURE_ORGANIZATION_ID, EXPENDITURE_ORGANIZATION_NAME, OVERRIDE_TO_ORGANIZATION_ID, NLR_ORGANIZATION_NAME, VENDOR_NUMBER, VENDOR_NAME, EMPLOYEE_VENDOR_NAME.
• Classification: EXPENDITURE_TYPE, EXPENDITURE_CATEGORY, REVENUE_CATEGORY_CODE, TRANSACTION_SOURCE, ORIG_TRANSACTION_REFERENCE, SYSTEM_LINKAGE_M, EXPENDITURE_STATUS_M, UNIT_OF_MEASURE_M.
• Financials: QUANTITY, RAW_COST, RAW_COST_RATE, BURDEN_COST / BURDENED_COST, BURDEN_COST_RATE, DENOM_RAW_COST, DENOM_BURDENED_COST, COST_DISTRIBUTED_FLAG, COST_DIST_REJECTION_CODE, RECEIPT_CURRENCY_AMOUNT, RECEIPT_EXCHANGE_RATE, ACCT_CURRENCY_CODE, ACCT_RATE_TYPE, ACCT_RATE_DATE.
• Dates: EXPENDITURE_ITEM_DATE, EXPENDITURE_ENDING_DATE.

Common Use Cases and Queries

Typical scenarios include expenditure adjustment review, cost distribution rejection analysis, and cross-validation between incurred-by and expenditure organizations. A representative query retrieves rejected distribution items for a project:

• SELECT PROJECT_NUMBER, TASK_NUMBER, EMPLOYEE_VENDOR_NAME, EXPENDITURE_TYPE, RAW_COST, BURDEN_COST, COST_DIST_REJECTION_CODE FROM APPS.PA_EXPEND_ITEMS_ADJUST_V WHERE PROJECT_NUMBER = :P_PROJECT AND COST_DIST_DISTRIBUTED_FLAG IS NULL;
• SELECT EXPENDITURE_ORGANIZATION_NAME, SUM(BURDEN_COST) FROM APPS.PA_EXPEND_ITEMS_ADJUST_V WHERE EXPENDITURE_ITEM_DATE BETWEEN :START AND :END GROUP BY EXPENDITURE_ORGANIZATION_NAME;

Because of its breadth and its HR security joins, the view can be expensive against large expenditure volumes; queries should be filtered by project, date, or organization wherever possible.