Search Results line_segment1

Overview

FV_BE_BA_FD_DTL_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, published as part of the Federal Budget Execution (FV) module documentation for releases 12.1.1 and 12.2.2. The name decomposes as Budget Account (BA) Fund Distribution (FD) Detail (DTL) view, and it presents fund-distribution line detail that has been associated with an XLA accounting event. Its primary role is to expose the accounting-flexfield segments and descriptive attributes of each budget execution transaction line in a flattened, query-friendly form, so that Federal reporting, reconciliation, and downstream integration programs do not have to navigate the normalized transaction-detail tables directly. The view is particularly significant because it surfaces the full 30-segment accounting key, including the terminal column line_segment30, alongside the derived fund-distribution account identifier produced by the ETRM accounting engine.

Underlying Base Objects

The view is defined over a set of ETRM transaction- and accounting-related objects. The documented base objects are FV_BE_TRX_HDRS (transaction headers, a synonym), FV_BE_TRX_DTLS (transaction detail lines), FV_BE_TRX_SUB_TYPES, FV_BE_TRANSACTION_TYPES, FV_BE_ACCOUNT_PAIRS, GL_LEDGERS, XLA_EVENTS_GT (the Subledger Accounting events global temporary table), and the ETRM package FV_BE_XLA_PKG. The header object supplies the event identifier, the detail object supplies the segment, attribute, and amount columns, the transaction-type and sub-type objects provide descriptive classification, GL_LEDGERS supplies the chart of accounts context, and XLA_EVENTS_GT links the line to its accounting event. FV_BE_TRX_DTLS is the dominant contributor of columns, since the segment1 through segment30, attribute1 through attribute15, and amount fields all originate there.

Key Columns

Every column in the select list is explicitly aliased. The identifier columns event_id and transaction_id (aliased Line_Number) key the row to the accounting event and the originating detail line. The Fund_Distribution_Account column is not stored but computed at runtime by calling FV_BE_XLA_PKG.get_ccid, passing the application short name 'SQLGL', the key flexfield name 'GL#', the chart of accounts from GL_LEDGERS, the current SYSDATE, and the concatenated budgeting_segments string. The 30 accounting segments are individually exposed as line_segment1 through line_segment30; line_segment30, the column most relevant to the query that led here, is a straight passthrough of the thirty-first-position segment from the transaction detail record. Descriptive columns include increase_decrease_flag, corrected_flag, group_id, approval_date, public_law_code, advance_type, dept_id, main_account, and transfer_description. Amounts are exposed as Accounted_Amount (from the detail amount), while attribute1 to attribute15 and the descriptive flexfield category are surfaced as line_attribute and line_attr_category columns. Transaction_Type and the debit/credit segment values from FV_BE_ACCOUNT_PAIRS round out the projection.

Common Use Cases and Queries

Typical usage centers on budget execution reconciliation, fund-distribution extraction, and Federal Treasury reporting that requires the full accounting string. A common pattern selects the account segments and the derived account identifier for a limited event range:

• SELECT event_id, line_number, line_segment1, line_segment30, accounted_amount FROM apps.fv_be_ba_fd_dtl_v WHERE event_id = :p_event_id;
• Locating lines whose thirtieth segment matches a specific value: SELECT transaction_id, fund_distribution_account FROM apps.fv_be_ba_fd_dtl_v WHERE line_segment30 = :p_segment30;
• Auditing the debit/credit account pair against the derived CCID: SELECT line_number, dr_account_segment_value, cr_account_segment_value, fund_distribution_account FROM apps.fv_be_ba_fd_dtl_v WHERE increase_decrease_flag = 'I';

Because Fund_Distribution_Account is derived at query time through a package call and SYSDATE, the view is not suitable for high-volume bulk extraction without indexing or materialization; users should filter on event_id, group_id, or transaction_id first to constrain the result set.