Search Results mt_status




Overview
Explore in AI Chat

Overview

GHR_MT_MISC_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the GHR product family (US Federal Human Resources) and is documented in the E-Business Suite Technical Reference Manual (ETRM) with a status of VALID. Its stated purpose is to expose data consumed by the Mass Transfer In and Mass Transfer Out concurrent processes, which move employees between agencies, positions, and organizational units in a single batch operation.

The view performs a projection rather than a join: it selects a subset of rows from the GHR_INTERFACE staging table and renames the generic INFORMATION1 through INFORMATION18 columns into meaningful aliases such as MT_PERSON_ID, MT_STATUS, and FROM_POSITION_ID. Because the Mass Transfer process is sensitive to interface record layout, this view provides a stable, descriptive interface layer so that PL/SQL packages and reports can reference business-meaningful column names rather than positional INFORMATIONn columns. The view is not a reporting-only artifact; it is a functional component of the transfer data pipeline, and changes to its definition can affect the Mass Transfer concurrent programs.

Underlying Base Objects

The view is defined exclusively over GHR_INTERFACE. In the ETRM metadata provided, the referenced base object is listed as GHR_INTERFACE (SYNONYM), meaning the definition resolves through a synonym to the underlying interface table in the APPS schema. No other tables, views, or PL/SQL functions are referenced.

The defining query is a single-table SELECT with one filter predicate:

  • Source object: GHR_INTERFACE
  • Filter: INFORMATION4 = 'MISCELANEOUS' (the literal is stored with this spelling in the view text)

Consequently, GHR_MT_MISC_V is a vertical and horizontal slice of GHR_INTERFACE. It returns only those interface rows whose INFORMATION4 value equals the literal 'MISCELANEOUS', and within those rows it exposes twenty-two named columns. Rows for other interface categories, and interface rows intended for other mass-transfer variants, are not returned. Because the view is a stored SQL definition, any DML against GHR_MT_MISC_V is not permitted; inserts and updates must target GHR_INTERFACE directly.

Key Columns

The twenty-two columns exposed by the view map directly to positions in GHR_INTERFACE. The most significant, particularly in relation to the search term "mt_person_id", is MT_PERSON_ID.

Common Use Cases and Queries

The view is most often queried during mass transfer troubleshooting: confirming that a person appears in the interface staging area, verifying the recorded status, and validating that the FROM and TO attributes were populated correctly before the process is run or re-run.

To locate all staged transfer records for a specific person, using the column matched by the mt_person_id search:

SELECT ghr_interface_id, mt_person_id, mt_name, mt_status, mt_process_date FROM apps.ghr_mt_misc_v WHERE mt_person_id = :p_person_id;

To review records that have not yet advanced past staging:

SELECT ghr_interface_id, mt_person_id, mt_status, mt_effective_date FROM apps.ghr_mt_misc_v WHERE mt_status IS NULL OR mt_status <> 'PROCESSED' ORDER BY mt_process_date;

To audit transfer attributes between source and destination:

SELECT mt_person_id, from_position_id, to_position_id, from_agency_code, duty_station_code FROM apps.ghr_mt_misc_v WHERE mt_process_date >= :p_from_date AND mt_inter_bg_transfer = 'Y';

It is important to note that the view is a filtered projection of GHR_INTERFACE. When counts from the view do not match expectations, the underlying GHR_INTERFACE table should be queried directly to determine whether rows are missing entirely or are being excluded by the INFORMATION4 = 'MISCELANEOUS' predicate.