Results for “gl_batch_name”

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

Overview

APPS.FABV_TRANS_HDRS is a read-only view in the Oracle E-Business Suite Assets (OFA) module. It is documented under ETRM 12.2.2 with a status of VALID and the description "Retrofitted," indicating that the object was reconstructed or re-pointed as part of an upgrade or patch cycle rather than authored as a native reporting interface. The view presents transaction header information from the Oracle Assets transaction subsystem, joining header-level data to its originating adjustment records. Its principal role is to expose a flattened, join-ready representation of asset transaction activity for reporting, reconciliation, and downstream integration. The view text is defined with WITH READ ONLY, so it cannot be used for DML and is intended strictly for query access.

Underlying Base Objects

The view is defined over two base objects, both referenced as APPS synonyms in the ETRM metadata:

• FA_TRANSACTION_HEADERS (alias TH) — the transaction header table, supplying transaction identity, type, date entered, transaction name, book, and asset linkage.
• FA_ADJUSTMENTS (alias AJ) — the adjustment line table, supplying the source type code and audit columns.

The join is performed on three columns simultaneously: TRANSACTION_HEADER_ID, BOOK_TYPE_CODE, and ASSET_ID. This composite join ensures that each header is matched only to adjustment rows belonging to the same accounting book and asset. Because the join is inner (WHERE, not an outer join), headers without a matching adjustment record are excluded from the result set. All access is read-only.

Key Columns

• TRANSACTION_HEADER_ID — Primary identifier of the transaction header; the principal join key back to Oracle Assets transaction data.
• TRANSACTION_TYPE_CODE — Code indicating the nature of the transaction (for example, addition, adjustment, transfer, or retirement).
• TRANSACTION_DATE_ENTERED — Date the transaction was entered into the system, commonly used for period and cut-off reporting.
• TRANSACTION_NAME — Descriptive name assigned to the transaction header.
• SOURCE_TYPE_CODE — From FA_ADJUSTMENTS, identifying the origin or classification of the adjustment line (for example, manual versus system-generated).
• BOOK_TYPE_CODE — The asset book in which the transaction was recorded; a key partitioning column for corporate versus tax books.
• ASSET_ID — Identifier of the asset affected by the transaction.
• LAST_UPDATE_DATE, LAST_UPDATED_BY — Standard audit columns sourced from FA_ADJUSTMENTS.

The documentation column listing also references a COMMENTS column and a GL_BATCH_NAME column. GL_BATCH_NAME is the GL batch (journal entry batch) identifier associated with the transaction, and it is the attribute most frequently searched for when users reconcile Oracle Assets activity to General Ledger journals. The current documented view text does not explicitly project GL_BATCH_NAME or COMMENTS, so the defined column list depends on the deployed view version; users should verify against ALL_TAB_COLUMNS on their specific 12.1.1 or 12.2.2 instance.

Common Use Cases and Queries

Typical uses include reconciling asset transactions to General Ledger, auditing transaction sources by book, and extracting transaction activity for period-close reporting. The following query lists transactions with their source classification for a given book and period:

• SELECT th.transaction_header_id, th.transaction_type_code, th.transaction_date_entered, th.book_type_code, th.asset_id, th.source_type_code FROM apps.fabv_trans_hdrs th WHERE th.book_type_code = :book AND th.transaction_date_entered BETWEEN :start_date AND :end_date;
• SELECT th.book_type_code, th.transaction_type_code, COUNT(*) FROM apps.fabv_trans_hdrs th GROUP BY th.book_type_code, th.transaction_type_code;

For GL batch reconciliation, where GL_BATCH_NAME is required, confirm its presence in the deployed view and join accordingly; because the view is read-only and inner-joined to FA_ADJUSTMENTS, transactions lacking adjustment rows will not appear. For header-only reporting, query FA_TRANSACTION_HEADERS directly.