Search Results insert_special_info

Overview

GHR_MTO_INT is the mass transfer-out integration package within the Oracle Human Resources (GHR) module of Oracle E-Business Suite. It supports the Mass Transfer functionality by extracting, staging, and inserting person-level records—along with their dependent assignments, addresses, extra information, special information, positions, and element entries—into the GHR interface tables for processing. The package is declared with AUTHID CURRENT_USER and carries a header revision string (ghmtoint.pkh 115.7) reflecting its long-standing role in the HRMS data migration and inter-business-group transfer architecture.

The core business purpose is to move a selected population of employees from a source business group to a target business group (or across transfer definitions) while preserving the full set of person-related data fragments that make up an employee record. The mass_transfer_out driver orchestrates this by writing records through the interface tables, which a later process consumes to create or update the destination records.

Key Procedures and Functions

The package exposes 28 documented procedures and functions. Among those most relevant to the caller searching for insert_assignment_f:

• GET_TRANSFER_PARAMETERS — Retrieves the transfer name, effective date, and inter-business-group transfer flag for a given mass transfer identifier.
• MASS_TRANSFER_OUT — The primary driver that, given a transfer ID and person ID, performs the outbound mass transfer for that individual.
• INSERT_ASSIGNMENT_F — Inserts an assignment record (based on the PER_ALL_ASSIGNMENTS_F rowtype) into the interface for the specified transfer and effective date.
• INSERT_ASSIGNMENT_EI — Inserts assignment extra information associated with a person and effective date.
• INSERT_PEOPLE_F / INSERT_PEOPLE_EI — Insert person records and their extra information.
• INSERT_SPECIAL_INFO — Inserts special information of a given flexfield type for a person.
• INSERT_ADDRESS — Inserts address records, with optional contact name and contact type to distinguish contact addresses.
• INSERT_POSITION / INSERT_POSITION_EI / INSERT_POSITION_DEFS — Insert position, position extra information, and position definition records.
• INSERT_ELEMENT_ENTRIES — Stages element entries for the transferred population.
• INSERT_MISC — Handles miscellaneous supporting records.
• UPDATE_PEOPLE_F / UPDATE_PEOPLE_EI / UPDATE_SPECIAL_INFO / UPDATE_ADDRESS / UPDATE_ASSIGNMENT_F — Perform the corresponding update operations when records already exist.
• SET_LOG_PROGRAM_NAME / LOG_MESSAGE — Provide logging and debugging control, routing messages through dbms_output or hr_utility.set_location depending on flags (g_dbms_output, g_log_enabled).

Parameter lists are deliberately omitted here; callers should consult the package specification for exact signatures.

Tables Accessed

Through APPS synonyms, the package reads and writes a set of core HRMS and interface tables. Person and assignment source data come from PER_ALL_PEOPLE_F and PER_ALL_ASSIGNMENTS_F. Supporting person-level attributes reside in PER_PEOPLE_EXTRA_INFO, PER_ASSIGNMENT_EXTRA_INFO, PER_ADDRESSES, and PER_CONTACT_RELATIONSHIPS. Position-related data is drawn from HR_ALL_POSITIONS_F, PER_POSITION_DEFINITIONS, PER_POSITION_EXTRA_INFO, HR_LOCATION_EXTRA_INFO, and PER_GRADES. The staging targets are the GHR interface and control tables: GHR_INTERFACE, GHR_INTERFACE_S, GHR_MASS_TRANSFERS, and GHR_PROCESS_LOG_S, the last providing the audit trail consumed by log_message.

Usage Notes

GHR_MTO_INT is not typically called directly by end users. It is invoked by the Mass Transfer concurrent program and by the HRMS business-group transfer flows, and it is referenced by 23 other packages—indicating its role as a shared integration layer. Custom or extension code should call the procedures in the same order the driver does, respecting the interface staging model, and should rely on set_log_program_name and log_message for diagnostics. Because the package operates with definer-independent current-user semantics, appropriate APPS privileges on the underlying synonyms are required.