Search Results xdp_fe_cmd_aud_trails_s

Overview

XDP_MACROS is the core PL/SQL package body in the APPS schema that implements the macro-processing and outbound communication framework used by Oracle E-Business Suite's E-Commerce Gateway / EDI-style integrations and, more broadly, by Oracle's Transactional Messaging and XML Gateway infrastructure (the XDP_ prefix denotes the "e-Commerce Gateway / Message Processing" component family). The package serves as the runtime engine that interprets declarative "macro" definitions, resolves parameter values from cached metadata, opens and manages HTTP connections to trading partners or middleware, dispatches message payloads, captures responses, evaluates response content, records audit trails, and applies retry logic on failure. Because it is a package body and not a public API, it is not directly referenced by any other database object; instead it is consumed internally by sibling packages such as XDP_ENGINE, XDP_ADAPTER_CORE, XDP_PARAM_CACHE, and XDP_PROCEDURE_BUILDER_UTIL. In EBS 12.1.1 and 12.2.2 the object is VALID and is essential whenever outbound transaction documents (purchase orders, invoices, ASNs, etc.) are transmitted through the Gateway's HTTP transport layer.

Key Procedures and Functions

The package exposes 26 documented routines. The primary send-path routines are SEND and SEND_SYNC, which dispatch a message either asynchronously or in a synchronous request/response fashion, and SEND_HTTP, which performs the actual HTTP transmission using UTL_HTTP. SEND_CONNECT establishes the connection, while APPENDCONNECTCOMMANDS, FETCH_CONNECT_COMMANDS, and RESETCOMMANDBUFFER manage the buffered command sequence used to build a connection handshake.

Response handling is provided by GET_RESPONSE, GET_LONG_RESPONSE (for payloads exceeding standard VARCHAR2 limits, using DBMS_LOB), and RESPONSE_CONTAINS, which tests the returned text for expected tokens. GET_PARAM_VALUE and GET_ATTR_VALUE resolve runtime values from parameter and attribute caches.

Error and audit routines include NOTIFY_ERROR, which raises or logs a failure via FND_MESSAGE, AUDIT, which writes audit records, and AUTO_RETRY_ENABLED, which determines whether a failed transmission should be retried. Lifecycle initializers are INITDEFAULT, INITFP, INITCONNECTION, and INITDISCONNECTION, with ENDPROC performing final cleanup.

Tables Accessed

The package references two documented tables through APPS synonyms:

• XDP_FE_CMD_AUD_TRAILS — the front-end command audit trail table, written by the AUDIT routine to record each dispatched command, its status, and error context.
• XDP_FE_CMD_AUD_TRAILS_S — the companion sequence used to generate primary keys for the audit trail rows. This is the object most directly associated with the user's search term.

Additional documented dependencies include DBMS_LOB (large-object handling for responses), PLITBLM (PL/SQL integer table bulk manipulation), and UTL_HTTP (network transport).

Usage Notes

XDP_MACROS is not invoked directly by forms or concurrent programs; it is called internally by XDP_ENGINE and the XDP_ADAPTER_CORE family during outbound document processing. In EBS 12.1.1 and 12.2.2 the package is typically triggered when a Gateway concurrent program or workflow activity selects a transaction for transmission. Because it is a private package body, customization should be avoided; instead, parameters should be tuned through the Gateway setup and audit results reviewed in XDP_FE_CMD_AUD_TRAILS. Any invalidation of this package body cascades to the six dependent packages listed in the ETRM dependency report.