Search Results fabv_trans_lines




Overview

FABV_TRANS_LINES is a read-only view in the APPS schema belonging to the Oracle Assets (OFA) product family. It is a retrofitted compatibility view, meaning it exists to provide a stable, backward-compatible interface over an underlying transactional table while shielding callers from the physical column layout of that table. In Oracle EBS 12.1.1 and 12.2.2, the view presents asset adjustment line information in a normalized, debit/credit-oriented format suitable for reporting, financial reconciliation, and integration with external systems that expect a two-column accounting presentation rather than a signed amount.

The name indicates that the view exposes transaction lines — individual asset adjustment distributions — rather than transaction headers. Each row corresponds to one adjustment line tied to a period, a book, an asset, and a distribution. Because the view is created WITH READ ONLY, it cannot be used as a DML target; all maintenance is performed against the underlying base table.

Underlying Base Objects

The documented base object is FA_ADJUSTMENTS, a synonym resolving to the APPS-owned asset adjustments table. The view text is a direct projection of that table:

The view carries no joins and no filters; it is a pure column-remapping and pivoting layer over FA_ADJUSTMENTS, which keeps it inexpensive but also means it inherits the row volume and any performance characteristics of the base table.

Key Columns

  • ACCOUNT_TYPE (ADJUSTMENT_TYPE): classifies the adjustment line, for example additions, transfers, revaluations, or retirements.
  • DEBIT_AMOUNT / CREDIT_AMOUNT: derived debit and credit amounts; exactly one is populated per row based on DEBIT_CREDIT_FLAG.
  • TRANSACTION_HEADER_ID: identifies the parent adjustment transaction, allowing lines to be grouped into a header.
  • SOURCE_TYPE_CODE: the source system or process that created the adjustment, such as manual entry, mass additions, or interface import.
  • BOOK_TYPE_CODE: the asset book against which the adjustment is recorded.
  • ASSET_ID: the asset to which the line belongs.
  • CODE_COMBINATION_ID: the accounting flexfield combination for the distribution.
  • DISTRIBUTION_ID: the specific distribution record associated with the line.
  • PERIOD_COUNTER_ADJUSTED: the period in which the adjustment is posted or effective. This is the column most relevant to the search term. It maps to FA_PERIODS via PERIOD_COUNTER and differs from PERIOD_COUNTER_CREATED, which records when the row was entered.
  • PERIOD_COUNTER_CREATED: the period in which the adjustment record was created.
  • LAST_UPDATE_DATE / LAST_UPDATED_BY: standard audit columns.

Common Use Cases and Queries

Typical usage includes: reconciling asset adjustments to the general ledger, reporting depreciation-adjusted balances by period, validating interface loads from mass additions, and comparing the posting period against the creation period to detect late adjustments. The following query lists debit and credit lines posted in a given period for a book:

  • SELECT transaction_header_id, asset_id, account_type, debit_amount, credit_amount
  • FROM fabv_trans_lines
  • WHERE book_type_code = 'CORP'
  • AND period_counter_adjusted = :p_period;

To detect adjustments posted in a period different from the one in which they were created, compare PERIOD_COUNTER_ADJUSTED against PERIOD_COUNTER_CREATED and join FA_PERIODS to resolve period names. Because the view is read-only and unfiltered, always restrict queries by BOOK_TYPE_CODE, PERIOD_COUNTER_ADJUSTED, or ASSET_ID to avoid full scans of FA_ADJUSTMENTS in high-volume environments.