Results for “release_revision”

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

Overview

The PA_PROJ_PO_DISTRIBUTIONS view, owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2, exposes project-related uninvoiced purchase order distributions for reporting and integration within the Projects (PA) module. Its primary purpose is to present, in the functional currency of the ledger, purchase order commitments that have been charged to a project and task but not yet invoiced, with non-recoverable tax added to the outstanding amount. Because procurement activity originates in Purchasing and Payables while project cost collection occurs in Projects, this view bridges the subledgers by joining purchase order header, line, and distribution data to project, task, and vendor information. It is most commonly consumed by commitment and funds-consumption reporting, custom unbilled Payables extracts, and reconciliation programs that compare committed, ordered, and invoiced balances at the project or task level.

Underlying Base Objects

The view is defined over a combination of purchasing, payables, projects, and HR objects. The core PO objects are PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_DISTRIBUTIONS_ALL, PO_RELEASES_ALL, PO_LINE_TYPES, PO_DOCUMENT_TYPES_ALL_TL, and the PO_VENDORS view. Project context is supplied through PA_PROJECTS_ALL, PA_TASKS, PA_TASKS_EXPEND_V, and PA_EXPENDITURE_TYPES. Personnel information comes from PER_ALL_PEOPLE_F, HR_ORGANIZATION_UNITS, and the HR_GENERAL and HR_SECURITY packages. Currency conversion is performed through the PA_MULTI_CURRENCY and PA_CURRENCY packages, while ledger context is drawn from GL_LEDGERS and profile values via FND_PROFILE. Additional logic is provided by PA utility packages including PA_CMT_UTILS, PA_FUNDS_CONTROL_UTILS, PA_PJC_CWK_UTILS, PA_TASK_UTILS, and PA_UTILS4. The view performs substantial DECODE-based logic to determine authorization status, approval flags, and document dates at either the release or header level.

Key Columns

The view returns document identification columns such as SEGMENT1 (PO number), REVISION_NUM, and RELEASE_NUM, along with computed authorization indicators that evaluate to 'Y' or 'N' based on the applicable approval status. Approval and date columns (CREATION_DATE, APPROVED_DATE, PRINTED_DATE) resolve from either the header or the release depending on whether a release exists. Requester and buyer identity columns expose PERSON_ID and FULL_NAME values. Vendor details derive from VENDOR_NAME and VENDOR_ID. Line-level attributes include LINE_NUM, ITEM_DESCRIPTION, and unit of measure. Amount columns — AMOUNT_ORDERED, AMOUNT_CANCELLED, and the net ordered amount — are converted to the functional currency using PA_MULTI_CURRENCY.CONVERT_AMOUNT_SQL when no stored rate exists, or by multiplying the stored RATE against the source amount.

Common Use Cases and Queries

Typical uses include identifying open commitments by project, reporting uninvoiced purchase order balances to support accrual or unbilled analyses, and validating funds control consumption.

• List uninvoiced commitments for a project: SELECT segment1, line_num, amount_ordered, amount_cancelled FROM pa_proj_po_distributions WHERE project_id = :p_project_id;
• Filter by approval status using the computed authorization flag.
• Join to PA_PROJECTS_ALL and PA_TASKS for organizational rollups.
• Aggregate net ordered amounts by vendor for supplier commitment reporting.

Because the view applies currency conversion and approval logic through PL/SQL packages, queries should be filtered narrowly to maintain acceptable performance.