Results for “fv_ipac”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FV_IPAC is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports federal Intra-Governmental Payment and Collection (IPAC) processing and interagency fund accounting. In U.S. federal deployments, IPAC is the Treasury mechanism through which one agency bills another for goods and services rendered. The FV_IPAC package provides the server-side logic that translates Treasury IPAC transactions into Oracle Receivables activity and posts the resulting accounting against interagency fund balances. Its classification in the ETRM repository is OTHER, indicating it is not a standard public API but an internal utility package used by the federal financials feature set. The package header header string ($Header: FVIPPROS.pls 120.11) shows it was last shipped in the 12.x code line and remains present in both 12.1.1 and 12.2.2. It is referenced by zero other packages, so its public procedures serve as entry points invoked from concurrent programs, forms, or external callers rather than from within other PL/SQL units.

Key Procedures and Functions

Three procedures are documented in the package specification.

• MAIN — The primary driver for IPAC transaction processing. It accepts a profile class, customer category, customer, transaction type, a transaction date range, and a contact phone number as inputs. It orchestrates the selection and processing of IPAC-eligible interagency transactions for the specified customer population and reporting window.
• CREATE_BULK_FILE — Generates a bulk file for IPAC processing. It accepts a single organization identifier (p_org_id) and is scoped to a specific operating unit, reflecting the multi-org architecture in which IPAC billings are produced per organization.
• CREATE_RECEIPT_ACCT_MAIN — Creates receipt accounting entries. It accepts a receipt method, a receipt date, and a GL date, driving the generation of accounting distributions for receipts tied to the specified receipt method and accounting period.

All three follow the standard concurrent-program signature convention: errbuf and retcode are the mandatory OUT parameters used by the Concurrent Manager to report completion status and error text.

Tables Accessed

The package reads and writes across Receivables, Cash Management, and federal fund accounting tables via APPS synonyms.

• Receivables: AR_DISTRIBUTIONS, AR_PAYMENT_SCHEDULES, and AR_RECEIPT_METHOD_ACCOUNTS support receipt accounting and distribution creation.
• Cash Management: CE_BANK_ACCOUNTS and CE_BANK_ACCT_USES_ALL supply bank account and organization-use information for receipt generation.
• Flexfields: FND_FLEX_VALUES, FND_FLEX_VALUE_HIERARCHIES, and FND_ID_FLEX_SEGMENTS resolve key flexfield values and hierarchies, including interagency fund hierarchies.
• Federal funds: FV_FACTS_USSGL_ACCOUNTS, FV_FUND_PARAMETERS, FV_INTERAGENCY_FUNDS_ALL, and FV_INTERAGENCY_FUNDS_S hold USSGL account balances, fund parameter configuration, and interagency fund definitions.
• IPAC staging: FV_IPAC_AR_BATCH_HDR_S and FV_IPAC_BILLING_ID_S store IPAC batch headers and billing identifiers generated during processing.
• FND_USER resolves the operating user for audit and security context.

Usage Notes

FV_IPAC procedures are designed to be launched as concurrent programs rather than called interactively. CREATE_BULK_FILE is typically run per operating unit to produce the outbound file submitted to Treasury for interagency billing, while MAIN coordinates broader IPAC transaction selection. CREATE_RECEIPT_ACCT_MAIN is scheduled after receipt creation to generate the corresponding accounting entries. Because the package is not referenced by other packages, integration is accomplished by registering these procedures as concurrent program executables with the standard errbuf/retcode interface. Custom code invoking them directly must supply the correct profile, customer, organization, and date parameters and must check retcode before accepting results. The p_org_id parameter on CREATE_BULK_FILE confirms multi-org awareness; callers should ensure the correct operating unit context is set. As an internal package outside the public API set, FV_IPAC is subject to change between releases and should be treated as unsupported for custom extensions.