FA_ADDITIONS_B contains descriptive information to help identify your assets.
When adding an asset, Oracle Assets inserts a row into this table and into the FA_ASSET_HISTORY table.
When changing the asset information stored in this table, Oracle Assets updates it in this table and also creates a new row in FA_ASSET_HISTORY.
When performing a unit retirement, Oracle Assets reduces the CURRENT_UNITS by the units retired.
FA_ASSET_HISTORY contains information about asset category change, capitalizations, unit adjustments, and partial unit retirements.
When you initially add an asset, Oracle Assets inserts one row into the table and this becomes the active row for the asset.
When you perform category change or unit adjustment for an asset, Oracle Assets marks this row as obsolete and inserts a new row.
If you either reclassify an asset or change its asset type in the period in which you added the asset, Oracle Assets simply updates the row, since the transaction has no financial impact.
At any point in time, there is only one active row in the table for an asset, and you can always identify it because it is the only one who’s DATE_INEFFECTIVE is NULL.
FA_ASSET_INVOICES contains the invoice information from Oracle Payables and Oracle Purchasing for the assets to track the source asset information.
This table also stores all costs interfaced from projects including labor and expenses.
Oracle Assets inserts a row into this table for each asset added with source line information.
FA_BOOKS contains the information needed for calculating depreciation. When you initially add an asset, Oracle Assets inserts one row into the table and that becomes the active row for the asset.
Whenever you change the asset’s depreciation information, or if you retire or reinstate it, Oracle Assets inserts another row into the table, which then becomes the new active row, and marks the previous row as obsolete.
At any point in time, there is only one active row in the table for an asset in any given depreciation book. Generally, Oracle Assets uses the active row, but if you run a report for a prior accounting period, Oracle Assets selects the row that was active during that period.
When you retire an asset, Oracle Assets inserts a new row to reduce the COST by the amount retired. When you reinstate an asset, Oracle Assets inserts a new row to increase the COST by the COST_RETIRED in the corresponding row in FA_RETIREMENTS.
One can mapped active row value in the table with Asset Workbench→ Financial Inquiry screen as follows
Column: – DATE_PLACED_IN_SERVICE
Date on which the asset was placed in service.
Column: – ADJUSTED_COST
Depreciable basis of the asset, calculated as recoverable cost for cost basis depreciation methods, and recoverable cost less the accumulated depreciation for net book value basis methods.
Column: – COST
Total recorded cost of the asset.
Column: – ORIGINAL_COST
Original cost of the asset at the time of its addition.
Column: – DATE_INEFFECTIVE
Date when the row became inactive.
Column: – TRANSACTION_HEADER_ID_IN
Identifier of the transaction that created the row.
Column: – TRANSACTION_HEADER_ID_OUT
Identifier of the transaction that terminated the row.
Column: – CIP_COST
Construction-in-Process cost of the asset.
Q1) How to identify active row in FA_BOOKS table
→ Date_ineffective and Transaction_header_id_out should be null.
FA_CATEGORIES_B stores information about your asset categories. This table provides default information when you add an asset. The depreciation program does not use this information to calculate depreciation.
FA_CATEGORY_BOOKS contains cost and reserve accounts for a book and category combination.
A row inserted into this table for each book to which the asset category is assigned.
For example, if you define a category for three depreciation books, Oracle Assets inserts three rows into this table.
FA_DEPRN_SUMMARY contains depreciation information for the assets. Each time the depreciation program is run, it inserts one row into this table for each asset.
FA_DEPRN_DETAIL contains the depreciation amounts that the depreciation program charges to the depreciation expense account in each distribution line. Oracle Fusion Assets uses this information to create depreciation expense journal entries.
The depreciation program inserts one row per distribution line for an asset each depreciation process run. For example, if you assign an asset to two different cost centers, the depreciation program inserts two rows in this table for the asset.
FA_BOOK_CONTROLS contains all information about the asset depreciation book.
Oracle Assets inserts rows to FA_TRANSACTION_HEADERS each time you enter a transaction.
TRANSACTION_TYPE_CODE identifies the type of transaction:
ADDITION – created by the Books and QuickAdditions forms and Mass Additions Post when you add an asset. Also created by the Books form when changing an asset’s financial data in the period you added it. Created by the Capitalize CIP Assets form when capitalizing a CIP asset.
ADDITION/VOID – created by the Books form when you make changes to an asset’s financial data in the period you added it. Also created by Mass Additions Post when you add a mass addition line to an asset in the period you added it. Oracle Assets voids the original ADDITION by changing the transaction type to ADDITION/VOID and creating a new ADDITION transaction with the new data.
ADJUSTMENT – created by the Books and Mass Change forms when you change an asset’s financial data after the period of addition. Also created by Mass Copy when copying adjustments to a tax book. Mass Additions Post creates this type for add-to-assets. CIP ADDITION – created by the Books and Quick Additions forms and Mass Additions Post for CIP addition. Also created by Mass Additions Post when adding mass additions lines to new CIP assets. CIP ADDITION/VOID – created by the CIP Asset Adjustments form and the Transfer Invoice Lines form when adjusting the cost of a CIP asset in the period you added it. Mass Additions Post also creates this transaction type when you add a mass addition line to a CIP asset in the period you added it. Oracle Assets voids the original CIP ADDITION by changing its type to CIP ADDITION/VOID and creating a new CIP ADDITION transaction with the new data. CIP ADJUSTMENT – created by the Transfer Invoice Lines form when changing a CIP asset’s cost in a period after the period you added the asset. Also created by Mass Additions Post when you add a mass additions line to a CIP asset after the period you added it. CIP REVERSE – created by the Capitalize CIP Assets form when you reverse capitalize a CIP asset in the period you capitalized it. FULL RETIREMENT and PARTIAL RETIREMENT – created by the Retirements form when you fully and partially retire an asset respectively. Also created by Mass Copy when copying these retirements to a tax book. RECLASS – created by the Additions form when changing the asset category. Also created by Mass Additions Post when you add a mass addition line and change the asset category of the existing asset to the category you assigned to the mass addition. REINSTATEMENT – created by the Retirements form when you reinstate a retired asset. Also created by Mass Copy when copying reinstatements to a tax book. TAX – created by the Reserve Adjustments form and Mass Tax Adjustments when you change tax reserves. TRANSFER – created by the Assignments form and Mass Transfers for transfers. TRANSFER IN – created by the Assignments and Quick Additions forms, and Mass Additions Post when assigning GL accounts, locations and employees to new assets. TRANSFER IN/VOID – created by the Assignments form when changing GL accounts, locations or employees in the period of addition. The form voids the original TRANSFER IN by changing the type to TRANSFER IN/VOID and creating a new TRANSFER IN transaction with the updated data. TRANSFER OUT and UNIT ADJUSTMENT – created by the Assignments form when you partially retire by units and adjust the number of units respectively.
FA_DISTRIBUTION_HISTORY contains information about the employee, location, and Accounting Flexfield values you assign to your assets.
The depreciation program uses this information to allocate depreciation expense and the Transfers form uses it to maintain an audit trail of asset transfers. .
When you initially assign distributions to an asset using the Transfers form, Oracle Assets inserts one row into this table for each distribution.
Whenever you transfer, retire, reinstate, or reclassify an asset, Oracle Assets marks the appropriate rows as obsolete and creates new rows that reflect changes in assigned units, employees, general ledger depreciation expense account, or location. .
Oracle Assets terminates a row by setting the DATE_INEFFECTIVE and TRANSACTION_HEADER_ID_OUT to the DATE_EFFECTIVE and TRANSACTION_HEADER_ID_IN of the new row. This means you can identify rows affected by the same transaction because they have the same DATE_EFFECTIVE / DATE_INEFFECTIVE and TRANSACTION_HEADER_ID_IN / TRANSACTION_HEADER_ID_OUT pairs.
For new rows, TRANSACTION_HEADER_ID_IN is the same as TRANSACTION_HEADER_ID of the row inserted into FA_TRANSACTION_HEADERS for the transaction, and DATE_EFFECTIVE is the system date. .
When you perform a full retirement, Oracle Assets updates the asset’s current distribution lines with the RETIREMENT_ID from FA_RETIREMENTS so you can easily determine which retirement affected the rows.
Oracle Assets stores the number of units retired as a negative number in TRANSACTION_UNITS. The sum of TRANSACTION_UNITS for the retired distribution lines matches the UNITS column in FA_RETIREMENTS, except the signs are opposite. .
When you perform a partial unit retirement, Oracle Assets updates only the rows affected by the retirement. For any distribution lines that have units remaining after the retirement, Oracle Assets inserts new rows into this table where UNITS_ASSIGNED is reduced by the units retired, and terminates the old rows. .
Partial cost retirements do not affect this table. .
If you reinstate a full retirement, Oracle Assets inserts new rows that are the same as those that were active when you retired the asset, except that they have a different DISTRIBUTION_ID, TRANSACTION_HEADER_ID_IN and DATE_EFFECTIVE.
If you reinstate a partial unit retirement, Oracle Assets inserts new rows that are the same as those that were active except UNITS_ASSIGNED increases by the units retired and the rows have a new DISTRIBUTION_ID, TRANSACTION_HEADER_ID_IN and DATE_EFFECTIVE.
Oracle Assets terminates the previous rows by setting TRANSACTION_HEADER_ID_OUT to the TRANSACTION_HEADER_ID of the reinstated transaction. . RETIREMENT_ID identifies all the rows affected by a retirement. . TRANSACTION_UNITS is the number of units affected by each retirement, reinstatement, transfer, and addition or reclassification transaction.
FA_MASS_ADDITIONS stores information about assets that you want to automatically add to Oracle Assets from another system. You can use this table to load assets for system conversions.
When you run the mass additions create process, Oracle Assets inserts one row into this table for each invoice line it selects from Oracle Payables.
When you run the Mass Additions Post process, Oracle Assets creates assets or adjustments from any rows in which the POSTING_STATUS is POST.
Mass additions post inserts rows into FA_ADDITIONS, FA_ASSET_HISTORY, FA_ASSET_INVOICES, FA_BOOKS, FA_DISTRIBUTION_HISTORY, FA_TRANSACTION_HEADERS, FA_INVOICE_TRANSACTIONS, FA_DEPRN_SUMMARY, FA_DEPRN_DETAIL, and FA_TRANSFER_DETAILS.
Oracle Assets then changes POSTING_STATUS and QUEUE_NAME to POSTED. POSTING_STATUS shows the status of a mass addition.
POSTING_STATUS and QUEUE_NAME are the same, except when you assign user-defined queue names, or you split or merge a mass addition. The following table summarizes the relationship between POSTING_STATUS and QUEUE_NAME: POSTING_STATUS QUEUE_NAME — Description =========================
NEW NEW — Status when mass addition is first created.
ON HOLD ON HOLD — Waiting for additional information before posting.
Posting Status after split
SPLIT — You divided a multi-unit mass addition into individual mass additions.
Posting Status after merge
MERGED — You merged other mass additions into this one.
POST ADD TO ASSET — You are adding a mass addition to an existing asset as a cost adjustment and the mass addition is ready for posting.
POST POST — Ready for posting.
POSTED POSTED — The Mass Additions Post program created an asset from this mass addition.
DELETE DELETE — Delete this mass addition.
The SPLIT_MERGED_CODE column tells you whether a mass addition was split or merged: MC Merged child – You merged this mass addition into another one. MP Merged parent – You merged other mass additions into this one.
SC Split child – Oracle Assets created this mass addition from a multi-unit mass addition. SP Split parent – You split this multi-unit mass addition into single-unit mass addition. When you add the cost of a mass addition to an existing asset, NEW_MASTER_FLAG is set to Yes by the Prepare Mass Additions form when the resulting asset has the asset category and description of the mass addition.
FA_ADJUSTMENTS stores information that Oracle Assets needs to create journal entries for transactions.
The posting program creates journal entries for regular depreciation expense from information in FA_DEPRN_DETAIL.
Oracle Assets inserts a row in this table for the debit and credit sides of a financial transaction. All the rows for the same transaction have the same value in the TRANSACTION_HEADER_ID column. .
The SOURCE_TYPE_CODE column tells you which program created the adjustment: . ADDITION — Depreciation program.
ADJUSTMENT– Expensed or Amortized Adjustment
CIP ADDITION–Depreciation program.
CIP ADJUSTMENT–Expensed or Amortized Adjustment
CIP RETIREMENT–Gain/loss program.
DEPRECIATION–Depreciation program (Retroactive transactions and expensed depreciation adjustments).
TAX–Reserve Adjustments form.
REVALUATION–Mass revaluation program . . .
The ADJUSTMENT_TYPE column tells you which type of account Oracle Assets adjusts. .
DEBIT_CREDIT_FLAG is DR if the amount is a debit and CR if the amount is a credit. .
ADJUSTMENT_AMOUNT is the amount debited or credited to the account. .
ANNUALIZED_ADJUSTMENT is the adjustment amount for a period times the number of periods in a fiscal year. The depreciation program uses it to calculate the depreciation adjustment for an asset when you perform multiple retroactive transactions on the asset. Oracle Assets calculates ADJUSTMENT_PER_PERIOD by dividing the
ADJUSTMENT_AMOUNT for a retroactive transaction by the number of periods between the period you entered the transaction and the period that it was effective. For current period transactions, this column is zero. .
PERIOD_COUNTER_CREATED IS the period that you entered the adjustment into Oracle Assets. .
PERIOD_COUNTER_ADJUSTED is the period to which the adjustment applies. It is the same as PERIOD_COUNTER_CREATED, unless you enter a reserve adjustment, in which case PERIOD_COUNTER_ADJUSTED is the last period of the fiscal year to which the adjustment applies. .
CODE_COMBINATION_ID indicates the Accounting Flexfield combination Oracle Assets debits or credits for all transactions except reclassifications and intercompany transfers. This CODE_COMBINATION_ID is generated using the Account Generator, and the posting program does not perform any further processing. . .
One thought on “Fixed Asset Tables R12 & Fusion Cloud”
for R12 fusion financial it’s a good information to get a better knowledge of fusion financial. it’s much useful to me. thank you for providing this information.