Results for “customer_dock_code”

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

Overview

The OE_LINE_ACKS_V view is a reporting and integration object within the Oracle E-Business Suite Order Management (ONT) module. Owned by the APPS schema and holding a VALID status, it exposes acknowledgement information associated with order lines. In EBS 12.1.1 and 12.2.2, order acknowledgements represent the outbound confirmation returned to a customer reflecting the accepted state of an order line, including pricing, sourcing, and configuration attributes. This view is therefore central to any interface, extraction, or report that must publish acknowledged line details to external systems, customer portals, or downstream fulfilment and billing processes.

Because inbound order data flows into Order Management through the Order Capture and order import interfaces, the acknowledgement view serves as the canonical read-only projection of the acknowledged line state. It is not a transactional entry point; rather it is consumed for querying and outbound integration, allowing applications to retrieve acknowledgement-relevant attributes without navigating the full line table structure.

Underlying Base Objects

According to the documented view metadata for EBS 12.2.2, OE_LINE_ACKS_V is defined over the base object OE_LINE_ACKS, exposed through a synonym. In practice this means the view is a denormalised or filtered projection of the underlying acknowledgement record set, joined or resolved against related Order Management entities such as order headers, line details, and the transactional attributes stored on the acknowledgement table.

The view text selects a broad column list beginning with ORDER_SOURCE_ID, ORIG_SYS_DOCUMENT_REF, ORIG_SYS_LINE_REF, and ORIG_SYS_SHIPMENT_REF, which are the standard Order Management integration references used to correlate EBS records with external source documents. Because the view surfaces both internal identifiers and external references in a single row shape, it aligns with the Order Management integration model in which the acknowledgement is exchanged using the same reference keys originally supplied by the source system.

Key Columns

• CUSTOMER_PAYMENT_TERM_ID — The payment term identifier carried on the acknowledged line, directly relevant to the user's search term. It allows reporting of the agreed payment terms per acknowledged order line.
• ORDER_SOURCE_ID, ORIG_SYS_DOCUMENT_REF, ORIG_SYS_LINE_REF, ORIG_SYS_SHIPMENT_REF — Source-system correlation keys used for outbound integration and reconciliation.
• HEADER_ID, LINE_ID, LINE_NUMBER — Internal Order Management identifiers linking the acknowledgement to its header and line records.
• ACKNOWLEDGMENT_FLAG, BOOKED_FLAG, CANCELLED_FLAG, CLOSED_FLAG, AUTHORIZED_TO_SHIP_FLAG — Status indicators describing the acknowledgement and lifecycle state of the line.
• CUSTOMER_ITEM, PRICE_LIST, CUSTOMER_ITEM_NET_PRICE, AGREEMENT, INVOICING_RULE — Commercial attributes confirming price, agreement, and billing arrangements conveyed in the acknowledgement.
• SHIP_TO_ORG, SOLD_TO_ORG, INVOICE_TO_ORG, DELIVER_TO_ORG — Party and location context for the acknowledged line.
• FULFILLED_QUANTITY, CANCELLED_QUANTITY, EARLIEST_ACCEPTABLE_DATE, LATEST_ACCEPTABLE_DATE — Quantities and scheduling dates returned to the customer.

Common Use Cases and Queries

Typical uses include generating customer order acknowledgements, reconciling inbound orders against acknowledged state, and extracting payment term and pricing details for downstream billing. The following sample retrieves acknowledged lines with their payment terms and source references:

SELECT order_number, line_number, orig_sys_document_ref,
     customer_payment_term_id, price_list, customer_item_net_price,
     acknowledgment_flag, booked_flag
FROM apps.oe_line_acks_v
WHERE order_number = :p_order_number;

A second scenario filters on the source document reference to reconcile an externally originated order, and a third queries by CUSTOMER_PAYMENT_TERM_ID to report all acknowledged lines sharing a payment term. Because the view is read-only and joins acknowledgement data, it is well suited to concurrent-program extracts and Oracle Integration style outbound feeds in both 12.1.1 and 12.2.2 environments.