FA-01: Asset Addition Diagnostic

Oracle EBS Fixed Assets asset addition failures occur at the intersection of the asset definition, the asset book, and the GL account distribution — and each layer can fail independently. When a new asset is manually added through the Assets form, Oracle FA validates the asset category against FA_CATEGORIES_B, the depreciation method and life against the book controls in FA_BOOK_CONTROLS, and the GL account distribution against GL_CODE_COMBINATIONS. Any one of these validations failing produces an error that prevents the asset from completing the addition process and reaching an IN SERVICE status.

The asset category is the most consequential setup element in asset addition. An asset category in Oracle FA carries the default depreciation method, asset life, prorate convention, and the default GL account assignments for the asset cost account, accumulated depreciation account, and depreciation expense account. When an asset is added with an incorrect category — either because the category was selected incorrectly by the requester, or because the correct category was not set up for the book — the asset will use incorrect depreciation parameters, potentially over- or under-depreciating the asset for its entire useful life. FA-01 identifies category mismatches before they become multi-period depreciation errors.

The Mass Additions process introduces a second addition pathway. When AP invoices for capitalizable assets are posted in Oracle Payables, the Post Mass Additions concurrent program copies the invoice distributions to FA_MASS_ADDITIONS, where an asset accountant reviews and prepares each line before running the Prepare Mass Additions and Post Mass Additions programs to convert them to actual asset records in FA_ADDITIONS_B. Errors in this pipeline — wrong category assigned during preparation, incorrect asset cost due to a split calculation error, missing employee or location assignment — are not visible until the asset accountant reviews the FA_MASS_ADDITIONS queue.

FA-01 runs a complete asset addition diagnostic — asset category and book assignment validation, depreciation method and life check against book controls, GL account distribution completeness and CCID validity, employee and location assignment, asset cost versus invoice cost reconciliation for mass additions, and duplicate asset detection by serial number and description. It surfaces every condition that will prevent the asset from being correctly added, depreciated, and reported.

Category & Book Validation

Asset category existence and active status in FA_CATEGORIES_B. Book assignment completeness — corporate and tax books. Depreciation method and life consistency with book controls.

GL Distribution Integrity

All three GL account types validated: cost account, accumulated depreciation account, and depreciation expense account. CCID active status in GL_CODE_COMBINATIONS for each.

Mass Addition Pipeline

FA_MASS_ADDITIONS queue status — ON HOLD, SPLIT, POST, POSTED. Invoice cost vs asset cost reconciliation. Split calculation accuracy. Category and location assignment completeness before posting.

Employee & Location

Location assignment in FA_LOCATIONS — active status. Employee assignment existence. Asset tag number recorded. Physical location consistent with depreciation expense account assignment.

Duplicate Detection

Serial number cross-reference against existing FA_ADDITIONS_B records. Description similarity matching for assets without serial numbers. Prior retirement check before duplicate confirmation.

════════════════════════════════════════════════════════════
  ORACLE EBS R12 — FA ASSET ADDITION DIAGNOSTIC
════════════════════════════════════════════════════════════
  Asset Number       : 112841
  Description        : Dell PowerEdge R750 Server
  Book               : US CORP
  Case Number        : FA-481020
  Report Date        : 20-FEB-2026 09:45:22
════════════════════════════════════════════════════════════

[ SECTION 1 — ASSET CATEGORY ]               STATUS: ✗ FAIL
────────────────────────────────────────────────────────────
  Category           : FURNITURE & FIXTURES
  Expected Category  : COMPUTER EQUIPMENT ✗
  Depr Method        : STL (Straight Line)
  Life Assigned      : 7 years ✗ — COMPUTER EQUIPMENT default: 3 years
  ✗ FAIL: Asset category FURNITURE & FIXTURES incorrect for server hardware
  Impact             : Asset will under-depreciate by $8,200/yr over 4 extra years

[ SECTION 2 — BOOK ASSIGNMENT ]              STATUS: ✓ PASS
────────────────────────────────────────────────────────────
  US CORP book active — asset date in service in open period ✓
  TAX book linked — no conflicts ✓

[ SECTION 3 — GL DISTRIBUTION ]              STATUS: ✓ PASS
────────────────────────────────────────────────────────────
  Cost account 01-100-1520-0000 — ACTIVE CCID ✓
  Accum depr 01-100-1521-0000 — ACTIVE CCID ✓
  Depr expense 01-500-6200-0000 — ACTIVE CCID ✓

[ SECTION 4 — LOCATION & EMPLOYEE ]          STATUS: ⚠ WARNING
────────────────────────────────────────────────────────────
  ⚠ Location: UNASSIGNED — tag number not recorded
  Employee           : J.MARTINEZ assigned ✓

[ SECTION 5 — DUPLICATE CHECK ]              STATUS: ✓ PASS
────────────────────────────────────────────────────────────
  No duplicate serial number or description match ✓

════════════════════════════════════════════════════════════
  DIAGNOSTIC SUMMARY
════════════════════════════════════════════════════════════
  1 blocking condition: incorrect asset category
  FIX: Recategorize asset 112841 to COMPUTER EQUIPMENT
  Life correction: 3 years, depr method: STL — saves $8,200/yr over-depr
════════════════════════════════════════════════════════════
  Backup Created  : CONS_BACKUP.FA_ADDITIONS_B_481020 ✓
  Registry ID     : 5041
════════════════════════════════════════════════════════════

Diagnostic Engine

Runs 35+ checks across asset category and book assignment validation, depreciation method and life against book controls, GL account distribution CCID validity across all three account types (cost, accum depr, depr expense), employee and location assignment, asset cost vs invoice cost reconciliation for mass additions, and duplicate detection by serial number.

Backup Created

Before any asset record is modified, CONS_BACKUP.FA_ADDITIONS_B_<case#>, FA_BOOKS_<case#>, and FA_DISTRIBUTION_HISTORY_<case#> are created and row counts verified.

Guided Data Fix

Category corrections on IN PROCESS assets are the primary direct-fix target — FA-01 updates CATEGORY_ID in FA_ADDITIONS_B and FA_BOOKS with full backup before any depreciation has run. Location assignments, tag numbers, and employee assignments are corrected directly with backup.

KB Article Generated

Complete KB article generated — asset number, category mismatch detail, depreciation impact calculation, fix applied, GL accounts verified. Upload directly to your knowledge base.

KB-FA-481020-001 · Script: FA-01

Asset 112841 Added with Incorrect Category — FURNITURE & FIXTURES vs COMPUTER EQUIPMENT

Module: Fixed Assets
Platform: EBS R12.2.10
Status: RESOLVED

Symptom

Asset 112841 (Dell PowerEdge R750 Server) added to US CORP book with category FURNITURE & FIXTURES (7-year life, STL). Correct category is COMPUTER EQUIPMENT (3-year life, STL). Asset cost $24,600 — incorrect category will cause $8,200/year under-depreciation over 4 extra years.

Root Cause

Asset addition form defaulted to FURNITURE & FIXTURES from the prior transaction in the session. The asset accountant did not override the default category for server hardware. The error was not caught by the AP invoice reviewer because the invoice description was generic.

Tables Affected

FA_ADDITIONS_B — ASSET_CATEGORY_ID (Asset 112841, CATEGORY_ID: 401 FURNITURE & FIXTURES)
FA_BOOKS — DEPRECIATION_METHOD_CODE, LIFE_IN_MONTHS (US CORP, Asset 112841 — 84 months vs correct 36)

Fix Applied

FA_ADDITIONS_B.ASSET_CATEGORY_ID corrected from 401 to 312 (COMPUTER EQUIPMENT) with full backup. FA_BOOKS.LIFE_IN_MONTHS corrected from 84 to 36. Depreciation recalculated for period — no prior depreciation had run. Asset location updated to DATACENTER-A.

Prevention

Asset addition form configured to require explicit category selection — no default carried from prior transaction. FA-01 category validation check to run as part of period-end asset addition review for all assets added during the period.

Incorrect Asset Category

Wrong category assigns incorrect depreciation method and life — producing years of incorrect depreciation if not caught before the first depreciation run. FA-01 calculates the total depreciation impact and corrects the category with full backup.

Error

Invalid GL Distribution Account

Disabled or end-dated CCID on the cost, accumulated depreciation, or depreciation expense account. Prevents the asset from generating correct journal entries. FA-01 identifies the disabled CCID and the active replacement.

Queue

Mass Addition ON HOLD

AP invoice line in FA_MASS_ADDITIONS stuck in ON HOLD status — missing category, split total mismatch, or cost issue. FA-01 identifies the hold reason and the correction needed to advance to POST.

Duplicate

Duplicate Asset by Serial Number

Same serial number exists on two active asset records — often from a mass addition that was posted twice or a manual addition entered in parallel with an in-flight mass addition. FA-01 identifies both records and the resolution path.

Table	Module	Purpose
FA_ADDITIONS_B	FA	Asset master — category, description, serial number, tag
FA_BOOKS	FA	Asset book assignments — depreciation method, life, cost
FA_DISTRIBUTION_HISTORY	FA	Asset GL distribution — cost account, location, employee
FA_CATEGORIES_B	FA	Asset category definitions — default method and life
FA_MASS_ADDITIONS	FA	AP-sourced addition queue — queue status, invoice link
FA_BOOK_CONTROLS	FA	Book configuration — allowed methods, current period
FA_DEPRN_DETAIL	FA	Depreciation history — confirms no prior deprn before correction
FA_LOCATIONS	FA	Location codes — active status
GL_CODE_COMBINATIONS	GL	Account combination validity — ENABLED_FLAG, date range

Decision Framework

How Every Fix Decision Is Made

Before any data is modified in a production Oracle database, AP-01 walks through a four-stage decision process. Every condition identified by the diagnostic maps to exactly one resolution path.

First Option — Always

Can the front end fix this?

Oracle's own forms and concurrent programs are always the first option. If the condition can be corrected through Oracle's standard UI — a form, a concurrent program, a setup screen — that path is taken first. No consultant SQL required, no database risk, and the fix is fully supported by Oracle. The diagnostic identifies these conditions explicitly and states the exact front-end navigation path.

✓ Functional Fix

When Front End Is Not Available

Is a direct data fix safe to apply?

When the front-end path is unavailable or would require an unacceptable volume of manual steps, a direct fix is evaluated against explicit criteria. All of the following must be true before proceeding:

→The fix mirrors exactly what Oracle's own code would have done if the underlying condition were corrected

→All dependent tables have been identified and will be updated in the same transaction

→The fix is fully reversible — a single INSERT from the backup table restores the original state

→The environment patch level has been confirmed against the fix logic version

⚡ Direct Fix

Hard Stops — No Exceptions

Does this require Oracle Support?

Certain table areas are never touched directly, regardless of how well the underlying structure is understood. The diagnostic flags these conditions and generates the Service Request documentation:

✗XLA subledger tables — XLA_EVENTS, XLA_AE_HEADERS — incorrect changes corrupt the subledger audit trail in ways undetectable until period close fails or an auditor requests a reconciliation

✗Workflow engine tables — WF_ITEMS, WF_ITEM_ACTIVITY_STATUSES — ad-hoc DML can corrupt the workflow engine state instance-wide

✗Recurring conditions after a fix — indicates a code defect, not a data error. Documented and submitted as a Service Request with a reproducible test case

⚠ Oracle Support

For All Approved Direct Fixes

Backup → Execute → Verify → Document

A timestamped backup table is created and row-count verified before the first UPDATE fires. Explicit parameter confirmation is required — the script will not self-execute. After execution, a verification query confirms the expected state. A complete change record — rows affected, before and after values, database username, timestamp — is written to the FIX_BACKUP_REGISTRY and becomes the primary artifact in the knowledge base entry for this incident.

📋 Documented

Condition Identified	Resolution Path	Notes
Incorrect asset category — wrong method/life assigned	Direct Fix	FA-01 corrects ASSET_CATEGORY_ID in FA_ADDITIONS_B and LIFE_IN_MONTHS/DEPRECIATION_METHOD_CODE in FA_BOOKS with full backup, provided no depreciation has run. If depreciation has run, a category reclassification transaction is required.
Invalid GL account distribution — disabled CCID	Direct Fix	FA-01 identifies the disabled CCID in FA_DISTRIBUTION_HISTORY and corrects CODE_COMBINATION_ID to the active replacement account with full backup. All three account types verified: cost, accum depr, depr expense.
Asset date in service in closed FA period	Direct Fix	FA-01 identifies the next open FA period and corrects DATE_PLACED_IN_SERVICE in FA_ADDITIONS_B with full backup. Pre-flight confirms asset has no depreciation rows in FA_DEPRN_DETAIL.
Missing location assignment — UNASSIGNED tag	Direct Fix	FA-01 corrects LOCATION_ID in FA_DISTRIBUTION_HISTORY with full backup. Location must be active in FA_LOCATIONS. Asset tag number updated in FA_ADDITIONS_B.TAG_NUMBER.
Asset cost vs AP invoice mismatch	Direct Fix	FA-01 compares FA_ADDITIONS_B.COST to the AP invoice distribution amount and corrects the cost with full backup when the variance is confirmed. Mass addition cost split errors are the most common source.
Duplicate asset by serial number	Functional First	FA-01 identifies the prior asset record with the same serial number. The duplicate is reviewed — if it is a genuine duplicate, one is retired via the Retirements form. If different assets share a serial number, the serial number is corrected.
Asset not assigned to corporate book	Functional First	Add the asset to the corporate book via Assets > Asset Books. FA-01 identifies which books the asset should belong to based on the asset category and the book assignment rules.
Mass addition in ON HOLD status	Direct Fix	FA-01 identifies the hold reason in FA_MASS_ADDITIONS.QUEUE_NAME and corrects the blocking condition (missing category, split error, cost issue) with full backup before changing status to POST.

Safeguards

Nothing Executes Without a Safety Net

Before any data fix runs, the script verifies pre-flight conditions and creates a complete verified backup. If any check fails, the script aborts. There is no partial execution path.

Pre-Flight Checks — All Must Pass

✓

POSTED_FLAG = 'N'

Will not modify a posted transaction under any circumstances

✓

ACCOUNTING_EVENT_ID IS NULL

Will not modify rows with an active or pending XLA accounting event

✓

No active database lock

Checks V$LOCK — will not proceed if another session holds a lock on target rows

✓

CONS_BACKUP schema writable

Backup schema must be accessible before any DML is permitted

✓

Explicit confirmation required

Script outputs a confirmation prompt — DML does not execute until consultant enters the case number as the execution parameter

Backup Methodology

Before the first UPDATE fires, the script creates a complete copy of every row to be modified. Tables are named CONS_BACKUP.<TABLE>_<CASE#> and persist permanently after execution.

FA_ADDITIONS_B

FA_BOOKS

FA_DISTRIBUTION_HISTORY

FA_CATEGORIES_B

Row count verified after backup creation. If backup fails for any reason the script aborts without executing any DML. Rollback is a single INSERT from the backup table. No reconstruction required.

FA-01 — Pre-Flight & Backup Verification

════════════════════════════════════════════════════════════
  PRE-FLIGHT SAFETY CHECK
════════════════════════════════════════════════════════════
  Asset Number       : 112841
  CAPITALIZED_FLAG   : NO — not yet capitalized ✓
  Depreciation Rows  : 0 rows in FA_DEPRN_DETAIL ✓ Safe to correct
  CONS_BACKUP Schema : Accessible ✓
  Session Lock Check : No locks detected ✓
────────────────────────────────────────────────────────────
  ALL PRE-FLIGHT CHECKS PASSED — Safe to correct category
════════════════════════════════════════════════════════════
  Creating : CONS_BACKUP.FA_ADDITIONS_B_481020
  Rows     : 1 row backed up ✓
  Creating : CONS_BACKUP.FA_BOOKS_481020
  Rows     : 2 rows backed up ✓ (CORP + TAX)
  Registry : FIX_BACKUP_REGISTRY — ID 5041 created ✓
────────────────────────────────────────────────────────────
  BACKUP COMPLETE
════════════════════════════════════════════════════════════
  Enter case number to confirm : 481020
  Confirmed. Correcting category and life...
════════════════════════════════════════════════════════════

Knowledge Base

Every Execution Produces a Record

The knowledge base article is generated automatically from the script's execution output. No manual documentation required. It becomes the institutional record — for the team, for auditors, and for every future engagement in the same environment.

Zero Manual Effort

Every field — environment, tables, before/after values, backup reference, root cause, prevention — is generated from actual execution output. Nothing is written by hand.

Patterns Surface Over Time

The first engagement produces findings. The third produces patterns. Recurring conditions that are invisible as individual incidents become obvious as knowledge base trends.

Survives Staff Turnover

The knowledge base is an institutional record of the Oracle environment. A new manager, a new DBA, or an external auditor can read exactly what happened, what was done, and what prevents recurrence.

KB-FA-481020-001

Asset 112841 Added with Incorrect Category — FURNITURE & FIXTURES vs COMPUTER EQUIPMENT

EBS R12.2.10 · Fixed Assets

● RESOLVED

Symptom

Root Cause

Tables

FA_ADDITIONS_B — ASSET_CATEGORY_ID (Asset 112841, CATEGORY_ID: 401 FURNITURE & FIXTURES)
FA_BOOKS — DEPRECIATION_METHOD_CODE, LIFE_IN_MONTHS (US CORP, Asset 112841 — 84 months vs correct 36)

Fix Applied

Prevention

R12 Guide (PDF)	Title & Chapter	Detail
120faug.pdf	Oracle Assets User Guide — Chapter 2: Asset Setup	pp. 2-1 to 2-44: Detail Additions, QuickAdditions, and asset descriptive details
120faug.pdf	Oracle Assets User Guide — Ch. 2: Mass Additions Process	pp. 2-28 to 2-65: Mass Additions from Payables, review, post, and cleanup
120faug.pdf	Oracle Assets User Guide — Ch. 2: FA_MASS_ADDITIONS Interface Table	pp. 2-64 to 2-91: Interface table column definitions and import validation

Asset Addition Diagnostic

Why This Fails — and What It Costs

What This Script Diagnoses

What the Report Looks Like

The Four-Layer Architecture in FA-01

Backup & Rollback for FA-01

Tables Backed Up — FA-01

Pre-Flight Safety Guards

FIX_BACKUP_REGISTRY Entry

Auto-Generated Knowledge Base Article

What This Script Finds

Incorrect Asset Category

Invalid GL Distribution Account

Mass Addition ON HOLD

Duplicate Asset by Serial Number

Tables Examined

How Every Fix Decision Is Made

Nothing Executes Without a Safety Net

Every Execution Produces a Record

Oracle Documentation References

Ready to Resolve This in Your Environment?

Why This Fails — and What It Costs

What This Script Diagnoses

What the Report Looks Like

The Four-Layer Architecture in FA-01

Backup & Rollback for FA-01

Tables Backed Up — FA-01

Pre-Flight Safety Guards

FIX_BACKUP_REGISTRY Entry

Auto-Generated Knowledge Base Article

What This Script Finds

Incorrect Asset Category

Invalid GL Distribution Account

Mass Addition ON HOLD

Duplicate Asset by Serial Number

Tables Examined

How Every Fix Decision Is Made

Nothing Executes Without a Safety Net

Every Execution Produces a Record

Oracle Documentation References

Related Diagnostic Scripts

Depreciation Run Diagnostic

FA Period Close Readiness

Mass Additions Diagnostic

AP Invoice Validation Diagnostic

Ready to Resolve This in Your Environment?