White Paper on INLK

Introduction:

Most of the legacy data comes in Excel and the payroll consultants need to
consolidate all the data into the SAP template with the relevant wage type values
against each month for each employee.

I am sure many of you would have spent enough days in consolidating excel
sheets and updating the legacy results in the SAP.

For beginners, please read this link to know how INLK works, before you proceed.
http://help.sap.com/saphelp_47x200/helpdata/en/5a/f57415558f4e52925b05aa5
7dad09d/content.htm

Any one who has undergone this exercise will definitely appreciate this paper.

Problem Statement: Midyear go-live with SAP Payroll, updating of legacy

payroll results into the SAP provided excel templates, this is one of the most
challenging and tire some task to carry out in any mid year go-live Payroll
Implementations, be it a new implementation or migration. Best solution
recommended by many is to go live at the F.Y beginning but not many
organisations can afford to do so.

Making the INLK ease

This white paper provides solutions to the above stated problem.

The solution what I am presenting is proven and helps you to complete the
exercise in no time. In my case it helped me to complete the INLK exercise in 2
days for 2000 users with 9 months data. i.e. April to December. This solution not
just saves your time but also reduces the project cost and helps to speed up the
implementation time especially it’s a boon in fixed cost projects.

Here I am talking about the process where the consolidation and transferring of
legacy payroll details into the SAP excel templates to update T558B and T558C
tables.

Me being the De facto project lead for that project, I was desperately trying to
pull in more people into my project to do this tedious task.

As the organisation had no enough skilled people on board to work on this

activity and HR team is not ready to share the sensitive payroll details among
their team. So I requested the client project Manager for a developer (not ABAP)
to write some coding and do some magic to update all the values into the SAP
excel templates. The guys who came to write a program has no idea about what
SAP or a wage type is.

The programmer has come up with an excellent small application written in

Visual Basic, and the size of the application is less than 200 KB. What all he did
was to read the legacy excel data and updated the different wage type values
against employee number in the SAP templates.

Author: Srikanth Bikumandla Page 1 11/18/2009

White Paper on INLK

How this application works.

Run the application, which looks like an MS-Access screen and here’s the magic
begins.

• Drag and drop the legacy file into the application. (Where all the source
files are kept in a common location, so that the target files created in the
same location)

• Click Convert. (Less than 10 seconds)

• Two new files are created with names as T558B.xls and T558C.xls

• Upload these via the standard program (HINUULK0)

• Run the INLK Schema to update payroll cluster.

Surprisingly the data was so accurate and random check was more than enough
to validate.

What are the pre requisites?

• Legacy employee numbers are changed to SAP employee numbers. Or use

external number range to use the same employee number. In our case we
have to change it as part of project change management.

• Add one row in the legacy excel sheet to identify which wage type/text is
represented by what value in SAP.

E.g.: Let’s see the records of some employees with legacy data.

/3F1 /3F2 /3E1 /3E2

Emp.N Ee. Er Ee Er
Month
o PF PF ESI ESI

08/20X
1091 700 700 100 200
X

08/20X
1405 900 900 100 200
X

08/20X
1502 800 800 100 200
X

Author: Srikanth Bikumandla Page 2 11/18/2009