Search Results fv_be_ba_fd_dtl_v




Overview
Explore in AI Chat

Overview

The APPS.FV_BE_BA_FD_DTL_V view is a reporting and integration object within the Oracle E-Business Suite Federal Financials (FV) product. Its documented purpose is to serve as the transaction extract lines source for Subledger Accounting (SLA), allowing SLA to identify the originating budgetary and fund distribution detail associated with federal accounting events. In this capacity the view acts as a bridge between the FV budgetary execution transaction tables and the SLA engine that generates final accounting entries. The view is owned by APPS, is marked VALID, and is present in both EBS 12.1.1 and 12.2.2 environments that have Federal Financials licensed and configured.

Because the view projects the accounting-relevant attributes of each transaction line — including the fund distribution account, the individual budgeting segment values, the increase/decrease indicator, and the accounted amount — it is a primary candidate whenever an SLA transaction extract is required for federal budgetary or fund control processing.

Underlying Base Objects

The ETRM metadata documents the following referenced objects for FV_BE_BA_FD_DTL_V:

The view text confirms that the primary driver is the transaction detail table aliased DTL (FV_BE_TRX_DTLS), joined to the events global temporary table (XLA_EVENTS_GT, alias GT) on EVENT_ID, to the transaction type table (FV_BE_TRANSACTION_TYPES, alias TT) via TRANSACTION_TYPE_ID, and to GL_LEDGERS (alias GL) via the chart of accounts. The FV_BE_XLA_PKG package is invoked through its GET_CCID function to resolve the fund distribution account (CCID) from the budgeting segment string, and account pair and sub-type objects supply the fed/rec code structure used by the extract.

Key Columns

  • EVENT_ID — Identifier of the SLA event driving the extract; joins to XLA_EVENTS_GT.
  • LINE_NUMBER — Derived from DTL.TRANSACTION_ID, uniquely identifying each extracted line.
  • TRANSACTION_TYPE_ID / SUB_TYPE — Transaction classification and sub-classification used to group and interpret the line.
  • FUND_DISTRIBUTION_ACCOUNT — The CCID returned by FV_BE_XLA_PKG.GET_CCID for GL# using the budgeting segments; the resulting distribution account code combination.
  • LINE_SEGMENT1 through LINE_SEGMENT30 — The individual budgeting segment values expanded from DTL for each line.
  • INCREASE_DECREASE_FLAG — Indicates whether the line represents an increase or decrease to the affected budget/fund balance. Combined with the signed accounted amount, it determines the direction of the SLA posting.
  • ACCOUNTED_AMOUNT — The amount mapped from DTL.AMOUNT, representing the accounted value to be journalized.
  • LINE_ATTRIBUTE1 through LINE_ATTRIBUTE15 / LINE_ATTR_CATEGORY — Descriptive flexfield context and attribute values carried through for extract completeness.
  • CORRECTED_FLAG, GROUP_ID — Flags and grouping identifiers supporting correction and grouping semantics in the extract.
  • TRANSACTION_TYPE — Human-readable approval transaction type from FV_BE_TRANSACTION_TYPES (TT.APPRN_TRANSACTION_TYPE).
  • DR / CR — Debit/credit indicators projected from the account pair information used by SLA.

Common Use Cases and Queries

The principal use case is configuring or troubleshooting SLA transaction extract definitions for Federal Financials budgetary accounting, particularly where increase/decrease directionality and budgeting segment distribution must be preserved into the final journal. Typical supporting queries include:

  • Reviewing all extract lines for a specific SLA event: SELECT event_id, line_number, transaction_type, sub_type, fund_distribution_account, increase_decrease_flag, accounted_amount FROM apps.fv_be_ba_fd_dtl_v WHERE event_id = :event_id;
  • Auditing the distribution of increase versus decrease activity: SELECT increase_decrease_flag, transaction_type, COUNT(*), SUM(accounted_amount) FROM apps.fv_be_ba_fd_dtl_v GROUP BY increase_decrease_flag, transaction_type;
  • Validating that budgeting segment values resolve to the expected fund distribution account for a given ledger.
  • Investigating extract completeness by joining EVENT_ID back to the SLA events temporary table.

Because the view depends on FV_BE_XLA_PKG.GET_CCID and XLA_EVENTS_GT, queries are typically executed within the SLA accounting/event processing context, where the events global temporary table is populated.