Search Results po_requisition_headers_all

Overview

The PO_REQUISITION_HEADERS_ALL table is a core transactional entity within Oracle E-Business Suite Purchasing (PO) module. It serves as the master header record for purchase requisitions, which are formal internal requests for the procurement of goods or services. Each row in this table represents a single, unique requisition document, establishing its fundamental attributes, approval status, and sourcing method. As an "ALL" table, it is multi-organization enabled, storing data for all operating units defined within the instance, which is critical for deployments with shared service centers or complex organizational structures. The table's integrity is enforced by primary keys on REQUISITION_HEADER_ID and SEGMENT1, ensuring each requisition has a unique system identifier and document number.

Key Information Stored

The table's columns capture the essential metadata for a requisition header. The primary identifier is REQUISITION_HEADER_ID, a unique system-generated sequence. The SEGMENT1 column stores the human-readable requisition number, often displayed in application screens and reports. Other critical columns typically include PREPARER_ID (linking to the employee who created it), AUTHORIZATION_STATUS (tracking the approval workflow state), TYPE_LOOKUP_CODE (defining the requisition type, such as Purchase or Internal), and DESCRIPTION. It also contains organizational context via ORG_ID and sourcing directives such as SOURCE_TYPE_CODE. Dates for preparation, last update, and approval are standard, along with control attributes for processing and interfacing with other modules like General Ledger.

Common Use Cases and Queries

This table is central for requisition reporting, audit trails, and integration processes. Common analytical queries involve joining with PO_REQUISITION_LINES_ALL to assess requisition volume, value, and item details. A typical pattern is to retrieve requisition headers pending approval or created within a specific date range for a given operating unit. For troubleshooting, one might query the header to understand the lifecycle of a requisition referenced in an error from a downstream interface. Sample SQL to find requisitions by number and status is:

• SELECT segment1, authorization_status, prepared_date FROM po_requisition_headers_all WHERE segment1 = '<REQ_NUMBER>' AND org_id = <ORG_ID>;

Integration use cases include drop-ship sales orders linking via OE_DROP_SHIP_SOURCES, kanban replenishment via MTL_KANBAN_CARD_ACTIVITY, and supply planning through MTL_SUPPLY.

Related Objects

PO_REQUISITION_HEADERS_ALL has extensive relationships across the EBS suite. Its most direct child is the PO_REQUISITION_LINES_ALL table, which holds the detailed line items for each header. As indicated by the foreign key metadata, it is referenced by numerous transactional and interface tables. Key dependencies include:

• PO_REQUISITION_LINES_ALL: Core child table for line details.
• PO_ACTION_HISTORY / PO_NOTIFICATIONS_ALL: Track approval workflow and notifications.
• MTL_SUPPLY / MTL_KANBAN_CARD_ACTIVITY: Integrate with Inventory and Manufacturing for material planning.
• OE_DROP_SHIP_SOURCES: Links to Order Management for drop-ship fulfillment.
• PO_REQUISITIONS_INTERFACE_ALL: Serves as the target for data imported via the Requisitions Open Interface.
• PO_PURGE_REQ_LIST / PO_HISTORY_REQUISITIONS_ALL: Support data archival and purge processes.

These relationships underscore the table's pivotal role as the authoritative source for requisition header data, feeding procurement, financial, and supply chain execution processes.