Results for “pa_expenditures”

50+ results




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

Overview

PA_EXPENDITURES is a single-organization (org-striped) reporting view in the Oracle Projects (PA) module of Oracle E-Business Suite, documented for releases 12.1.1 and 12.2.2. The object exposes expenditure transaction header data — the record of costs incurred against projects and tasks — in a form that is filtered automatically to the organization of the current session. It is the operational counterpart to the multi-organization table PA_EXPENDITURES_ALL: rather than querying the base table and manually restricting rows by ORG_ID, applications and reports can query this view and rely on the operating unit context supplied by the user's environment.

In EBS reporting and integration, the view serves as a stable, security-aware access point for project cost information. It is commonly consumed by Discoverer workbooks, Oracle Reports, BI Publisher data models, and custom interfaces that must respect multi-org (MOAC) partitioning without embedding ORG_ID predicates explicitly. The ETRM metadata records the view as "Single-Org" and notes that it is not implemented as a database object in every environment, meaning availability is contingent on the schema configuration of the instance.

Underlying Base Objects

The view is defined over a single documented base object: PA_EXPENDITURES_ALL. The ETRM record lists no other referenced base objects. The view text selects a defined column list from PA_EXPENDITURES_ALL and applies an ORG_ID predicate that resolves the organization from the session's CLIENT_INFO value.

The filtering logic is typical of EBS single-org views. It extracts the first ten characters of USERENV('CLIENT_INFO') — the MOAC operating unit identifier set by the application during login — and compares it against the ORG_ID column. Where ORG_ID is null, or where the session value cannot be resolved, the DECODE/TO_NUMBER construct falls back to a sentinel value of -99, ensuring deterministic behavior rather than unrestricted row return. Because the view is defined over PA_EXPENDITURES_ALL, it inherits all column definitions of the base table; no joins or aggregations are introduced.

Key Columns

The view exposes the full expenditure header column set. The most significant columns include:

Common Use Cases and Queries

Typical uses include reconciling expenditure batches, extracting approved costs for downstream interfaces, and validating control totals before running cost distribution and interface accounting. A representative query retrieves approved batches for the current operating unit:

  • SELECT expenditure_id, expenditure_ending_date, expenditure_class_code, control_total_amount, acct_currency_code FROM pa_expenditures WHERE expenditure_status_code = 'APPROVED' ORDER BY expenditure_ending_date;
  • SELECT expenditure_id, incurred_by_person_id, wf_status_code, transfer_status_code FROM pa_expenditures WHERE transfer_status_code <> 'Y';

Because the view is single-org, queries should be run in the correct operating unit context via MOAC initialization; the view will silently return only rows for the active organization. Developers should confirm the object's existence in their instance, as the ETRM record indicates it is not implemented in every database.