Results for “requestor_person_id”

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

Overview

The PA_PROJ_APPR_REQ_DISTRIBUTIONS view is a Projects (PA) module reporting object owned by the APPS schema. It presents all approved and unpurchased requisition distributions that are project related, providing a consolidated, currency-aware picture of commitment-level purchasing activity tied to projects and tasks. In Oracle EBS 12.1.1 and 12.2.2, the view functions as a denormalized read model over the internal PA_PROJ_REQ_DISTRIBUTIONS view, exposing requisition header, line, and distribution attributes alongside project, task, expenditure, and organizational context.

Because purchasing requisitions represent pre-purchase commitments, the view is commonly used for commitment reporting, project cost forecasting, and budget-versus-commitment analysis. Its inclusion of both denominated and accounted currency amounts, together with exchange rate metadata, makes it suitable for multi-currency environments where project managers and financial analysts require consistent figures across ledgers. The view is restricted to rows where the approved flag equals 'Y', so it deliberately excludes unapproved or rejected requisitions, and by design reflects only distributions that have not yet been converted to purchase orders or otherwise consumed by purchasing activity.

Underlying Base Objects

The documented definition of the view is a single SELECT over PA_PROJ_REQ_DISTRIBUTIONS, aliased as PRD, filtered by PRD.APPROVED_FLAG = 'Y'. The view therefore inherits its join logic, security, and currency derivations from that underlying Projects view rather than from base purchasing tables directly.

ETRM metadata for release 12.2.2 records the following referenced objects: PA_PROJ_REQ_DISTRIBUTIONS (VIEW), and the packages FND_PROFILE, HR_GENERAL, HR_SECURITY, PA_MULTI_CURRENCY, PA_TASK_UTILS, and PA_UTILS4. In practice, these references indicate that the underlying view applies:

• Profile option resolution via FND_PROFILE (for example, currency and reporting preferences).
• Organization and person security through HR_SECURITY and HR_GENERAL.
• Currency conversion and rate-type resolution through PA_MULTI_CURRENCY.
• Task and project utility derivations through PA_TASK_UTILS and PA_UTILS4.

Consequently, querying this view invokes security and currency logic that must be considered when planning performance or diagnosing row visibility differences between users.

Key Columns

The view exposes thirty-five columns spanning three logical groupings. Purchasing identifiers include REQ_NUMBER, DOCUMENT_TYPE, REQ_LINE, REQUISITION_HEADER_ID, REQUISITION_LINE_ID, and REQ_DISTRIBUTION_ID, providing the join path back to requisition header and line data. Descriptive and supplier attributes include ITEM_DESCRIPTION, NEED_BY_DATE, CREATION_DATE, VENDOR_NAME, VENDOR_ID, REQUESTOR_PERSON_ID, and REQUESTOR_NAME.

Quantity and value columns comprise UNIT, UNIT_PRICE, QUANTITY, DENOM_CURRENCY_CODE, DENOM_AMOUNT, ACCT_CURRENCY_CODE, and AMOUNT, complemented by exchange rate metadata: ACCT_RATE_DATE, ACCT_RATE_TYPE, and ACCT_EXCHANGE_RATE. Project and task context is supplied by PROJECT_NUMBER, PROJECT_NAME, TASK_NUMBER, TASK_NAME, PROJECT_ID, and TASK_ID. Expenditure classification is provided by EXPENDITURE_TYPE, EXPENDITURE_CATEGORY, REVENUE_CATEGORY, EXPENDITURE_ITEM_DATE, EXPENDITURE_ORGANIZATION, and EXPENDITURE_ORGANIZATION_ID.

Common Use Cases and Queries

Typical scenarios include commitment reporting for a project or task, reconciliation of requisition commitments against project budgets, and forecasting of future expenditure based on approved but unpurchased demand. Analysts frequently filter on PROJECT_NUMBER or EXPENDITURE_ITEM_DATE and aggregate AMOUNT by EXPENDITURE_CATEGORY or TASK_NUMBER.

• Commitments by project:

  SELECT PROJECT_NUMBER, PROJECT_NAME, SUM(AMOUNT) COMMITMENT
  FROM APPS.PA_PROJ_APPR_REQ_DISTRIBUTIONS
  GROUP BY PROJECT_NUMBER, PROJECT_NAME;

• Detail by task and expenditure type:

  SELECT REQ_NUMBER, TASK_NUMBER, EXPENDITURE_TYPE, QUANTITY, AMOUNT
  FROM APPS.PA_PROJ_APPR_REQ_DISTRIBUTIONS
  WHERE PROJECT_NUMBER = :project_number;

• Currency exposure:

  SELECT DENOM_CURRENCY_CODE, ACCT_CURRENCY_CODE, ACCT_RATE_TYPE, SUM(DENOM_AMOUNT), SUM(AMOUNT)
  FROM APPS.PA_PROJ_APPR_REQ_DISTRIBUTIONS
  GROUP BY DENOM_CURRENCY_CODE, ACCT_CURRENCY_CODE, ACCT_RATE_TYPE;

Because row visibility is governed by HR security and profile settings, reports should be run under a responsibility whose security profile matches the intended project organizations.