Management of Global Employees

/wp-content/uploads/2012/12/pic1_167571.jpg

Management of Global Employees

In order to enable the Management of Global employment module in ECC 6.0, SAP Global setting require the concurrent employment switch “CCURE GLEMP” to be enabled. This is the Master data switch which enables you to activate the parts of the Concurrent Employment component (PA-CE) that are required for the Management of Global Employees component (PA-GE) (such as the decoupled infotype framework).

/wp-content/uploads/2012/12/pic1_167571.jpg

*** Imp Note:

Before implementing global employment, it’s advisable to raise an OSS note with SAP .SAP will send a questionnaire which needs to be filled in .SAP will then give a feedback regarding GME implementation.

Before activating the system switch (CCURE GLEMP) and after receiving an answer from SAP, the following master switch needs to be activated by a technical consultant.

Transaction SE24,

Object Type: CL_HRCE_MASTERSWITCHES

Double click on the CHECK_RELEASED method (This will require an access key)

When you have the key un-comment the line “ce_is_released = true”

You activate the Management of Global Employees component by typing an X in the Value abbreviation field.

By doing so, you allow users to access the relevant Management of Global Employment infotypes.

The relevant infotypes are:

n  0702 : Documents

n  0703 : Documents on Dependants

n  0704 : Information on Dependants

n  0705 : Information on Checklists

n  0706 : Compensation Package Offer

n  0707 : Activation Information

n  0708 : Details on Global Commuting

n  0710 : Details on Global Assignment

n  0715 : Status of Global Assignment

Please note that The CCURE GLEMP switch enables you to activate Management of Global Employeeseven if Concurrent Employment is switched off (CCURE MAINS switch).

l  Concurrent Employment and Management of Global Employees have the technical and conceptual solution in common.

l  The Decoupled Infotype Framework allows the ability to have the user interface separated from the business logic, so that it becomes easier to build new transactions at infotype level, for example to create a new transaction similar to the transaction PA30, without having to deal with the dynpro logic. It will support the creation of new web applications, as well.  The principle of data sharing will be supported thanks to the new infotype framework.

l  The New Logical Database enables reporting based on the person or on the personnel assignment.

l  The Concurrent Employment Model is a conceptual solution for CE and MGE using the available tools on HR It is also the basis of the conceptual solution for Management of Global Employees.

l  For release R/3 Enterprise the component Management of Global Employees and Payroll for the Global Employee support you in all the processes involved in sending an employee to work abroad.

PIC2.JPG

When the switch is enabled, as a consequence the new Infotype framework is activated. This in turn will reflect in changes in Infotype Screens (Standard infotypes such as IT 0002, 0006, 0077 will be called from MP0002_CE and MP0006_CE etc), new fields will be enabled and the Global Employment set of infotypes will be activated.  Also a new set of validation rules will be applied to the above mentioned infotypes fields as part of the CE switch activation.

Any new generation applications will leverage the business logic and field characteristics of the decoupled infotype framework.  Therefore, Employee Self-Service and HCM Processes and Forms will function in the same way as ECC to preserve data integrity.

As a result, the current configuration for actions and Infotypes will need to be thoroughly tested and changed to accommodate the new settings. Tables, Infosets and logical database changes (PNP vs PNPCE) will need to considered and tested.  Certain reports will now need to be run using the concurrent employment logical database PNPCE instead of PNP.  As well, any custom reports should use the PNPCE logical database to be able to access the employees across assignments.

To enable the Payroll for Global Employment, the CCURE GLOPY switch will need to be enabled. This however is optional and not mandatory for Management of Global Employment to work. By activating this switch the payroll schema for global employment will be activated.  If you need to run payroll in either host or home country, Payroll for Global Employment is required.

Example:  A UK employee is on assignment in the US.  The employee is paid from the US payroll, but the social insurance payments are paid from the UK payroll.  The UK payroll will send the social insurance payments to the US payroll for processing.

If you plan to pay active people out of both countries in ECC, the Concurrent Employment functionality is required.  These employees will have separate active personnel numbers linked by the person ID using infotype 0709.  They also will be linked by the org management Central Person object (CP).

The person ID can be configured in the following ways:

  1. First personnel number assigned
  2. Central person number
  3. Personnel ID number (eg. Social Security Number)
  4. Customer defined by customization in a BAdI

The following types of actions are used for Management of Global Employees:

  1. Planning:  A new personnel number will be created in the new country.  The new personnel number will be inactive to avoid being put in headcounts.  Once planning is complete, the Global Assignment Status infotype 0715 must be set to “To Be Activated” for activation to take place.
  2. Host Activation:  Once the assignment starts, a new action will be executed in the new personnel number.  The employee will be active in the new country.
  3. Home Activation (Withdrawn):  After the host record has been activated, the Home Activation can occur.  If the employee’s home record should not be in headcounts and payroll, the home record would be withdrawn using this action.
  4. Home Activation (Active):  After the host record has been activated, the Home Activation can occur.  If the employee’s home record should be in headcounts and payroll, the home record would be set to active using this action.
  5. Other non-MGE actions can be used subsequent to these being executed.

When Management of Global Employees is activated, PA30 will change to show the additional assignments a person has.

PIC4.JPG

You can view all the assignments in an overview screen

You will also be able to view the detail on the assignments in a side-by-side comparison

pic5.JPG

Advantages of Management of Global Employees

  1. Allows tracking of employees who go on temporary or permanent assignment to other countries
  2. Automatically maintains the person ID and makes it visible to the user in PA30.
  3. Visibility of the planning and activation phases of permanent and temporary global assignments.
  4. You can maintain compensation packages specific to MGE.
  5. You can track documents required for MGE.
  6. Infotypes will be updated in the same way in PA30/40 and new generation applications like ESS and HCM Processes and Forms.
  7. Data updated on one personnel assignment can automatically be copied to the other assignment.  For example if a permanent residence changes for an employee that moved from Germany to the US, both records will be kept in sync.
  8. Payroll can handle payments from one country to another.
  9. Compensation packages related to MGE can be maintained and tracked.  Policies are maintained in the system to facilitate a global process.
  10. Checklists can be maintained to guide HR relocation.
  11. Dependents accompanying the employee can be tracked.
  12. Offer letters to the employee can be printed based on the compensation package offer and other infotypes in the system.

Disadvantages of Management of Global Employees

  1. Added complexity of infotype sharing configuration.
  2. Additional payroll configuration and complexity if payments need to be made from onecountry to the other.
  3. Certain infotypes that use the decoupled infotype framework have more stringent logic than the old dynpro-based infotypes.
  4. Any old user exits must be ported over the BAdIs that support the decoupled infotype framework.

Was this article helpful?

Related Articles

Leave A Comment?

You must be logged in to post a comment.