Search Results requisition_document_number




Overview
Explore in AI Chat

Overview

POBV_REQUISITION_DISTRIBUTIONS is an APPS-owned read-only database view in the Oracle E-Business Suite Purchasing (PO) module, documented in ETRM as "Retrofitted" and current through release 12.2.2. It presents requisition distribution information by joining the distribution-level records of PO_REQ_DISTRIBUTIONS_ALL to their parent requisition lines and headers, and resolves the inventory organization identifier to a descriptive organization unit name. The view therefore functions as a denormalized reporting and integration surface for purchase requisition accounting distributions.

Its role is chiefly analytical and interface-oriented: it consolidates the distribution rows that carry accounting, encumbrance, budgetary control, project, and tax attributes into a single queryable object, eliminating the need for report developers to reconstruct the header-line-distribution hierarchy themselves. Because the definition is declared WITH READ ONLY and includes operating-unit security through the '_SEC:RD.ORG_ID' predicate, it is intended for inquiry and extraction rather than transactional update. The _LA: pseudo-column expressions embedded in the definition signal that the view is exposed through Oracle's application framework with attribute-level value translation, for example mapping YES/NO lookup codes and GL lookup meanings for fields such as the encumbrance and funds-check flags.

Underlying Base Objects

The documented base objects are PO_REQ_DISTRIBUTIONS_ALL, PO_REQUISITION_LINES_ALL, PO_REQUISITION_HEADERS_ALL, and HR_ALL_ORGANIZATION_UNITS (all referenced through APPS synonyms). The join path is hierarchical:

The distribution table is the driving table; line and header tables supply lineage and document identity, while the organization table supplies the operating unit name. The view is bound by operating-unit security on the distribution's ORG_ID, meaning only distributions for the session's authorized operating units are returned.

Key Columns

Common Use Cases and Queries

Typical uses include reconciling encumbered versus unencumbered distribution amounts, auditing allocation apportionment, monitoring failed funds checks, extracting project-related requisition distributions, and feeding downstream reporting on tax recovery and GL close status. A representative query returning allocation detail for a requisition document is:

  • SELECT DISTRIBUTION_NUMBER, LINE_NUMBER, REQUISITION_DOCUMENT_NUMBER, OPERATING_UNIT_NAME, ALLOCATION_TYPE, ALLOCATION_VALUE, REQ_LINE_AMOUNT, ENCUMBERED_AMOUNT FROM APPS.POBV_REQUISITION_DISTRIBUTIONS WHERE REQUISITION_DOCUMENT_NUMBER = :segment1 AND ALLOCATION_VALUE IS NOT NULL;
  • SELECT OPERATING_UNIT_NAME, SUM(REQ_LINE_AMOUNT), SUM(ENCUMBERED_AMOUNT) FROM APPS.POBV_REQUISITION_DISTRIBUTIONS WHERE TRUNC(CREATION_DATE) BETWEEN :start_date AND :end_date GROUP BY OPERATING_UNIT_NAME;
  • SELECT DISTRIBUTION_ID, REQUISITION_DOCUMENT_NUMBER, FAILED_FUNDS_LOOKUP_CODE FROM APPS.POBV_REQUISITION_DISTRIBUTIONS WHERE ENCUMBERED_FLAG = 'N' AND FAILED_FUNDS_LOOKUP_CODE IS NOT NULL;

Because the view is read-only and secured by operating unit, it is safe for ad hoc inquiry, BI Publisher data sources, and interface extracts, but it must not be used as a target for DML.