Search Results pjm_po_commitments_v

Overview

The PJM_PO_COMMITMENTS_V view is a reporting and inquiry construct within the Oracle E-Business Suite Project Manufacturing (PJM) module. Its documented purpose is to present project-related unreceived purchase order distributions, effectively acting as a commitment reporting view for procurement activity tied to project and task structures. In project-driven manufacturing and contracting environments, commitments represent the value of goods or services that have been ordered but not yet received. Accurate visibility into these unreceived commitments is essential for project cost forecasting, budget validation, and encumbrance-style reporting.

This view consolidates header, release, line, and distribution-level purchasing data and enriches it with supplier, buyer, requisitioner, currency, and approval context. It is intended for use in reports and inquiries where project managers and cost analysts need to understand outstanding obligations against their projects. It also serves integration scenarios, such as extracting commitment data into external project costing, budgeting, or data warehouse systems, without requiring direct joins across the base Oracle Purchasing tables.

Underlying Base Objects

The documented ETRM metadata for this object lists no formally documented referenced base objects, and it also notes that the view is "Not implemented in this database." The absence of documented base objects means the object should be treated as an interface or legacy artifact rather than a delivered, supported database object in every environment. Where the view is present, its definition — as shown in the view text — is constructed over the standard Oracle Purchasing tables and related entities. The aliases in the SELECT statement reveal the constituent sources:

• POH — PO_HEADERS_ALL (purchase order header).
• POR — PO_RELEASES_ALL (release information for blanket or planned orders).
• POL — PO_LINES_ALL (purchase order lines).
• PLL — PO_LINE_LOCATIONS_ALL (line locations/shipments).
• POD — PO_DISTRIBUTIONS_ALL (distribution-level quantity and amount data).
• REQ and BUY — derived from per_all_people_f or similar person sources, providing the requester and buyer identities.
• V — vendor information (po_vendors / po_vendor_sites style source).
• PDT — po_document_types or a type lookup source, providing the document type name.
• G and LT — currency and line-type lookup sources used for rate and unit-of-measure logic.

The view therefore represents a denormalized consolidation of the purchasing data model, filtered to distributions associated with project information.

Key Columns

The columns exposed by the view map closely to purchasing and commitment concepts. Segment1, revision numbers, and release numbers identify the document. Authorization and approved-date expressions use DECODE logic to determine, at both header and release level, whether a document is authorized and whether an approval date exists, returning 'Y' or 'N'. The document type name classifies the transaction.

Requisitioner and buyer columns expose person identifiers and full names. Vendor name and vendor ID identify the supplier. The line number and item description describe the ordered item. Unit of measure is suppressed for amount-type orders, and price_override multiplied by the distribution rate yields the effective unit price. Currency code, functional currency, rate date, rate type, and exchange rate support multi-currency commitment valuation. Quantity columns capture ordered, cancelled, delivered, billed, and derived unreceived quantities, alongside corresponding amount columns such as billed amount and extended commitment value. These combinations allow unreceived commitment value to be computed as ordered minus delivered or cancelled quantities, valued at the effective price.

Common Use Cases and Queries

The principal use case is commitment reporting for projects, aggregating unreceived purchase order distributions to forecast future costs. A sample query might sum the unreceived commitment value grouped by project, task, or vendor:

• SELECT vendor_name, currency_code, SUM(unreceived_amount) FROM pjm_po_commitments_v GROUP BY vendor_name, currency_code;
• SELECT segment1, release_num, line_num, item_description, quantity_ordered, quantity_delivered FROM pjm_po_commitments_v WHERE authorization_flag = 'Y';
• Filtering by requisitioner or buyer for procurement responsibility analysis.
• Extracting approved, unreceived distributions for budgeting or encumbrance reconciliation.

Because the object is documented as not implemented, teams should verify its existence and definition in each environment before relying on it for production reporting, and confirm the exact column names returned by DESC on the deployed view.