Search Results po_reqexpress_lines_all

Overview

The PO_REQEXPRESS_LINES_ALL table is a core data repository within the Oracle E-Business Suite Purchasing (PO) module. It stores the line-level details for express requisition templates, which are standardized forms used to streamline and expedite the creation of requisitions for frequently ordered items or services. These templates, defined in the PO_REQEXPRESS_HEADERS_ALL table, allow users to quickly generate requisitions by populating predefined values, thereby enforcing procurement policies and reducing data entry errors. The table's multi-org structure, indicated by the "_ALL" suffix, supports multiple operating units within a single installation.

Key Information Stored

The table's primary key, comprised of EXPRESS_NAME and SEQUENCE_NUM, uniquely identifies each line within a specific express template. Key columns store critical procurement data for each template line. This includes suggested sourcing information such as SUGGESTED_VENDOR_ID, SUGGESTED_VENDOR_SITE_ID, and SUGGESTED_BUYER_ID. Item or category details are captured in CATEGORY_ID and ITEM_ID columns. The LINE_TYPE_ID defines the type of purchase (e.g., Goods, Services). For templates linked to existing purchase orders, PO_HEADER_ID and PO_LINE_ID provide references. Other columns store descriptive information (DESCRIPTION), quantity (QUANTITY), unit of measure (UNIT_MEAS_LOOKUP_CODE), and pricing data, forming a comprehensive template blueprint.

Common Use Cases and Queries

Primary use cases involve auditing template usage, troubleshooting requisition creation, and generating custom reports on procurement patterns. Common analytical queries include listing all lines for a specific template to understand its full composition or identifying templates that suggest a particular vendor for spend analysis. For instance, a query to audit template completeness might join to the headers table and check for critical missing suggested data. When an express requisition is created, the application uses this table as the source to populate the requisition lines (PO_REQUISITION_LINES_ALL). Technical support often queries this table to verify the template data that propagated to a problematic requisition, using the express name as the key filter.

Related Objects

The table maintains extensive foreign key relationships with other Purchasing and Inventory entities, central to its role in the application's data model.

• PO_REQEXPRESS_HEADERS_ALL: Joined via EXPRESS_NAME. This is the parent table containing the template header.
• PO_VENDORS & PO_VENDOR_SITES_ALL: Joined via SUGGESTED_VENDOR_ID and SUGGESTED_VENDOR_SITE_ID, respectively, to provide supplier details.
• PO_AGENTS: Joined via SUGGESTED_BUYER_ID to identify the proposed buyer.
• PO_HEADERS_ALL & PO_LINES_ALL: Joined via PO_HEADER_ID and PO_LINE_ID for templates created from an existing purchase order line.
• PO_LINE_TYPES_B: Joined via LINE_TYPE_ID to define the procurement line type.
• MTL_CATEGORIES_B: Joined via CATEGORY_ID for catalog-based purchasing.
• PO_VENDOR_CONTACTS: Joined via SUGGESTED_VENDOR_CONTACT_ID.