Search Results get_order_line

Overview

The APPS.XDP_INTERFACES_PUB_W package body is a public wrapper that exposes the XDP (eXchange Data Platform / order interface) integration layer to Oracle EBS callers. XDP provides a mechanism to receive external order data — typically from a trading partner, a partner application, or a middleware tier — and to translate that inbound stream into the structures required for downstream Oracle Order Management processing. The "_PUB_W" suffix follows the standard Oracle wrapper convention, indicating that this package is a thin public shell generated around an internal implementation package (the "_PUB" portion represents the PL/SQL API surface, while "_W" denotes the wrapper layer that performs datatype mapping and provides a stable, externally callable signature). The header comment (XDPINPWB.pls 120.1, dated 2005/06/22) indicates a legacy module maintained since the 11i era and carried forward into 12.1.1 and 12.2.2.

The body includes the standard Rosetta date/number mapping helpers used by Oracle's generated wrapper code. rosetta_g_miss_num_map translates between FND_API.G_MISS_NUM and an internal sentinel, and rosetta_g_miss_date_in_map normalizes FND_API.G_MISS_DATE values, ensuring that "missing" semantics survive across the JDBC/PLSQL boundary. Delimiter constants built via FND_GLOBAL.LOCAL_CHR and package-level CLOB variables (lg_line_clob, lg_line_param_clob, lg_order_param_clob) support the assembly of large delimited payloads into CLOBs for parsing and transport.

Key Procedures and Functions

• PROCESS_ORDER — The primary entry point. It accepts an API version, standard FND_API control parameters (p_init_msg_list, p_commit, p_validation_level), standard output parameters (x_return_status, x_msg_count, x_msg_data), and a large set of positional interface parameters (p7_a0 through p7_a26, plus JTF varray parameters p8_a0 and p8_a1). These positional names are the hallmark of a generated interface wrapper: each position maps to an element of the external order feed. The routine validates and stages the inbound order for subsequent processing.
• GET_ORDER_DETAILS — Retrieves the detailed line-level content of a previously received or staged order, returning the full set of order line attributes required by downstream consumers.
• GET_ORDER_STATUS — Returns the current processing status of an order that has been submitted through the interface, allowing callers to poll for completion without re-reading the full order body.
• GET_CLOBS — Exposes the internally assembled CLOB payloads (order header/line data and associated parameters) to callers that need the raw delimited representation rather than parsed record structures. This supports diagnostics and downstream tools that consume the payload directly.

Tables Accessed

The ETRM metadata documents only one referenced program unit: DBMS_LOB. Because this is a public wrapper, table access is predominantly performed by the underlying internal package rather than by the wrapper itself. The wrapper's direct dependency on DBMS_LOB is consistent with the CLOB-centric design visible in the body, where order and line payloads are accumulated in CLOB variables before being parsed or returned. In practice, associated processing writes into XDP interface staging tables and reads order-related setup, but those accesses are deferred to the internal implementation layer rather than appearing in this wrapper.

Usage Notes

This package is not typically invoked by end users or Oracle Forms directly. It is called by concurrent programs, inbound integration adapters, and custom PL/SQL that need a stable public signature for submitting and interrogating orders through the XDP interface. The standard FND_API output parameters mean callers should check x_return_status for FND_API.G_RET_STS_SUCCESS or ERROR and inspect x_msg_count/x_msg_data for diagnostics. Because the package body is generated wrapper code, it should not be modified directly; changes belong in the underlying internal package. The metadata records no packages referencing this object, so it functions as a top-level entry point rather than a shared utility. When migrating between 12.1.1 and 12.2.2, note that the API classification is OTHER, meaning Oracle supports it as an interface but not as a formally versioned public API with guaranteed backward compatibility across point releases.