Search Results pa_cost_dist_lines_all_bas




Overview
Explore in AI Chat

Overview

APPS.PA_STATUS_EI_V is a status-reporting view in Oracle E-Business Suite Projects (PA), published in the ETRM reference for 12.1.1 and 12.2.2. It presents expenditure item activity in a flattened, presentation-ready form: each row corresponds to an expenditure item as recorded in the cost distribution lines, joined to descriptive attributes such as employee, vendor, job, organization, expenditure comment, transaction source, and currency conversion type. The view is a status view in the sense that it drives expenditure item inquiry and reporting surfaces rather than storing data itself. It complements the PA_STATUS package and wraps or derives from PA_STATUS_EI_DRIVE_V, applying row-level security through the PA_SECURITY package. For implementers searching for pa_cost_dist_lines_all_bas, this view is the documented consumer of that base table and is the appropriate place to read cost-distribution-level expenditure data with descriptive context already resolved.

Underlying Base Objects

The ETRM metadata lists eleven referenced objects. The principal fact source is PA_COST_DIST_LINES_ALL_BAS (referenced as a synonym), the cost distribution lines base table. PA_STATUS_EI_DRIVE_V supplies the driving expenditure item rows, and the leading hint on ACT combined with NO_MERGE(ACT) in the view text indicates the optimizer is directed to drive from the ACT inline set and to prevent merging of that block. Descriptive joins include PER_ALL_PEOPLE_F for the incurred-by person, PER_JOBS for job name, HR_ALL_ORGANIZATION_UNITS_TL for the non-labor resource organization name, PO_VENDORS for supplier details, PA_EXPENDITURE_COMMENTS for the expenditure comment, PA_TRANSACTION_SOURCES for the user-facing transaction source, and GL_DAILY_CONVERSION_TYPES twice for the receipt and project conversion types. PA_SECURITY and PA_STATUS are package references used within the view definition to enforce organization and project security and to derive status attributes.

Key Columns

Identification and classification columns include EXPENDITURE_ITEM_ID, PROJECT_ID, TASK_ID, EXPENDITURE_ITEM_DATE, EXPENDITURE_TYPE, EXPENDITURE_CATEGORY, REVENUE_CATEGORY_CODE, and TASK_NUMBER/TASK_NAME. Amount and quantity measures include QUANTITY, RAW_COST, BURDENED_COST, BILLABLE_QUANTITY, BILLABLE_RAW_COST, BILLABLE_BURDENED_COST, and REVENUE. Party columns resolve the incurring entity: INCURRED_BY_PERSON_ID with EMPLOYEE_NAME and EMPLOYEE_NUMBER, JOB_ID with JOB_NAME, and vendor attributes VENDOR_ID, VENDOR_NUMBER, and VENDOR_NAME; the derived columns EMPLOYEE_VENDOR_NAME and EMPLOYEE_VENDOR_NUMBER use NVL to return whichever of the employee or vendor values is populated. Organization columns include INCURRED_BY_ORGANIZATION_ID, OVERRIDE_TO_ORGANIZATION_ID, EXPENDITURE_ORGANIZATION_ID, EXPENDITURE_ORGANIZATION_NAME, NLR_ORGANIZATION_ID, and NLR_ORGANIZATION_NAME. Multi-currency columns cover RECEIPT_CURRENCY_CODE/AMOUNT/EXCHANGE_RATE, DENOM_CURRENCY_CODE with DENOM_RAW_COST and DENOM_BURDENED_COST, and ACCT_CURRENCY_CODE, ACCT_RATE_TYPE, ACCT_RATE_DATE, ACCT_EXCHANGE_RATE, ACCT_RAW_COST, ACCT_BURDENED_COST, and ACCT_EXCHANGE_ROUNDING_LIMIT, alongside PROJECT_CURRENCY_CODE and its rate attributes. SYSTEM_REFERENCE2 and SYSTEM_REFERENCE4 are carried from CDL to expose source document linkage, and ORG_ID and EXPENDITURE_ORG_ID provide the multi-org context.

Common Use Cases and Queries

Typical uses include expenditure inquiry reports, cost audit extracts, billing reconciliation, and interfaces requiring cost distribution detail with resolved party and organization names. A minimal lookup by project and period is shown below.

  • Filter by project, task, and PA_PERIOD for period-end cost review.
  • Join or restrict on ORG_ID to respect operating unit security.
  • Use ACCT_* columns for accounting-currency reporting and PROJECT_* columns for project-currency reporting.
  • Use SYSTEM_LINKAGE_FUNCTION and SYSTEM_LINKAGE_M to trace back to the originating subledger transaction.

SELECT expenditure_item_id, project_id, task_number, expenditure_item_date,
  expenditure_category, employee_vendor_name, burdened_cost, acct_burdened_cost
FROM apps.pa_status_ei_v
WHERE project_id = :p_project_id
  AND pa_period = :p_pa_period
  AND org_id = :p_org_id;

Because the view enforces PA_SECURITY and PA_STATUS logic, it is preferable to direct queries against PA_COST_DIST_LINES_ALL_BAS when secured, presentation-ready expenditure item data is required.