Results for “acct_flex_num”

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

Overview

FA_TRANSACTION_HEADERS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the OFA (Oracle Assets) product family. It exposes a denormalized, filtered result set of asset transaction header records that are meaningful for unit-based and transfer-related asset movements. Rather than returning every row of FA_TRANSACTION_HEADERS, the view restricts its output to four transaction types: TRANSFER, TRANSFER IN, UNIT ADJUSTMENT, and TRANSFER OUT. This makes the view a purpose-built reporting construct for tracking asset unit reallocations, inter-entity transfers, and the effective unit balance of an asset at the point of a given transaction.

Because the view also joins to FA_BOOK_CONTROLS, it filters strictly to the corporate book class and to currently effective book controls, ensuring that only active corporate books are represented. The view is read-only in nature and is typically consumed by reports, concurrent programs, and integration extracts that need transaction-level unit context without performing the multi-table joins themselves. It is particularly relevant to queries involving CURRENT_UNITS, which is surfaced directly from FA_ASSET_HISTORY.UNITS via the alias AH.UNITS.

Underlying Base Objects

The view is defined over four base objects, all referenced through SYNONYMs in the APPS schema:

• FA_ADDITIONS_B — supplies the asset master information, including ASSET_NUMBER (aliased from AD.ASSET_NUMBER).
• FA_ASSET_HISTORY — supplies historical asset state, notably UNITS, which is projected as CURRENT_UNITS, and the DATE_EFFECTIVE / DATE_INEFFECTIVE range used to correlate history to the transaction date.
• FA_BOOK_CONTROLS — supplies book type context and the accounting flex structure (ACCT_FLEX_NUM), and enforces the corporate book class restriction.
• FA_TRANSACTION_HEADERS — the driving table, supplying the transaction header columns such as TRANSACTION_HEADER_ID, TRANSACTION_TYPE_CODE, DATE_EFFECTIVE, and the descriptive flexfield attribute columns.

Joins are performed on ASSET_ID between FA_ADDITIONS_B, FA_ASSET_HISTORY, and FA_TRANSACTION_HEADERS, and on BOOK_TYPE_CODE between FA_BOOK_CONTROLS and FA_TRANSACTION_HEADERS. Temporal conditions ensure the asset history row is effective as of the transaction's DATE_EFFECTIVE, and that the book control row is currently in effect (NVL(BC.DATE_INEFFECTIVE, SYSDATE+1) > SYSDATE).

Key Columns

• ROW_ID — the ROWID of the underlying FA_TRANSACTION_HEADERS row, useful for direct row identification.
• TRANSACTION_HEADER_ID — primary identifier of the transaction header.
• BOOK_TYPE_CODE — the asset book in which the transaction was recorded.
• ASSET_ID / ASSET_NUMBER — the asset identifier and its user-facing number.
• TRANSACTION_TYPE_CODE — restricted to TRANSFER, TRANSFER IN, UNIT ADJUSTMENT, or TRANSFER OUT.
• TRANSACTION_SUBTYPE — finer classification of the transaction.
• DATE_EFFECTIVE / TRANSACTION_DATE_ENTERED — the effective and entry dates of the transaction.
• TRANSACTION_NAME / TRANSACTION_KEY — descriptive and key attributes of the transaction.
• CURRENT_UNITS — the asset's unit count from FA_ASSET_HISTORY at the effective transaction date; the column most frequently targeted in user searches.
• ACCT_FLEX_NUM — the accounting flexfield structure identifier from the book controls.
• ATTRIBUTE1 through ATTRIBUTE15 and ATTRIBUTE_CATEGORY_CODE — descriptive flexfield columns.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — audit columns.

Common Use Cases and Queries

Typical scenarios include reconciling unit adjustments per asset and per corporate book, auditing transfer activity across books, and feeding downstream integrations that require the asset unit balance as of each transaction.

Example: retrieve current units for unit adjustment transactions on a given asset:

• SELECT asset_number, transaction_type_code, date_effective, current_units FROM apps.fa_transaction_headers_v WHERE asset_id = :p_asset_id AND book_type_code = :p_book ORDER BY date_effective;

Example: list all transfer-related transactions within a date range:

• SELECT transaction_header_id, asset_number, transaction_type_code, date_effective, current_units FROM apps.fa_transaction_headers_v WHERE date_effective BETWEEN :p_from AND :p_to AND transaction_type_code IN ('TRANSFER','TRANSFER IN','TRANSFER OUT');

Because the view already constrains transaction types and enforces corporate book and effective-dated history logic, consumers should be aware that non-transfer and non-unit-adjustment transaction types, as well as non-corporate books, will not appear in results.