This chapter discusses how to:
Implement employee data security for global assignments.
Define global assignment types.
Classify types of company-paid travel.
Define deductions and earnings for assignment compensation.
Set up education data for assignments.
This section discusses:
Employee data security.
Security access setup for global assignments.
Security for one home and one host.
Security for one home and multiple, concurrent hosts.
Security for permanent transfers.
Security access to employee data assumes greater importance when processing global assignments because human resources (HR) administrators at multiple locations need access to data on the same employee. With multiple current home or host data at various locations around the world, security access can be a logistical nightmare.
The PeopleSoft Enterprise Human Resources system eliminates this worry. Employees going on global assignments have at least one home record, which falls under the jurisdiction of the HR administrators at the home base, and at least one host record, which falls under the jurisdiction of the HR administrators at the host location. Human Resources automatically checks each current employment record to identify all primary permission list groups that should have security access to the employee data.
As delivered, Human Resources implements employee data security with users grouped into primary permission list classes and data grouped by department. You can modify the implementation of data security by using user IDs, locations, or other groupings, but for our discussion here, PeopleSoft assumes that you use primary permission list classes and departments.
See Also
Setting Up and Administering HRMS Security
PeopleTools PeopleBook: PeopleSoft Application Designer
Often, employees have data pertaining to one home and one host: they have a permanent job and go on one assignment after another, sequentially. To demonstrate how organizational security works, this section discusses a few examples of simple and complex global assignment situations involving Yves Chabot, an employee permanently based at KF1 company headquarters in France, in department 13000.
Step 1: First Assignment
In 1994, Yves went on a four-year temporary assignment to the Edinburgh, Scotland office, department 21300. His home data in France uses employment record 0, and his host data for Scotland uses employment record 1. To administer human resource tasks for Yves, HR administrators in both France and Scotland need access to his data.
French administrators belong to the DPFRA primary permission list class, which allows them access to data for French departments that are in the company. The administrators in Scotland belong to the DPGBR primary permission list class, which allows them access to data for all departments that are in the U.K.
Human Resources checks to see if any future or current data rows for either employment record number (0 and 1) match the departmental access that is available to primary permission list classes for the HR staff in the France and U.K. headquarters. A match exists for both primary permission list classes, so users in both classes have access to Yves’s job data for both employment records:
Employment Record |
Department |
DPFRA |
DPGBR |
0 |
13000 |
Access |
Access |
1 |
21300 |
Access |
Access |
Step 2: Second Assignment - Consecutive
In 1998, Yves completes his assignment in Edinburgh and begins another temporary assignment in Sydney, Company KAB/Department 12000. HR administrators indicate that his temporary assignment in Scotland is over, which causes the data row that contains data on this assignment (in employment record 1) to become history because it’s no longer current. Thus, when Yves’s assignment to Sydney takes effect, the users that are in the DPGBR primary permission list class don’t have access to Yves’s data.
The HR administrators that are in Sydney belong to the primary permission list class DPAUS, which gives them access to data for all departments in Australia.
When Yves begins his new assignment in Sydney, the assignment data uses employment record 1, the same number that is used for his assignment in Edinburgh. Because the data row that contains information about Sydney is current, the system now permits users in the DPAUS primary permission list class to access Yves's employee data:
Employment Record |
Department |
DPGBR |
DPAUS |
0 |
13000 |
No Access |
Access |
1 |
12000 |
No Access |
Access |
The system continues to permit French users to access all of Yves’s historical and current employee data.
The security process for multiple, concurrent host assignments is nearly the same as it is with one host. The system checks all current data rows for employment record numbers to determine which users and classes should have access to employee data, but there are more employment records and users.
Step 1: Second Assignment - Concurrent
Suppose that Yves’s story is changed. While he is working on temporary assignment in Sydney, he gets a second, concurrent temporary assignment in Singapore, department 15000. The HR administrators who are operating in the Singapore office belong to the DPSGP primary permission list class, which allows them access to data for all departments that are in Singapore.
Because Yves has concurrent assignments, the Singapore assignment uses employment record 2. Now, three primary permission list classes need access to his employee data: HR administrators in France, Australia, and Singapore.
The system checks to see if any future or current data rows in the three employment record numbers (0, 1, and 2) match the departmental access that is available to all three primary permission list classes. A match exists in all cases, so Yves's job data is accessible to users that are in the three classes:
Employment Record |
Department |
DPFRA |
DPAUS |
DPSGP |
0 |
13000 |
Access |
Access |
Access |
1 |
12000 |
Access |
Access |
Access |
2 |
15000 |
Access |
Access |
Access |
Step 2: First Assignment Completed
In 2000, Yves completes his assignment in Singapore but continues to work on a temporary assignment that is in Sydney.
HR administrators indicate that his temporary assignment in Singapore is over. However, because the current row in Yves’s employment record, 2, still reflects a Singapore department, the users who are in Singapore can continue to access Yves's data. Thus, the system permits French, Australian, and Singaporean users access to all of Yves's historical and current employee data:
Employment Record |
Department |
DPFRA |
DPAUS |
DPSGP |
0 |
13000 |
Access |
Access |
Access |
1 |
12000 |
Access |
Access |
Access |
2 |
15000 |
Access |
Access |
Access |
Singaporean users continue to have access to Yves's information until another data row is inserted in employment record 2 and another department is selected. At that point, the data row that contains the Singapore department becomes a history row, so they no longer have access.
When an employee goes from a temporary assignment to permanent status, the system automatically determines which of the primary permission list classes should continue to have access.
Step 1: Second Assignment Completed
In 2001, Yves completes his temporary assignment in Sydney and transfers back to the French headquarters.
HR administrators indicate that his temporary assignment in Sydney is over. However, as with the Singaporean, the Australian users continue to have access to Yves's data because the current row in Yves's employment record 1 still reflects an Australian department:
Employment Record |
Department |
DPFRA |
DPAUS |
DPSGP |
0 |
13000 |
Access |
Access |
Access |
1 |
12000 |
Access |
Access |
Access |
2 |
15000 |
Access |
Access |
Access |
The system continues to permit French, Australian, and Singaporean users to access all of Yves's historical and current employee data.
Step 2: Permanent Transfer
In 2003, Yves’s managers decide that things run better in Sydney when Yves is on assignment there, so they transfer him back to Sydney, but this time permanently. This means that Yves’s home data now belongs in Sydney.
Using the Job Data pages, administrators transfer Yves back permanently for employment record 0, which is where his permanent (home) data is stored. Because this causes the data row that contains his French department to become a history row, the French users no longer have access to Yves’s data:
Employment Record |
Department |
DPFRA |
DPAUS |
DPSGP |
0 |
13000 |
No Access |
Access |
Access |
1 |
12000 |
No Access |
Access |
Access |
2 |
15000 |
No Access |
Access |
Access |
Employment records 1 and 2 contain data about temporary assignments that Yves went on in the past, with the current data rows still reflecting departments that are in Australia and Singapore. Although they are inactive data rows, they are still current rows, not history. Thus, Australian users have access to Yves's department because the department in both employment records is Australia.
Singapore administrators continue to have access because employment record 2 still contains a current row with an Australian office. These users have access until another data row is inserted in employment record 2 and another department is selected. At that point, the data row that contains the Australian department becomes a history row, so they no longer have access to Yves’s information.
Note. If you use global and local country functionality with PeopleSoft Enterprise Human Resources: Administer Workforce, then address additional security considerations.
To set up and configure global assignments, use the Assignment Type Table (ASSGN_TYPE_TABLE), Travel Type Table (TRAVEL_TYPE_TABLE), Earnings (EARNINGS_TABLE1), and Deductions (DEDUCTION_TABLE1) components.
This section discusses how to create new types of employee assignments.
Page Name |
Object Name |
Navigation |
Usage |
ASSGN_TYPE_TABLE |
Set Up HRMS, Product Related, Workforce Administration, Global Assignments, Assignment Type Table |
Create new types of employee assignments. |
Access the Assignment Type Table page.
(GER) Defining German Assignment Types
When entering assignment types for Germany, select from these options:
Type |
Description |
A01 |
Assignment In-Country. |
A02 |
Assignment Expat DBA taxfree. |
A03 |
Assignment Expat DBA taxable. |
A04 |
Assignment Expat ATE taxfree. |
A05 |
Assignment Expat ATE taxable. |
D01 |
Business Related Travel In-Country. |
D02 |
Business Related Travel Out-of-Country. |
D03 |
Assembly Assignment DBA taxable |
This section discusses how to classify types of company-paid travel.
Page Name |
Object Name |
Navigation |
Usage |
TRAVEL_TYPE_TABLE |
Set Up HRMS, Product Related, Workforce Administration, Global Assignments, Travel Type Table |
Classify types of company-paid travel. Use the codes that you set up here to make travel arrangements for employees and their dependents in the Company Paid Travel page. |
Access the Travel Type Table page.
Effective Date |
Enter the date the travel type becomes effective. |
Status |
Select a status for the travel type. Available options: Active or Inactive |
Description |
Enter a descriptive label for the travel type you are defining. |
Home Leave |
Select to indicate that a worker is going on leave to his or her home (permanent) location. If you select Home Leave, the system automatically disables the fields in the To section on the Company Paid Travel page when this travel type is used. |
This section provides an overview of assignment deductions and earnings and discusses how to:
Add deduction codes and classification information.
Define tax treatments.
Add earnings codes.
Employees on global assignments often are entitled to supplemental earnings, such as cost-of-living adjustments and hardship premiums. You might also take additional deductions from the employee’s paycheck because of estimated taxes.
Enter earnings and deductions as they relate to home and host assignment data. For example, an employee might receive a cost-of-living adjustment that is paid for by the host location and a hardship premium that the home location absorbs. Enter these components in multiple currencies; the system automatically calculates the equivalent amounts in the home currency.
To identify recurring payments or isolated incidents of supplemental earnings or deductions, track compensation data by employee and payment instruction type. PeopleSoft includes two types of payment instructions: global compensation and one-time payments. These are sufficient for most compensation that relates to global assignments.
If the organization is not using PeopleSoft Enterprise Payroll for North America and you want to track assignment compensation, set up deduction, tax, and earnings information on the Earnings and Deductions components.
You can track assignment compensation on the Assignment Compensation component.
See Adding Deduction Codes and Classification Information.
Note. Use the Payroll for North America Earnings and Deductions tables (Set Up HRMS, Product Related, North American Payroll) to
set up earnings and deductions if you use Payroll for North America. The global assignments tables do not contain enough information
to substitute for the payroll tables.
Make the tables in the Global Assignments menu display-only to ensure that all updates take place by using the pages in North
American Payroll.
See Also
Defining Earnings Codes and Earnings Programs
Adding Deduction Codes and Classification Information
Tracking Assignment Compensation and Currency Fluctuation
Page Name |
Object Name |
Navigation |
Usage |
DEDUCTION_TABLE1 |
Set Up HRMS, Product Related, Workforce Administration, Global Assignments, Deductions |
Add deduction codes and classification information. |
|
DEDUCTION_TABLE2 |
Click the Deduction Table2 tab on the Deduction Table page. |
Define tax treatments for assignment deductions. |
|
EARNINGS_TABLE1 |
Set Up HRMS, Product Related, Workforce Administration, Global Assignments, Earnings |
Add earnings codes for global assignments. |
Access the Deduction Table page.
For deduction codes for global assignments, enter a Plan Type of 00.
Warning! Enter information in these fields only: Effective Date, Description, and Short Description. Otherwise, the system assumes that the code that you define here is for payroll purposes when you enter the code on other assignment pages. You could also receive an error message if you don’t fill in all of the required fields that are on the other pages for the table that is in the North American Payroll or Payroll Interface menus, depending on the payroll system that you use.
Access the Deduction Table2 page.
Deduction Classification |
Select a deduction type. |
Canadian Sales Tax |
Select the type that is required in Canada. |
Access the Earnings Table page.
Warning! Enter information in these fields only: Effective Date, Description, and Short Description. Otherwise, the system assumes that the code that you define here is for payroll purposes when you enter the code on other assignment pages. You could also get an error message because you don’t fill in all of the required fields that are on the other pages for the table that is in the North American Payroll or Payroll Interface menus, depending on the payroll system that you use.
To set up additional education data, use the Majors (MAJOR_TABLE), School/Program Table (INTL_SCHPGM_TABLE), and School/Program Contact Table (INTL_CONTACT_TABLE) components.
This section provides an overview of assignment education data and discusses how to:
Enter school and orientation program information.
Track contacts for schools and programs.
The organization may provide financial assistance to employees who are on global assignments, such as school tuition for children and language and orientation classes for adults. PeopleSoft Enterprise Human Resources helps determine any educational assistance to which employees are entitled and tracks multiple institutions.
If the organization offers education allowances for employees or dependents, set up information about the schools and programs that are available to the employees and their dependents.
Setting Up Majors
Use the Majors page if you need to set up a new major for global assignments.
See PeopleSoft Enterprise Human Resources 8.9 PeopleBook: Manage Competencies.
Page Name |
Object Name |
Navigation |
Usage |
INTL_SCHPGM_TABLE |
Set Up HRMS, Product Related, Workforce Administration, Global Assignments, Define Education Related Info, School/Program Table |
Enter school and program information. |
|
INTL_CONTACT_TABLE |
Set Up HRMS, Product Related, Workforce Administration, Global Assignments, Define Education Related Info, School/Program Contact Table |
Track contacts for schools and programs. Note. You must already have set up information for international schools and programs in the School/Program table. |
|
MAJOR_TABLE |
Set Up HRMS, Product Related, Workforce Administration, Global Assignments, Define Education Related Info, Majors |
Include areas of study most commonly associated with school degrees or certificates. |
Access the School/Program Table page.
Sch/Pgm Typ (school or program type) |
Select a school or program type. Options are: Language School, Private School, Public School, Other, and Local Customs. |
Int/Ext (internal or external) |
Select Internal to the organization or External. |
See Also
Setting Up Local Country Functionality
Access the School/Program Contact Table page.
Contact # (contact number) |
Enter the contact number of the school or program. For example, enter the headmistress of a school as the first contact, and the assistant headmistress as the second contact. |
Contact Phone Numbers |
Select the phone type and enter the phone number for the contact. Add new data rows to list more than one contact phone number for each contact. |