Search Results po_amount_ordered

Overview

PA_PROJ_COMMITMENT_STATUS is an Oracle E-Business Suite view owned by the APPS schema in the Projects (PA) module. It presents a consolidated, project-level picture of commitment costs, aggregating three distinct classes of encumbrance and pre-invoice activity: requisitions, purchase orders, and pending vendor invoices. Rather than exposing individual commitment transactions, the view rolls these amounts up by project, making it suitable for dashboards, funds-check reporting, project manager reviews, and integration extracts that require a single commitment position per project. Because it resides in the APPS schema and is defined over the PA commitment base view, it inherits the standard Oracle EBS security and profile-driven behavior of its underlying packages. It is available in both 12.1.1 and 12.2.2 with the same documented column layout; the 12.2.2 ETRM metadata confirms its status as VALID and lists its full dependency set.

Underlying Base Objects

The view text is a single aggregate query over PA_PROJ_COMMITMENT_BASE_VIEW, grouped by PROJECT_NUMBER, PROJECT_NAME, and PROJECT_ID. Each measure column is produced by a SUM() over the corresponding base column, so PA_PROJ_COMMITMENT_STATUS is a summarized projection of the base view rather than a direct join of transactional tables.

The documented dependencies of the view are predominantly PL/SQL packages referenced by the base view and its supporting logic: AP_INVOICES_PKG, FND_PROFILE, HR_GENERAL, HR_SECURITY, PA_CMT_UTILS, PA_CURRENCY, PA_FUNDS_CONTROL_UTILS, PA_MULTI_CURRENCY, PA_PJC_CWK_UTILS, PA_TASK_UTILS, and PA_UTILS4, together with the PA_PROJ_COMMITMENT_BASE_VIEW object itself. These packages supply currency conversion, multi-currency handling, funds control, HR security (organization/project access), and commitment utility logic. Consequently, amounts returned are already subject to the calling user's security profile and the applicable functional currency and conversion rules.

Key Columns

• PROJECT_NUMBER — The user-visible project number; part of the grouping key.
• PROJECT_ID — The internal unique identifier for the project; the safest join key to PA_PROJECTS and other PA entities.
• PROJECT_NAME — The descriptive project name; part of the grouping key.
• REQ_AMOUNT_OPEN — Total open requisition commitment amount for the project (approved requisitions not yet converted to purchase orders).
• PO_AMOUNT_ORDERED — Total amount ordered on purchase orders for the project.
• PO_AMOUNT_DELIVERED — Portion of the ordered amount that has been received or delivered.
• PO_AMOUNT_OPEN — The open (undelivered or unbilled) purchase order commitment remaining for the project.
• AP_AMOUNT_PENDING — Pending vendor invoice amount awaiting validation, accounting, or payment; represents AP commitments not yet finalized.

All measure columns are numeric sums in the applicable currency; the view itself does not carry a currency code column, so currency context must be derived from the project or the session.

Common Use Cases and Queries

Typical uses include project commitment dashboards, budget-vs-commitment reconciliation, funds availability checks, and periodic extracts into reporting or data warehouse layers. The following query returns the commitment position for a specific project:

• SELECT project_number, project_name, req_amount_open, po_amount_ordered, po_amount_delivered, po_amount_open, ap_amount_pending FROM apps.pa_proj_commitment_status WHERE project_id = :p_project_id;
• SELECT project_number, SUM(po_amount_open) total_open_po FROM apps.pa_proj_commitment_status GROUP BY project_number ORDER BY total_open_po DESC; — to rank projects by open purchase order commitment.
• SELECT p.project_number, c.po_amount_ordered, c.po_amount_delivered, (c.po_amount_ordered - c.po_amount_delivered) undelivered FROM apps.pa_proj_commitment_status c, apps.pa_projects_all p WHERE c.project_id = p.project_id AND p.project_status_code = 'APPROVED'; — to identify undelivered commitment on active projects.

Because the view aggregates and applies security and currency logic, results reflect the querying user's access and functional currency settings. For transaction-level drill-down, query PA_PROJ_COMMITMENT_BASE_VIEW or the underlying requisition, purchasing, and AP tables directly.