Search Results req_line_amount




Overview
Explore in AI Chat

Overview

PO_REQ_DISTRIBUTIONS_V is an APPS-owned view in the Oracle E-Business Suite Purchasing (PO) module. In the ETRM metadata it is described as "10SC ONLY - Retrofitted," indicating that this object originated as a custom or localized database object associated with a specific 10SC implementation and was subsequently retrofitted into the standard APPS schema for support in EBS 12.1.1 and 12.2.2. The view exposes the distribution-level detail of purchase requisitions, providing a reporting and integration layer over the transactional distribution records maintained by the core application.

The object is published with a status of VALID in the APPS schema, meaning it is accessible to custom reports, concurrent programs, forms personalizations, and external integrations that connect with the APPS credentials. Because it is a view and not a table, it carries no independent storage and reflects the state of its underlying base object at query time. Its principal role is to consolidate the requisition distribution attributes—including accounting flexfield references, encumbrance information, project and task associations, and tax recovery data—into a single queryable interface.

Underlying Base Objects

According to the documented view metadata for 12.2.2, PO_REQ_DISTRIBUTIONS_V is defined over a single referenced base object: PO_REQ_DISTRIBUTIONS, accessed through a synonym. The view text confirms this relationship with a straightforward projection: SELECT ... FROM PO_REQ_DISTRIBUTIONS.

The view does not perform joins to lookup tables, nor does it aggregate or restrict rows. It is a column-selective wrapper, meaning every distribution row present in PO_REQ_DISTRIBUTIONS is returned. The only transformation applied in the view text is the expression NVL(ENCUMBERED_FLAG, 'N'), which guarantees that the ENCUMBERED_FLAG column is never returned as NULL. All other columns map directly to their base table counterparts. Because the view reads from the synonym rather than a fully qualified table name, the resolution depends on the APPS schema synonym pointing to the PO base table.

Key Columns

Common Use Cases and Queries

The view is typically used to report on requisition distributions and their encumbrance status, including integration scenarios that extract distribution data for external budgeting or project systems. A representative query retrieving encumbered distributions for an operating unit is shown below.

  • Encumbrance reporting: SELECT distribution_id, requisition_line_id, encumbered_flag, encumbered_amount FROM po_req_distributions_v WHERE encumbered_flag = 'Y' AND org_id = :p_org_id;
  • Funds check failures: SELECT distribution_id, failed_funds_lookup_code, encumbered_amount FROM po_req_distributions_v WHERE failed_funds_lookup_code IS NOT NULL;
  • Project-related distributions: SELECT distribution_id, project_id, task_id, expenditure_type FROM po_req_distributions_v WHERE project_related_flag = 'Y';
  • GL encumbrance period analysis: SELECT gl_encumbered_period_name, SUM(encumbered_amount) FROM po_req_distributions_v GROUP BY gl_encumbered_period_name;

Because the view applies no row filtering and no joins, consumers should apply their own multi-org and date predicates and be aware that performance mirrors that of querying the base table directly.