Search Results insert_assignment_ei

Overview

GHR_MTO_INT is the internal PL/SQL package that implements the mass transfer-out side of the Oracle Human Resources Mass Transfer functionality in Oracle E-Business Suite. In EBS 12.1.1 and 12.2.2, this package performs the static, set-based movement of person, assignment, address, special information, and position records between business groups or organizations. It is classified as a partner/internal API (API classification OTHER) rather than a public, supported application programming interface, and it is not intended for direct customer invocation. The package carries the AUTHID CURRENT_USER directive, so it executes with the privileges of the calling schema, and it contains internal instrumentation — a package constant identifier, a log-enabled flag, a dbms_output switch, and a logging program name — that routes diagnostic output either to dbms_output or to hr_utility.set_location. The package is referenced by 23 other packages, indicating that it sits within a call hierarchy driven by the Mass Transfer concurrent program rather than being called in isolation.

Key Procedures and Functions

The documented 28 procedures fall into several functional groups. Parameter resolution and diagnostics are handled by GET_TRANSFER_PARAMETERS, which retrieves the transfer name, effective date, and inter-business-group indicator for a given mass transfer identifier; SET_LOG_PROGRAM_NAME, which establishes the program name used in log output; and LOG_MESSAGE, which writes a diagnostic message attributed to a named procedure.

The principal driver is MASS_TRANSFER_OUT, which accepts a transfer identifier and person identifier and, along with the standard concurrent program error buffer and return code, orchestrates the transfer of the individual's records. The insertion procedures apply the retrieved transfer parameters to each entity type: INSERT_PEOPLE_F and INSERT_PEOPLE_EI for the person record and person extra information; INSERT_ASSIGNMENT_F and INSERT_ASSIGNMENT_EI for assignment and assignment extra information; INSERT_SPECIAL_INFO for flexfield-based special information; and INSERT_ADDRESS, which optionally carries contact name and contact type when the address belongs to a contact rather than the person. Position-related procedures comprise INSERT_POSITION, INSERT_POSITION_EI, and INSERT_POSITION_DEFS. Remaining procedures include INSERT_ELEMENT_ENTRIES, INSERT_MISC, and a corresponding family of update procedures — UPDATE_PEOPLE_F, UPDATE_PEOPLE_EI, UPDATE_SPECIAL_INFO, UPDATE_ADDRESS, and UPDATE_ASSIGNMENT_F — that maintain existing rows when the target record already exists.

Tables Accessed

The package reads and writes the core HR tables through APPS synonyms. Person data is held in PER_ALL_PEOPLE_F and its descriptive flexfield companion PER_PEOPLE_EXTRA_INFO; assignment data resides in PER_ALL_ASSIGNMENTS_F with PER_ASSIGNMENT_EXTRA_INFO for additional attributes. Address and contact data are handled through PER_ADDRESSES and PER_CONTACT_RELATIONSHIPS. Position processing touches HR_ALL_POSITIONS_F, PER_POSITION_DEFINITIONS, and PER_POSITION_EXTRA_INFO, while grade validation references PER_GRADES and location-level information uses HR_LOCATION_EXTRA_INFO. Interface, staging, and audit data are captured in GHR_INTERFACE, GHR_INTERFACE_S, GHR_MASS_TRANSFERS, and GHR_PROCESS_LOG_S, the last supplying run-time logging and the former storing the mass transfer definition consumed by GET_TRANSFER_PARAMETERS.

Usage Notes

GHR_MTO_INT is invoked indirectly, principally by the Oracle HRMS Mass Transfer concurrent program (Mass Transfer Out), which calls the package for each selected person once the transfer parameters have been resolved. Customers and partners should not call these procedures directly, since the package is an internal implementation unit whose signature is not guaranteed across patches or upgrades; the supported extension points for mass transfer are the documented public HR APIs and the concurrent program parameters. When troubleshooting, the internal logging flags are useful: enabling dbms_output provides a procedural trace, while the default behaviour writes location information through hr_utility.set_location for use with HR diagnostics. Because the package operates with caller privileges and writes extensively to PER_ALL_ASSIGNMENTS_F date-tracked rows, any custom code that invokes it must run within an environment where effective-dating validation and business-group security are correctly established.