Search Results fv_top_exclusion_criteria_all

Overview

The FV_TOP_EXCLUSION_CRITERIA_ALL table is a core data repository within the Oracle E-Business Suite Federal Financials (FV) module, specifically for versions 12.1.1 and 12.2.2. It serves a critical control function in the Treasury Offset Program (TOP) process, which is a mandatory federal requirement for agencies to withhold certain payments (like vendor invoices or federal salaries) to satisfy delinquent debts owed to the government. This table stores the business rules and criteria that define which payment transactions are excluded from submission to the TOP. By configuring these exclusions, federal agencies ensure compliance while preventing the inappropriate withholding of payments that are legally or procedurally exempt from the offset process.

Key Information Stored

While the provided metadata does not list specific columns, the table's purpose and its documented foreign key relationship indicate the nature of the data it holds. Based on standard Federal Financials implementation, key columns typically include identifiers for the exclusion rule itself, such as a unique CRITERIA_ID, and context columns like ORG_ID. The most significant column, as confirmed by the foreign key, is PAYMENT_REASON_CODE. This column stores a code that links to a defined payment reason in the IBY_PAYMENT_REASONS_B table. The presence of this specific foreign key strongly implies that a primary method of defining an exclusion is by payment reason (e.g., "Tax Payment," "Grant Payment"). Other potential columns may include effective date ranges, creation and last update audit fields, and indicators for the type of payment stream (e.g., accounts payable, travel) to which the rule applies.

Common Use Cases and Queries

The primary use case is the configuration and maintenance of TOP exclusion rules by system administrators or financial controllers. During the payment batch process, the Federal Financials engine queries this table to filter out transactions that match the defined exclusion criteria before generating the TOP submission file. A common reporting need is to audit all active exclusion rules. A sample query would be:

• SELECT criteria_id, payment_reason_code, start_date_active, end_date_active FROM fv_top_exclusion_criteria_all WHERE sysdate BETWEEN start_date_active AND NVL(end_date_active, sysdate+1) AND org_id = :org_id;

Another critical operational query would join to the payment reasons table to get the meaning of the code, ensuring the rules are correctly set up: SELECT exc.*, prn.name FROM fv_top_exclusion_criteria_all exc, iby_payment_reasons_b prn WHERE exc.payment_reason_code = prn.payment_reason_code.

Related Objects

The table has a direct and documented foreign key relationship, which is fundamental to its operation.

• IBY_PAYMENT_REASONS_B: This is the master table for payment reason codes within Oracle Payments (IBY). The FV_TOP_EXCLUSION_CRITERIA_ALL.PAYMENT_REASON_CODE column references IBY_PAYMENT_REASONS_B.PAYMENT_REASON_CODE. This relationship ensures that exclusions are defined using valid, standardized reason codes assigned to invoices and payments elsewhere in the system.

As a central control table, FV_TOP_EXCLUSION_CRITERIA_ALL is also likely referenced by various Federal Financials program units and views responsible for the TOP extraction logic, though these are not specified in the provided metadata.