Search Results tsp_amount

Overview

The view APPS.GHR_MT_ELEMENT_ENTRIES_V is a filtered projection over the Oracle E-Business Suite HRMS generic interface table GHR_INTERFACE. It isolates a single logical interface stream — Federal / public-sector payroll element entries identified by the discriminator value PER_ELEMENT_ENTRIES in the INFORMATION4 column — and re-labels the generic positional INFORMATION1..INFORMATION46 columns with descriptive aliases. This aliasing is the primary purpose of the view: it converts an opaque staging table layout into a self-documenting row set that consumers, reports, and downstream concurrent programs can query without reference to a separate column-mapping document.

The view is named with the GHR_MT_ prefix, indicating it belongs to the Oracle HRMS multi-table / global HR interface family. In Oracle EBS 12.1.1 and 12.2.2 the object is deployed under the APPS schema and forms part of the integration pathway used by HRMS interface loaders to move external (or legacy) payroll and benefits data into Oracle Payroll / Oracle HRMS. It exposes the raw interface rows prior to or after processing by the interface loader, making it a read-only reporting surface rather than a transactional table.

Underlying Base Objects

The view is defined exclusively over a single referenced object listed in the ETRM metadata:

• GHR_INTERFACE (a SYNONYM resolving to the APPS table of the same underlying name).

GHR_INTERFACE is the shared staging table used across the HRMS multi-table interface. Rather than being a dedicated table per data type, it stores heterogeneous records and uses a type discriminator column (INFORMATION4) to separate logical streams. GHR_MT_ELEMENT_ENTRIES_V applies the predicate WHERE INFORMATION4 = 'PER_ELEMENT_ENTRIES' to the base table, so the view logically models one segment of that shared table. There are no joins to other tables in the view definition; all attributes are derived by aliasing columns already present on GHR_INTERFACE, so it inherits the base table's indexing and its data lifecycle. No base table privilege other than SELECT on the synonym is required.

Key Columns

The columns fall into three groups: identifiers, control/status fields, and payroll element entry attributes.

• Identifiers and routing: GHR_INTERFACE_ID (from INTERFACE_ID) is the primary row identifier; MT_SOURCE (SOURCE_NAME) and MT_TABLE_NAME (INFORMATION4) identify the originating source and logical stream.
• Control and timing: MT_PROCESS_DATE (PROCESS_DATE), MT_EFFECTIVE_DATE (DATE_FROM), MT_STATUS (INFORMATION2), and MT_PERSON_ID (INFORMATION3) drive the loader and provide row status and effective dating.
• Element entry and salary details: The remaining aliases carry payroll values — for example MT_NAME, MT_INFORMATION_TYPE, MT_INTER_BG_TRANSFER, TOTAL_SALARY, SALARY, LOCALITY_ADJUSTMENT, ADJUSTED_PAY, OTHER_PAY, FEGLI, RETIREMENT_PLAN and its meaning, ENROLLMENT, HEALTH_PLAN, TEMPS_TOTAL_COST, and the Thrift Savings Plan group (TSP_AMOUNT, TSP_RATE, TSP_G_FUND, TSP_F_FUND, TSP_C_FUND, TSP_STATUS, TSP_STATUS_DATE, TSP_ELIGIBILITY_DATE).
• Within-grade increase (WGI): WGI_STATUS, WGI_DATE_DUE, WGI_PAY_DATE, WGI_LAST_INCREASE_DATE, and the postponement fields WGI_POSTPONMT_EFFECTIVE and WGI_POSTPONMT_DETERM_DUE.
• Allowance and premium indicators: auo_amount / auo_premium_pay_ind, ap_amount / ap_premium_pay_ind, and the trailing percentage and rate columns (TO_RETENTION_ALLOW_PERCENTAGE, TO_SUPERVISORY_DIFF_PERCENTAGE, TO_STAFFING_DIFF_PERCENTAGE, TO_BASIC_SALARY_RATE, TO_ADJUSTED_BASIC_PAY, TO_TOTAL_SALARY).

Common Use Cases and Queries

Because the view is read-only and pre-filtered, it is typically used for reconciliation, staging review, and pre-load validation rather than for maintenance. Typical scenarios include verifying that element entry records were staged before running the interface loader, checking status and effective dates, and auditing salary and benefit amounts. A simple query follows:

SELECT GHR_INTERFACE_ID,
       MT_PERSON_ID,
       MT_NAME,
       MT_STATUS,
       MT_EFFECTIVE_DATE,
       SALARY,
       TOTAL_SALARY
FROM   APPS.GHR_MT_ELEMENT_ENTRIES_V
WHERE  MT_STATUS IS NOT NULL;

To identify rows awaiting processing for a specific person, the MT_PERSON_ID and MT_PROCESS_DATE columns are the natural filters. To review benefits and retirement detail, the analyst selects the RETIREMENT_PLAN, FEGLI, and TSP_% columns. In practice, the per_element_entries search that surfaces this view reflects its role as the canonical, human-readable projection of element entry interface data within the HRMS multi-table integration in Oracle EBS 12.1.1 and 12.2.2.