Search Results po_reqexpress_headers_all




Overview
Explore in AI Chat

Overview

The PO_REQEXPRESS_HEADERS_ALL table is a core data structure within the Oracle E-Business Suite Purchasing (PO) module, specifically for versions 12.1.1 and 12.2.2. As indicated by its description, it stores the header-level information for templates used in creating express requisitions. Express requisitions are simplified, template-driven requisitions that enable users to quickly request frequently ordered items without navigating the full, standard requisition entry process. This table acts as the master definition for these reusable templates, holding the template's identifying and descriptive attributes. Its ALL suffix signifies it is a multi-organization table, meaning it stores data partitioned by the ORG_ID (Operating Unit) to support a multi-org architecture.

Key Information Stored

The table's primary purpose is to define and identify each unique express requisition template. The most critical column is EXPRESS_NAME, which serves as the unique identifier for a template and is the primary key (PO_REQEXPRESS_HEADERS_UK1). While the provided ETRM excerpt does not list all columns, typical columns in such a header table would include CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and DESCRIPTION to provide an overview of the template's purpose. The ORG_ID column is essential for determining the operating unit context. Other likely columns control template availability and usage, such as an ACTIVE flag or START_DATE and END_DATE columns.

Common Use Cases and Queries

This table is central to the administration and reporting of express requisition templates. Common functional and technical activities include auditing template usage, identifying templates by operating unit, and troubleshooting data integrity. A fundamental query retrieves all active templates for a specific operating unit:

  • SELECT express_name, description, creation_date FROM po_reqexpress_headers_all WHERE org_id = :org_id AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);

For reporting purposes, one might join this table to the lines table (PO_REQEXPRESS_LINES_ALL) to generate a complete list of items defined within each template. Data fix scripts often reference the EXPRESS_NAME from this table to correct or purge related line data. Understanding the templates defined in this table is also crucial for supporting users who utilize the express requisitions functionality.

Related Objects

The primary related object is the PO_REQEXPRESS_LINES_ALL table, which stores the individual item lines associated with each template header. As documented in the foreign key relationship, PO_REQEXPRESS_LINES_ALL.EXPRESS_NAME references PO_REQEXPRESS_HEADERS_ALL.EXPRESS_NAME. This creates a one-to-many relationship where a single header template can have multiple item lines. The table is also integral to the underlying APIs and forms that drive the "Requisition Templates" and "Create Requisitions from Templates" functions within the Purchasing application. While not explicitly listed in the excerpt, it is often joined in views that provide consolidated reporting on requisition templates.