Search Results source_dest_code

Overview

FA_ADJUSTMENTS_MRC_V is a multireporting compliance (MRC) view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OFA (Oracle Assets) product family. It exposes adjusted asset transaction distribution data segregated by set of books, allowing users to query adjustment and journal entry information for a specific reporting ledger. The view effectively filters the underlying adjustment records to the set of books that corresponds to the session context established through USERENV('CLIENT_INFO'), ensuring that only data relevant to the active reporting ledger is returned. This behavior is characteristic of MRC-enabled views in 12.1.1 and 12.2.2, which present secondary ledger or reporting ledger data alongside the primary ledger. The view is therefore most commonly used for cross-ledger reporting, reconciliation of asset adjustments against journal entries, and downstream integration where adjustment lines must be attributed to a specific set of books. Because it is read-only, it serves reporting and inquiry functions rather than transactional data entry.

Underlying Base Objects

The view is defined over a single documented base object, FA_MC_ADJUSTMENTS (exposed as a synonym), which is the MRC adjustment table used by Oracle Assets. The view text selects from FA_MC_ADJUSTMENTS, aliased as FMCADJ, and applies the predicate FMCADJ.SET_OF_BOOKS_ID = NVL(TO_NUMBER(SUBSTRB(USERENV('CLIENT_INFO'), 45, 10)), -1). This predicate parses the client information string to derive the active set of books identifier and restricts the result set accordingly. The NVL fallback to -1 means that when no valid set of books context is established, no rows are returned. All columns exposed by the view map directly to columns of FA_MC_ADJUSTMENTS, with no joins or aggregations applied, so the view functions essentially as a context-filtered projection of the base table.

Key Columns

The view exposes the complete column set of the MRC adjustment table. Notable columns include:

• SET_OF_BOOKS_ID — identifies the reporting set of books; central to the view's filtering predicate.
• TRANSACTION_HEADER_ID and ADJUSTMENT_LINE_ID — link adjustment records to their transaction and line context.
• ASSET_ID — the asset to which the adjustment applies.
• ASSET_INVOICE_ID — the asset invoice association, used to trace adjustments back to invoice-based asset additions; this is the column most relevant to the user's search term.
• ADJUSTMENT_TYPE, SOURCE_TYPE_CODE, and SOURCE_DEST_CODE — classify the nature and origin of the adjustment.
• DEBIT_CREDIT_FLAG and ADJUSTMENT_AMOUNT — define the accounting direction and value.
• CODE_COMBINATION_ID — the accounting flexfield combination for the distribution.
• JE_HEADER_ID and JE_LINE_NUM — reference the generated journal entry.
• PERIOD_COUNTER_CREATED and PERIOD_COUNTER_ADJUSTED — identify the accounting periods involved.
• ANNUALIZED_ADJUSTMENT — the annualized value of the adjustment.
• Global attribute columns (GLOBAL_ATTRIBUTE1–20, GLOBAL_ATTRIBUTE_CATEGORY) — descriptive flexfield support.
• DEPRN_OVERRIDE_FLAG and TRACK_MEMBER_FLAG — depreciation override and member tracking indicators.

Common Use Cases and Queries

Typical use cases include reconciling asset adjustments to journal entries, analyzing invoice-related adjustments through ASSET_INVOICE_ID, and reporting adjustment activity by set of books. A representative query retrieving adjustments for an asset invoice is:

SELECT asset_id, asset_invoice_id, adjustment_type, adjustment_amount, code_combination_id, je_header_id, je_line_num FROM fa_adjustments_mrc_v WHERE asset_invoice_id = :invoice_id;

To summarize adjustments by type within the active set of books:

SELECT adjustment_type, debit_credit_flag, SUM(adjustment_amount) FROM fa_adjustments_mrc_v GROUP BY adjustment_type, debit_credit_flag;

Because filtering depends on USERENV('CLIENT_INFO'), callers must ensure the correct reporting ledger context is initialized before querying; otherwise the view returns no rows. This makes it suitable for concurrent programs and forms that set the MRC context, and for ad hoc reporting executed within an environment where the set of books is properly assigned.