Search Results fv_summary_consolidate_all




Overview
Explore in AI Chat

Overview

The FV_SUMMARY_CONSOLIDATE_ALL table is a core data repository within the Oracle E-Business Suite Federal Financials (FV) module. It functions as the foundational table for two critical federal payment processes: the generation of Summary Schedules and the creation of the Consolidated Payment File. This table is essential for managing and tracking payment batches that are destined for submission to the U.S. Department of the Treasury, specifically through systems like the Automated Standard Application for Payments (ASAP). Its role is to maintain the necessary linkage between internal payment batch data and the external control numbers required for federal reporting and consolidation.

Key Information Stored

While the full column list is not detailed in the provided metadata, the description and foreign key relationship define its critical data elements. The table centrally stores Payment Batch names, which are the internal identifiers for groups of payments. Crucially, it associates these batches with a Control Number and a Consolidated Schedule Number. These numbers are vital for federal processing and audit trails. A key structural column is PAYMENT_INSTRUCTION_ID, which establishes a foreign key relationship to the IBY_PAY_INSTRUCTIONS_ALL table in the Oracle Payments module. This link connects the federal consolidation data to the underlying payment instructions that define the payment methods, bank accounts, and payment details.

Common Use Cases and Queries

The primary use case is the execution of the "Summary Schedules and Consolidated Payment File" process within Federal Financials. This process queries FV_SUMMARY_CONSOLIDATE_ALL to identify batches marked for consolidation, retrieves their associated control numbers, and generates the mandated Treasury-formatted output files. Common reporting queries involve joining this table to payment instruction and payment batch details to validate data before submission. A typical SQL pattern might be:

  • Selecting batches for a specific schedule: SELECT PAYMENT_BATCH_NAME, CONTROL_NUM, CONSOLIDATED_SCHEDULE_NUM FROM FV.FV_SUMMARY_CONSOLIDATE_ALL WHERE REQUEST_ID = :p_request_id;
  • Validating the link to payment instructions: SELECT SCA.* FROM FV.FV_SUMMARY_CONSOLIDATE_ALL SCA, IBY.IBY_PAY_INSTRUCTIONS_ALL IA WHERE SCA.PAYMENT_INSTRUCTION_ID = IA.PAYMENT_INSTRUCTION_ID;

Related Objects

The most directly related object, as defined by its foreign key, is the IBY_PAY_INSTRUCTIONS_ALL table in the IBY (Oracle Payments) schema. This relationship is fundamental, as the PAYMENT_INSTRUCTION_ID in FV_SUMMARY_CONSOLIDATE_ALL references the primary key of IBY_PAY_INSTRUCTIONS_ALL. This ties the federal summary and consolidation data directly to the core Oracle Payments engine. The table is also intrinsically linked to the application form and concurrent program named "Summary Schedules and Consolidated Payment File," which serves as the primary interface and engine for populating and utilizing this table's data.