Search Results m4r_3c4_document_num_s




Overview

CLN_NTFYINVC_PKG is a valid PL/SQL package body owned by the APPS schema. It belongs to the Oracle E-Business Suite supply chain and financials integration layer, specifically the CLN (Notification and Supply Chain Collaboration) family of packages. Its principal business function is to manage the notification, transfer, and rejection handling of invoices exchanged between Oracle Payables, Oracle Receivables, and external trading partners through the Oracle EDI/e-Commerce Gateway infrastructure. The package coordinates invoice import status handling, invoice rejection processing, and communication of invoice events to system administrators and process owners. It is classified under the OTHER API classification in the ETRM metadata for release 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes fourteen documented procedures and functions. Their purposes are as follows:

Tables Accessed

The package reads and writes several application tables via APPS synonyms. Invoice interface processing uses AP_INVOICES_INTERFACE and AP_INVOICE_LINES_INTERFACE, while rejection handling draws on AP_INTERFACE_REJECTIONS and CLN_AP_INVOICE_REJECTION_ARCH. Receivables and transfer data come from AR_DOCUMENT_TRANSFERS and AR_PAYMENT_SCHEDULES_ALL, with tax data sourced from AR_XML_INVOICE_TAX_V. Trading partner and gateway activity is captured through ECX_DOCLOGS, ECX_EXT_PROCESSES, ECX_TP_HEADERS, and ECX_TRANSACTIONS. Supporting lookups include HZ_PARTY_SITES, OE_ORDER_HEADERS, OE_ORDER_LINES, and the M4R_3C4_DOCUMENT_NUM_S sequence, which is the object specifically referenced in the document numbering search. FND_CONCURRENT_REQUESTS and related FND utilities supply concurrent request context, and WF_ENGINE and WF_EVENT provide workflow event support.

Usage Notes

Because the object is a package body rather than a standalone API, CLN_NTFYINVC_PKG is not typically invoked directly by end users. It is called from within the CLN notification framework, from concurrent programs that process inbound and outbound invoice transactions, and from custom extensions that require invoice notification or rejection logic. It depends on CLN_NP_PROCESSOR_PKG, CLN_3C3_INVOICE_V, CLN_RN_UTILS, and CLN_DEBUG_PUB for processing, view access, utilities, and debugging respectively. The ETRM metadata records that it is referenced by one other package and references no fewer than twenty-five other database objects, confirming its role as a coordinator rather than an entry point. Developers extending invoice notification behavior should reference these procedures rather than duplicating their logic.