Search Results fv_bd_controls

Overview

FV_BD_CONTROLS is a Federal Financials (FV) module table that stores budgetary discount control records. In Oracle EBS 12.1.1 and 12.2.2, the FV product supports U.S. federal government accounting requirements, including budgetary accounting, funds control, and the reconciliation of proprietary and budgetary transactions. FV_BD_CONTROLS functions as a control and staging structure tied to payment activity, holding discount-related budgetary data that downstream federal accounting processes consume.

From a Data Vault modeling perspective, the metadata's FK structure suggests this object is satellite-leaning. It does not appear to be a standalone hub or a pure link; instead, it depends on a parent business entity (the invoice payment) and carries descriptive and control attributes. Its unique index on INVOICE_PAYMENT_ID indicates a one-to-one or near one-to-one dependency on the payment record, which is characteristic of a satellite attached to a payment hub.

Key Information Stored

The table contains 12 documented columns. The most significant are the business-key and control columns.

• INVOICE_PAYMENT_ID — The foreign key to AP_INVOICE_PAYMENTS_ALL and the business-key candidate, enforced by the unique index FV_BD_CONTROLS_U1. This links each control row to a specific invoice payment in Payables.
• GROUP_ID — A grouping identifier used to associate related budgetary discount records, typically for batch processing or concurrent program runs.
• CONTROL_FLAG — A status/control indicator that governs the processing state of the budgetary discount record.
• REQUEST_ID — The concurrent request that created or last processed the row, supporting auditability and rerun tracing.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns identifying when and by whom the record was modified.
• CREATION_DATE, CREATED_BY — Standard EBS audit columns capturing record creation.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program context identifying the application and program responsible for the last update, plus the update timestamp.

There is no separate documented surrogate primary key beyond the unique business-key index on INVOICE_PAYMENT_ID.

Common Use Cases and Queries

The principal use case is auditing and reconciling budgetary discount processing against invoice payments. Analysts join FV_BD_CONTROLS to AP_INVOICE_PAYMENTS_ALL to trace which payments have associated discount control records and whether processing completed successfully. A representative query:

• SELECT c.invoice_payment_id, c.control_flag, p.amount, p.payment_date FROM fv.fv_bd_controls c, ap.ap_invoice_payments_all p WHERE c.invoice_payment_id = p.invoice_payment_id AND c.control_flag = :flag;
• Batch monitoring: filter by REQUEST_ID or GROUP_ID to verify all rows for a concurrent run were processed.
• Audit reporting: use analysis of CONTROL_FLAG and PROGRAM_UPDATE_DATE to identify stalled or unprocessed discount records.

Related Objects

The following objects are most relevant to FV_BD_CONTROLS:

• AP_INVOICE_PAYMENTS_ALL — Parent table; joined via FV_BD_CONTROLS.INVOICE_PAYMENT_ID = AP_INVOICE_PAYMENTS_ALL.INVOICE_PAYMENT_ID. This is the primary documented FK.
• AP_INVOICE_PAYMENTS — The base payment table underlying AP_INVOICE_PAYMENTS_ALL, useful for supplementary payment detail.
• AP_INVOICES_ALL — Links payments to their originating invoices for invoice-level reconciliation.
• FV_BUDGET_ACCOUNTS / FV budgetary distribution tables — Federal Financials tables that receive budgetary accounting entries generated for payment discounts.
• GL_JE_LINES — Where resulting accounting entries for budgetary discount adjustments may be viewed.

Together these objects support the Federal Financials flow from invoice payment through budgetary discount control to general ledger accounting.