Search Results fv_tc_offsets




Overview

FV_TC_OFFSETS is a transaction table in the FV (Federal Financials) product of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. The table stores treasury confirmation offset information — records that reconcile or adjust a treasury payment confirmation against a corrected treasury payment number. In federal financial operations, treasury confirmations must be matched to disbursements issued by the U.S. Department of the Treasury; when a confirmation does not match the expected payment, an offset record is created to capture the correcting relationship, the offsetting party, and the monetary amount. The table therefore serves as the audit and reconciliation layer that keeps the federal disbursement ledger aligned with Treasury's reported activity.

Metadata mined from the foreign-key structure classifies FV_TC_OFFSETS as standalone under a heuristic Data Vault model. This suggests a modeling approach in which the table behaves as an independent hub-like entity rather than a dependent link or satellite; no inbound or outbound foreign keys to other EBS tables were documented. Implementers designing a warehouse or reconciliation layer around this object should treat it as a self-contained record of offset events keyed by its own identity.

Key Information Stored

The table contains 27 documented columns. The most important are:

The distinction between the surrogate key (FV_TC_OFFSET_ID) and the business key (CORRECTED_TREASURY_PAY_NUMBER) is important: integrations should join on the business key when exchanging data with Treasury-facing systems, while internal logic should use the surrogate identifier for referential stability.

Common Use Cases and Queries

The table supports reconciliation, audit, and reporting activities. A typical reconciliation query compares original and corrected Treasury payment numbers and totals offset amounts by party:

  • Identify offsets for a specific Treasury payment: SELECT * FROM fv.fv_tc_offsets WHERE original_treasury_pay_number = :pay_num;
  • Summarize offsets by party and amount: SELECT offset_party_name, SUM(offset_amount) FROM fv.fv_tc_offsets GROUP BY offset_party_name;
  • Audit recently changed offset records: SELECT fv_tc_offset_id, last_updated_by, last_update_date FROM fv.fv_tc_offsets WHERE last_update_date > SYSDATE - 30;
  • Trace corrections for a disbursement using the linking key: SELECT * FROM fv.fv_tc_offsets WHERE check_id = :check_id;

Reporting use cases include Treasury discrepancy aging reports, federal disbursement correction audits, and agency-level offset trend analysis using the ATTRIBUTE flexfield columns for categorization.

Related Objects

The documented metadata records no foreign-key relationships, consistent with its standalone classification. Logical dependencies to consider when querying or integrating include:

  • FV_TREASURY_CONFIRMATIONS — the parent confirmation records whose payment numbers (original and corrected) are referenced here.
  • FV_PAYMENTS / payment tables keyed by CHECK_ID, which supply the underlying disbursement detail.
  • AP_CHECKS — the Payables check records that ultimately correspond to the CHECK_ID value.
  • FV_TC_OFFSETS-related concurrent programs in the Federal Financials module that create offset records during confirmation processing.
  • FND_FLEX_VALUES — the value-set source for ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 descriptive flexfield validation.

Because the object is standalone at the schema level, implementers should verify join paths against the product's application logic rather than relying on declared constraints.