Results for “oe_line_acks”

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

Overview

OE_LINE_ACKS is an Order Management (ONT) transactional table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores acknowledgement information for order lines. In the Order-to-Cash flow, it holds the outbound acknowledgment records that communicate order line details — quantities, dates, pricing, shipping, and customer information — back to the requesting party, typically through EDI or XML processing. The table is owned by the ONT schema and is documented as VALID in the ETRM repository.

The physical schema documented for 12.2.2 contains 522 columns, reflecting the wide, denormalized structure characteristic of Order Management interface and staging tables. Records are keyed by HEADER_ID and LINE_ID, with CHANGE_SEQUENCE and CHANGE_DATE supporting versioned acknowledgment history. Based on the foreign key topology mined from the metadata — which shows this table referencing OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, and numerous HZ and RA master tables — a Data Vault modeling heuristic would suggest classifying OE_LINE_ACKS as a link entity, since it primarily captures relationships and events between order headers, order lines, customers, and reference masters rather than serving as a standalone hub.

Key Information Stored

The columns below are the most operationally significant for Order Management and integration work:

• HEADER_ID — Foreign key to OE_ORDER_HEADERS_ALL, tying the acknowledgment record to its parent order.
• LINE_ID and LINE_NUMBER — Order line identifier and user-visible line number.
• ORIG_SYS_DOCUMENT_REF and ORIG_SYS_LINE_REF — Original system document and line references, essential for EDI/XML correlation.
• CHANGE_SEQUENCE and CHANGE_DATE — Versioning columns that identify the acknowledgment iteration.
• ACKNOWLEDGMENT_FLAG, FIRST_ACK_CODE, LAST_ACK_CODE, FIRST_ACK_DATE, LAST_ACK_DATE — Acknowledgment status and timing history.
• ORDERED_QUANTITY, SHIPPED_QUANTITY, CANCELLED_QUANTITY, FULFILLED_QUANTITY — Quantity fields carried on the acknowledgment.
• PROMISE_DATE, SCHEDULE_SHIP_DATE, SCHEDULE_ARRIVAL_DATE — Commitment dates communicated to the customer.
• INVENTORY_ITEM_ID and ORDERED_ITEM — Item identification on the acknowledged line.
• SHIP_TO_CUSTOMER_ID, INVOICE_TO_CUSTOMER_ID, DELIVER_TO_CUSTOMER_ID — Customer party references (FKs to HZ_CUST_ACCOUNTS).
• UNIT_SELLING_PRICE and UNIT_LIST_PRICE — Pricing sent with the acknowledgment.
• ORG_ID — Multi-org operating unit identifier.
• TOP_MODEL_LINE_ID — References the top model line for configured items in OE_ORDER_LINES_ALL.

No surrogate primary key column is named in the documented metadata; the table functions as an interface/staging structure where HEADER_ID, LINE_ID, and CHANGE_SEQUENCE together form the effective business key for a given acknowledgment version. The presence of ORIG_SYS_DOCUMENT_REF and ORIG_SYS_LINE_REF further supports their use as external business-key candidates.

Common Use Cases and Queries

Typical scenarios include EDI 855 acknowledgment extraction, reconciliation of acknowledged versus ordered quantities, and audit reporting on change history.

• Acknowledgment status reporting — join OE_LINE_ACKS to OE_ORDER_HEADERS_ALL to list orders with outstanding or rejected acknowledgments for a date range.
• Quantity reconciliation — compare ORDERED_QUANTITY, SHIPPED_QUANTITY, and CANCELLED_QUANTITY by LINE_ID to detect fulfillment gaps.
• EDI/interface extraction — select records by CHANGE_SEQUENCE and ORIG_SYS_DOCUMENT_REF to build outbound acknowledgment messages.
• Change history audit — filter by LAST_ACK_DATE and LAST_ACK_CODE to trace the latest acknowledgment state per line.

A representative query pattern selects a.header_id, a.line_id, a.change_sequence, a.last_ack_code, a.ordered_quantity from oe_line_acks a where a.org_id = :org_id and a.last_ack_date between :from_date and :to_date, joined to oe_order_headers_all h on h.header_id = a.header_id.

Related Objects

The most significant related objects, based on documented foreign key relationships, are:

• OE_ORDER_HEADERS_ALL — joined via HEADER_ID; provides the parent order context.
• OE_ORDER_LINES_ALL — joined via TOP_MODEL_LINE_ID; supplies the order line and configuration hierarchy.
• HZ_CUST_ACCOUNTS — referenced through SHIP_TO_CUSTOMER_ID, INVOICE_TO_CUSTOMER_ID, DELIVER_TO_CUSTOMER_ID, and END_CUSTOMER_ID.
• HZ_CUST_ACCT_SITES_ALL — referenced via SHIP_TO_ADDRESS_ID for ship-to address detail.
• HZ_CUST_SITE_USES_ALL — referenced via END_CUSTOMER_SITE_USE_ID.
• HR_ALL_ORGANIZATION_UNITS — referenced by SHIP_FROM_ORG_ID and SOLD_FROM_ORG_ID for warehouse and selling organization identification.
• RA_RULES — referenced by ACCOUNTING_RULE_ID and INVOICING_RULE_ID for revenue and billing schedules.
• RA_TERMS_B and RA_SALESREPS_ALL — provide payment terms and sales representative defaults.
• OE_ORDER_SOURCES — referenced by ORDER_SOURCE_ID to identify the originating order channel.
• PON_OFFER_COMMITMENTS, CST_COST_TYPES, MTL_CUSTOMER_ITEMS, and PO_LINE_TYPES_B — supply commitment, costing, customer item, and line type references respectively.

Because OE_LINE_ACKS mirrors the OE_ORDER_LINES_ALL structure, most Order Management APIs and concurrent programs that export or import order acknowledgments interact with it directly or through dependent interface tables.