Results for “ghr_mt_analysis_criteria_v”

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

Overview

GHR_MT_ANALYSIS_CRITERIA_V is a database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the GHR - US Federal Human Resources product family. Its documented purpose is to support mass transfer in and out processes for data transfer, specifically the analysis phase in which candidate records are evaluated against transfer criteria before the actual data movement occurs. The view is registered with a status of VALID in ETRM and is classified as a VIEW object type.

Rather than presenting a normalized relation, GHR_MT_ANALYSIS_CRITERIA_V projects a wide, denormalized row shape from a single interface table. This design is deliberate: mass transfer processes in GHR consume criteria rows in a positional, column-oriented format, and the view supplies that shape with business-friendly aliases. The view therefore functions as a reporting and integration surface, allowing concurrent programs, SQL*Plus sessions, and custom extensions to query analysis criteria using semantically named columns instead of the generic INFORMATIONn columns of the underlying interface.

Underlying Base Objects

The documented view metadata lists a single referenced base object: the synonym GHR_INTERFACE. In Oracle EBS, this synonym resolves to the APPS-owned interface table that stores staged mass transfer data. GHR_MT_ANALYSIS_CRITERIA_V is defined as a simple projection over that object, with no joins, unions, or aggregation in the definition. The view text selects directly from the interface source and applies column aliasing only.

Because the view depends entirely on GHR_INTERFACE, its contents reflect whatever rows the mass transfer in and out processes have staged for analysis. Row lifecycle — insertion, update, deletion, and purge — is governed by the GHR mass transfer concurrent programs rather than by the view, which remains read-only in practice.

Key Columns

• GHR_INTERFACE_ID — aliased from INTERFACE_ID; the unique identifier of the interface row and the primary correlation key for the staged analysis record.
• MT_PROCESS_DATE — aliased from PROCESS_DATE; the date the mass transfer analysis was processed.
• MT_SOURCE — aliased from SOURCE_NAME; identifies the origin of the data being analyzed.
• MT_EFFECTIVE_DATE — aliased from DATE_FROM; the effective date associated with the transfer criteria evaluation.
• MT_NAME, MT_STATUS, MT_PERSON_ID — aliased from INFORMATION1 through INFORMATION3; carry the criteria name, status, and person identifier.
• MT_TABLE_NAME, MT_INFORMATION_TYPE, MT_INTER_BG_TRANSFER — aliased from INFORMATION4 through INFORMATION6; identify the target table, the information category, and the inter-business-group transfer indicator.
• SEGMENT1 through SEGMENT30 — aliased from INFORMATION7 through INFORMATION36; hold the criteria segment values used to match records for transfer.
• SEGMENT1_MEANING through SEGMENT21_MEANING — aliased from INFORMATION73 through INFORMATION93; provide the translated display values for the corresponding segments.

Common Use Cases and Queries

The view is most commonly queried to inspect which criteria rows were staged for a given mass transfer run, to validate segment matching before executing the transfer, and to troubleshoot records that were excluded from transfer. A representative query selects the core identifiers alongside the first several segments and their meanings for a specific interface run:

• SELECT ghr_interface_id, mt_process_date, mt_source, mt_name, mt_status, mt_person_id FROM apps.ghr_mt_analysis_criteria_v WHERE mt_status = 'PENDING';
• SELECT ghr_interface_id, mt_table_name, mt_information_type, mt_inter_bg_transfer, segment1, segment1_meaning FROM apps.ghr_mt_analysis_criteria_v WHERE mt_person_id = :person_id;
• SELECT mt_table_name, COUNT(*) FROM apps.ghr_mt_analysis_criteria_v GROUP BY mt_table_name;

Because the view exposes only a projection of GHR_INTERFACE, it should be treated as a read-only analytical surface. Any corrective action against staged criteria data must be performed on the base interface table through the supported GHR mass transfer processes or concurrent programs, not through the view.