Search Results req_line




Overview
Explore in AI Chat

Overview

The PA_PROJ_PEND_REQ_DISTRIBUTIONS view is a Projects (PA) module reporting object owned by the APPS schema. Its documented purpose is to expose project-related requisition distributions that are both unapproved and unpurchased, providing a consolidated, security-aware window into outstanding project commitments originating in Oracle Purchasing. In Oracle EBS 12.1.1 and 12.2.2 the view is registered with status VALID and is intended for reporting, inquiry, and integration usage rather than transactional data entry.

Because it surfaces pending (not yet approved) requisition distribution lines against project, task, and expenditure attributes, the view supports commitment visibility and pipeline analysis prior to the creation of purchase orders or actual commitments. Users searching on the identifier req_line are typically working with the REQ_LINE column, which corresponds to the requisition line number of the underlying distribution record.

Underlying Base Objects

The view is defined over the base object PA_PROJ_REQ_DISTRIBUTIONS (itself a view), filtered by the predicate APPROVED_FLAG != 'Y'. All columns are projected directly from the base object using the alias PRD, without joins or aggregations in the outer view text.

The documented referenced base objects also include a set of supporting packages: FND_PROFILE, HR_GENERAL, HR_SECURITY, PA_MULTI_CURRENCY, PA_TASK_UTILS, and PA_UTILS4. These are invoked through the base object hierarchy to resolve profile option values, apply organization and HR security (HR_SECURITY, HR_GENERAL), perform multi-currency conversion logic (PA_MULTI_CURRENCY), and resolve task and project attributes (PA_TASK_UTILS, PA_UTILS4). The dependence on HR_SECURITY and FND_PROFILE means that rows returned are subject to the operating unit, organization, and responsibility-level security context of the querying session.

Key Columns

Common Use Cases and Queries

Typical scenarios include auditing unapproved project requisition commitments, reconciling project pipeline against budget, and feeding external systems with pending requisition data. A sample query listing pending distributions for a given project is:

  • SELECT req_number, req_line, project_number, task_number, expenditure_type, quantity, amount, need_by_date FROM apps.pa_proj_pend_req_distributions WHERE project_number = :p_project_number ORDER BY req_number, req_line;
  • SELECT req_number, req_line, project_number, vendor_name, amount FROM apps.pa_proj_pend_req_distributions WHERE req_line = :p_req_line;

Results depend on the caller's organization and HR security profile settings, so responsibilities with restricted organization access will see a correspondingly restricted row set. Because the view excludes approved requisitions, it should be used specifically for pending, pre-commitment reporting rather than for approved requisition or purchase order analysis.