Results for “ghr_mt_position_definitions_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GHR_MT_POSITION_DEFINITIONS_V is an APPS-owned database view within the Oracle E-Business Suite, delivered as part of the GHR — US Federal Human Resources product family. Its documented purpose is to support the mass transfer in and out processes, exposing interface staging data used to move position definition records between environments or business groups. The view is classified as VALID in the ETRM metadata and is defined over the GHR_INTERFACE synonym, which resolves to the GHR_INTERFACE base table in the APPS schema.

The view acts as a filtered, column-renamed projection rather than a physical entity. It isolates rows in GHR_INTERFACE where INFORMATION4 equals 'PER_POSITION_DEFINITIONS', meaning only interface payloads describing PER_POSITION_DEFINITIONS records are surfaced. Columns from the generic interface table, such as INFORMATION1 through INFORMATION47, are aliased into meaningful business names — MT_NAME, MT_STATUS, MT_PERSON_ID, POSITION_DEFINITION_ID, SEGMENT1 through SEGMENT30, and so on. In an EBS 12.1.1 or 12.2.2 environment, this view supports integration and diagnostic reporting for the mass transfer utility, allowing technical and functional users to inspect exactly what the delivery process will read or has written.

Underlying Base Objects

The documented base object is GHR_INTERFACE, referenced through a synonym. GHR_INTERFACE is a large, denormalized staging table whose INFORMATION1–INFORMATION47 columns serve as a generic container for heterogeneous interface payloads. The WHERE clause INFORMATION4 = 'PER_POSITION_DEFINITIONS' acts as the discriminator, ensuring the view returns only the subset of interface rows related to position definitions rather than assignment, person, or other mass transfer entity types that share the same table.

Because the view maps generic INFORMATIONn columns to typed aliases, it also indirectly reflects the column layout of PER_POSITION_DEFINITIONS, including its key flexfield structure (ID_FLEX_NUM) and SEGMENT1–SEGMENT30 attributes. No joins are present in the documented view text; it is a single-table selection with projection and filtering only. Consequently, the view is read-only and carries no independent storage, triggers, or constraints of its own.

Key Columns

• GHR_INTERFACE_ID — Surrogate identifier for the interface row, derived from INTERFACE_ID.
• MT_PROCESS_DATE / MT_SOURCE / MT_EFFECTIVE_DATE — Process timing and source-of-record attributes used to track a mass transfer run.
• MT_NAME / MT_STATUS / MT_PERSON_ID — Descriptive name, current status, and associated person identifier for the staged record.
• MT_TABLE_NAME / MT_INFORMATION_TYPE / MT_INTER_BG_TRANSFER — Target table name, payload classification, and business group transfer indicator.
• POSITION_DEFINITION_ID — Primary identifier of the position definition being transferred; the column most frequently referenced by users searching on position_definition_id.
• ID_FLEX_NUM / SUMMARY_FLAG / ENABLED_FLAG — Key flexfield structure, summary indicator, and enablement status.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Active date range of the position definition.
• SEGMENT1 through SEGMENT30 — Position key flexfield segment values, mapped from INFORMATION13–INFORMATION42.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE.

Common Use Cases and Queries

Typical scenarios include diagnosing a mass transfer that has not produced expected positions, validating staged position data before running the transfer-in process, and reconciling interface rows against populated PER_POSITION_DEFINITIONS records. Because the view filters to a single INFORMATION4 value, it is a safe reporting entry point that avoids other interface payload types.

To locate a specific position definition in the interface:

SELECT position_definition_id, mt_name, mt_status, mt_source, mt_effective_date FROM apps.ghr_mt_position_definitions_v WHERE position_definition_id = :position_definition_id;

To review pending or failed transfers for a processing date:

SELECT ghr_interface_id, mt_name, mt_status, mt_person_id, mt_inter_bg_transfer FROM apps.ghr_mt_position_definitions_v WHERE mt_process_date >= :from_date AND mt_status <> 'COMPLETE' ORDER BY mt_process_date;

To inspect flexfield segment content for a staged position definition:

SELECT position_definition_id, segment1, segment2, segment3, enabled_flag, summary_flag FROM apps.ghr_mt_position_definitions_v WHERE position_definition_id = :position_definition_id;

These queries should be run with the APPS schema or an equivalent synonym, and results interpreted alongside the mass transfer log for the corresponding run.