Results for “po_reqexpress_headers_uk1”

6 results




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

Overview

PO_REQEXPRESS_HEADERS_ALL is a Purchasing (PO) module table that stores template headers for express requisitions in Oracle E-Business Suite 12.1.1 and 12.2.2. Express requisitions allow buyers and requesters to create purchase requisitions rapidly by selecting a predefined template that carries default header-level attributes and associated line defaults. This table holds the header portion of those templates, while the corresponding line-level definitions are maintained in PO_REQEXPRESS_LINES_ALL. The object is owned by the PO schema and is classified as VALID in the ETRM 12.2.2 data model.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a hub-leaning classification. The table is referenced by PO_REQEXPRESS_LINES_ALL through the EXPRESS_NAME column, which indicates that it behaves as a business entity keyed by a natural identifier rather than a pure transactional or descriptive satellite. Each row represents a reusable express requisition template header, uniquely identified in the documentation by the primary key PO_REQEXPRESS_HEADERS_UK1 on EXPRESS_NAME.

Key Information Stored

The table contains 33 documented columns. The most significant are listed below.

  • EXPRESS_NAME — The business name of the express requisition template; the primary key component and the column referenced by PO_REQEXPRESS_LINES_ALL.
  • ORG_ID — Operating unit identifier; combined with EXPRESS_NAME in unique index PO_REQEXPRESS_HEADERS_U1, making (EXPRESS_NAME, ORG_ID) the principal business-key candidate.
  • DESCRIPTION — Free-text description of the template for user reference.
  • TYPE_LOOKUP_CODE — Lookup code classifying the requisition template type.
  • INACTIVE_DATE — Date on which the template becomes inactive and unavailable for use.
  • RESERVE_PO_NUMBER — Flag/indicator governing reservation of purchase order numbering for requisitions created from the template.
  • USSGL_TRANSACTION_CODE — Government accounting transaction code used in federal/Public Sector implementations.
  • GOVERNMENT_CONTEXT — Government-specific context flag associated with the template.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The standard EBS descriptive flexfield columns for capturing installation-specific template attributes.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns tracking record creation and modification.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program context columns identifying the request that created or last updated the row.

The surrogate primary key is PO_REQEXPRESS_HEADERS_UK1 on EXPRESS_NAME. The unique index PO_REQEXPRESS_HEADERS_U1 (EXPRESS_NAME, ORG_ID) represents the documented business-key candidate, reflecting that template names are unique per operating unit.

Common Use Cases and Queries

Typical reporting and integration scenarios include listing active templates for a given operating unit, identifying templates approaching or past their inactive date, and joining header and line template definitions to reproduce a complete template structure. A representative query returning active templates follows:

  • SELECT eh.express_name, eh.description, eh.type_lookup_code, eh.inactive_date FROM po.po_reqexpress_headers_all eh WHERE eh.org_id = :org_id AND (eh.inactive_date IS NULL OR eh.inactive_date > SYSDATE) ORDER BY eh.express_name;
  • SELECT eh.express_name, el.line_num, el.item_description FROM po.po_reqexpress_headers_all eh, po.po_reqexpress_lines_all el WHERE eh.express_name = el.express_name AND eh.org_id = :org_id;
  • Audit reporting on templates created or updated by concurrent programs, joining on REQUEST_ID and PROGRAM_ID against FND_CONCURRENT_REQUESTS.

Related Objects