Results for “po_text_hdr”

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

Overview

PO_TEXT_HDR is the header text table for the Oracle Process Manufacturing (OPM) Purchasing application, owned by the GML schema. In Oracle EBS 12.1.1 and 12.2.2, it serves as the central repository for text identifiers that are referenced by purchasing documents across the OPM Logistics module. Rather than storing the text content itself, PO_TEXT_HDR holds the master key (TEXT_CODE) that anchors descriptive text to vendors, orders, receipts, returns, costs, and blanket purchase orders. This design centralizes text handling and allows many transactional and master records to share a single, standardized text reference.

From a Data Vault modeling perspective, the heuristic classification for this table is hub-leaning. PO_TEXT_HDR behaves as a business hub whose primary key, TEXT_CODE, is referenced as a foreign key by numerous surrounding tables. It is not a link table (it does not resolve a many-to-many relationship between two hubs) and not a satellite (it does not carry descriptive attributes beyond audit columns). This classification is offered as a modeling suggestion mined from the foreign key structure rather than as an official Oracle designation.

Key Information Stored

The documented physical schema contains six columns in the GML schema. The most significant are listed below.

• TEXT_CODE — The primary key of the table and the sole business-key candidate. Defined through the unique index PO_TEXT_HDR_PK, it uniquely identifies each text header record and is the column referenced by every dependent foreign key in the OPM Purchasing table set.
• LAST_UPDATE_DATE — Timestamp of the most recent modification to the row, used for audit and incremental extract logic.
• LAST_UPDATED_BY — The application user identifier responsible for the last change.
• LAST_UPDATE_LOGIN — The login identifier associated with the last update, supporting session-level auditing.
• CREATION_DATE — Timestamp when the text header row was first created.
• CREATED_BY — The application user identifier that created the row.

The surrogate key is effectively TEXT_CODE itself; no separate numeric surrogate is documented. The remaining five columns are standard EBS WHO columns used for auditability and change tracking, and they play no role in joining or business identification.

Common Use Cases and Queries

The principal use case for PO_TEXT_HDR is resolving text references on OPM purchasing documents. A typical query joins a transactional table to the header text table to confirm or validate the text code assigned to a document.

• Text code validation — verifying that a TEXT_CODE on a purchase order header or detail exists in PO_TEXT_HDR before downstream processing.
• Referential integrity reporting — identifying orphaned TEXT_CODE values on dependent documents that no longer resolve to a header record.
• Audit and lineage — using LAST_UPDATED_BY and LAST_UPDATE_DATE to trace who established or modified a text header reference.
• Reconciliation extracts — pulling the set of active text codes for reporting on document text coverage across orders, receipts, and vendor master records.

A representative join pattern is: SELECT o.ORDER_NO, o.TEXT_CODE FROM PO_ORDR_HDR o, PO_TEXT_HDR t WHERE o.TEXT_CODE = t.TEXT_CODE; Equivalent joins apply to PO_ORDR_DTL, PO_RECV_HDR, PO_RECV_DTL, PO_VEND_MST, and the other dependent tables. Counts of dependents by document type are frequently used to gauge how widely text headers are reused.

Related Objects

PO_TEXT_HDR is referenced by a broad set of OPM purchasing and vendor tables through the shared TEXT_CODE column. The most significant are listed below.

• PO_ORDR_HDR and PO_ORDR_DTL — purchase order header and detail, joined on TEXT_CODE.
• PO_RECV_HDR, PO_RECV_DTL, and PO_RECV_HST — receiving header, detail, and history.
• PO_RTRN_HDR and PO_RTRN_DTL — return header and detail.
• PO_VEND_MST, PO_VEND_CLS, PO_VEND_ASC — vendor master, classification, and association records.
• PO_BPOS_HDR and PO_BPOS_DTL — blanket purchase order header and detail.
• PO_COST_MST and PO_COST_DTL — cost master and detail.
• PO_DIST_DTL, PO_RELS_SCH, PO_VGLD_CLS, and PO_VTRD_CLS — distribution detail, release schedules, and vendor trade/grade classifications.

All of these objects carry a TEXT_CODE column that forms a foreign key back to the PO_TEXT_HDR primary key, confirming the table's role as the hub for text references throughout the OPM Purchasing application.