Search Results fv_ipac_import_u1

Overview

FV.FV_IPAC_IMPORT is an interface table in the Oracle E-Business Suite Federal Financials (FV) product family. It serves as the staging and import surface for Intra-Governmental Payment and Collection (IPAC) disbursement transactions, capturing the flat-file detail transmitted between federal trading partners before that data is validated and converted into invoice and payment records. The table resides in the APPS_TS_INTERFACE tablespace, is owned by the FV schema, and carries an ETRM status of VALID. The physical footprint is substantial: 155 documented columns, reflecting the breadth of Treasury, ALC, DUNS, SGL, and contract data required to represent a full IPAC settlement line.

From a modeling perspective, the metadata heuristic classifies this object as standalone, meaning it has no strong outbound foreign key relationships within the mined dependency set. That classification is consistent with an interface or staging table: it is populated by an inbound file load process rather than by transactional referential integrity constraints, and its IPAC_IMPORT_ID unique index functions as a load-surrogate key rather than as a foreign-key target. In Data Vault terms, this table is best modeled as a staging satellite anchored to an IPAC transaction hub, with the import identifier serving as the load hash key.

Key Information Stored

The table is keyed on the surrogate identifier IPAC_IMPORT_ID, which is enforced as unique by index FV_IPAC_IMPORT_U1 and is the primary business-key candidate. A secondary non-unique index, FV_IPAC_IMPORT_N1, indexes GROUP_ID, which groups records belonging to the same import run.

The most significant columns fall into four functional groups:

• Batch control: BATCH_NAME, GROUP_ID, DATA_FILE, REQUEST_ID, and RECORD_STATUS identify the import batch and track processing state.
• Agency and party identification: SUBMITTER_ALC, ORIGINATING_ALC, CUSTOMER_ALC, RECEIVER_DUNS, SENDER_DUNS, VENDOR_ID, and VENDOR_SITE_ID establish trading-partner context.
• Transaction and reference detail: TRANSACTION_ID, IPAC_DOC_REF_NUMBER, DETAIL_LINE_NUMBER, TRANSACTION_TYPE, ACCOMPLISHED_DATE, and ACCOUNTING_DATE describe the underlying obligation event.
• Amounts and accounting distribution: SUMMARY_AMOUNT, DETAIL_AMOUNT, QUANTITY, UNIT_PRICE, and the SGL_NUMBER* / SGL_AMOUNT* series (up to sixteen lines) capture the Treasury Standard General Ledger postings.

Columns INVOICE_ID, INVOICE_LINE_ID, INT_INVOICE_ID, INT_INVOICE_LINE_ID, ORG_ID, and SET_OF_BOOKS_ID link the staged record to downstream EBS invoice and ledger entities after successful import.

Common Use Cases and Queries

Federal Financials administrators use this table to diagnose failed or partially processed IPAC imports. A common diagnostic query filters by import run and status:

• SELECT IPAC_IMPORT_ID, BATCH_NAME, TRANSACTION_ID, RECORD_STATUS FROM FV.FV_IPAC_IMPORT WHERE GROUP_ID = :group_id;
• Aggregate reconciliation of detail lines against the submitted summary: SELECT SUMMARY_AMOUNT, SUM(DETAIL_AMOUNT) FROM FV.FV_IPAC_IMPORT WHERE IPAC_IMPORT_ID = :id GROUP BY SUMMARY_AMOUNT;
• Traceability from staged record to created invoice: SELECT IPAC_IMPORT_ID, INVOICE_ID, INVOICE_LINE_ID FROM FV.FV_IPAC_IMPORT WHERE INVOICE_ID IS NOT NULL AND TRUNC(CREATION_DATE) = :run_date;
• Stale interface audit: SELECT COUNT(*) FROM FV.FV_IPAC_IMPORT WHERE RECORD_STATUS = 'NEW' AND CREATION_DATE < SYSDATE - 30;

Reporting use cases include reconciling SGL balances by Treasury Account Symbol, auditing unmapped vendor or DUNS values that block import, and validating that ACCOMPLISHED_DATE falls within the correct fiscal period.

Related Objects

Dependency mining identifies one outbound reference from this table:

• FTE_INVOICE_LINES — joined via FV_IPAC_IMPORT.INVOICE_LINE_ID, providing the invoice line populated after a successful import conversion.

Downstream integration additionally depends on the Invoice and Invoice Line tables (via INVOICE_ID and INT_INVOICE_ID), the vendor and vendor site entities (VENDOR_ID, VENDOR_SITE_ID), the ledger reference table (SET_OF_BOOKS_ID), and the concurrent request framework (REQUEST_ID). The IPAC import concurrent program and its associated validation package read from this interface table, map validated rows into Payables invoice structures, and update RECORD_STATUS upon completion.