Results for “po_amount_ordered”

31 results




Overview
Explore in AI Chat

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

Overview

PA_PROJ_COMMITMENT_BASE_VIEW is a public Oracle E-Business Suite view owned by the APPS schema and defined in the Projects (PA) product. It is a VALID database object in both release 12.1.1 and 12.2.2. The view functions as the consolidated base layer beneath the project commitment reporting view PA_PROJ_COMMITMENT_STATUS. Its purpose is to normalize commitment and expenditure data that originates from several distinct transactional sources into a single, uniform column structure so that downstream reporting objects, concurrent programs, and inquiry screens can retrieve project commitments without issuing multiple disjoint queries.

Commitments in Oracle Projects represent anticipated costs that have not yet been recognized as actual expenditure. These originate from approved requisitions, purchase orders, and uninvoiced supplier invoices. PA_PROJ_COMMITMENT_BASE_VIEW gathers these amounts alongside the full list of projects, exposing them in one projection. This makes it a foundational integration and reporting object for funds checking, budget-versus-commitment analysis, and project cost control.

Underlying Base Objects

The view is defined as the UNION ALL of four component queries, each drawing from a distinct source:

ETRM metadata also records numerous programmatic dependencies referenced through these underlying views and the wider commitment reporting stack, including PA_CMT_UTILS, PA_CURRENCY, PA_MULTI_CURRENCY, PA_FUNDS_CONTROL_UTILS, PA_PJC_CWK_UTILS, PA_TASK_UTILS, PA_UTILS4, AP_INVOICES_PKG, FND_PROFILE, HR_GENERAL, and HR_SECURITY. HR_SECURITY and FND_PROFILE are significant because the commitment reporting chain applies organizational and responsibility-level security, and currency packages indicate multi-currency handling of commitment amounts.

Key Columns

The view exposes ten columns. The first five establish the reporting grain and are populated identically across all four UNION ALL branches:

  • PROJECT_NUMBER and PROJECT_NAME — project identification attributes.
  • PROJECT_ID — the internal project identifier used for joins and foreign keys.
  • TASK_NUMBER and TASK_NAME — task-level identification; these are NULL in the branch sourced from PA_PROJECTS.

The remaining five columns carry the commitment amounts, each populated by exactly one branch and set to zero elsewhere:

  • REQ_AMOUNT_OPEN — open approved requisition commitment amount.
  • PO_AMOUNT_ORDERED — value of purchase order amounts ordered.
  • PO_AMOUNT_DELIVERED — value of purchase order amounts delivered but not yet invoiced.
  • PO_AMOUNT_OPEN — outstanding purchase order commitment, aligned to AMOUNT_OUTSTANDING_INVOICE in the source.
  • AP_AMOUNT_PENDING — pending supplier invoice amount from AP invoice distributions.

Common Use Cases and Queries

Typical uses include producing commitment detail reports, reconciling requisition and purchase order commitments against actual invoice costs, and driving project funds control checks. Because the view is a base layer, most implementations query PA_PROJ_COMMITMENT_STATUS rather than this view directly; however, it is used when a normalized, source-tagged projection is required.

A representative query aggregating commitments by project:

  • SELECT project_number, project_name, project_id, SUM(req_amount_open) req_open, SUM(po_amount_ordered) po_ordered, SUM(po_amount_delivered) po_delivered, SUM(po_amount_open) po_open, SUM(ap_amount_pending) ap_pending FROM apps.pa_proj_commitment_base_view GROUP BY project_number, project_name, project_id;

To isolate task-level detail while excluding the project master rows, add a filter such as WHERE task_number IS NOT NULL. All queries should be executed with the appropriate APPS responsibility context so that the underlying HR security and profile logic is honored.