Search Results mt_table_name




Overview
Explore in AI Chat

Overview

APPS.GHR_MT_MISC_V is a reporting and integration view in the Oracle E-Business Suite (EBS) covering releases 12.1.1 and 12.2.2. It exposes a subset of the generic GHR interface staging table, isolating rows that carry miscellaneous mass-transfer or mass-update transactions rather than standard hire, termination, or transfer records. Its primary role is to make interface staging data queryable in a stable, pre-aliased form so that concurrent programs, extracts, and downstream data loads can read a consistent column set without re-implementing the underlying decoding logic against the raw interface table.

The view is part of the GHR (HRMS interface) family of objects. The user search term "mt_process_date" maps directly to the view's PROCESS_DATE column, which is aliased as MT_PROCESS_DATE. This column records the date on which the miscellaneous interface row was processed or is scheduled to be processed by the Mass Transfer / Mass Update process.

Underlying Base Objects

Per documented ETRM metadata for release 12.2.2, the view is owned by the APPS schema and is defined over a single referenced base object, GHR_INTERFACE, accessed through a synonym. There are no joins in the view definition; the view is a straight projection with a WHERE filter.

The defining filter is WHERE INFORMATION4 = 'MISCELANEOUS'. The literal is spelled with the omission of a second "L" as it appears in the source metadata, so any code that depends on the view inherits this filter exactly as defined. The view therefore does not present all interface rows; it presents only those whose generic INFORMATION4 attribute is populated with the miscellaneous indicator. The interface row is identified by INTERFACE_ID, which the view surfaces as GHR_INTERFACE_ID.

Key Columns

The view performs extensive column renaming to give the generic INFORMATION1 through INFORMATION18 attributes a domain-specific identity. Columns of interest include:

Common Use Cases and Queries

Typical scenarios include auditing outstanding miscellaneous mass-transfer rows, diagnosing why a row failed processing, and extracting staging data for reconciliation. Because the view is already filtered and aliased, queries are simpler than against GHR_INTERFACE.

Find rows awaiting or dated by process date:

SELECT mt_person_id, mt_name, mt_process_date, mt_status
FROM   apps.ghr_mt_misc_v
WHERE  mt_process_date >= TRUNC(SYSDATE) - 30
ORDER BY mt_process_date DESC;

List "from/to" positional changes for a person:

SELECT ghr_interface_id, mt_effective_date,
       from_position_title, to_position_id,
       duty_station_code, mt_inter_bg_transfer
FROM   apps.ghr_mt_misc_v
WHERE  mt_person_id = :person_id;

Note that the view is read-oriented; corrections must be applied to the base GHR_INTERFACE row.