Search Results notify_recipient

Overview

APPS.AP_XML_INVOICE_INBOUND_PKG is a PL/SQL package in the Oracle E-Business Suite Payables (AP) module that supports the processing of supplier invoices received as XML documents through the inbound interface. Its principal business role is to handle the post-import activities associated with the Payables open interface: validating and interpreting inbound XML invoice payloads, assembling derived values such as operating unit, supplier identity, and supplier e-mail address, transforming mapped values before they reach the interface tables, logging rejection reasons, and dispatching notifications when a supplier invoice transaction succeeds or fails. The package therefore sits between the XML inbound processing engine and the AP_INVOICES_INTERFACE / AP_INVOICE_LINES_INTERFACE staging tables, providing the business logic that determines whether an inbound XML document is accepted for downstream invoice creation. It is documented as VALID in the APPS schema and is classified as an "OTHER" API, meaning it is not a public, supported integration API in the same sense as the Open Interface APIs, but rather an internal processor that may be referenced by related inbound components.

Key Procedures and Functions

The ETRM metadata documents twelve procedures and functions. START_OPEN_INTERFACE is the driving entry point that initiates processing of the inbound XML invoice into the Payables open interface. DERIVE_ORG_ID, DERIVE_VENDOR_ID, and DERIVE_EMAIL_ADDRESS populate the operating unit identifier, the supplier identifier, and the supplier contact e-mail address respectively, typically by looking up values that are not explicitly supplied in the XML payload. GET_TOKEN_DISPLAY_FIELD supports the XML mapping/token framework by returning display fields used during payload interpretation. SET_TAXABLE_FLAG2 and CORRECT_CHARGE_TYPE adjust inbound invoice line attributes before they are staged, setting taxability and normalizing the charge type so the interface accepts the line. AFTER_MAP provides post-mapping processing logic that runs once XML elements have been mapped to interface columns. CHANGE_CASE handles textual case normalization of mapped values. NOTIFY_SUPPLIER and NOTIFY_RECIPIENT generate and route notification messages to the supplier and to internal recipients, with SEND_EMAIL performing the underlying e-mail transmission. Together these procedures embody the validation, derivation, correction, and notification stages of the inbound XML invoice lifecycle.

Tables Accessed

The package references AP_INVOICES_INTERFACE and AP_INVOICE_LINES_INTERFACE, the header and line staging tables into which inbound invoice data is loaded before validation and transfer into the production invoice tables. AP_INTERFACE_REJECTIONS is used to record rows that fail validation, preserving rejection reasons for review. AP_P2P_INBOUND_NOTIFICATION_S stores notification definitions and state for the procure-to-pay inbound notification process. AP_SYSTEM_PARAMETERS_ALL and FINANCIALS_SYSTEM_PARAMS_ALL supply ledger and Payables system options needed for supplier, operating unit, and organizational defaults. FND_CONCURRENT_REQUESTS is queried or updated in connection with concurrent program execution context. PO_HEADERS_ALL supports linkage of inbound invoice documents to the originating purchase order. DUAL is referenced for single-row derivations, and PLITBLM is the PL/SQL internal table type used by the token/mapping utilities. Access to these objects is through APPS synonyms, consistent with the package's APPS schema ownership.

Usage Notes

AP_XML_INVOICE_INBOUND_PKG is invoked indirectly rather than directly by end users. It is referenced by AP_APXIIMPT_XMLP_PKG, the package associated with the Payables XML invoice import concurrent program, which calls the inbound processing logic as part of loading XML invoice documents into the open interface. It is also referenced by one other package and by itself, indicating recursive or shared internal calls. Customers typically interact with the package through the XML Invoice Import concurrent program or through the supplier-facing inbound document channel rather than by calling its procedures from a form. Custom code should treat these procedures as internal implementation details: because the package is classified as OTHER and is not published as a supported API, direct calls risk breakage on patching or upgrade. In Oracle EBS 12.1.1 and 12.2.2 the package remains valid in the APPS schema, and its behavior is governed by the Payables open interface options and the system parameters it reads.