Search Results ghr_mt_element_entries_v




Overview
Explore in AI Chat

Overview

GHR_MT_ELEMENT_ENTRIES_V is a reporting and integration 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 narrow and process-specific: it exposes element entry data consumed by the Mass Transfer In and Mass Transfer Out processes, which move employees between organizational units, payrolls, or assignments and require the associated element entries to be replicated or recreated at the destination. In EBS releases 12.1.1 and 12.2.2 the view carries a VALID status, indicating it is a supported, compiled component of the federal HR data model rather than a customization artifact.

Because the view abstracts its source data through the GHR_INTERFACE staging table, it functions as a controlled projection rather than a live transactional query. Consumers interact with a stable, predictable column set even though the physical storage is a generic key-value interface structure. This design is characteristic of the GHR mass transfer framework, where batch processes deposit records into GHR_INTERFACE and downstream routines read them back through purpose-built views.

Underlying Base Objects

The view is defined over a single documented base object: GHR_INTERFACE, accessed through a synonym. GHR_INTERFACE is the generic interface table used by GHR mass transfer and related data-transfer utilities; it stores incoming and outgoing records in a loosely typed layout of INFORMATION1 through INFORMATION columns plus control columns that classify the row.

The view text applies a hard-coded filter, INFORMATION4 = 'PER_ELEMENT_ENTRIES', which restricts the result set to rows tagged for element entry processing. The selected projection is limited to INFORMATION44, INFORMATION45, and INFORMATION46, which the ETRM documentation maps to the business-meaningful columns described below. No joins, aggregations, or outer queries are documented, so the view is effectively a filtered, renamed slice of the interface table. This means row volume, commit behavior, and purge strategy all follow the lifecycle of GHR_INTERFACE itself.

Key Columns

The ETRM column listing documents three exposed columns, each an alias over a generic interface attribute:

  • TO_BASIC_SALARY_RATE — corresponds to INFORMATION44; carries the basic salary rate to be applied to the element entry at the mass transfer destination.
  • TO_ADJUSTED_BASIC_PAY — corresponds to INFORMATION45; carries the adjusted basic pay value for the destination element entry, typically reflecting locality or special rate adjustments relevant to federal pay administration.
  • TO_TOTAL_SALARY — corresponds to INFORMATION46; carries the total salary figure to be written to the destination record.

The "TO_" prefix consistently denotes the target-side value in a transfer operation, reinforcing that the view supplies destination amounts rather than current or source amounts. Consumers should note that the interface row's classification depends on INFORMATION4, which is filtered by the view and therefore not projected to callers.

Common Use Cases and Queries

Typical use is diagnostic and operational: verifying that the mass transfer In/Out processes staged the correct destination amounts before the transfer is applied, or reconciling amounts after a batch run. Because the underlying table is shared, queries should be scoped carefully and run outside peak processing windows.

A representative query follows:

SELECT to_basic_salary_rate,
       to_adjusted_basic_pay,
       to_total_salary
FROM   apps.ghr_mt_element_entries_v;

To correlate results with interface control data, join back to the base table using the documented filter:

SELECT i.information1,
       i.information4,
       i.information44 to_basic_salary_rate,
       i.information45 to_adjusted_basic_pay,
       i.information46 to_total_salary
FROM   apps.ghr_interface i
WHERE  i.information4 = 'PER_ELEMENT_ENTRIES';

Such queries are useful when validating a mass transfer batch, troubleshooting missing or zero destination amounts, or auditing the staged data prior to committing the transfer. The view should not be used as a substitute for the element entry transactional tables when reporting on live employee compensation; it reflects interface staging content only.