Search Results current_mhc_period_counter




Overview
Explore in AI Chat

Overview

The view APPS.IGI_MHC_CURR_REVAL_DTL_V is a reporting and integration construct within Oracle E-Business Suite that presents the current mass revaluation details for assets processed under the Mass Handling Charge (MHC) revaluation framework. It is owned by the APPS schema and is defined over the IGI_MHC_REVALUATION_DETAIL base table (accessed through a synonym). The view's purpose is to expose only the rows that represent the effective, latest state of a revaluation for a given asset, book, and period, thereby shielding downstream consumers—reports, concurrent programs, and interfaces—from obsolete or superseded rows that accumulate in the underlying detail table across successive revaluation runs.

Structurally, the view is a filtered, self-joining query. It restricts rows to those where ACTIVE_FLAG = 'Y', RUN_MODE = 'L', and NVL(ACTIVE_FLAG,'Y') <> 'N', and then applies a correlated subquery that selects the maximum ROWID per combination of BOOK_TYPE_CODE, ASSET_ID, and CURRENT_MHC_PERIOD_COUNTER. A further nested subquery limits the selection to the highest MASS_REVAL_ID for that same combination. The net effect is a single effective row per asset/book/current MHC period, representing the most recent mass revaluation transaction.

Underlying Base Objects

The sole documented base object referenced by this view is IGI_MHC_REVALUATION_DETAIL, a synonym resolving to the table that stores the line-level results of mass revaluation processing. The view is defined exclusively over this table, aliased three times (MRS1, MRS2, MRS3) in the view text. There are no joins to external master tables such as FA_BOOKS or FA_ASSETS within the view definition itself, so contextual asset and book attributes must be obtained by joining the view to those tables in downstream queries. This tight coupling to a single base table means that the view functions essentially as a de-duplication and active-row filter over IGI_MHC_REVALUATION_DETAIL.

Key Columns

The view exposes the full set of analytical columns required to reconcile revaluation outcomes:

Common Use Cases and Queries

Typical use cases include revaluation reporting, reconciliation against fixed asset books, and integration feeds to general ledger or external reporting systems. A common query retrieves the current revaluation detail for a specific book and asset:

  • SELECT asset_id, book_type_code, current_mhc_period_counter, net_book_value, revaluation_reserve FROM apps.igi_mhc_curr_reval_dtl_v WHERE book_type_code = :book AND asset_id = :asset;
  • SELECT category_id, SUM(revaluation_reserve) FROM apps.igi_mhc_curr_reval_dtl_v GROUP BY category_id;
  • Reconciliation joins the view to FA_BOOKS or FA_ASSETS on ASSET_ID and BOOK_TYPE_CODE to compare revalued versus book balances.

Because the view already filters to the latest active MASS_REVAL_ID and maximum ROWID per period, queries against it should not add redundant de-duplication logic. Note also that the filter on RUN_MODE = 'L' implies only "live" (as opposed to simulation or unposted) runs are surfaced, and rows with ACTIVE_FLAG set to 'N' are excluded even when the NVL predicate would otherwise permit nulls.