Search Results trigger_rejection

Overview

The APPS.CLN_3C3_AP_TRIGGER_PKG package body is a component of the Oracle E-Business Suite (EBS) Advanced Procurement / payables customization layer, specifically an extension developed for the "3C3" integration. Its primary business function is to act as a thin orchestration wrapper that invokes the rejection-processing logic for payables invoices originating from an external or third-party (3C3) system. The package does not itself implement rejection logic; instead, it delegates to CLN_NTFYINVC_PKG.TRIGGER_REJECTION, which handles the notification and invoice rejection workflow. In this sense, CLN_3C3_AP_TRIGGER_PKG serves as an entry-point API that isolates callers from the underlying notification package, allowing the rejection trigger behaviour to be invoked in a controlled and loggable manner.

Because it is classified as an OTHER API rather than a standard Oracle public API, this package is part of a customer or partner extension and is not shipped as part of the core Oracle Payables product. Its behaviour is therefore governed by the customization's own release and patch cycle, and it should be treated as a custom object when assessing upgrade impact between 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM metadata documents a single procedure:

• TRIGGER_REJECTION — This is the sole documented entry point. Its purpose is to initiate the rejection of a payables invoice in response to an external rejection event. The procedure accepts identifiers that describe the invoice and its context, including an invoice identifier, a group identifier, a concurrent request identifier, and an external document reference, and forwards them unchanged to CLN_NTFYINVC_PKG.TRIGGER_REJECTION. No other procedures or functions are documented in the package body.

The procedure contains no independent business logic beyond debug instrumentation and the delegation call. This thin-wrapper design is intentional: it centralises the call site so that the heavier processing in CLN_NTFYINVC_PKG can be reused without duplicating code.

Tables Accessed

The documented metadata lists no direct table references accessed via APPS synonyms. This is consistent with the package's role as a delegation wrapper: it does not perform DML itself. Any inserts, updates, or queries against payables and notification tables occur inside the called package, CLN_NTFYINVC_PKG, which is responsible for the actual data manipulation. As a result, this package has no documented read/write footprint of its own, and its transactional behaviour must be understood by examining the downstream package.

Usage Notes

The package is typically invoked when an external system signals that an invoice should be rejected — for example, from a concurrent program, an interface, or a wrapper PL/SQL block that processes inbound 3C3 rejection messages. Calling applications execute TRIGGER_REJECTION with the invoice and grouping context, and the procedure forwards the request to the notification package.

A distinguishing feature is its debug instrumentation. The package declares a package-level variable, l_debug_level, initialised from the profile option CLN_DEBUG_LEVEL with a default of 5. This is directly relevant to the search term cln_debug_level. When the profile value is 2 or lower, entry and exit banners are written via cln_debug_pub.Add; when it is 1 or lower, the incoming parameter values are also logged. Administrators can therefore raise the verbosity of this trigger by lowering the CLN_DEBUG_LEVEL profile setting. Note that the profile is read once at package initialisation, so a session may need to be re-established (or the package re-instantiated) for a changed value to take effect. Because the package is referenced by one other package, changes to its signature or delegation target should be regression-tested across all callers.