Search Results ghr_mt_assignment_ei_v




Overview
Explore in AI Chat

Overview

GHR_MT_ASSIGNMENT_EI_V is a database view owned by the APPS schema in Oracle E-Business Suite. It is delivered as part of the GHR product, US Federal Human Resources. The view's documented purpose is to support mass transfer in and out processes used for data transfer. In the GHR mass transfer architecture, records destined for assignment-level processing are staged in a generic interface table, and this view reshapes those staged rows into a business-meaningful projection of assignment extra information attributes.

The view plays an integration role rather than an end-user reporting role. It abstracts the positional INFORMATION1 through INFORMATION52 columns of the underlying interface staging table into named columns such as MT_EFFECTIVE_DATE, MT_PERSON_ID, ASSIGNMENT_ID, and the full AEI_ATTRIBUTE and AEI_INFORMATION attribute sets. This abstraction allows mass transfer programs and concurrent processes to read, validate, and transform staged assignment extra information data without depending on the physical column layout of the staging table. Because the object is a view, it stores no data itself; all content is derived at query time from the base object.

Underlying Base Objects

According to the documented ETRM metadata for 12.2.2, the referenced base object is GHR_INTERFACE, accessed through a synonym. GHR_INTERFACE is the shared staging table for the GHR mass transfer interface; it is a wide, generic table in which each row carries a source name, an effective date, a person reference, and numerous payload columns named INFORMATION1 through INFORMATIONn. The view maps those positional columns to semantically labelled output columns, one-to-one, using column aliases.

Key aliases visible in the view text include INTERFACE_ID to GHR_INTERFACE_ID, PROCESS_DATE to MT_PROCESS_DATE, SOURCE_NAME to MT_SOURCE, DATE_FROM to MT_EFFECTIVE_DATE, and INFORMATION1 through INFORMATION5 to MT_NAME, MT_STATUS, MT_PERSON_ID, MT_TABLE_NAME, and MT_INFORMATION_TYPE respectively. INFORMATION6 is exposed as MT_INTER_BG_TRANSFER, INFORMATION7 as ASSIGNMENT_EXTRA_INFO_ID, and INFORMATION8 as ASSIGNMENT_ID. INFORMATION9 through INFORMATION13 carry INFORMATION_TYPE, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE. The remainder of the INFORMATION columns are mapped directly to the twenty AEI_ATTRIBUTE columns, the ten AEI_INFORMATION columns, and standard audit columns including LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE. Note that the documented excerpt truncates at INFORMATION52; the full view definition continues beyond the provided extract.

Key Columns

  • GHR_INTERFACE_ID — Primary identifier of the staging row, aliased from INTERFACE_ID; used to correlate errors and log messages back to the source record.
  • MT_PROCESS_DATE / MT_EFFECTIVE_DATE — The run date and the effective date of the mass transfer action, aliased from PROCESS_DATE and DATE_FROM.
  • MT_SOURCE — Identifies the mass transfer process (in or out) that produced the row.
  • MT_NAME, MT_STATUS, MT_PERSON_ID, MT_TABLE_NAME, MT_INFORMATION_TYPE — Descriptive and routing attributes carried in INFORMATION1 through INFORMATION5.
  • MT_INTER_BG_TRANSFER — Flag indicating a transfer between business groups, carried in INFORMATION6.
  • ASSIGNMENT_EXTRA_INFO_ID and ASSIGNMENT_ID — Foreign references to the assignment extra information record and its parent assignment.
  • AEI_ATTRIBUTE_CATEGORY, AEI_ATTRIBUTE1–20, AEI_INFORMATION_CATEGORY, AEI_INFORMATION1–10 — The descriptive flexfield context and segment values for the assignment extra information entity.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent request and program audit columns used for traceability.
  • WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, mapped from INFORMATION35 through INFORMATION39.

Common Use Cases and Queries

Typical uses centre on monitoring and troubleshooting mass transfer runs affecting assignment extra information. A query by source and status isolates rows from a particular process, while a query by person or assignment identifies the staged attributes for a specific employee. The following examples use standard EBS conventions.

  • List staged rows for one process run: SELECT MT_SOURCE, MT_PERSON_ID, ASSIGNMENT_ID, MT_STATUS FROM ghr_mt_assignment_ei_v WHERE MT_PROCESS_DATE = :p_date;
  • Retrieve attribute values for a specific assignment: SELECT ASSIGNMENT_EXTRA_INFO_ID, AEI_ATTRIBUTE_CATEGORY, AEI_ATTRIBUTE1, AEI_INFORMATION1 FROM ghr_mt_assignment_ei_v WHERE ASSIGNMENT_ID = :p_assignment_id;
  • Trace rows to the originating concurrent request: SELECT GHR_INTERFACE_ID, REQUEST_ID, PROGRAM_ID, MT_STATUS FROM ghr_mt_assignment_ei_v WHERE REQUEST_ID = :p_request_id;
  • Filter inter-business-group transfers: SELECT MT_PERSON_ID, ASSIGNMENT_ID, MT_INTER_BG_TRANSFER FROM ghr_mt_assignment_ei_v WHERE MT_INTER_BG_TRANSFER = 'Y';

Because the view performs no filtering or joins, all predicates execute against the base staging table, and performance is governed by the indexes on GHR_INTERFACE and the selectivity of the query conditions. No data should be inserted or updated through this view; it is intended strictly for read access.