Search Results distribution_quantity




Overview
Explore in AI Chat

Overview

APPS.POBV_REQUISITION_DISTRIBUTIONS is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2, registered under FND Design Data PO.POBV_REQUISITION_DISTRIBUTIONS. The view exposes accounting distribution information for requisition lines. Each row represents a single distribution on a purchase requisition line, combining the distribution record itself with descriptive information carried on the parent requisition header and line. Because it is a BIS view, it is intended for reporting, ad hoc query, and integration consumption rather than for transactional update. It presents a denormalized, read-only perspective that joins distribution, line, header, and operating unit attributes into a single access point, enabling tools and interfaces to retrieve requisition distribution detail without writing multi-table joins against the underlying PO tables. For users who search on "requisition_document_number," this view is significant because it exposes REQUISITION_DOCUMENT_NUMBER as a VARCHAR2(20) column, allowing requisition header document numbers to be reported and filtered directly alongside their distribution-level accounting attributes.

Underlying Base Objects

The documented base objects referenced by the view are PO_REQ_DISTRIBUTIONS_ALL, PO_REQUISITION_LINES_ALL, PO_REQUISITION_HEADERS_ALL, and HR_ALL_ORGANIZATION_UNITS, all accessed through APPS synonyms. PO_REQ_DISTRIBUTIONS_ALL supplies the distribution-level records and is keyed by REQUISITION_DISTRIBUTION_ID. PO_REQUISITION_LINES_ALL provides line context and the LINE_NUMBER column. PO_REQUISITION_HEADERS_ALL supplies header attributes, including REQUISITION_DOCUMENT_NUMBER and the operating unit reference. HR_ALL_ORGANIZATION_UNITS resolves the operating unit identifier to a descriptive name, exposed as OPERATING_UNIT_NAME. The relationships follow the standard requisition hierarchy: header to line to distribution, with the operating unit joined for descriptive reporting. This structure means the view reflects only requisitions that have distributions, and distribution rows without valid parent records are not retrievable through normal joins.

Key Columns

Common Use Cases and Queries

Typical uses include reconciling requisition commitments, reporting encumbered distribution amounts by operating unit, and extracting distribution detail for interfaces. A representative query retrieves distributions for a given requisition document number:

SELECT requisition_document_number, line_number, distribution_number, operating_unit_name, distribution_quantity, encumbered_amount, req_line_currency_amount FROM apps.pobv_requisition_distributions WHERE requisition_document_number = 'REQ-10023' ORDER BY line_number, distribution_number;

A second common pattern aggregates encumbrance by operating unit:

SELECT operating_unit_name, SUM(encumbered_amount) total_encumbered FROM apps.pobv_requisition_distributions GROUP BY operating_unit_name;

Because the view is a reporting construct, queries should apply the required operating unit and ledger security context appropriate to the calling application.