Search Results fv_bd_controls_u1

Overview

FV_BD_CONTROLS is a table in the FV schema (Oracle E-Business Tax / ETRM) that stores budgetary discount control transactions associated with invoice payments. Within the Oracle EBS 12.1.1 and 12.2.2 data model, it functions as a control and staging surface used by the budgetary discount reconciliation and journal import processes, allowing the application to group invoice payment records and flag their processing status before downstream accounting entries are generated.

Based on the documented foreign key relationship — INVOICE_PAYMENT_ID referencing AP_INVOICE_PAYMENTS_ALL — and the absence of child tables referencing FV_BD_CONTROLS, the object exhibits a heuristic Data Vault classification of satellite-leaning. In Data Vault modeling terms, this suggests the table behaves as a descriptive satellite attached to the invoice payment hub (AP_INVOICE_PAYMENTS_ALL), carrying control flag state and concurrent program audit attributes rather than serving as an independent hub or a linking table. The registration in FND Design Data (FV.FV_BD_CONTROLS) confirms it is a seeded, application-owned object.

Key Information Stored

The table contains 12 documented columns. The most significant are:

• INVOICE_PAYMENT_ID (NUMBER 15) — Invoice payment identifier. It is the column of the unique index FV_BD_CONTROLS_U1 and is therefore the documented business-key candidate and the foreign key to AP_INVOICE_PAYMENTS_ALL. It is not a system-generated surrogate; it derives its identity from the invoice payment.
• GROUP_ID (NUMBER 15) — Group identifier used by journal import; the basis of the non-unique index FV_BD_CONTROLS_N1, used to consolidate rows processed together.
• CONTROL_FLAG (VARCHAR2) — A Y or N flag indicating the control status of the budgetary discount transaction.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard WHO columns capturing the user and timestamp audit trail.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent Program WHO columns identifying the concurrent request and program that last touched the row.

The unique index FV_BD_CONTROLS_U1 on INVOICE_PAYMENT_ID enforces one control record per invoice payment, making that column the effective primary key from a business perspective.

Common Use Cases and Queries

The table is typically queried to reconcile invoice payments awaiting or undergoing budgetary discount processing, and to trace which concurrent request last modified a control row. A representative query joins the table to AP_INVOICE_PAYMENTS_ALL:

• SELECT c.INVOICE_PAYMENT_ID, c.GROUP_ID, c.CONTROL_FLAG FROM FV.FV_BD_CONTROLS c WHERE c.CONTROL_FLAG = 'N'; — retrieves payments not yet processed.
• Grouping by GROUP_ID to count records per journal import batch.
• Joining to FND_CONCURRENT_REQUESTS on REQUEST_ID to identify the program run that produced or updated rows.
• Joining to AP_INVOICE_PAYMENTS_ALL on INVOICE_PAYMENT_ID to report payment-level detail for discount accounting.

Reporting use cases include exception reports for unflagged control records and audit trails for concurrent program activity.

Related Objects

• AP_INVOICE_PAYMENTS_ALL — Parent of INVOICE_PAYMENT_ID; the primary reference target.
• AP_INVOICE_PAYMENT_HISTORY_ALL — Related payment history for discount reconciliation.
• FND_CONCURRENT_REQUESTS — Joined via REQUEST_ID for program run auditing.
• FND_USER — Joined via LAST_UPDATED_BY / CREATED_BY.
• FND_CONCURRENT_PROGRAMS — Joined via PROGRAM_ID.
• GL_JE_BATCHES / GL_IMPORT_REFERENCES — Downstream journal import targets keyed by GROUP_ID.