Results for “book_type_name”

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

Overview

FII_GL_BOOK_FA_BOOK_LCV is a collection view owned by the APPS schema within the Financial Intelligence (FII) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to serve as the collection view for the Fixed Assets Book level of the GL Book dimension. In practical terms, this view exposes asset book attributes that correspond to a given General Ledger book, allowing Financial Intelligence reporting, extraction, and dimensional collection routines to reconcile and align FA book context with GL book context.

Because it is a collection view rather than a transactional entity, FII_GL_BOOK_FA_BOOK_LCV is typically consumed by FII's collection and staging processes, which gather dimensional metadata prior to loading it into the FII reporting schema. This makes it a foundational object for building dimensional hierarchies and cross-referencing FA book definitions with GL books in enterprise performance and financial intelligence reporting. The presence of BOOK_TYPE_NAME directly supports the common search pattern where users look up the descriptive asset book type associated with a book.

Underlying Base Objects

The view metadata documents that FII_GL_BOOK_FA_BOOK_LCV is defined over a single underlying object: FIIBV_GL_BOOK_FA_BOOK_LCV. No other base tables are documented in the ETRM metadata, and no additional referenced base objects are recorded. The prefix FIIBV suggests a Financial Intelligence base view that itself consolidates or transforms the raw GL and FA book data before it is projected through the LCV collection layer.

Structurally, the view selects a defined column set from that base view, mapping the business attributes (book identifiers, name, type, currency, calendars) and appending placeholders for five user attribute columns. In the view text, these trailing columns appear as NULL, NULL, NULL, NULL, NULL, which correspond positionally to USER_ATTRIBUTE1 through USER_ATTRIBUTE5 in the documented column list. This design gives consuming processes a consistent, denormalized row shape regardless of whether the underlying source fully populates all descriptor flexfields.

Key Columns

• FA_BOOK_PK — The primary key of the Fixed Assets book record, uniquely identifying the book.
• BOOK_FK — Foreign key reference associating the record with its book dimension entry.
• BOOK_TYPE_NAME — The descriptive name of the asset book type; this is the column most relevant to lookups searching for "book_type_name."
• NAME — The name of the book or associated dimension member.
• FA_BOOK — The Fixed Assets book identifier used in FA processing.
• CURRENCY_CODE — The functional or book currency assigned to the book.
• DEPRE_CALANDAR — The depreciation calendar assigned to the book (note the documented spelling).
• INSTANCE — The instance or environment identifier associated with the book record.
• PRORATE_CALENDAR — The prorate calendar used for depreciation proration.
• LAST_UPDATE_DATE — Audit timestamp of the last modification, used for incremental collection.
• USER_ATTRIBUTE1–5 — Descriptive flexfield or extension slots, exposed as placeholders in this view.

Common Use Cases and Queries

The primary scenario is dimensional collection and reporting, where FII routines gather FA book metadata tied to GL books. A second scenario is ad hoc lookup of book type names for reconciliation or cross-validation against GL book definitions. A representative query follows:

• SELECT fa_book_pk, book_fk, book_type_name, name, currency_code FROM apps.fii_gl_book_fa_book_lcv WHERE book_type_name = :p_book_type;
• SELECT fa_book, book_type_name, depre_calandar, prorate_calendar FROM apps.fii_gl_book_fa_book_lcv ORDER BY book_type_name;
• SELECT l.book_fk, l.book_type_name, l.currency_code FROM apps.fii_gl_book_fa_book_lcv l WHERE l.last_update_date >= :p_since;

Because the view is read-oriented and denormalized, it should be used for querying and extraction rather than for direct DML. Reporting logic should rely on the documented columns above and treat the user attribute placeholders as currently unpopulated.