Results for “t_v30”
26 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OE_UPDATE_ACK_UTIL is a utility package in the Oracle Order Management (OE) module of Oracle E-Business Suite, owned by the APPS schema and classified as a UTIL (utility) object. Its principal business function is to process and persist order acknowledgment data received from external trading partners through the EDI/XML inbound order cycle. When a customer or trading partner returns an acknowledgment (ACK) against a previously transmitted sales order, the acknowledgment must be reconciled to the corresponding order header and order line records. OE_UPDATE_ACK_UTIL performs the controlled update of the EDI acknowledgment staging tables and the resulting order-level acknowledgment status, ensuring that the order management application reflects the partner's confirmed, rejected, or changed values.
The package is defined with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the definer, which is typical for utility packages invoked from EDI concurrent programs and internal Order Management processing. The header comment indicates a source version of 120.3.12020000.2, dated 2013, consistent with the 12.1.1 and 12.2.2 code lines.
Key Procedures and Functions
The package exposes eight documented procedures and functions. The user search term t_date corresponds directly to a declared PL/SQL collection type at the top of the package specification: TYPE T_DATE IS TABLE OF DATE; (line 6). This is part of an extensive family of associative/collection types (T_NUM, T_V240, T_V60, T_V30, T_V1, T_V1000, and others) used throughout the package to pass bulk arrays of dates, numbers, and strings between the update routines and record structures such as Line_Rec_Type.
- UPDATE_HEADER_ACK_FIRST — Processes the initial (first-pass) update of header-level acknowledgment information against the order header acknowledgment records.
- UPDATE_HEADER_ACK_LAST — Completes the final header-level acknowledgment update, typically after all line-level processing has been reconciled.
- UPDATE_LINE_ACK_FIRST — Performs the first-pass update of line-level acknowledgment data.
- UPDATE_LINE_ACK_LAST — Performs the concluding line-level acknowledgment update.
- DERIVE_ACK_VALUES — Derives the acknowledgment values (status, dates, changed attributes) that must be applied to the order from the inbound ACK data.
- RAISE_DERIVE_ACK_DATA_EVENT — Raises the business event associated with derived acknowledgment data, supporting the Oracle Workflow / Business Event integration used in Order Management.
- OE_EDI_SELECTOR — Serves as the EDI selector routine that identifies and selects the appropriate acknowledgment records for processing.
- WRITE_ACK_DATA_VALUES — Writes the computed acknowledgment data values to the target acknowledgment tables.
Tables Accessed
The package reads and writes the acknowledgment and order data through APPS synonyms. OE_HEADER_ACKS and OE_LINE_ACKS are the acknowledgment tables that store partner-returned acknowledgment detail; these are the primary update targets. OE_HEADERS_INTERFACE and OE_LINES_INTERFACE hold inbound interface records prior to validation. OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL are the base order tables whose acknowledged attributes may be reconciled. Customer and site information is resolved via HZ_CUST_ACCT_SITES and HZ_CUST_SITE_USES_ALL. OE_XML_MESSAGE_SEQ_S supplies message sequence numbers, WF_PARAMETER_LIST_T supports Workflow event parameters, PLITBLM is the standard EBS PL/SQL table-of-varchar2 utility type, and DUAL is used for scalar computations.
Usage Notes
OE_UPDATE_ACK_UTIL is an internal utility rather than an end-user-callable API. It is invoked indirectly by the Order Management acknowledgment processing flows, including EDI inbound order acknowledgment concurrent programs and the Order Management XML/EDI processing logic. It is referenced by three other packages, indicating its role as a shared service within the acknowledgment processing stack. Customizations should avoid calling this package directly; instead, the supported EDI and Order Management acknowledgment flows should be used. The presence of the T_DATE collection type and the First/Last update pattern reflects a deliberate two-phase update strategy that separates initial derivation from final commitment of acknowledgment values.