Search Results insert_position

Overview

The APPS.GHR_MTO_INT package is a PL/SQL interface package belonging to the Oracle HRMS Mass Transfer Operations (MTO) subsystem. Its principal business function is to execute the outbound side of a mass transfer — the process by which a defined population of employees, assignments, positions, and related entities are selected, validated, and materialised into the GHR interface tables for downstream transfer between business groups or across legislative data groups. The package declares AUTHID CURRENT_USER and exposes a set of public procedures used to insert and update records in the core HR tables and their corresponding extra information tables as part of a mass transfer run. It also provides logging and parameter-retrieval utilities that support the atomic, auditable execution of a transfer.

Key Procedures and Functions

The package exposes 28 documented procedures, organised around distinct functional groupings:

• Transfer driver and control: GET_TRANSFER_PARAMETERS retrieves the transfer name, effective date, and inter-business-group indicator for a given mass transfer identifier. MASS_TRANSFER_OUT is the principal entry point that orchestrates the outbound mass transfer for a specified person.
• Logging: SET_LOG_PROGRAM_NAME establishes the program name used in log entries, while LOG_MESSAGE writes diagnostic and audit messages to the GHR process log.
• People inserts: INSERT_PEOPLE_F and INSERT_PEOPLE_EI create person records in PER_ALL_PEOPLE_F and associated extra information respectively.
• Position handling (directly relevant to the user query "insert_position"): INSERT_POSITION, INSERT_POSITION_EI, and INSERT_POSITION_DEFS create position records in HR_ALL_POSITIONS_F, position extra information in PER_POSITION_EXTRA_INFO, and position definitions in PER_POSITION_DEFINITIONS. These routines are invoked when the transferred population includes positions that must be replicated in the destination business group.
• Assignment inserts: INSERT_ASSIGNMENT_F and INSERT_ASSIGNMENT_EI create assignment and assignment extra information records.
• Address and contact inserts: INSERT_ADDRESS writes to PER_ADDRESSES, optionally carrying contact name and contact type for contact-address scenarios.
• Other inserts: INSERT_SPECIAL_INFO and INSERT_ELEMENT_ENTRIES handle special information types and payroll element entries; INSERT_MISC covers residual entity types.
• Update counterparts: Parallel update procedures — UPDATE_PEOPLE_F, UPDATE_PEOPLE_EI, UPDATE_SPECIAL_INFO, UPDATE_ADDRESS, and UPDATE_ASSIGNMENT_F — manage records that already exist and require modification during the transfer.

Tables Accessed

Through APPS synonyms the package reads and writes: HR_ALL_POSITIONS_F, PER_POSITION_DEFINITIONS, and PER_POSITION_EXTRA_INFO (position creation and definitions); PER_ALL_PEOPLE_F and PER_PEOPLE_EXTRA_INFO (person records and extra information); PER_ALL_ASSIGNMENTS_F and PER_ASSIGNMENT_EXTRA_INFO (assignment records); PER_ADDRESSES and PER_CONTACT_RELATIONSHIPS (addresses and contacts); PER_GRADES (grade validation); HR_LOCATION_EXTRA_INFO (location extra information); and the control/interface tables GHR_INTERFACE, GHR_INTERFACE_S, GHR_MASS_TRANSFERS, and GHR_PROCESS_LOG_S, which hold transfer definitions, staging rows, and log output. PER_POSITION_EXTRA_INFO and PER_POSITION_DEFINITIONS are the tables specifically targeted by the INSERT_POSITION* procedures.

Usage Notes

GHR_MTO_INT is an internal HRMS interface package rather than a public API, and is referenced by 23 other packages within the GHR mass transfer framework. It is typically invoked from the Mass Transfer Operations concurrent program (and the associated MTO forms) rather than called directly from custom code. Because the package writes directly to date-tracked HR tables and their extra information tables, invocations are expected to run within the transaction and validation context established by the mass transfer driver; log messages are routed through HR_UTILITY.SET_LOCATION or optionally through DBMS_OUTPUT when the internal g_dbms_output flag is enabled. Customisations should avoid calling the INSERT_POSITION, INSERT_PEOPLE_F, or other write procedures directly, since business-group and date-track integrity is enforced by the surrounding mass transfer orchestration.