Search Results date_active

Overview

FA_BOOK_CONTROLS_HISTORY is an Oracle Assets (OFA) repository table in the FA schema that records the full change history of depreciation book setup information. In Oracle EBS 12.1.1 and 12.2.2, each row captures the effective configuration of a given depreciation book for a bounded period of time, enabling the system to retain prior settings for audit, reporting, and historical calculations whenever book controls are modified through the Book Controls window or related concurrent processes.

The table is distinct from FA_BOOK_CONTROLS, which holds the current, active definition of each book. Where FA_BOOK_CONTROLS presents a single row per BOOK_TYPE_CODE, FA_BOOK_CONTROLS_HISTORY preserves a time-versioned record keyed by BOOK_TYPE_CODE and DATE_ACTIVE, allowing successive versions of the same book to be retained indefinitely. The documented physical schema contains 132 columns.

Based on the heuristic Data Vault classification derived from the foreign-key structure, the object is identified as standalone; no enforced foreign-key relationships to other tables were mined. In a Data Vault modeling suggestion, this would be treated as a satellite-like structure attached to a book business key, with DATE_ACTIVE functioning as the effectivity or load-date discriminator rather than a true hub or link.

Key Information Stored

The primary key is FA_BOOK_CONTROLS_HISTORY_PK, comprising BOOK_TYPE_CODE and DATE_ACTIVE. A unique index, FA_BOOK_CONTROLS_HISTORY_U1, mirrors these same two columns (BOOK_TYPE_CODE, DATE_ACTIVE), confirming them as the business-key candidates for version identification. BOOK_TYPE_CODE identifies the depreciation book, while DATE_ACTIVE marks the date on which that version of the book configuration became effective.

DATE_INACTIVE and DATE_INEFFECTIVE delimit the validity window of a historical row. BOOK_TYPE_NAME provides the descriptive book name, and SET_OF_BOOKS_ID links the book to its ledger in General Ledger. Operational control flags include AMORTIZE_FLAG, GL_POSTING_ALLOWED_FLAG, ALLOW_MASS_CHANGES, ALLOW_DEPRN_ADJUSTMENTS, ALLOW_REVAL_FLAG, ALLOW_CIP_ASSETS_FLAG, ALLOW_IMPAIRMENT_FLAG, and ALLOW_BACKDATED_TRANSFERS_FLAG, each governing whether a specific Assets activity is permitted for that book.

Journal entry mapping is governed by the JE_*_CATEGORY columns, notably JE_ADDITION_CATEGORY, JE_ADJUSTMENT_CATEGORY, JE_TRANSFER_CATEGORY, JE_RETIREMENT_CATEGORY, JE_DEPRECIATION_CATEGORY, JE_RECLASS_CATEGORY, JE_REVAL_CATEGORY, and the corresponding JE_CIP_* categories. Integration with Subledger Accounting and General Ledger is further supported by GL_JE_SOURCE and ORG_ID. Audit and multi-org context columns include LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN, ORG_ID, and the ATTRIBUTE1–15, GLOBAL_ATTRIBUTE1–20, and ATTRIBUTE_CATEGORY_CODE flexfields.

Common Use Cases and Queries

The most frequent use case is reconstructing which book settings were in effect on a specific date, which is essential when reconciling depreciation or journal entries generated in a prior period. The user search term "date_active" corresponds directly to the effectivity discriminator used in these queries.

• Retrieving the settings effective on a given date: SELECT * FROM fa_book_controls_history WHERE book_type_code = :book AND date_active <= :as_of_date AND (date_inactive IS NULL OR date_inactive > :as_of_date);
• Listing all configuration versions for a book: SELECT book_type_code, date_active, date_inactive, gl_posting_allowed_flag, allow_reval_flag FROM fa_book_controls_history WHERE book_type_code = :book ORDER BY date_active DESC;
• Auditing when a specific control changed, such as revaluation or impairment enablement, by comparing adjacent DATE_ACTIVE rows.
• Report validation for period-end depreciation runs, confirming that posting and adjustment flags matched the intended book configuration.

Because the effective-dated pattern is preserved, the table is well suited to point-in-time reporting and to identifying configuration drift across periods.

Related Objects

• FA_BOOK_CONTROLS — the active counterpart holding current book setup; joined on BOOK_TYPE_CODE.
• FA_BOOKS — book-level assignments of assets; associated through BOOK_TYPE_CODE.
• FA_DEPRN_BOOK_CONTROLS or related book-control tables that inherit settings.
• FA_ADDITIONS, FA_DEPRECIATION, FA_ADJUSTMENTS, and FA_RETIREMENTS — asset transactions whose journal categories reference the JE_*_CATEGORY columns defined here.
• GL_SETS_OF_BOOKS — linked via SET_OF_BOOKS_ID.
• Subledger Accounting / GL journal sources referenced by GL_JE_SOURCE.

No enforced foreign keys were documented for this object; associations above are by shared business columns such as BOOK_TYPE_CODE and SET_OF_BOOKS_ID.