Results for “fa_adjustments”

50+ results




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

Overview

FA_ADJUSTMENTS is a transaction-level table in the Oracle Assets (OFA) module of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the accounting adjustment records that the Create Accounting / posting program consumes in order to generate journal entry lines in the General Ledger. Each row represents an individual adjustment line associated with a fixed asset transaction, capturing the debit or credit amount, the account combination to be charged, the affected asset, and the depreciation period context in which the adjustment was created and adjusted. In practice, FA_ADJUSTMENTS functions as the bridge between asset transaction processing and General Ledger journal creation, holding the pre-posted detail that determines how asset activity flows into GL balances.

From a dimensional modeling perspective, the mined foreign-key structure suggests a link classification (heuristic Data Vault). The table records associations among a transaction header, an asset, a distribution, a book, and GL code combinations, making it a relationship-bearing object rather than a pure hub or satellite. This classification should be treated as a modeling suggestion only; the table is native to the Oracle Assets operational schema and is not designed as a Data Vault construct.

Key Information Stored

The table contains 45 documented columns in the 12.2.2 physical schema. The most significant for functional and reporting purposes include:

The twenty GLOBAL_ATTRIBUTE columns plus GLOBAL_ATTRIBUTE_CATEGORY provide the standard Oracle descriptive flexfield extension mechanism. There is no single surrogate primary key documented; the unique index FA_ADJUSTMENTS_U1 supplies the business-key candidate.

Common Use Cases and Queries

FA_ADJUSTMENTS is typically queried to audit or reconcile asset adjustments against General Ledger postings. A common reporting pattern joins the table to FA_ADDITIONS_B for asset identification and to GL_CODE_COMBINATIONS for account description:

SELECT a.TRANSACTION_HEADER_ID, a.ASSET_ID, a.ADJUSTMENT_AMOUNT,
a.DEBIT_CREDIT_FLAG, a.CODE_COMBINATION_ID, a.JE_HEADER_ID
FROM FA_ADJUSTMENTS a
WHERE a.BOOK_TYPE_CODE = :book
AND a.PERIOD_COUNTER_CREATED = :period;

Typical scenarios include verifying which adjustments have been posted to GL (JE_HEADER_ID populated versus null), reconciling adjustments to their originating transactions, and analyzing annualized versus actual adjustment amounts for depreciation impact. The DEPRN_OVERRIDE_FLAG and TRACK_MEMBER_FLAG support specialized depreciation and member-tracking behavior when set.

Related Objects

The following objects are directly referenced through the documented foreign keys:

  • FA_TRANSACTION_HEADERS — joined on TRANSACTION_HEADER_ID; the parent transaction record.
  • FA_ADDITIONS_B — joined on ASSET_ID; the asset master.
  • FA_DISTRIBUTION_HISTORY — joined on DISTRIBUTION_ID; distribution detail.
  • FA_BOOK_CONTROLS — joined on BOOK_TYPE_CODE; book definition and control settings.
  • FA_DEPRN_PERIODS — joined on BOOK_TYPE_CODE with PERIOD_COUNTER_CREATED and PERIOD_COUNTER_ADJUSTED; period definitions.
  • GL_CODE_COMBINATIONS — joined on CODE_COMBINATION_ID; accounting flexfield combinations.
  • GL_JE_LINES — joined on JE_HEADER_ID and JE_LINE_NUM; the generated journal lines.

These relationships confirm the table's role as the linkage point between asset transactions and General Ledger journal creation.