Search Results ap_inv_import_event_s

Overview

APPS.AP_IMPORT_INVOICES_PKG is the core Payables package responsible for loading invoice data from the Oracle E-Business Suite open interface tables into the production Payables tables. It is the programmatic engine behind the Payables Open Interface Import process, transforming staged records from AP_INVOICES_INTERFACE, AP_INVOICE_LINES_INTERFACE, and related interface structures into validated, approved, and accounted invoices in AP_INVOICES_ALL and AP_INVOICE_LINES_ALL. In the Oracle EBS 12.1.1 and 12.2.2 releases, this package is classified as an "OTHER" API, meaning it is an Oracle-owned internal package that is invoked by shipped concurrent programs and forms rather than a formally published public API. The header comment identifies the file as apiimptb.pls at version 120.100.12020000.11, indicating the package has been maintained through multiple release updates, most recently around 2013. It also participates in the cleanup lifecycle for imported invoices through purge routines, and is referenced by 14 other packages across the Payables and Payments modules.

Key Procedures and Functions

The package exposes five documented program units:

• IMPORT_INVOICES — The primary driver procedure. It accepts the batch context (batch name, GL date, source, group ID), hold information, commit cycle counts, the concurrent request ID, a debug switch, and an organization ID, then processes the staged interface rows to create actual invoices. The signature was extended to support payment request type invoices, adding parameters for the invoice interface identifier and an approval requirement flag.
• IMPORT_PURGE — Removes previously imported interface records and their dependent data, typically invoked after a successful import run to clean the open interface tables.
• XML_IMPORT_PURGE — Parallel purge routine tailored to XML-originated invoice imports, allowing cleanup of XML payload records that are no longer required.
• SUBMIT_PAYMENT_REQUEST — Creates and submits payment request invoices, supporting the payment request invoice flow handled inside the import process.
• GET_INFO_1 — A helper function used to retrieve informational reference data during import processing.

The body also contains a private helper, DELETE_ATTACHMENTS, which removes attachment associations for an interface invoice and is called by IMPORT_PURGE and by the APXIIPRG.rdf report.

Tables Accessed

The package reads and writes a wide set of Payables and shared tables. Interface tables AP_INVOICES_INTERFACE and AP_INVOICE_LINES_INTERFACE are the source of staged data, while AP_INVOICES_ALL and AP_INVOICE_LINES_ALL are the destination tables where validated invoices and lines are created. AP_INTERFACE_REJECTIONS captures rows that fail validation, and AP_INV_IMPORT_EVENT_S records import event history. Setup and reference tables include AP_SYSTEM_PARAMETERS_ALL and FINANCIALS_SYSTEM_PARAMS_ALL (system options and defaults), FND_CURRENCIES (currency validation), AP_PRODUCT_SETUP, AP_PAYMENT_SCHEDULES (payment schedule generation), GL_PERIOD_STATUSES (GL date validation against open periods), and FA_BOOK_CONTROLS for asset-related processing. FND_ATTACHED_DOCUMENTS is queried by the attachment deletion routine, which then delegates removal to FND_ATTACHED_DOCUMENTS2_PKG.

Usage Notes

AP_IMPORT_INVOICES_PKG is normally invoked indirectly through the Payables Open Interface Import concurrent program, which supplies the batch name, source, GL date, hold code, and commit cycle parameters gathered from the program's submission form. It is also called by other Payables processes and by custom code that needs to drive an interface load programmatically, such as inbound integrations from external procurement or legacy systems. Because the package is classified as OTHER rather than a public API, Oracle does not guarantee backward compatibility on its internal signatures, so custom callers should validate against each target release (for example 12.1.1 versus 12.2.2) and avoid hard-coding parameter positions that may change between patches. The debug switch parameter enables diagnostic output via FND_LOG, which is useful when troubleshooting rejected interface rows.