Search Results document_purpose_code

Overview

OE_HEADER_ACKS_V is an Oracle E-Business Suite view owned by the APPS schema and defined within the Order Management (ONT) product family. As its name implies, the view exposes information about acknowledgements for order headers — the confirmation records that document how a trading partner responded to a purchase order transmitted through Oracle EDI/XML Gateway processing. It is a denormalized reporting and integration construct, joining the acknowledgement header table to customer, party, and trading partner data so that trading partner, customer account, and site information can be presented together with the acknowledgement itself.

The view is particularly relevant in order-to-cash and inbound order integrations, where sold-to, ship-to, and deliver-to party data flows alongside the acknowledgement status. For the searched term sold_to_address_id, OE_HEADER_ACKS_V is the natural access point: the underlying OE_HEADER_ACKS table carries the SOLD_TO_ORG_ID column, and the view publishes it as SOLD_TO_ORG_ID, complemented by SOLD_TO_ORG (the display value), SOLD_TO_PHONE_ID, and the customer identification columns resolved from HZ_CUST_ACCOUNTS and HZ_PARTIES.

Underlying Base Objects

The ETRM 12.2.2 metadata documents the following referenced objects: ECE_TP_DETAILS, ECE_TP_HEADERS, HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES, HZ_CUST_SITE_USES_ALL, HZ_PARTIES, and OE_HEADER_ACKS, all accessed through synonyms. OE_HEADER_ACKS is the driving table, supplying the acknowledgement-specific columns (FIRST_ACK_CODE, LAST_ACK_CODE, FIRST_ACK_DATE, LAST_ACK_DATE, ACKNOWLEDGMENT_FLAG). The HZ_* tables provide the resolved customer identity: HZ_CUST_ACCOUNTS supplies CUST_ACCOUNT_ID and ACCOUNT_NUMBER, while HZ_PARTIES supplies PARTY_NAME. HZ_CUST_ACCT_SITES and HZ_CUST_SITE_USES_ALL provide the site and site-use context referenced by the sold-to, ship-to, and deliver-to organization identifiers. The ECE_TP_HEADERS and ECE_TP_DETAILS tables supply trading partner header and detail context from the EDI/XML Gateway layer, linking the acknowledgement to the external trading partner exchange.

Key Columns

• HEADER_ID, ORDER_NUMBER, ORIG_SYS_DOCUMENT_REF, ORDERED_DATE, ORG_ID — the order header identity and originating document reference.
• SOLD_TO_ORG_ID, SOLD_TO_ORG, SOLD_TO_PHONE_ID — the sold-to organization and its display value and phone; these are the columns most relevant to the searched term, with the address reference carried via the sold-to organization identifier.
• CUSTOMER_ID, CUSTOMER_NAME, CUSTOMER_NUMBER — resolved through NVL from HA columns or HZ_CUST_ACCOUNTS / HZ_PARTIES.
• SHIP_TO_ORG_ID, SHIP_TO_ORG, SOLD_FROM_ORG_ID, SOLD_FROM_ORG, SHIP_FROM_ORG_ID, SHIP_FROM_ORG — party and warehouse location context.
• FIRST_ACK_CODE, LAST_ACK_CODE, FIRST_ACK_DATE, LAST_ACK_DATE, ACKNOWLEDGMENT_FLAG — acknowledgement status and timing.
• BOOKED_FLAG, CANCELLED_FLAG, CLOSED_FLAG, ERROR_FLAG — order lifecycle state.
• ATTRIBUTE1–ATTRIBUTE20, CONTEXT — DFF flexfield context and segments.

Common Use Cases and Queries

Typical scenarios include tracking acknowledgement codes and dates per order, resolving the sold-to customer name and number, and extracting sold-to/ship-to context for integration or reconciliation against EDI trading partner records.

Sample query retrieving acknowledgement and sold-to details:

SELECT ack.order_number,
       ack.orig_sys_document_ref,
       ack.sold_to_org_id,
       ack.sold_to_org,
       ack.customer_id,
       ack.customer_name,
       ack.first_ack_code,
       ack.last_ack_code,
       ack.last_ack_date
  FROM apps.oe_header_acks_v ack
 WHERE ack.org_id = :p_org_id
   AND ack.last_ack_date >= TRUNC(SYSDATE) - 7
 ORDER BY ack.last_ack_date DESC;

For trading partner reconciliation, join to ECE_TP_HEADERS and ECE_TP_DETAILS on the originating document reference to correlate acknowledgements with the transmitted order envelope and partner transaction details.