Results for “je_reval_category”

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

Overview

FA_BOOK_CONTROLS is the master configuration table for Oracle Assets (OFA). Each row defines a depreciation book and holds the control information that governs how every asset assigned to that book is depreciated, accounted for, and posted to the General Ledger. In the Oracle E-Business Suite 12.1.1 and 12.2.2 data models, the table resides in the FA schema and is owned by the OFA - Assets product. It is one of the most heavily referenced tables in the module: the single value BOOK_TYPE_CODE, its primary key, propagates into nearly every transaction, depreciation, and reporting table in Oracle Assets.

Functionally, FA_BOOK_CONTROLS determines the depreciation calendar, the journal entry categories used for each transaction type, the set of books linkage to GL, and a wide range of behavioral flags controlling mass changes, revaluation, cost ceilings, deferred depreciation, and impairment. Because of this breadth, the row for a given book is effectively the policy record for that book.

Consistent with a heuristic Data Vault classification, the table is hub-leaning. BOOK_TYPE_CODE behaves as a business key that anchors a large number of dependent satellites and link tables (depreciation summaries, transaction headers, distribution accounts, and so on). Treating it as a hub with surrounding satellites is a reasonable modeling suggestion, since the columns on the table mix identification (BOOK_TYPE_CODE, BOOK_TYPE_NAME) with volatile control attributes better suited to satellite structures.

Key Information Stored

The table is documented with 153 columns. The most consequential are summarized below.

• BOOK_TYPE_CODE — The unique business identifier for the book and the subject of the unique index FA_BOOK_CONTROLS_U1 and the primary key FA_BOOK_CONTROLS_PK. It is the surrogate-to-business bridge column on which essentially all downstream foreign keys depend.
• BOOK_TYPE_NAME — The user-facing name of the depreciation book.
• SET_OF_BOOKS_ID — Foreign key to GL_SETS_OF_BOOKS_11I, linking the asset book to its General Ledger set of books for posting.
• DEPRN_CALENDAR and PRORATE_CALENDAR — Foreign keys to FA_CALENDAR_TYPES defining the depreciation and prorate calendars applied to assets in the book.
• Fiscal and period control columns — CURRENT_FISCAL_YEAR, INITIAL_PERIOD_COUNTER, LAST_PERIOD_COUNTER, LAST_DEPRN_RUN_DATE, and LAST_PURGE_PERIOD_COUNTER track the book's position in the depreciation cycle.
• Journal entry category columns — JE_ADDITION_CATEGORY, JE_ADJUSTMENT_CATEGORY, JE_DEPRECIATION_CATEGORY, JE_RETIREMENT_CATEGORY, JE_RECLASS_CATEGORY, JE_TRANSFER_CATEGORY, JE_REVAL_CATEGORY, JE_DEFERRED_DEPRN_CATEGORY, JE_DEPRN_ADJUSTMENT_CATEGORY, and the CIP variants (JE_CIP_*). Each references GL_JE_CATEGORIES_TL to control GL posting categories.
• Behavioral flags — GL_POSTING_ALLOWED_FLAG, ALLOW_MASS_CHANGES, ALLOW_DEPRN_ADJUSTMENTS, ALLOW_CIP_ASSETS_FLAG, ALLOW_REVAL_FLAG, ALLOW_PURGE_FLAG, ALLOW_IMPAIRMENT_FLAG, ALLOW_BONUS_DEPRN_FLAG, and CALCULATE_NBV.
• Mass copy and distribution linkage — MASS_COPY_SOURCE_BOOK, MASS_REQUEST_ID, and DISTRIBUTION_SOURCE_BOOK, which reference FA_BOOK_CONTROLS itself and FND_CONCURRENT_REQUESTS.

The distinction between the surrogate primary key and business-key candidate is important here: FA_BOOK_CONTROLS_PK and the unique index FA_BOOK_CONTROLS_U1 both key on BOOK_TYPE_CODE, making it the de facto business key of the object.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios involve enumerating the configured books and their key behaviors, or joining control attributes into transaction-level reports. A common pattern retrieves the control row alongside its GL linkage:

SELECT bc.book_type_code,
       bc.book_type_name,
       bc.set_of_books_id,
       bc.deprn_calendar,
       bc.current_fiscal_year,
       bc.gl_posting_allowed_flag
FROM   fa_book_controls bc;

To audit which books post to which ledger and with which categories, join GL_JE_CATEGORIES_TL and GL_SETS_OF_BOOKS_11I on the documented foreign keys. To reconcile depreciation activity, join FA_DEPRN_SUMMARY or FA_DEPRN_DETAIL on BOOK_TYPE_CODE. Troubleshooting journals or running the depreciation program frequently requires inspecting DEPRN_STATUS, DEPRN_REQUEST_ID, and LAST_DEPRN_RUN_DATE for the target book.

Related Objects

The following are among the most significant dependent objects, per the documented foreign key relationships.

• FA_DEPRN_PERIODS — references BOOK_TYPE_CODE and tracks open/closed periods per book.
• FA_DEPRN_SUMMARY and FA_DEPRN_DETAIL — depreciation balances and detail lines, joined on BOOK_TYPE_CODE.
• FA_BOOKS — the asset-level book assignments, keyed by BOOK_TYPE_CODE.
• FA_TRANSACTION_HEADERS — transaction header records carrying BOOK_TYPE_CODE.
• FA_CATEGORY_BOOKS and FA_CATEGORY_BOOK_DEFAULTS — category-level defaults per book.
• FA_DISTRIBUTION_ACCOUNTS and FA_MASS_CHANGES — distribution and mass-maintenance processing tied to the book.
• GL_SETS_OF_BOOKS_11I — via SET_OF_BOOKS_ID.
• GL_JE_CATEGORIES_TL — via the multiple JE_*_CATEGORY columns.
• FND_CONCURRENT_REQUESTS — via MASS_REQUEST_ID, DEPRN_REQUEST_ID, and CREATE_ACCOUNTING_REQUEST_ID.

Together these relationships confirm the table's position as the configuration hub of Oracle Assets, with BOOK_TYPE_CODE serving as the pervasive join key across the OFA schema.