This chapter provides an overview of intercompany transfer tracking and discusses how to:
Set up employee data for intercompany transfers.
Enter and maintain home and host data for intercompany transfers.
Work with search page security.
Run the Intercompany Transfer report.
Whenever you need to track intercompany transfers (shukkou), whether as a home company or a host company, you enter a new job record with standard actions such as transfer, termination, and hire, but with specific action reasons that are related to intercompany transfers. You can use the Pay Group field on the Job Data - Payroll page to indicate which company is the compensation owner.
This section discusses home and host data for intercompany transfers and lists prerequisites.
The tables in the two sections that follow provide summarized data entry obligations and requirements for different intercompany transfer scenarios. The first table addresses only the hosting of intercompany transfers; the second table addresses both temporary and permanent intercompany transfers.
A later section provides details of data entry for a series of scenarios.
See Entering and Maintaining Home and Host Data for Intercompany Transfers.
This table explains the abbreviations that are used in the two subsequent tables:
Code |
Description |
Action |
ICT |
Intercompany Transfer |
Shukkou |
TICT |
Temporary Intercompany Transfer |
Zaiseki-Shukkou |
PICT |
Permanent Intercompany Transfer |
Tenseki-Shukkou |
HICT |
Hosting Intercompany Transfer |
Shukkou-Ukeire |
HTICT |
Hosting Temporary Intercompany Transfer |
Zaisekki-Shukkou no Ukeire |
HPICT |
Hosting Permanent Intercompany Transfer |
Tenseki-Shukkou no Ukeire |
SL |
Supervisor Level |
Yakushoku |
AA |
Additional Appointment |
Kenmu |
PA |
Primary Appointment |
Shumu |
Hosting Temporary and Permanent Intercompany Transfers
The following table summarizes the information and security requirements for hosting temporary intercompany transfers from companies within a group that uses PeopleSoft HCM and from other companies that don't use PeopleSoft HCM:
ICT Type |
PA Location |
Information and Security Required Within Affiliated Companies that Use PeopleSoft HCM |
Information and Security Required for Affiliated Companies that Do Not Use PeopleSoft HCM |
1 HTICT |
Host (Own Company) |
|
|
2 HPICT |
Host (Own Company) |
Employee information is maintained at host (own) company only. |
Host company information, using Intercompany Transfer Company/Department and Intercompany Transfer Supervisor Level codes. |
Temporary and Permanent Intercompany Transfers
This table summarizes the information and security requirements for temporary intercompany transfers to companies within a group that uses PeopleSoft HCM and to other companies that don't use PeopleSoft HCM:
ICT Type |
PA Location |
AA at Home Company? |
Information and Security Required Within Affiliated Companies that Use PeopleSoft HCM |
Information and Security Required for Affiliated Companies that Do Not Use PeopleSoft HCM |
TICT |
Host |
No |
|
|
PICT |
N/A (Completely terminated from home company) |
N/A |
Employee information will be maintained at host company only. |
N/A |
Before you enter intercompany transfers for an employee, complete these steps:
Set up a dummy pay group to use as the compensation indicator if you track intercompany transfers in which the host company (that is, not your company) is responsible for paying the employee.
Note. This setup is reversed if your company is the hosting company; that is, you set up a dummy pay group to track hosted intercompany transfers where the home company pays the employee.
Set up company and department codes to use for tracking intercompany transfers to and from companies that are not registered in the Company table.
Set up supervisor level and IC Trans External supervisor level codes to use for tracking intercompany transfers to and from companies that are not registered in the Company table.
Note. You can track intercompany transfers (shukkou) as additional appointments (kenmu) if you set up and use the additional appointment functionality.
See Also
(JPN) Setting Up Intercompany Transfer Company Data
(JPN) Tracking Additional Appointments (Kenmu)
Indicating the Home or Host Compensation Owner
This section discusses how to:
Track intercompany transfers.
Indicate the home or host compensation owner.
Note. This section discusses the basics of how to set up an intercompany transfer. See the next section for detailed examples of data entry and maintenance.
See Also
Entering and Maintaining Home and Host Data for Intercompany Transfers
Whenever you need to track intercompany transfers, whether as a home company or a host company, set up the employee data:
Enter a new job record with standard actions such as transfer, termination, and hire, but with specific action reasons that are related to intercompany transfers.
Complete the intercompany transfer fields in the Japan section of the Work Location page.
Selecting Actions and Reasons for Intercompany Transfers
These are the actions and reasons that you use on the Administer Workforce pages when you work with intercompany transfers:
Action |
Reason |
Transfer |
Intercompany transfer. |
|
Completion of intercompany transfer. |
Termination |
Permanent intercompany transfer. |
|
Completion of (hosted) intercompany transfer. |
Hire |
Temporary intercompany transfer. |
|
Permanent intercompany transfer. |
See Also
Entering Employee Job Location and Position Information
You can use the Pay Group field on the Job Data - Payroll page (Workforce Administration, Job Information, Job Data, Payroll) to identify whether the home or the host company is responsible for paying an employee on temporary intercompany transfer. If the home company is paying, put the employee in a standard pay group with other employees. If the host company is paying, put the employee in a designated dummy pay group that has no payroll processing implications for your (home) company.
Similarly, if you are the host for a temporary intercompany transfer, put the employee in a standard pay group if you are paying the employee, or into a designated dummy pay group if the home company is paying the employee.
Note. When the Payroll System field is set to Other on the Job Data - Payroll page, the Pay Group field is not a required field. You can use the field as described previously whether it is required or not.
See Also
Entering Payroll Processing Data
The following three sets of scenarios detail the data input and maintenance requirements by the home or host company. Sets B and C are similar, but reflect different security conditions.
The sets of scenarios are:
Set A: Single Company Using a Single PeopleSoft HCM Database.
Set B: Multiple Companies Using a Single PeopleSoft HCM Database (with security restrictions).
Set C: Multiple Companies Using a Single PeopleSoft HCM Database (without security restrictions).
This section discusses several scenarios for a single company that uses a single human resources database.
Note. Additional Employment Instance is not used for any scenarios in set A. The scenarios in set A are applicable when multiple companies use a single human resources database but the information—for the home or host company relevant to a particular intercompany transfer—is not stored in that database.
Scenario A1: TICT
Home Company Inputs
Table |
Fields |
Input |
JOB |
Action |
Transfer. |
Reason |
Temporary intercompany transfer. |
|
Department ID |
Department ID that indicates temporary intercompany transfer. |
|
Pay Group |
If the home company is responsible for compensation, no change occurs to the pay group. If not, enter a dummy pay group to indicate that the host (other) company is responsible for compensation. No processing is associated with dummy pay groups. |
|
JOB_JR |
Intercompany Transfer Flag |
Host company information. |
Business Unit code |
If the home company is a normal (internal) company, enter the code. If not, leave this field blank. |
|
Company code |
If the Host company is a normal (internal) company, enter the code. If it is an external company, enter the ICT Company code. |
|
Department code |
If the host company is a normal (internal) company, enter the department code. If it is an external company, enter the ICT Department code. |
|
Sup Lvl ID code |
If the host company is a normal (internal) company, enter the supervisor level ID. If it is an external company, enter the ICT supervisor level ID. |
|
ICT Start Date |
Actual start date of intercompany transfer. |
|
ICT End Date |
Expected end date of ICT. |
Host Company Inputs
Not applicable.
Scenario A2: Completion of TICT
Home Company Inputs
Table |
Fields |
Input |
JOB |
Action |
Transfer. |
Reason |
Completion of ICT. |
|
Department ID |
Employee's home company department. |
|
Pay Group |
Employee's home company pay group. |
Host Company Inputs
Not applicable.
Scenario A3: PICT
Home Company Inputs
Table |
Fields |
Input |
Job |
Action |
Termination. |
Reason |
Permanent intercompany transfer. |
|
JOB_JR |
Intercompany Transfer Flag |
Host company information. |
Business Unit (code) |
If the home or host company is a normal (internal) company, enter the code. If not, leave this field blank. |
|
Company code |
If the host company is a normal (internal) company, enter the code. If it is an external company, enter the ICT Company code. |
|
Department code |
If the host company is a normal (internal) company, enter the Department code. If it is an external company, enter the ICT Department code. |
|
Sup Lvl ID code |
If the host company is a normal (internal) company, enter the supervisor level ID. If it is an external company, enter the ICT supervisor level ID. |
Host Company Inputs
Not applicable.
Scenario A4: HTICT
Home Company Inputs
Not applicable.
Host Company Inputs
Table |
Fields |
Input |
JOB |
Action |
Hire. |
Reason |
Temporary intercompany transfer. |
|
Pay Group |
If host (own) company is responsible for compensation, enter the pay group in which you want the employee. If not, enter a dummy pay group to indicate that the home (other) company is responsible for compensation. |
|
Employee Class |
Hosting intercompany transfer. |
|
JOB_JR |
Intercompany Transfer Flag |
Home company information. |
Business Unit (code) |
If the home or host company is a normal (internal) company, enter the code. If not, leave this field blank. |
|
Company code |
If the host company is a normal (internal) company, enter the code. If it is an external company, enter the ICT Company code. |
|
Department code |
If the host company is a normal (internal) company, enter the Department code. If it is an external company, enter the ICT Department code. |
|
Sup Lvl ID code |
If the host company is a normal (internal) company, enter the supervisor level ID. If it is an external company, enter the ICT supervisor level ID. |
|
ICT Start Date |
Actual start date of intercompany transfer. |
|
ICT End Date |
Expected end date of ICT. |
Scenario A5: Completion of HTICT
Home Company Inputs
Not applicable.
Host Company Inputs
Table |
Fields |
Input |
JOB |
Action |
Termination. |
Reason |
Completion of TICT. |
Scenario A6: HPICT
Home Company Inputs
Not applicable.
Host Company Inputs
Table |
Fields |
Input |
JOB |
Action |
Hire. |
Reason |
Permanent intercompany transfer. |
|
Pay Group |
Pay group in which you want this employee. |
|
Employee Class |
Hosting intercompany transfer. |
|
JOB_JR |
Intercompany Transfer Flag |
Home company information. |
Business unit code |
If the home or host company is a normal (internal) company, enter the code. If not, leave this field blank. |
|
Company code |
If the host company is a normal (internal) company, enter the code. If it is an external company, enter the ICT Company code. |
|
Department: code |
If the host company is a normal (internal) company, enter the Department code. If it is an external company, enter the ICT Department code. |
|
Sup Lvl ID code |
If the host company is a normal (internal) company, enter the supervisor level ID. If it is an external company, enter the ICT supervisor level ID. |
This section discusses several scenarios for multiple companies that use a single human resources database.
Conditions:
Both home and host companies use the same database and business unit, company, department ID, and supervisor level ID.
Security settings make it impossible for either company to access the other's information.
Scenario B1: TICT
Home Company Inputs (Temporary Intercompany Transfer - TICT)
Table |
Fields |
Input |
JOB |
Action |
Transfer. |
Reason |
Temporary intercompany transfer. |
|
Department ID |
Dummy ID that indicates temporary intercompany transfer. |
|
Pay Group |
If home (own) company is responsible for compensation, no change occurs to the pay group. If not, enter a dummy pay group to indicate that the host (other) company is responsible for compensation. No processing is associated with dummy pay groups. |
|
Job Indicator |
Because the host company enters information by using concurrent jobs functionality, it is Secondary. |
|
JOB_JR |
Intercompany Transfer Flag |
Host company information. |
Business unit code |
Business unit to which the employee will be sent. |
|
Company code |
Host company to which the employee will be sent. |
|
Department ID code |
Host department in which the employee will be. |
|
Sup Lvl ID code |
Supervisor level that employee will take in host company. |
|
ICT Start Date |
Actual start date of intercompany transfer. |
|
ICT End Date |
Expected end date of ICT. |
Host Company Inputs (Hosting Temporary Intercompany Transfer - TICT)
Table |
Fields |
Input |
JOB |
Employee ID |
If accessing through Add Employment Instance, use the same employee ID as the home company. If accessing through the Add a Person page, assign a new ID. |
Employee Record # |
Employee ID is 1 or higher. |
|
Action |
Hire. |
|
Reason |
Temporary intercompany transfer. |
|
Company |
Host company. |
|
Department ID |
Host department in which the employee will be. |
|
Pay Group |
If host (own) company is responsible for compensation, the pay group in which you want this employee. If not, enter a dummy pay group to indicate that the home (other) company is responsible for compensation. |
|
Employee Class |
Hosting intercompany transfer. |
|
Job Indicator |
Primary. |
|
JOB_JR |
Intercompany Transfer Flag |
Home company information. |
|
Business unit code |
Employee's home business unit. |
Company code |
Employee's home company. |
|
Department ID code |
Employee's home department. |
|
ICT Start Date |
Actual start date of intercompany transfer. |
|
ICT End Date |
Expected end date of ICT. |
Scenario B2: Completion of TICT
Home Company Inputs (Completion of Temporary Intercompany Transfer)
Table |
Fields |
Input |
JOB |
Action |
Transfer. |
Reason |
Completion of temporary intercompany transfer. |
|
Department ID |
Home company department in which the employee will be. |
|
Pay Group |
Pay group for home company that is responsible for compensation. |
|
Job Indicator |
Primary. |
Host Company Inputs (Completion of Hosting Temporary Intercompany Transfer)
Table |
Fields |
Input |
JOB |
Action |
Termination. |
Reason |
Completion of temporary intercompany transfer. |
|
Job Indicator |
Secondary. |
Scenario B3: PICT
Home Company Inputs (Permanent Intercompany Transfer - PICT)
Table |
Fields |
Input |
JOB |
Action |
Termination. |
Reason |
Permanent intercompany transfer. |
|
Job Indicator |
Because the host company entered information by using concurrent jobs functionality, it is Secondary. |
|
JOB_JR |
Intercompany Transfer Flag |
Host company information. |
Business unit code |
Business unit to which the employee is transferring. |
|
Company code |
Host company to which the employee is transferring. |
|
Department ID code |
Employee's host department. |
|
Sup Lvl ID code |
Supervisor level that employee will have in host company. |
Host Company Inputs (Hosting Permanent Intercompany Transfer - PICT)
Table |
Fields |
Input |
JOB |
Employee ID |
If accessing through Add Employment Instance, use the same employee ID as the home company. If accessing through the Add a Person page, assign a new ID. |
Employee Record # |
If accessing through the Concurrent Jobs page, the employee ID is 1 or higher. |
|
Action |
Hire. |
|
Reason |
Permanent intercompany transfer. |
|
Pay Group |
Regular host company pay group in which the employee will be. |
|
Employee Class |
Hosting intercompany transfer. |
|
Job Indicator |
Primary. |
|
JOB_JR |
Intercompany Transfer Flag |
Home company information. |
Business Unit code |
Business unit from which the employee comes. |
|
Company code |
Home company to which the employee belongs. |
|
Department ID code |
Home department in which the employee was. |
This section discusses several scenarios for multiple companies that use a single PeopleSoft HCM database.
Conditions:
Both home and host companies use the same database and business unit, company, department ID, and supervisor level ID.
Security settings allow all companies to access each other's information.
Scenario C1: TICT
Home Company Inputs (Temporary Intercompany Transfer - TICT)
Table |
Fields |
Input |
JOB |
Action |
Transfer. |
Reason |
Temporary intercompany transfer. |
|
Department ID |
Dummy ID that indicates temporary intercompany transfer. |
|
Pay Group |
If home (own) company is responsible for compensation, no change occurs to the pay group. If not, enter a dummy pay group to indicate that the host (other) company is responsible for compensation. |
|
Job Indicator |
Because the host company enters information by using concurrent jobs functionality, it is Secondary. |
|
JOB_JR |
Intercompany Transfer Flag |
Host company information. |
ICT Start Date |
Actual start date of intercompany transfer. |
|
ICT End Date |
Expected end date of ICT. |
Host Company Inputs (Hosting Temporary Intercompany Transfer - TICT)
Table |
Fields |
Input |
JOB |
Employee ID |
If accessing through Add Employment Instance, use the same employee ID as the home company. If accessing through the Add a Person page, assign a new ID. |
Employee Record # |
If accessing through the Concurrent Jobs page, the employee ID is 1 or higher. |
|
Action |
Hire. |
|
Reason |
Temporary intercompany transfer. |
|
Company |
Host company. |
|
Department ID |
Host department in which the employee will be. |
|
Pay Group |
If host (own) company is responsible for compensation, the pay group in which you want this employee. If not, enter a dummy pay group to indicate that the home (other) company is responsible for compensation. |
|
Employee Class |
Hosting intercompany transfer. |
|
Job Indicator |
Primary. |
|
JOB_JR |
Intercompany Transfer Flag |
Home company information. |
ICT Start Date |
Actual start date of intercompany transfer. |
|
ICT End Date |
Expected end date of ICT. |
Scenario C2: Completion of TICT
See Scenario B2: Completion of Temporary Intercompany transfer.
Scenario C3: PICT
Home Company Inputs (Permanent Intercompany Transfer - PICT)
Table |
Fields |
Input |
JOB |
Action |
Termination. |
Reason |
Permanent intercompany transfer. |
|
Job Indicator |
Because the host company entered information by using concurrent jobs functionality, it is Secondary. |
|
JOB_JR |
Intercompany Transfer Flag |
Host company information. |
Host Company Inputs (Hosting Permanent Intercompany Transfer - PICT)
Table |
Fields |
Input |
JOB |
Employee ID |
If accessing through Add Employment Instance, use the same employee ID as the home company. If accessing through the Add a Person page, assign a new ID. |
Employee Record # |
If accessing through the Concurrent Jobs page, the employee ID is 1 or higher. |
|
Action |
Hire. |
|
Reason |
Permanent intercompany transfer. |
|
Pay Group |
Regular host company pay group in which the employee will be. |
|
Employee Class |
Hosting intercompany transfer. |
|
Job Indicator |
Primary. |
|
JOB_JR |
Intercompany Transfer Flag |
Home company information. |
This section discusses how department security (Search Page Security on PERS_SRCH_COR and EMPLMT_SRCH_COR) works when you use the system's Multiple Jobs functionality.
Note. You can set up this security in many different ways. Your specific business requirements determine how you set up yours. This section describes one example of how you may set up your security.
This information makes the following assumptions:
You want to manage two companies in one database: company A and company B, where company B is a subsidiary of company A.
The entire organization of company A belongs to business unit A (BUA), and the entire organization of company B belongs to business unit B (BUB).
You have defined two setIDs: SIDA and SIDB for companies A and B, respectively.
Neither company's workers have meaningful employee IDs; that is, the ID does not identify the company.
For example, a person with employee ID 1002 may belong to company B, whereas workers with employee IDs 1001 and 1003 belong to company A.
This security has two users: USR1 and USR2.
USR1 has the right to access the sales department of company A, and USR2 has the right to access the sales department of company B.
Following these assumptions, the next table represents the job rows for the person with employee ID 1001, who:
Was originally hired by company A.
Went on a temporary intercompany transfer to company B (scenario B1).
Returned to company A (scenario B3).
Went on permanent intercompany transfer to company B (scenario B6).
Key: In this table, Empl Rec# = Employment Record Number, Co. = Company, ICT = InterCompany Transfer, A/R = Action/Reason, D = Department, and J = Job Indicator.
Event |
Empl Rec#0 |
Empl Rec#1 |
1. Hired by company A |
A/R − Hired Co. − A D − Sales J − Primary |
NA |
2. Temporary ICT to company B |
A/R − Transfer/ICT Co. − A D − Human Resources J − Secondary |
A/R − Hire/Temporary ICT Co. − B D − Sales J − Primary |
3. Returned to company A |
A/R −Transfer/Completion of Temporary ICT Co. − A D − Sales J − Primary |
A/R −Termination/Completion of Temporary ICT Co. − B D − Sales J − Secondary |
4. Permanent ICT to company B 4a. Terminated from company A 4b. Hired (or rehired) by company B |
A/R − Termination / Permanent ICT Co. − A A/R − Hired or rehired / Permanent ICT Co. − B D − Sales J − Primary |
NA |
This example shows how departmental security (search page security) works for users who have security right access to a department. Users can do one of the following:
Access all employees whose current jobs belong to that department when PERS_SRCH_GBL is used as the search table.
Access the particular record numbers for employees whose current job is in the department when EMPLMT_SRCH_GBL is used as the search table.
This table shows which users have access to which data at each of the four events described for employee 1001:
Event |
Personal Data |
Empl Rec#0 Data |
Empl Rec#1 Data |
PERS_SRCH_GBL |
EMPLMT_SRCH_GBL |
EMPLMT_SRCH_GBL |
|
1. Hired by company A |
USR1 |
USR1 |
NA |
2. Temporary ICT to company B |
USR1 and USR2 |
USR1 |
USR2 |
3. Returned to company A |
USR1 and USR2 |
USR1 |
USR2 |
4a. Permanent ICT to company B 4b. Hired or rehired by company B |
USR1 and USR2 USR2 |
USR1 USR2 |
USR2 USR2 |
This section lists the page used to run the JPN Completion of IC Transfer report.
Page Name |
Definition Name |
Navigation |
Usage |
RUNCTL_PER065_JPN |
Workforce Administration, Job Information, Reports, Completion of IC Transfer JPN, Completion of IC Transfer JPN |
Run the JPN Completion of IC Transfer report (PER065JP), which lists employees on temporary intercompany transfer. The home company uses this report to confirm employees who are anticipated to return from temporary intercompany transfer. |