Results for “write_ack_data_values”

8 results




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

Overview

OE_UPDATE_ACK_UTIL is a utility PL/SQL package body in the Oracle E-Business Suite Order Management (ONT) module, owned by the APPS schema. Its primary business function is to maintain order acknowledgment state on sales order headers and lines when acknowledgment data is received or generated. In inbound EDI and XML order flows, customer acknowledgments must be reflected back onto the corresponding order header and line records so that order management and fulfillment processes can distinguish acknowledged orders from unacknowledged ones. This package encapsulates that logic, updating the ordering tables with acknowledgment codes and dates, synchronizing the header acknowledgment staging records, and maintaining the XML message identifier associated with the acknowledgment.

The package is classified as a UTIL object within the ETRM documentation set, indicating that it provides reusable low-level services invoked by other acknowledgment and EDI processing packages rather than being a user-facing API. The ETRM metadata records that it is referenced by three other packages, confirming its role as a shared building block in the Order Management acknowledgment architecture.

Key Procedures and Functions

  • UPDATE_HEADER_ACK_FIRST — Records the first acknowledgment against a sales order header. The procedure accepts a header identifier and an acknowledgment code, locks the header row, updates the first acknowledgment code and date on the order header, increments lock control, and stamps the XML message identifier. It also deletes rejected staging rows from the lines and headers interface tables and marks the header acknowledgment record as acknowledged.
  • UPDATE_HEADER_ACK_LAST — Performs the analogous update for the most recent acknowledgment on the order header.
  • UPDATE_LINE_ACK_FIRST — Applies first-acknowledgment information to individual order lines.
  • UPDATE_LINE_ACK_LAST — Applies latest-acknowledgment information to individual order lines.
  • DERIVE_ACK_VALUES — Determines the acknowledgment code and related values to be applied, supporting the header and line update routines.
  • RAISE_DERIVE_ACK_DATA_EVENT — Raises the business event associated with derived acknowledgment data, enabling downstream subscribers to react to acknowledgment changes.
  • OE_EDI_SELECTOR — Provides selection logic used in EDI acknowledgment processing, most likely to determine eligible orders or transactions for the acknowledgment workflow.
  • WRITE_ACK_DATA_VALUES — Persists acknowledgment data values, serving as the write-side partner to the derivation logic.

Tables Accessed

The package reads and writes OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL to persist acknowledgment codes, dates, lock control values, and XML message identifiers on the live order. It maintains the staging and audit tables OE_HEADER_ACKS and OE_LINE_ACKS, which drive first-acknowledgment detection and the acknowledged flag. Interface cleanup touches OE_HEADERS_INTERFACE and OE_LINES_INTERFACE, removing rejected rows associated with the same order source, original system document reference, and request identifier. OE_XML_MESSAGE_SEQ_S supplies sequence values for XML message IDs, while DUAL supports sequence selection. Customer-related tables HZ_CUST_ACCT_SITES and HZ_CUST_SITE_USES_ALL appear in the package's broader references, as do WF_PARAMETER_LIST_T and PLITBLM for workflow parameter handling and PL/SQL table support.

Usage Notes

OE_UPDATE_ACK_UTIL is not typically invoked directly from a form. It is called by the acknowledgment processing packages, EDI inbound programs, and XML message handlers that feed order acknowledgment data into Order Management. Concurrent programs that process inbound acknowledgments, as well as custom extensions that need to mark orders as acknowledged, reference the update routines. The historically significant code paths — including the first-acknowledgment code assignment, the header row lock with FOR UPDATE NOWAIT to avoid contention, and the shift from OE_ORDER_HEADERS to OE_ORDER_HEADERS_ALL — reflect fixes delivered through version 12.1.1 and 12.2.2. The presence of the OE_CODE_CONTROL release-level check indicates version-dependent behavior, so implementations upgrading between 12.1.1 and 12.2.2 should verify that the package body matches the deployed code level.