Results for “po_reqexpress_lines_all”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PO_REQEXPRESS_LINES_ALL is a Purchasing (PO) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the line-level definitions of Express Requisition templates. Express Requisitions allow buyers and requesters to pre-build reusable requisition content — commonly recurring items, suggested suppliers, negotiated pricing, and sourcing attributes — so that repetitive requisitions can be generated quickly without re-entering identical data. The header of each template resides in PO_REQEXPRESS_HEADERS_ALL, while this table holds one row per template line. The schema owner is PO, and the object is documented as VALID with 75 columns in ETRM 12.2.2.

From a data-modeling perspective, the metadata classifies this object heuristically as a link table. That classification is a modeling suggestion rather than a functional constraint: the table primarily connects an express requisition template to external master and transactional entities (items, categories, vendors, vendor sites, contacts, buyers, and reference purchase documents) rather than serving as an independent hub.

Key Information Stored

The table's structure distinguishes a composite business key from descriptive and foreign-key attributes.

Common Use Cases and Queries

Functional users typically access this table indirectly through the Purchasing Express Requisition setup forms, but reporting and integration scenarios read it directly. A common pattern retrieves the lines of a specific template:

  • SELECT sequence_num, item_id, suggested_quantity, unit_price, suggested_vendor_id FROM po_reqexpress_lines_all WHERE express_name = :p_name ORDER BY sequence_num;
  • Join to PO_REQEXPRESS_HEADERS_ALL on EXPRESS_NAME to report template-level metadata alongside lines.
  • Join to PO_VENDORS and PO_VENDOR_SITES_ALL to validate that suggested suppliers and sites remain active before requisition creation.
  • Join to MTL_CATEGORIES_B via CATEGORY_ID for category-based spend analysis of recurring requisition content.
  • Filter by ORG_ID to scope reporting to a single operating unit.
  • Audit queries filter on LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATED_PROGRAM to trace template maintenance.

Related Objects

The FK relationships documented for this table define the primary reference surface:

  • PO_REQEXPRESS_HEADERS_ALL: parent table joined via EXPRESS_NAME.
  • PO_LINES_ALL and PO_HEADERS_ALL: referenced through PO_LINE_ID and PO_HEADER_ID for template lines copied from existing purchases.
  • PO_LINE_TYPES_B: referenced via LINE_TYPE_ID.
  • PO_VENDORS, PO_VENDOR_SITES_ALL, PO_VENDOR_CONTACTS: referenced through SUGGESTED_VENDOR_ID, SUGGESTED_VENDOR_SITE_ID, and SUGGESTED_VENDOR_CONTACT_ID.
  • PO_AGENTS: referenced via SUGGESTED_BUYER_ID for the default buyer.
  • MTL_CATEGORIES_B: referenced via CATEGORY_ID and IP_CATEGORY_ID.

Standard form and API access to these templates is exposed through the Purchasing Express Requisition setup and requisition creation flows, which read and populate this table rather than requiring direct DML.