Migrating Data from SAP S∕4HANA to Employee Central

Objectives

After completing this lesson, you will be able to:
  • Migrate data to Employee Central
  • Migrate pay calendar to Employee Central

Work Schedule Migration to Employee Central

Here's how you can migrate work schedules from the SAP S∕4HANA system to Employee Central.

Set up work schedule rules in your SAP S∕4HANA system.

Set up a proxy to your Employee Central instance.

Make sure that the Upsert Data from SAP ERP or SAP S4HANA to SAP SuccessFactors Employee Central Using the OData API integration flow from the SAP ERP or SAP S/4HANA Integration with SAP SuccessFactors Employee Central: Employee and Organizational Data integration package is set up when you use SAP Cloud Integration as the middleware.

To migrate work schedule rules, use the Transfer Work Schedule Rules from ERP to Employee Central (ECTIM_TRANSFER_WSR) transaction in your SAP S∕4HANA system. This transaction calls the ECTIM_TRANSFER_WSR_TO_EC program. You can use this program to make work schedules available from Job Information of employees in SAP S/4HANA. For example, when the master data is maintained in Employee Central and replicated to SAP S∕4HANA because you use SAP S∕4HANA as the Time Management system.

Note

What's called Work Schedule in Employee Central is the same as Work Schedule Rule in the SAP S∕4HANA system.

The program transfers information from the following Customizing tables in the SAP S∕4HANA system to Employee Central:

  • Work Schedule Rules (T508A, T508S)

  • Period Work Schedules (T551A)

  • Daily Work Schedule (T550A, T550S)

  • Break Schedules (T550P)

Here's an overview of the tables in SAP S∕4HANA:

Work Schedule Rules: Tables in SAP S∕4HANA

Procedure

The program uses the generic OData upsert middleware process to transfer the data to Employee Central. Make the following settings on the selection screen of the program:

  1. Specify your Employee Central instance.

    The Employee Central instance defines which language versions the program is to transfer when creating the external names of the WorkSchedule and WorkScheduleDayModel objects in Employee Central. In the SAP S∕4HANA system, the descriptions to be transferred are stored in the Text Table for Work Schedule Rules (T508S) and Daily Work Schedule Texts (T550S) tables. The program transfers all languages that are mapped for the Employee Central instance in Customizing for Personnel Management, under Integration with SuccessFactors Employee Central → Business Integration Builder → Organizational Data Integration → Map Languages from Employee Central and ERP. If the Text Table for Work Schedule Rules  (T508S) and Daily Work Schedule Texts (T550S) tables may not contain any entries for the work schedule rules to be transferred. If so, the program transfers the external code of the work schedule rule to the External Name field, but only for the default Employee Central language.

  2. Select the work schedule rules to be transferred, using one of the following options:

    • Specify various selection criteria, such as the rule’s employee subgroup grouping or the public holiday calendar assigned to the rule.

    • Select a transport request. For example, a request that you've used to transport your work schedule rules from your test system to your productive system.

    • Select all work schedule rules that are currently stored with the status Failed in the Inventory of Replicated Foundation Objects (ECPAO_FO_INVT) table and are assigned to the Employee Central instance you entered previously.

  3. Define how the program deals with day work schedule variants.

    Some work schedule rules use daily work schedules that have multiple day variants assigned. Employee Central cannot handle such variants. That’s why you must decide how the program handles such work schedule rules:

    • You can transfer all work schedule rules, ignoring day variants. That is, use the default variant also for those work schedule rules that have a specific day variant assigned (meaning, for which the Daily Work Schedule Variant (VARIA) field in the Daily Work Schedule (T550A) table is not empty).

    • You can omit work schedule rules that use multiple daily work schedule variants.

  4. Define how the program deals with paid work breaks.

    Some work schedule rules use daily work schedules that have paid work breaks assigned. Employee Central cannot handle paid breaks. That’s why you must decide how the program is to handle such work schedule rules:

    • You can transfer only unpaid work breaks when creating the WorkScheduleDayModelSegment objects in Employee Central for the work schedule rules.

    • You can completely omit work schedule rules that use daily work schedules with breaks that have paid periods (meaning, for which the Paid Break Period (PDBEZ) field in the Break Schedules (T550P) table has an entry other than 0).

  5. Select the time recording variant.

    The time recording variant of a work schedule rule (duration or clock time) must be the same as for all work schedule day models assigned to the work schedule. The following options are available for choosing the time recording variant:

    • Use the time recording variant Duration for all work schedules and work schedule day models.

    • Use the time recording variant Clock Time for all work schedules and work schedule day models, but omit work schedules that have cross-midnight shifts.

    • Use the time recording variant Clock Time for all work schedules and work schedule day models, but use Duration for work schedules that have cross-midnight shifts.

    • Use the time recording variant Clock Time for all work schedules.

      Note

      This option is available from the SP31 package. The Cross midnight work schedules (schedules where the working time starts on one day and ends the next day) are now supported in SAP SuccessFactors Employee Central. This option then uses clock time for all work schedules and supports sending the cross-midnight work schedules to EC.

    • Use the option Transfer Day Work Schedule's Flextime as 'Flextime Bandwidth' segment so that the field Planned working time in the Flextime are mapped to the Flextime Bandwidth category and the Normal working time in the Flextime are mapped to the Scheduled working time.

      Note

      This option is applicable only for Clock Time.

      Handling of day schedules with Flextime across midnight:

      • Case 1: Planned working time and Normal working time are not cross-midnight shift: Then the report updates above segments to Flextime bandwidth and Scheduled working time segments respectively for the Work Schedule Day Model.

      • Case 2: Planned working time and Normal working time are both across midnight: Then the report updates to Flextime bandwidth and Scheduled working time segments respectively for the Work Schedule Day Model.

      • Case 3: Planned working time is not cross-midnight shift but Normal working time is cross-midnight shift: This is an invalid case as Planned working time would always be greater than Normal Working time as per ERP configurations.

      • Case 4: Planned working time is cross-midnight shift but Normal working time is not cross-midnight shift: EC does not allow creation of such flex time bandwidths in the day work schedule. Hence, the report skips the work schedules that have at least one such day work schedule.

  6. Define whether the program is to carry out a test run first.

    You can carry out a test run of the program to output the result to the SAP List Viewer, without triggering the actual transfer to Employee Central. SAP List Viewer shows the data in a tree view. You can check what would be transferred (and what wouldn’t). If you clear the Test Mode checkbox, the program triggers the actual upsert to Employee Central using the default logical port defined for data replication from SAP S∕4HANA to Employee Central. The result screen shows statistical information such as how many work schedule rules were upserted, had errors, or were skipped.

Pay Calendar Information Export from SAP S/4HANA

Before you migrate Pay Calendar to Employee Central, you must export the payroll calendar dates to a CSV file.

Context

To export the payroll calendar, run the Export Payroll Calendar Dates (PAOCF_EC_PAY_CALENDAR_INFO) report.

Procedure

  1. Go to transaction SE38.
  2. Enter program: PAOCF_EC_PAY_CALENDAR_INFO.
  3. On the Selection Criteria screen:

    • Enter the Country Grouping.

    • Choose the Payroll Area in ERP.

    • Enter the From Payroll Year.

    • Enter the To Payroll Year.

  4. On the Value Mapping Details screen:

    • Choose the EC Instance from the F4 help for the EC Instance ID with which the value mapping entity is associated.

    • Choose the Value Mapping Entity that must be used for fetching the EC paygroup code values for the given ERP payroll areas.

      Note

      Value mapping entity must be of the Generic Object Key type. If no value mapping entity name is specified, then payroll area mappings are not considered.

  5. On the Download Options screen:
    • If you select the Use Server Path option, you can later transfer the data from the application server location to a local drive.

      Note

      The default option to download the report file is Application Server.

    • If you select the Use Local Drive Path option, you must specify where the CSV file is to be stored.

    Pay Calendar report supports downloading the pay calendar information into a CSV file either to an application server or local drive. The download log file shows all the success, error, and warning messages. It also includes the number of files that were downloaded and from where the file is downloaded from.

    Note

    The files might contain sensitive data. Additional authorization is performed to check if the user has the right to download the CSV file. Only specific authorized users must be allowed for this operation. The downloads that are triggered by a user to the application server or local server are logged through the table ECPAO_OBJ_DWNLD along with the timestamp details.

    Further, it is your responsibility for the retention and deletion of these files from the application server or local machine.

    The below authorizations are required to be able to download the CSV files:
    Authorization ObjectAuthorization FieldAuthorization Value
    S_DATASET(for application server)ACTVT34
    S_DATASET(for application server)FILENAME/usr/*
    S_DATASET(for application server)PROGRAM

    CL_ECPAO_FILE_ON_SERVER*

    PAOCF_EC_PAY_CALENDAR_INFO

    S_TABU_NAMACTVT02
    S_TABU_NAMTABLEECPAO_OBJ_DWNLD
  6. Execute the report to export the Pay Calendar information to a CSV file.

Results

The dates are exported to a CSV file and looks similar to the following screenshot.

Screenshot of a Pay Calendar CSV File.

Pay Calendar Information Import to Employee Central

You can import the Pay Calendar information to Employee Central.

Procedure

  1. Go to the Admin Center. In the Tools search field, enter Import and Export Data.
  2. Choose Import Data.
  3. Choose Pay Calendar.
  4. Choose Incremental Load.Screenshot of the Import and Export Data screen. The CSV File tab is selected.
  5. To browse for the csv file, select Choose File.
  6. Choose Import.

    You can check and validate the pay calendar in the Admin Center under Manage Data.

    Screenshot of the Manage Data screen. A sample Pay Calendar is shown.

Employee Global Assignment in SAP S∕4HANA

You can migrate an employee having global assignment in SAP S∕4HANA system.

In SAP S∕4HANA, you must store information about an employee's global assignment in the following infotypes:

  • To determine which is the host and which is the home assignment, use the Details on Global Assignment (0710) infotype. This infotype must be maintained for the infoporter tool to identify the global assignment employment type. Otherwise, the HR process is identified incorrectly.
  • To determine which personnel number is used to send biographical and personal information to Employee Central, use the Main Personnel Assignment (0712) infotype with the SuccessFactors (SFSF) subtype.

    Note

    If the planned end date in the 0710 Infotype is greater than the actual termination date, then the system considers the termination date of an employee from the Infotype 0000–Actions. However, if the planned end date in the 0710 Infotype is less than the actual termination date, then the system considers only the Infotype 0710–Planned End Date, as this is a data issue. Hence, you must extend the end date of the employee in Infotype 0710.

The data from both the host and the home assignments is migrated to Employee Central. In Employee Central, the employee's biographical and personal information is taken from the personnel number that you have marked as the main personnel assignment in SAP S∕4HANA.

If you've defined a cutoff date for data replication, this can affect the start date of the global assignment: If the cutoff date is later than the actual start date of the global assignment, the cutoff date is used. If the cutoff date is between the start date and the end date of the host assignment, the Job Information record for the host assignment is transferred to Employee Central using the PSEUDO_ADDGA event reason for the Add Global Assignment event.

Note

If there are more than two multiple contracts for an employee (starting after the earliest transfer date) involving two PERNR's, then this scenario is not supported. This can include the scenario involving global assignment. For example: There is a global assignment from PERNR 1 to PERNR 2 (which is terminated when the assignment period ends.) Then, there is an international transfer to the second country/region from PERNR 1 to PERNR 2 (which is rehired). In this case, if the global assignment happens before the earliest transfer date, then this would be ignored and only the international transfer from country/region one to country/region two will be considered.

  • When there is a global assignment from PERNR 1 to PERNR 2, the personal information (infotype 0002), global information (0002 or its secondary infotypes), and address details (infotype 0006) from both the PERNR's are replicated based on the earliest transfer date. In this case, you must maintain infotype 0712 (main personnel assignment) for the 2nd PERNR and maintain the home PERNR as the leading PERNR during the global assignment period. Based on this, the host address is created in EC, with address type host for the host PERNR along with the home address, which is mapped with the home PERNR.

    Note

    From Employee Central, you must make sure that the host address type is available in the Employee Central picklist.

  • For global assignment user, if the permanent residence address is maintained for both the assignments (home & host), then the home PERNR holds the home address type and the host PERNR holds the host address type in the Employee Central system.

    Note

    The Emp_users_sys_id field must be added to the perAddress enitity with the configurations: Enabled = True, Visibility = view & allow import = Yes in the Employee Central system. This field must be included in the view cluster (VC_ECPAO_MAP) field mapping for address entity.

  • The e-mail address and phone number of an employee are extracted from the employee who is active. If both the PERNR's are active, the system migrates the host PERNR's e-mail address and phone number.

    If there is no data available for the host PERNR, then the system gets the information from the other PERNR mapped with the same person. For global assignment, the system tries to send the host PERNR's e-mail address and phone number, based on the infotype 0712.

  • The biographical information of an employee is always extracted from the home PERNR only irrespective of the employment status.

  • For the National ID information portlet, the system extracts the assignment data.

Note

If you have not maintained the infotype 0712 (main personnel assignment), then the host address type for the host PERNR would not be created. Instead, a home subtype is created for both home and host PERNR. Similarly for biographical, an e-mail address,and phone number of an employee are extracted only from the home PERNR, even if it is inactive.

When a global assignment configuration object is enabled in Employee Central to create global assignment events like Away on Global Assignment and Back from Global Assignment, the following points must be considered:

  • Equivalent custom actions for the previously mentioned events must be explicitly created for the pernrs in the ERP system.

  • Additional value mapping for the events must be done. For example, custom Action for Away on Global Assignment must be mapped to the event AGA(Away on global Assignment) on EC.

As the upsert is a full purge, if the previously mentioned actions are not performed, the automatic events created in Employee Central are deleted if:

  • A change from ERP is sent to home assignment.
  • The replication from ERP is triggered again.

Log in to track your progress & complete quizzes

Learning

SAP FacebookSAP YoutubeSAP LinkedIn