Results for “ghr_mt_positions_v”

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

Overview

GHR_MT_POSITIONS_V is an Oracle E-Business Suite view owned by the APPS schema and categorized under the GHR – US Federal Human Resources product family. In Oracle EBS 12.1.1 and 12.2.2, the object carries a VALID status and is documented as a data-transfer view consumed by mass transfer in and out processes. Its principal role is to expose rows staged in the GHR mass-transfer interface in a horizontally flattened, denormalized form so that concurrent programs and integration routines can read and interpret those rows without performing repeated lookups against the underlying interface table.

Rather than presenting a normalized transactional structure, the view maps a generic set of INFORMATION columns to semantically meaningful aliases. This design allows the mass transfer processes to remain decoupled from the physical layout of the interface table, while still giving callers readable column names. Because the view is a reporting and integration artifact rather than a transaction-entry surface, it is typically queried within PL/SQL packages, concurrent program result sets, and ad hoc reconciliation reports.

Underlying Base Objects

Per the ETRM 12.2.2 documented metadata, GHR_MT_POSITIONS_V is defined over a single referenced base object: GHR_INTERFACE, which is exposed in the APPS schema as a SYNONYM. There are no additional documented base tables, views, or joins. All columns returned by the view therefore originate directly from GHR_INTERFACE.

The view performs a column-projection transformation rather than a join or aggregation. Each INFORMATIONn column in GHR_INTERFACE is renamed to a descriptive alias, and the interface identifier column is renamed to GHR_INTERFACE_ID. Because the mapping is purely positional, the view inherits the row count, filtering, and storage characteristics of the parent interface table, and its contents depend entirely on what the mass transfer processes have most recently loaded.

Key Columns

The view exposes a mixture of process-control columns and position-attribute columns. The most significant include:

• GHR_INTERFACE_ID – Unique identifier of the interface row, aliased from INTERFACE_ID; used to track and correlate staged records.
• MT_PROCESS_DATE – Date the mass transfer process processed the row.
• MT_SOURCE and MT_TABLE_NAME – Identify the originating source and interface table for data lineage.
• MT_EFFECTIVE_DATE, MT_NAME, MT_STATUS, MT_PERSON_ID, MT_INFORMATION_TYPE, and MT_INTER_BG_TRANSFER – Core descriptive and control attributes of the transfer record.
• POSITION_ID, BUSINESS_GROUP_ID, JOB_ID, ORGANIZATION_ID, LOCATION_ID, and POSITION_DEFINITION_ID – Key foreign references that identify the position and its organizational context.
• SUCCESSOR_POSITION_ID and RELIEF_POSITION_ID – Map the successor and relief position relationships. RELIEF_POSITION_ID is the column most directly associated with the user search term "relief_position_id" and is aliased from INFORMATION12.
• DATE_EFFECTIVE, DATE_END, COMMENTS, FREQUENCY, NAME, PROBATION_PERIOD, PROBATION_PERIOD_UNITS, REPLACEMENT_REQUIRED_FLAG, TIME_NORMAL_START, TIME_NORMAL_FINISH, and WORKING_HOURS – Detailed position attributes.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE – Concurrent program tracing columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE20 – Descriptive flexfield segments.
• OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and CREATED_BY – Standard audit and optimistic-locking columns.

Common Use Cases and Queries

Typical uses include validating staged mass-transfer rows before submission, reconciling positions affected by a transfer run, and locating records that reference a relief or successor position. The following queries illustrate these patterns.

Listing unprocessed position transfer rows:

• SELECT GHR_INTERFACE_ID, MT_PERSON_ID, POSITION_ID, RELIEF_POSITION_ID, MT_STATUS FROM GHR_MT_POSITIONS_V WHERE MT_STATUS IS NULL;

Identifying relief position assignments for a given position:

• SELECT GHR_INTERFACE_ID, POSITION_ID, SUCCESSOR_POSITION_ID, RELIEF_POSITION_ID FROM GHR_MT_POSITIONS_V WHERE RELIEF_POSITION_ID IS NOT NULL AND POSITION_ID = :p_position_id;

Auditing staged records for a specific concurrent request:

• SELECT GHR_INTERFACE_ID, MT_TABLE_NAME, REQUEST_ID, PROGRAM_ID, LAST_UPDATE_DATE FROM GHR_MT_POSITIONS_V WHERE REQUEST_ID = :p_request_id ORDER BY GHR_INTERFACE_ID;

Because the view is not joined to position or assignment tables, effective use generally requires joining its POSITION_ID, BUSINESS_GROUP_ID, and ORGANIZATION_ID columns to the corresponding HR position entities when descriptive context is needed.