Search Results po_requisition_lines_all

Overview

The PO_REQUISITION_LINES_ALL table is a core transactional entity within Oracle E-Business Suite Purchasing (PO) module for versions 12.1.1 and 12.2.2. It stores the detailed line-level information for every purchase requisition created in the system. Each record in this table represents a specific item or service requested, linking to its parent requisition header. As a multi-organization table (indicated by the '_ALL' suffix), it contains data for all operating units, with access typically controlled by a security profile. This table is fundamental to the requisitioning process, capturing the material, quantity, pricing, and sourcing details that are later used for purchase order creation, sourcing, and requisition reporting.

Key Information Stored

The table's primary key is REQUISITION_LINE_ID, which uniquely identifies each requisition line. Critical foreign keys define its relationships within the application. REQUISITION_HEADER_ID links the line to its parent document in PO_REQUISITION_HEADERS_ALL. Key descriptive and transactional columns include ITEM_ID, ITEM_DESCRIPTION, QUANTITY, UNIT_PRICE, and LINE_TYPE_ID (linking to PO_LINE_TYPES_B). Sourcing and supplier information is captured via SUGGESTED_BUYER_ID, VENDOR_ID, VENDOR_SITE_ID, and BLANKET_PO_HEADER_ID. The table also integrates with other EBS modules through columns like CATEGORY_ID (Inventory), WIP_ENTITY_ID (Work in Process), TAX_CODE_ID (Payables), and CURRENCY_CODE. The PARENT_REQ_LINE_ID supports complex requisition structures.

Common Use Cases and Queries

This table is central for requisition inquiry, audit reporting, and data extraction for interfaces. Common scenarios include tracking requisition status, analyzing spend by category or requestor, and identifying lines sourced from blanket agreements. A typical query joins to the header table and relevant lookup tables:

• Requisition Line Detail Report: SELECT prl.requisition_line_id, prh.segment1 req_num, prl.line_num, prl.item_description, prl.quantity, prl.unit_price, prl.need_by_date FROM po_requisition_lines_all prl, po_requisition_headers_all prh WHERE prl.requisition_header_id = prh.requisition_header_id AND prh.org_id = :p_org_id;
• Lines Linked to a Blanket Purchase Order: SELECT * FROM po_requisition_lines_all WHERE blanket_po_header_id IS NOT NULL;
• Requisition Analysis by Category: SELECT mc.segment1 category, SUM(prl.quantity * prl.unit_price) total_amount FROM po_requisition_lines_all prl, mtl_categories_b mc WHERE prl.category_id = mc.category_id GROUP BY mc.segment1;

Related Objects

PO_REQUISITION_LINES_ALL has extensive relationships, as shown in the metadata. Its primary parent is PO_REQUISITION_HEADERS_ALL. It is a key source for downstream procurement processes, referenced by PO_LINE_LOCATIONS_ALL when requisition lines are converted to purchase order shipments. Key foreign key dependencies include PO_LINE_TYPES_B, PO_AGENTS, MTL_CATEGORIES_B, PO_VENDORS, and FND_CURRENCIES. It is also referenced by other modules, such as AHL_OSP_ORDER_LINES (Complex Maintenance) and JAI_PO_REQ_LINES (Localizations), demonstrating its integration scope. For programmatic access, developers typically use the PO_REQUISITIONS_PKG or PO_REQ_LINES_PKG APIs rather than direct DML.