Search Results req_line_quantity




Overview
Explore in AI Chat

Overview

APPS.POR_DISTRIBUTIONS_ALL_V is a reporting and integration view in Oracle E-Business Suite that presents requisition distribution information enriched with allocation calculations derived from the parent requisition line. It exists primarily to expose a business-friendly projection of the underlying PO_REQ_DISTRIBUTIONS_ALL table, joining each distribution to its owning requisition line so that quantity, percentage, and monetary amount can be presented on a per-distribution basis. In the Oracle EBS 12.1.1 and 12.2.2 environments, this view is frequently encountered in Purchasing (PO) and iProcurement reporting, encumbrance analysis, and custom extensions that must display how a requisition line has been split across accounting distributions, projects, and tasks.

The view is documented in the ETRM repository under the APPS schema and is defined over the two core requisition tables. Because it derives calculated columns such as PERCENTAGE and AMOUNT rather than storing them, it is a read-only construct intended for query, not for DML. The column REQ_LINE_QUANTITY, which is the term the user searched for, appears both as a directly selected column and as the basis for several derived values.

Underlying Base Objects

According to the documented view definition, POR_DISTRIBUTIONS_ALL_V is defined as a join between two base objects, both referenced through synonyms in the APPS schema:

  • PO_REQ_DISTRIBUTIONS_ALL (aliased DIST) — the driving table holding the requisition distribution records.
  • PO_REQUISITION_LINES_ALL (aliased LINE) — the requisition line table supplying line-level quantity and unit price.

The join condition is DIST.REQUISITION_LINE_ID = LINE.REQUISITION_LINE_ID, a straightforward parent-child relationship. Every row in the view therefore represents one requisition distribution, augmented with attributes from its parent line. Because PO_REQ_DISTRIBUTIONS_ALL is the driving table and no outer join is applied to the line, distributions whose parent line is absent will not appear, though referential integrity normally prevents this situation. The view references both tables through APPS synonyms, meaning it must be queried as APPS.POR_DISTRIBUTIONS_ALL_V (or via a synonym) in both 12.1.1 and 12.2.2, where the underlying table structures are unchanged.

Key Columns

The view exposes the full set of distribution columns plus three derived expressions:

Common Use Cases and Queries

Typical scenarios include reconciling requisition distributions against budgets, auditing how a line quantity was apportioned, and feeding project cost collection. A representative query returning distribution quantities and their percentage share of the line is shown below.

SELECT d.requisition_line_id, d.distribution_num, d.req_line_quantity, d.percentage, d.amount, d.encumbered_flag
FROM apps.por_distributions_all_v d
WHERE d.requisition_line_id = :p_line_id
ORDER BY d.distribution_num;

Aggregation across a line confirms that allocations total the requisition quantity:

SELECT requisition_line_id, SUM(req_line_quantity) total_qty, SUM(percentage) total_pct
FROM apps.por_distributions_all_v
GROUP BY requisition_line_id;

Project-related distributions are commonly filtered using PROJECT_RELATED_FLAG, while encumbrance reporting joins on ENCUMBERED_FLAG and SET_OF_BOOKS_ID. Because the PERCENTAGE and AMOUNT columns are computed at query time, care should be taken when LINE.UNIT_PRICE or LINE.QUANTITY are null, since the derived values may then be null or undefined.