Results for “fafv_trans_lines”

22 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FAFV_TRANS_LINES is a read-only Oracle E-Business Suite view owned by the APPS schema and belongs to the OFA (Oracle Assets) product family. In the EBS 12.1.1 and 12.2.2 data models, it exposes the accounting transaction lines generated by Oracle Assets adjustments, presenting them in a debit/credit normalized form suitable for reporting, reconciliation, and subledger-to-general-ledger analysis. Unlike the base adjustment table FA_ADJUSTMENTS, which stores a single signed adjustment amount, this view splits the amount into distinct DEBIT_AMOUNT and CREDIT_AMOUNT columns using the debit/credit indicator on each adjustment row.

The view joins Assets adjustments to depreciation periods, the general ledger chart of accounts, and the Subledger Accounting (XLA) tables that link each adjustment line to its corresponding accounting entry. Because of this linkage, FAFV_TRANS_LINES is typically used when there is a need to trace an Assets adjustment source line to the SLA journal line it produced, rather than for simple transactional queries. The view is defined WITH READ ONLY, so it cannot be used for data modification.

Underlying Base Objects

The documented base objects referenced by FAFV_TRANS_LINES are:

  • FA_ADJUSTMENTS (SYNONYM) — the primary source of adjustment lines, including adjustment amount, debit/credit flag, book, asset, and distribution identifiers.
  • FA_DEPRN_PERIODS (SYNONYM) — joined twice (aliased DP1 and DP2) to resolve the period name for the adjusted period and the period in which the adjustment was created.
  • GL_CODE_COMBINATIONS (SYNONYM) — supplies the accounting flexfield combination associated with the adjustment.
  • XLA_AE_LINES (SYNONYM) — the Subledger Accounting journal lines linked to the distribution.
  • XLA_DISTRIBUTION_LINKS (SYNONYM) — the bridge between the source distribution and the SLA accounting entry, filtered to APPLICATION_ID = 140 (Assets) and SOURCE_DISTRIBUTION_TYPE = 'TRX'.

The joins constrain each adjustment line to its matching depreciation period names, chart of accounts combination, and SLA accounting line, so only adjustments that have been successfully linked to accounting entries are returned.

Key Columns

  • DEBIT_AMOUNT — the adjustment amount returned only when the debit/credit flag is 'DR'; otherwise null. This is the column most commonly searched for in reporting.
  • CREDIT_AMOUNT — the adjustment amount returned only when the flag is 'CR'; otherwise null.
  • ADJUSTMENT_TYPE — the classification of the adjustment (for example, cost or depreciation adjustments).
  • TRANSACTION_HEADER_ID / DISTRIBUTION_ID — identifiers used to trace the adjustment back to its source transaction and distribution.
  • SOURCE_TYPE_CODE / BOOK_TYPE_CODE / ASSET_ID — source, depreciation book, and asset context for the line.
  • CODE_COMBINATION_ID and the descriptive flexfield column "_KF:EXPENSE_ACCOUNT" — the accounting flexfield reference resolved through GL_CODE_COMBINATIONS.
  • PERIOD_ADJUSTED / PERIOD_CREATED — period names derived from the two FA_DEPRN_PERIODS joins, identifying when the adjustment applies and when it was entered.
  • LAST_UPDATE_DATE / LAST_UPDATED_BY — audit columns reflecting the most recent change to the adjustment row.

Common Use Cases and Queries

The view is typically queried to reconcile Assets adjustments with SLA journal entries, to report debits and credits by book and period, or to investigate a specific asset's adjustment activity. A representative query filtering on the debit amount is:

  • SELECT asset_id, book_type_code, period_adjusted, debit_amount, credit_amount FROM apps.fafv_trans_lines WHERE debit_amount IS NOT NULL AND book_type_code = :book ORDER BY period_adjusted;
  • Aggregation by book and period to compare total adjustments with General Ledger balances.
  • Joining TRANSACTION_HEADER_ID or DISTRIBUTION_ID back to FA_ADJUSTMENTS for detailed source inspection.

Because the view requires populated XLA distribution links, adjustments that have not yet been accounted may be absent, which is an important consideration when reconciling results.