Search Results hz_cust_accounts




Overview
Explore in AI Chat

Overview

OE_HEADER_ACKS is a transactional table in the ONT (Order Management) schema that stores acknowledgement information exchanged between Oracle E-Business Suite and external trading partners for order headers. In Oracle EBS 12.1.1 and 12.2.2, this table functions as the inbound/outbound staging ground for acknowledgement documents processed through Order Management's XML/EDI message framework. When an order is transmitted to a customer or supplier and an acknowledgement is returned (for example, an Order Acknowledgment or Purchase Order Acknowledgment message), the header-level attributes of that acknowledgement are persisted here for validation, error handling, and downstream booking.

The table carries 342 documented columns in the 12.2.2 ETRM schema, reflecting its role as a wide, denormalized interface representation of the order header. Because it is keyed by HEADER_ID referencing OE_ORDER_HEADERS_ALL, a Data Vault heuristic classifies this object as a link — it associates an order header with its acknowledgement context and the parties, organizations, and reference data surrounding that acknowledgement. This classification is a modeling suggestion only; in native EBS terms the table is a transactional detail table, not a hub or satellite.

Key Information Stored

The most consequential columns fall into four groups:

The surrogate primary key is HEADER_ID. Business-key candidates include ORDER_NUMBER within an operating unit and ORIG_SYS_DOCUMENT_REF combined with ORDER_SOURCE_ID. Standard EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and the ATTRIBUTE1–ATTRIBUTE20/GLOBAL_ATTRIBUTE1–20 flexfields are present for extensibility.

Common Use Cases and Queries

Typical scenarios include reconciling inbound acknowledgement messages that failed validation, reporting on acknowledgement turnaround times, and auditing which orders received acknowledgements before booking.

  • Pending acknowledgements by status: SELECT ORDER_NUMBER, FIRST_ACK_CODE, LAST_ACK_DATE FROM OE_HEADER_ACKS WHERE ACKNOWLEDGMENT_FLAG = 'Y' AND INTERFACE_STATUS = 'PENDING';
  • Error triage: filter on ERROR_FLAG = 'Y' or non-null INTERFACE_STATUS to isolate failed messages awaiting correction and resubmission.
  • Turnaround metrics: compute LAST_ACK_DATE - FIRST_ACK_DATE per ORDER_SOURCE_ID to measure trading-partner responsiveness.
  • Reporting joins: link to OE_ORDER_HEADERS_ALL on HEADER_ID to enrich acknowledgement data with booked order detail.

Because the table is interface-oriented and can be large, queries should always be filtered by ORG_ID, ORDER_SOURCE_ID, or a date range on CHANGE_DATE/LAST_ACK_DATE to avoid full scans.

Related Objects

The documented foreign keys identify the principal related objects: