Search Results fv_be_account_pairs




Overview
Explore in AI Chat

Overview

FV_BE_ACCOUNT_PAIRS is a transaction table in the FV (Federal Financials) product of Oracle E-Business Suite. It stores the account pairings that link transaction types and sub-types to specific debit and credit account segment values. In Federal Financials implementations, this table drives the automatic derivation of accounting flexfield combinations when budgetary and proprietary transactions are generated, ensuring that each transaction type and sub-type combination resolves to a defined debit/credit account pair for a given ledger.

The ETRM metadata classifies this object, using a heuristic derived from its foreign key structure, as standalone within a Data Vault model. It does not behave as a classic hub, link, or satellite; instead it functions as a reference or mapping table that links transaction type definitions to chart-of-accounts segment values. Modeling suggestions should therefore treat it as a mapping/reference entity rather than a transaction hub or a dependent satellite.

Key Information Stored

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

  • CHART_OF_ACCOUNTS_ID — Identifies the chart of accounts (accounting flexfield structure) under which the account pairing applies. This foreign key references GL_MGT_SEG_UPGRADE_H.
  • BE_TT_ID — The budgetary execution transaction type identifier. This foreign key references FV_BE_TRANSACTION_TYPES and is the primary business driver of each row.
  • SUB_TYPE — Discriminates the transaction sub-type paired with the transaction type, allowing multiple account pairings per transaction type.
  • LEDGER_ID — The ledger for which the account pair is valid; account pairings can differ by ledger, so this column is essential for correct resolution in multi-ledger implementations.
  • DR_ACCOUNT_SEGMENT_VALUE — The debit account segment value applied to transactions matching the type/sub-type key.
  • CR_ACCOUNT_SEGMENT_VALUE — The credit account segment value applied to the same matching transactions.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS WHO columns capturing audit and concurrency information.

No explicit surrogate primary key column is documented in the provided metadata; the business-key candidate is the combination of CHART_OF_ACCOUNTS_ID, BE_TT_ID, SUB_TYPE, and LEDGER_ID, which uniquely identifies the account pairing for a transaction type, sub-type, and ledger. In the physical schema, row identity is typically enforced through a unique index over these business-key columns rather than a single generated surrogate.

Common Use Cases and Queries

Typical usage includes determining which debit and credit accounts will be generated for a given transaction type and sub-type, validating that every active transaction type has an account pairing, and auditing account pairings across ledgers. A representative query is:

  • Join FV_BE_ACCOUNT_PAIRS to FV_BE_TRANSACTION_TYPES on BE_TT_ID to report transaction type names alongside their debit and credit segment values.
  • Filter by LEDGER_ID and CHART_OF_ACCOUNTS_ID to review pairings for a specific ledger or chart of accounts.
  • Use an outer join from FV_BE_TRANSACTION_TYPES to FV_BE_ACCOUNT_PAIRS to find transaction types missing account pairings.
  • Query by SUB_TYPE to confirm that each sub-type resolves to the intended debit/credit accounts before period close.

Related Objects

The most significant related objects are the foreign-key parents and the surrounding Federal Financials reference structures:

  • FV_BE_TRANSACTION_TYPES — joined via BE_TT_ID; defines the budgetary execution transaction types whose accounts are paired here.
  • GL_MGT_SEG_UPGRADE_H — joined via CHART_OF_ACCOUNTS_ID; supplies the chart of accounts context.
  • GL_LEDGERS / GL_LEDGER_CONFIGURATIONS — joined via LEDGER_ID to resolve ledger names and configurations.
  • FND_FLEX_VALUES — joined on DR_ACCOUNT_SEGMENT_VALUE and CR_ACCOUNT_SEGMENT_VALUE to resolve segment value descriptions.
  • FV_BE_TRANSACTION_TYPE_SUBTYPES — used with SUB_TYPE to validate the type/sub-type combinations.

Together these objects form the reference layer that governs automatic account derivation in Federal Financials, with FV_BE_ACCOUNT_PAIRS serving as the central mapping between transaction classification and accounting flexfield values.