Search Results mass_transfer_in
Overview
The APPS.GHR_MTI_INT package is the integration entry point for the Oracle E-Business Suite mass transfer process, specifically the "transfer in" operation. In Oracle Human Resources (Oracle HRMS), the Global HR (GHR) mass transfer feature enables HR administrators to move groups of employees between organizational units, business groups, or other transferrable entities in a single controlled transaction rather than through individual record updates. The package name reflects its role: MTI denotes "Mass Transfer In," and INT denotes its function as an interface or integration layer that coordinates the underlying data manipulation.
The package header carries the version identifier ghmtiint.pkh 120.0.12010000.1, dated 28 July 2008, which is consistent with the code line shipped for EBS 12.1.1 and carried forward into 12.2.2. The header declares a single global constant, g_package, used for error-message prefixing, and a global boolean g_validate used to toggle validation behavior during execution. In ETRM, the object is classified as OTHER, meaning it is not a standard, fully supported public API, but is instead an internal integration package invoked by the mass transfer infrastructure.
Key Procedures and Functions
The documented interface exposes exactly one procedure: MASS_TRANSFER_IN. Its declared parameter list is:
p_errbuf out NOCOPY varchar2— the standard concurrent-program error buffer, populated with messages in the event of failure.p_retcode out NOCOPY number— the standard concurrent-program return code, indicating success or failure to the calling framework.p_transfer_id in number— the identifier of the mass transfer record to be processed.p_business_group_id in number— the business group context under which the transfer is performed.
The use of p_errbuf and p_retcode confirms that this procedure is designed to be called as a concurrent program executable, allowing the mass transfer to run as a background job. The p_transfer_id parameter coordinates the procedure with a previously defined mass transfer definition, while p_business_group_id scopes the operation to the correct legislative and organizational context.
Tables Accessed
The package accesses the following tables through APPS synonyms:
GHR_MASS_TRANSFERS— the driving table holding the mass transfer definition and status for the suppliedp_transfer_id.PER_ALL_PEOPLE_F— the core person record; used to identify and update the employees affected by the transfer.PER_PERSON_TYPES— validates and applies the appropriate person type for the transferred employees.PER_ASSIGNMENT_STATUS_TYPES— governs the assignment status applied during the transfer.PER_PEOPLE_EXTRA_INFO— stores and reads additional person-level information that may be carried through the transfer.FND_ID_FLEX_STRUCTURES_TL— the translated key flexfield structure definitions used to validate descriptive flexfield context for the affected records.
Usage Notes
GHR_MTI_INT.MASS_TRANSFER_IN is normally invoked by the Oracle HRMS mass transfer concurrent program, not directly by end users. Because it conforms to the concurrent manager calling convention, it may also be registered as a custom concurrent executable, provided a valid mass transfer definition already exists. The package is referenced by zero other documented packages, confirming it is a top-level integration routine rather than a shared utility. Developers extending mass transfer behavior should treat it as an internal interface: direct calls require a committed GHR_MASS_TRANSFERS row, correct business group context, and awareness that validation semantics are controlled by the g_validate flag internal to the package body.
-
PACKAGE: APPS.GHR_MTI_INT
12.1.1
-
PACKAGE: APPS.GHR_MTI_INT
12.2.2
-
PACKAGE BODY: APPS.GHR_MASS_CHANGES
12.1.1
-
PACKAGE BODY: APPS.GHR_MASS_CHANGES
12.2.2
-
PACKAGE BODY: APPS.GHR_MTI_INT
12.2.2
-
PACKAGE BODY: APPS.GHR_MTI_INT
12.1.1
-
APPS.GHR_MASS_CHANGES dependencies on GHR_PA_REQUESTS_PKG
12.1.1
-
APPS.GHR_MASS_CHANGES dependencies on GHR_API
12.2.2
-
APPS.GHR_MASS_CHANGES dependencies on HR_API
12.1.1
-
APPS.GHR_MASS_CHANGES dependencies on GHR_API
12.1.1
-
APPS.GHR_MASS_CHANGES dependencies on HR_API
12.2.2
-
APPS.GHR_MTI_INT dependencies on PER_PERSON_TYPES
12.2.2
-
APPS.GHR_MASS_CHANGES dependencies on GHR_PA_REQUESTS_PKG
12.2.2
-
APPS.GHR_MTI_INT dependencies on PER_PERSON_TYPES
12.1.1
-
APPS.GHR_MTI_INT dependencies on GHR_MTI_INT
12.1.1
-
APPS.GHR_MTI_INT dependencies on GHR_MTI_INT
12.2.2
-
APPS.GHR_MASS_CHANGES dependencies on HR_UTILITY
12.1.1
-
APPS.GHR_MASS_CHANGES dependencies on HR_UTILITY
12.2.2
-
APPS.GHR_MASS_CHANGES dependencies on GHR_PA_REQUESTS
12.1.1
-
APPS.GHR_MTI_INT dependencies on GHR_MASS_TRANSFERS
12.1.1
-
APPS.GHR_MTI_INT dependencies on GHR_MASS_TRANSFERS
12.2.2
-
APPS.GHR_MASS_CHANGES dependencies on GHR_MSL_PKG
12.2.2
-
PACKAGE BODY: APPS.GHR_MTI_APP
12.1.1
-
PACKAGE BODY: APPS.GHR_MTI_APP
12.2.2
-
APPS.GHR_MASS_CHANGES dependencies on GHR_PA_REQUESTS
12.2.2
-
APPS.GHR_MTI_APP dependencies on GHR_MASS_CHANGES
12.1.1
-
APPS.GHR_MTI_APP dependencies on GHR_MASS_CHANGES
12.2.2