Search Results requestor_person_id




Overview
Explore in AI Chat

Overview

The APPS.PA_PROJ_REQ_DISTRIBUTIONS_V view is a reporting and integration object in Oracle E-Business Suite Projects (PA). It presents project-related requisition distribution information by joining purchasing requisition data with project, task, expenditure type, and expenditure organization attributes. In Oracle EBS 12.1.1 and 12.2.2, the view is registered under the APPS schema and is flagged VALID. Its FND Design Data reference is PA.PA_PROJ_REQ_DISTRIBUTIONS_V, indicating ownership by the Projects application.

The view is primarily intended for inquiry, reporting, and interface purposes where a denormalized, read-only representation of requisition distributions associated with projects is required. Because it consolidates descriptive purchasing attributes with project accounting attributes, it allows report writers and integration developers to avoid writing complex multi-table joins against the raw transaction tables.

Underlying Base Objects

According to the documented metadata (ETRM 12.2.2), the view references the following base objects:

These synonyms resolve to the underlying purchasing, projects, and human resources tables in the EBS database. The view federates data across these applications, producing one row per requisition distribution enriched with project accounting context.

Key Columns

The view exposes requisition, purchasing, project accounting, and currency columns. Key items include:

Common Use Cases and Queries

Typical usage includes reporting on project requisition commitments, identifying requisitions raised by specific requestors, and validating currency conversion associated with project expenditures. Because the user specifically searched for requestor_person_id, a common query filters by that column:

SELECT REQ_NUMBER, REQ_LINE, REQUESTOR_PERSON_ID, REQUESTOR_NAME, PROJECT_NUMBER, TASK_NUMBER, DENOM_AMOUNT, APPROVED_FLAG FROM APPS.PA_PROJ_REQ_DISTRIBUTIONS_V WHERE REQUESTOR_PERSON_ID = :p_person_id;

Other frequent patterns include aggregating requisition amounts by project or task, listing distributions for a project within a date range using NEED_BY_DATE or EXPENDITURE_ITEM_DATE, and joining REQ_DISTRIBUTION_ID back to PO_REQ_DISTRIBUTIONS_ALL for drill-down. Reports may also group by EXPENDITURE_CATEGORY or RESOURCE_CLASS to summarize project commitment by cost classification. Because the view is read-only, it should be used for querying and integration extraction rather than direct DML.