Search Results orig_appointment_auth_code_1

Overview

APPS.GHR_MT_INTERFACE_V is a reporting and integration view in the Oracle EBS Human Resources (HR) module, belonging to the GHR (Global Human Resources) family of MT (Mass Transaction / Interface) objects. It presents a consolidated, interface-ready projection of person-level records together with their associated assignment, element entry, position, and miscellaneous attributes. The view is intended to feed downstream processes — typically federal or public-sector HR interfaces — where employee data must be extracted in a flattened, type-normalized form suitable for external consumption.

The view's design reflects its role as a staging/interface layer: string columns are truncated to precise lengths using SUBSTR, and date columns are re-typed via TO_DATE with explicit format masks, ensuring that the output conforms to a fixed, predictable contract regardless of the underlying storage. This makes GHR_MT_INTERFACE_V particularly relevant to agencies that must exchange person data with external systems (for example, payroll or benefits providers).

Underlying Base Objects

The ETRM 12.2.2 metadata documents the following referenced base objects:

• FND_DATE (PACKAGE) — used for date conversion/validation utilities.
• GHR_MT_PEOPLE_F_V and GHR_MT_PEOPLE_EI_V — the person and person extra-information (EI) views supplying biographical and descriptive attributes.
• GHR_MT_ASSIGNMENTS_F_V and GHR_MT_ASSIGNMENT_EI_V — assignment records and assignment extra information.
• GHR_MT_ELEMENT_ENTRIES_V — payroll/benefits element entry data.
• GHR_MT_POSITIONS_V and GHR_MT_POSITION_EI_V — position and position extra information.
• GHR_MT_MISC_V — miscellaneous/transfer-related fields such as agency codes.
• GHR_MT_ANALYSIS_CRITERIA_V — analysis criteria used for MT record selection.

The view therefore joins person, assignment, position, element entry, and miscellaneous MT views into a single denormalized result set, aliasing the person source as PEOP, the person EI sources as PEI_1 through PEI_4, and miscellaneous data as MISC.

Key Columns

The columns exposed by GHR_MT_INTERFACE_V fall into several logical groups:

• MT control columns: MT_NAME, MT_PROCESS_DATE, MT_EFFECTIVE_DATE, MT_SOURCE, MT_STATUS, MT_PERSON_ID, and MT_INTER_BG_TRANSFER identify the mass transaction record, its processing state, and any inter-business-group transfer flag. MT_PERSON_ID is explicitly cast with TO_NUMBER.
• Person biographical data: FIRST_NAME, MIDDLE_NAMES, LAST_NAME, FULL_NAME (truncated to 240 characters), DATE_OF_BIRTH, MARITAL_STATUS, SEX, TITLE, NATIONAL_IDENTIFIER, NATIONALITY, WORK_TELEPHONE, and EMPLOYEE_NUMBER.
• Dates: EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, and START_DATE, each converted using a 'DD/MM/YYYY' mask.
• Extra information (EI) attributes: CITIZENSHIP, VETERANS_PREFERENCE, VETERANS_PREFERENCE_FOR_RIF, VETERANS_STATUS, APPOINTMENT_TYPE, FERS_COVERAGE, TYPE_OF_EMPLOYMENT, RACE_OR_NATIONAL_ORIGIN, and ORIG_APPOINTMENT_AUTH_CODE_1, along with their descriptive "meaning" counterparts (e.g., CITIZENSHIP_DESC, VETERANS_STATUS_DESC, FERS_COVERAGE_DESC).
• Miscellaneous: AGENCY_CODE_TRANSFER_FROM and related transfer information sourced from MISC.

The user search term "mt_name" maps directly to the first column in the select list, MT_NAME, which serves as the primary identifier for the mass transaction that produced each row.

Common Use Cases and Queries

This view is typically queried for interface extraction, reconciliation, or troubleshooting of MT-record processing. A representative query filters by transaction name and status:

• Extract all persons for a given mass transaction: SELECT MT_PERSON_ID, FULL_NAME, EMPLOYEE_NUMBER, MT_STATUS FROM APPS.GHR_MT_INTERFACE_V WHERE MT_NAME = :p_mt_name;
• List distinct transactions and their processing dates: SELECT DISTINCT MT_NAME, MT_PROCESS_DATE, MT_SOURCE FROM APPS.GHR_MT_INTERFACE_V ORDER BY MT_PROCESS_DATE;
• Report on veterans' preference and citizenship attributes for a batch: SELECT MT_PERSON_ID, CITIZENSHIP_DESC, VETERANS_PREFERENCE_DESC, VETERANS_STATUS_DESC FROM APPS.GHR_MT_INTERFACE_V WHERE MT_NAME = :p_mt_name;

Because the view normalizes types and truncates strings, it is well suited for feeding fixed-width or length-constrained external interfaces, and for validation reporting prior to interface submission.