Search Results resend_doc

Overview

APPS.CLN_RESEND is a lightweight PL/SQL package in Oracle E-Business Suite that supports the "resend" capability within XML Gateway collaboration processing. Its single documented purpose, stated in the package header, is to "Resend a collaboration." When a business document (for example, a purchase order, ASN, or invoice transmitted through Oracle XML Gateway) fails to reach the trading partner, or when the partner confirms non-receipt, an operator can trigger a resend directly from the Collaboration History form rather than recreate the original transaction. CLN_RESEND encapsulates that retransmission logic, delegating the actual outbound delivery back to XML Gateway.

The package header identifies it as ECX (E-Commerce Gateway) source with a version banner dated 2006, and the ETRM classification lists it as an "OTHER" API owned by APPS. The user search terms "CANCEL," "RE-START," and "SUPPORT" align with this operational exception-handling context: cancel a stuck collaboration, restart processing, or obtain support when retransmission is required.

Key Procedures and Functions

One procedure is documented:

• RESEND_DOC — The resend routine invoked when the Resend button is clicked in the Collaboration History Forms. Its stated main purpose is to resend the document through XML Gateway. It accepts the collaboration identifier as its input and uses it to locate the original collaboration and re-initiate outbound transmission. No other parameters are documented, and the header notes "No specific notes."

The specification exposes only this one program unit; there are no documented functions, and the package is declared and terminated with the standard PACKAGE CLN_RESEND AS ... END CLN_RESEND; syntax.

Tables Accessed

Three APPS synonyms are documented as referenced by this package:

• CLN_COLL_HIST_HDR — Collaboration History header table. Provides the parent collaboration record identified by the collaboration ID passed to RESEND_DOC.
• CLN_COLL_HIST_DTL — Collaboration History detail table. Holds the message-level detail lines associated with the header, used to reconstruct what must be resent.
• ECX_DOCLOGS — XML Gateway document log. Records inbound and outbound document activity; the package uses it to reference the original transmission and to leave an audit trail of the resend.

Together these tables allow the package to identify the failed collaboration, retrieve its payload context, and hand the document back to XML Gateway for a fresh transmission attempt.

Usage Notes

• Form invocation. The primary entry point is the Collaboration History form, where the Resend button triggers RESEND_DOC. This is the documented and supported path.
• No package dependents. ETRM records zero other packages referencing CLN_RESEND, so it is effectively a terminal, UI-facing utility rather than a shared library routine.
• Custom code. Because it is an APPS-owned "OTHER" API, direct calls from custom code are technically possible but not part of the standard documentation; the form remains the recommended interface.
• Version applicability. The 120.0 header applies across 12.1.1 and 12.2.2. The package is specific to XML Gateway collaborations and does not apply to non-ECX workflows.
• Support context. For cancel/restart scenarios on stuck collaborations, the correct functional action is the form-based resend, which routes through this package; diagnostic investigation should reference CLN_COLL_HIST_HDR, CLN_COLL_HIST_DTL, and ECX_DOCLOGS.
• Authorization. As an APPS-owned object, execution is subject to standard APPS schema grants and function security on the calling form.