Search Results pa_proj_req_distributions




Overview
Explore in AI Chat

Overview

PA_PROJ_REQ_DISTRIBUTIONS is an APPS-owned reporting view in Oracle E-Business Suite that exposes project-related purchase requisition distributions originating in Oracle Purchasing. As documented in the ETRM metadata, the view "displays project-related distributions in Oracle Purchasing that have not yet been purchased as a purchase order." It therefore serves as a demand-side pipeline view: it identifies committed project expenditure that has been requisitioned but not yet converted into a purchase order commitment. This makes it valuable for project cost controllers, procurement analysts, and buyers who need visibility over outstanding requisitioned demand charged to projects and tasks. The view is valid in both EBS 12.1.1 and 12.2.2 and is defined in the APPS schema.

Underlying Base Objects

The view is constructed over a join of Purchasing, Projects, and HR/GL objects. The requisition side draws from PO_REQUISITION_HEADERS_ALL and PO_REQUISITION_LINES_ALL, while distribution-level detail comes from PO_REQ_DISTRIBUTIONS_ALL. Project context is supplied by PA_PROJECTS_ALL, PA_TASKS, and PA_TASKS_EXPEND_V, with expenditure classification from PA_EXPENDITURE_TYPES. Organizations are resolved through HR_ORGANIZATION_UNITS, and the requisitioning person through PER_ALL_PEOPLE_F. Document and line type descriptions come from PO_DOCUMENT_TYPES_ALL_TL and PO_LINE_TYPES. Currency and functional amounts are handled via the GL_LEDGERS synonym and the PA_MULTI_CURRENCY package, while security and utility logic is provided by PA_TASK_UTILS, PA_UTILS4, HR_SECURITY, HR_GENERAL, and FND_PROFILE. This combination reflects that the view is a cross-product construct joining procurement transactions to project accounting attributes.

Key Columns

The view exposes a broad set of columns derived from its base objects:

Common Use Cases and Queries

Typical usage centres on identifying uncommitted requisitioned project spend. A buyer might list approved requisition lines awaiting a purchase order, while a project accountant reconciles project cost pipelines.

  • Outstanding approved requisitions by project: 
    SELECT p.segment1, p.name, t.task_number, r.segment1, r.line_num,
       r.currency_code, r.req_line_amount
FROM   apps.pa_proj_req_distributions r,
       apps.pa_projects_all p,
       apps.pa_tasks t
WHERE  r.project_id = p.project_id
AND    r.task_id = t.task_id
AND    r.authorization_status = 'Y';
  • Pipeline by expenditure category: aggregate req_line_amount grouped by expenditure_category to forecast project spend not yet committed.
  • Currency exposure reporting: filter on currency_code and rate where the requisition currency differs from the functional ledger currency.

The view is read-only, so queries should always qualify records by project, task, or approval status to keep result sets meaningful.