Search Results pa_expenditure_groups




Overview
Explore in AI Chat

Overview

The PA_EXPENDITURE_GROUPS view is a Single-Org (organization-striped) reporting view within the Oracle Projects (PA) module of Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes expenditure group records as they apply to the current operating organization (ORG_ID) determined by the user's session context. Expenditure groups represent batch containers into which Oracle Projects and Oracle Purchasing collect expenditure items prior to their being interfaced into Oracle Projects and processed by the cost distribution and interface programs. The view is used primarily for querying, reporting, and integration scenarios where a business needs to identify open or closed expenditure groups, monitor accumulated control counts and total amounts, and reconcile batch processing against source transactions.

In the ETRM 12.2.2 metadata the view is flagged as "Not implemented in this database," meaning the object is documented as a repository definition rather than a physical artifact in that particular environment; nevertheless, the view text is fully described and reflects the standard Oracle Projects data model shipped with the product.

Underlying Base Objects

The documented view is defined exclusively over the base table PA_EXPENDITURE_GROUPS_ALL, which holds expenditure group definitions across all organizations. No other base objects are referenced in the documented metadata. The Single-Org designation is enforced through a WHERE clause that filters rows by ORG_ID. The predicate derives the current organization identifier from the USERENV('CLIENT_INFO') session value, taking the first ten characters, using a leading blank character to detect a null value, and defaulting to -99 when no client information is present. Rows are returned only when the group's ORG_ID (with NULL coerced to -99) matches the derived session organization. This is the standard Oracle multi-org view pattern that restricts query results to the operating unit currently set in the user's session.

Key Columns

Common Use Cases and Queries

The view is most often queried to list expenditure groups for the current organization, to identify open groups awaiting interface, and to reconcile control totals against actual collected amounts. Because ORG_ID filtering is automatic, no explicit organization predicate is normally required.

  • List all groups for the session organization:
    SELECT expenditure_group, expenditure_group_status_code, expenditure_ending_date, control_count, control_total_amount FROM pa_expenditure_groups;
  • Identify open groups by source and cutoff date:
    SELECT expenditure_group, transaction_source, system_linkage_function, expenditure_ending_date FROM pa_expenditure_groups WHERE expenditure_group_status_code = 'OPEN';
  • Reconcile control totals for interface processing:
    SELECT expenditure_group, control_count, control_total_amount FROM pa_expenditure_groups WHERE expenditure_ending_date >= :from_date;
  • Audit user activity against group definitions:
    SELECT expenditure_group, created_by, creation_date, last_updated_by, last_update_date FROM pa_expenditure_groups ORDER BY last_update_date DESC;

In integration designs, the view provides a secure, organization-scoped read layer over PA_EXPENDITURE_GROUPS_ALL that avoids direct queries against the _ALL table and honors the Multi-Org session model.