Search Results ap_amount_pending




Overview
Explore in AI Chat

Overview

The APPS.PA_PROJ_COMMITMENT_STATUS view is a public Oracle E-Business Suite database object that consolidates project commitment cost information for reporting and integration purposes. Its FND Design Data identifier is PA.PA_PROJ_COMMITMENT_STATUS, and it resides in the APPS schema with a VALID status. The view is classified as public, meaning it may be used for custom reporting or other data requirements without restriction. It presents project commitment costs spanning the full procurement and payables lifecycle, including requisitions, purchase orders, and pending vendor invoices. The view is owned by APPS and is defined over project accounting base objects, so it reflects the commitment accounting model maintained by Oracle Project Costing rather than raw transactional tables.

Underlying Base Objects

The view is defined primarily over APPS.PA_PROJ_COMMITMENT_BASE_VIEW, a view object that supplies the underlying commitment aggregation. The ETRM metadata documents the following referenced base objects: AP_INVOICES_PKG (PACKAGE), FND_PROFILE (PACKAGE), HR_GENERAL (PACKAGE), HR_SECURITY (PACKAGE), PA_CMT_UTILS (PACKAGE), PA_CURRENCY (PACKAGE), PA_FUNDS_CONTROL_UTILS (PACKAGE), PA_MULTI_CURRENCY (PACKAGE), PA_PJC_CWK_UTILS (PACKAGE), PA_PROJ_COMMITMENT_BASE_VIEW (VIEW), PA_TASK_UTILS (PACKAGE), and PA_UTILS4 (PACKAGE). Several of these packages supply helper logic for currency conversion, security, and commitment calculation. Notably, HR_SECURITY and HR_GENERAL indicate that the view applies organizational security, so rows returned are filtered according to the user's access. PA_PROJ_COMMITMENT_STATUS is not referenced by any other database object, confirming it serves strictly as a reporting endpoint rather than an intermediate dependency.

Key Columns

The user specifically searched for PO_AMOUNT_ORDERED, which represents the net ordered commitment on a purchase order after cancellations are applied. It is the figure most commonly used to compare original buying intent against delivery and invoicing progress.

Common Use Cases and Queries

Typical applications include commitment reporting, budget-versus-commitment analysis, and feeds into external data warehouses. Because the view aggregates requisition, PO, and pending invoice amounts, it supports rapid identification of open commitments without joining multiple transactional tables. A simple query returns all columns for each project:

SELECT PROJECT_NUMBER, PROJECT_NAME, PROJECT_ID, REQ_AMOUNT_OPEN, PO_AMOUNT_ORDERED, PO_AMOUNT_DELIVERED, PO_AMOUNT_OPEN, AP_AMOUNT_PENDING FROM APPS.PA_PROJ_COMMITMENT_STATUS;

A focused query isolates ordering activity for a specific project:

SELECT PROJECT_NUMBER, PO_AMOUNT_ORDERED, PO_AMOUNT_DELIVERED, PO_AMOUNT_OPEN FROM APPS.PA_PROJ_COMMITMENT_STATUS WHERE PROJECT_NUMBER = :project_number;

Because HR security is applied through the referenced packages, results are automatically restricted to the projects accessible to the querying user. This makes the view appropriate for self-service reporting as well as scheduled extraction programs.