Search Results fv_ipac_batch_s

Overview

FV_IPAC_DISBURSEMENT_PKG is a valid PL/SQL package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It supports the Intra-Governmental Payment and Collection (IPAC) disbursement process used by federal agencies that operate on the Federal Financials shared services architecture within EBS. IPAC is the U.S. Treasury mechanism through which one federal agency bills another for goods or services rendered; the disbursement flow represented by this package takes IPAC charge records and transforms them into payables transactions so that the buying agency's books reflect the corresponding disbursement.

In practical terms, the package reads IPAC batch and import staging data, validates and enriches it against interagency funds, CCR vendor, and purchasing tables, and then creates invoices and invoice distributions that flow through the Oracle Payables open interface. It also records import history and error rows so that the IPAC reconcile and audit trail remains intact. The package is classified as OTHER in the API taxonomy, meaning it is an internal implementation unit rather than a publicly published API.

Key Procedures and Functions

Two documented units comprise the package body:

• MAIN — The principal entry point and orchestration routine. MAIN drives the disbursement build: it selects the IPAC batch and import records to be processed, applies validations, invokes the supporting logic to construct Payables open interface rows, and manages error capture and history insertion. It is the routine a concurrent program or calling process would invoke to run a disbursement cycle.
• UPD_IA_MAIN — The update component associated with the interagency main processing path. It performs the maintenance/write-back work on the IPAC and interagency fund records generated or affected during a disbursement run, updating status and related values after the main processing pass completes.

No formal parameter lists are documented in the ETRM metadata; procedure signatures should be confirmed directly against the source in the target instance.

Tables Accessed

Dependency metadata shows the package reads and writes a broad set of APPS synonyms. The central business tables are FV_IPAC_BATCH_S, FV_IPAC_IMPORT, FV_IPAC_IMPORT_ERRORS, and FV_IPAC_IMPORT_HISTORY, which hold batch headers, staged IPAC import rows, rejected records, and run history respectively. Interagency and vendor context is drawn from FV_INTERAGENCY_FUNDS, FV_INTERAGENCY_FUNDS_S, FV_CCR_VENDORS, and FV_OPERATING_UNITS.

Payables integration and validation rely on AP_INVOICES, AP_INVOICES_INTERFACE, AP_INVOICES_INTERFACE_S, AP_INVOICES_V, AP_INVOICE_DISTRIBUTIONS, AP_INVOICE_DISTRIBUTIONS_V, AP_INVOICE_LINES_INTERFACE, AP_INVOICE_LINES_INTERFACE_S, AP_INTERFACE_GROUPS_S, AP_INTERFACE_REJECTIONS, AP_LOOKUP_CODES, and AP_RECURRING_PAYMENTS_V. Purchasing validation uses PO_HEADERS, PO_LINES, PO_DISTRIBUTIONS, PO_VENDORS, and PO_VENDOR_SITES. Utility dependencies include FND_CONCURRENT, FND_DATE, FND_GLOBAL, FND_LOG, FND_PROFILE, FND_REQUEST, MO_GLOBAL, MO_UTILS, MTL_UNITS_OF_MEASURE_VL, and FV_UTILITY.

Usage Notes

FV_IPAC_DISBURSEMENT_PKG is invoked during IPAC disbursement processing, typically from an IPAC-related concurrent program or from supporting Federal Financials forms, and executed under a valid MOAC operating-unit context (hence the MO_GLOBAL and MO_UTILS dependencies) with FND_GLOBAL establishing session identity. Because MAIN writes into the Payables open interface and history tables, it is normally run in a scheduled or on-demand batch mode followed by the standard Payables Invoice Import concurrent request. The package is not referenced by any other database object, so it represents a top-level entry point rather than a called utility. Customizations should call the documented procedures rather than modifying the package body, and errors generated during a run should be reviewed via FV_IPAC_IMPORT_ERRORS.