Search Results cln_3c3_ap_trigger_pkg




Overview
Explore in AI Chat

Overview

The APPS.CLN_3C3_AP_TRIGGER_PKG package is a customized Oracle E-Business Suite database component that resides in the APPS schema and is declared with AUTHID CURRENT_USER. The naming convention (CLN_3C3) associates it with a customer-specific extension—commonly tied to a 3C3 or similar external document exchange framework—layered on top of the Oracle Payables (AP) module. Its function is to act as an integration trigger, allowing an external system or workflow to signal Oracle Payables that a document (an invoice) should be rejected, based on an external document reference.

The package is registered in ETRM with an API classification of OTHER, indicating that it is not part of the standard Oracle public API set but rather a bespoke object. It is referenced by one other package and exposes a single documented procedure, making it a narrow, purpose-built entry point rather than a broad utility library. As the source header indicates ($Header: CLN3C3TS.pls 120.0 ... noship $), this object is not shipped as part of standard Oracle functionality.

Key Procedures and Functions

  • TRIGGER_REJECTION — The sole documented procedure in the package. It accepts an invoice identifier, a group identifier, a request identifier, and an external document reference, and is intended to initiate or record a rejection of an invoice in Oracle Payables. The inclusion of p_group_id and p_request_id suggests the procedure is invoked within a batch or concurrent processing context (for example, an Invoice Validation or Payables Open Interface run), where a group and a concurrent request number are naturally available. The p_external_doc_ref parameter indicates the procedure is driven by a reference originating from an external system, which is then resolved to the internal p_invoice_id.

No functions or additional procedures are documented in the ETRM metadata. The package specification exposes only this single procedure, so the internal implementation (not shown) may delegate to standard Payables APIs or to helper logic within the referenced dependent package.

Tables Accessed

The ETRM metadata for this package does not list any explicitly documented tables referenced through APPS synonyms. This absence is itself informative: the package likely performs its work indirectly by calling other PL/SQL APIs (the one package that references it, or standard Payables APIs) rather than issuing direct DML against base tables.

In practice, a procedure with this signature—given an invoice ID, group ID, request ID, and external document reference—would typically interact with Oracle Payables invoice tables such as AP_INVOICES_ALL and AP_INVOICE_LINES_ALL, and possibly with rejection or hold records. Because the metadata does not confirm these accesses, they should be treated as inferred rather than documented. Implementers verifying behavior in 12.1.1 or 12.2.2 should inspect the package body and trace the dependent package to confirm the exact table footprint before relying on any assumed DML.

Usage Notes

This package is a custom integration object and is not invoked by standard Oracle Payables screens. Typical invocation scenarios include:

  • Concurrent program / batch processing — Called from a concurrent program that processes externally supplied rejection instructions, using the current request ID and invoice group as context.
  • Custom forms or OAF pages — Invoked from a customized Payables screen or an external-facing form where an invoice must be rejected based on an external reference.
  • Workflow or interface calls — Triggered by an inbound interface or workflow process that manages the lifecycle of invoices exchanged with an external system.

Because the package is declared AUTHID CURRENT_USER, executing users require appropriate grants on any underlying objects it touches. Any modification, upgrade, or patching of the Payables module should include a review of this package, since it is not covered by Oracle's standard certification and may break if dependent objects change between 12.1.1 and 12.2.2.