Search Results quantity_overbilled




Overview
Explore in AI Chat

Overview

PA_PROJ_APPR_PO_DISTRIBUTIONS is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Projects (PA) application family. Its documented purpose in both the 12.1.1 and 12.2.2 releases is to present all approved and uninvoiced purchase order distributions that are project related. In practice, the view answers the question: which committed, approved purchase order commitments still carry an open (uninvoiced) balance against a project or task? This makes it a foundational object for commitment reporting, project funds checking, and downstream integration with purchasing and payables data.

The view derives its rows from PA_PROJ_PO_DISTRIBUTIONS and filters on EVER_APPROVED_FLAG = 'Y', guaranteeing that only distributions that reached an approved purchasing state are exposed. Because the parent view already resolves PO distributions to project, task, and expenditure attributes, this view is essentially a curated, project-facing projection of purchasing commitment data.

Underlying Base Objects

The view's FROM clause references a single base object, PA_PROJ_PO_DISTRIBUTIONS, aliased POD. All column references are prefixed POD., confirming a direct projection (no joins, unions, or aggregations in the view text). The 12.2.2 ETRM metadata nonetheless lists several referenced objects, which reflects dependencies exposed through the underlying view and the package logic that populates PO-derived columns:

  • PA_PROJ_PO_DISTRIBUTIONS (VIEW) — the direct source of every column in PA_PROJ_APPR_PO_DISTRIBUTIONS.
  • PA_UTILS4, PA_CMT_UTILS, PA_PJC_CWK_UTILS, PA_TASK_UTILS, PA_FUNDS_CONTROL_UTILS — Projects utility packages that resolve project/task validation, expenditure categorization, and commitment/funds-control rules.
  • PA_CURRENCY, PA_MULTI_CURRENCY — packages supporting the dual-currency (denominated vs. accounted) amounts exposed by the view.
  • HR_GENERAL, HR_SECURITY — HR packages used to resolve person names (requestor, buyer) and to apply security profiles for person data.
  • FND_PROFILE — the EBS profile-option package, used to obtain user/application context such as currency and security settings.

Because every column is inherited unchanged, the view provides no additional transformation beyond the approval filter.

Key Columns

The view exposes a wide column set covering document identity, financial quantities, and project attribution. The user search term "printed_date" maps to the PRINTED_DATE column, which records the date the purchase order document was printed. This is a standard column on PO documents and, in this view, allows reporting on committed project spend by the point at which the PO was physically or electronically printed, rather than merely approved.

Common Use Cases and Queries

Typical scenarios include commitment reconciliations, "uninvoiced PO" reports, buyer/requestor activity analysis, and currency exposure reviews. Because the view is filter-ready, queries can be narrowed by project, date, or currency without touching base purchasing tables.

  • Outstanding project commitments by project:
    SELECT project_number, po_number, printed_date, amount_outstanding_invoice FROM pa_proj_appr_po_distributions WHERE amount_outstanding_invoice > 0;
  • Printed but uninvoiced POs within a period (uses printed_date):
    SELECT po_number, vendor_name, printed_date, acct_currency_code, amount_outstanding_invoice FROM pa_proj_appr_po_distributions WHERE printed_date BETWEEN :from_date AND :to_date;
  • Buyer/requestor activity on a project or task:
    SELECT buyer_name, requestor_name, SUM(amount_ordered) FROM pa_proj_appr_po_distributions WHERE project_number = :project GROUP BY buyer_name, requestor_name;
  • Currency exposure analysis:
    SELECT denom_currency_code, acct_currency_code, SUM(denom_amt_outstanding_invoice), SUM(amount_outstanding_invoice) FROM pa_proj_appr_po_distributions GROUP BY denom_currency_code, acct_currency_code;

These queries leverage the view's dual-currency columns and the PRINTED_DATE field, making it suitable for both functional reporting and integration extracts.