Online Tutorials & Training Materials | STechies.com
Register Login

INLK Legacy Data Transfer Interview Questions and Answers

|| || 0

INLK Legacy Data Transfer Interview Questions and Answers
Stechies

 INLK Legacy Data Transfer - FAQ

Q: What is INLK and Who should use it?

A: INLK is a payroll schema which can be used to transfer payroll results from non-SAP system to SAP payroll system. This schema is useful for customers who plan to go live in the middle of the financial year. This schema is used to transfer the values needed for the annual reports and tax computation from legacy system. The schema assumes that no prior payroll results exists for the employees in the SAP payroll system. The schema makes use of the data as created in the payroll accounts table T558B and T558C for transferring the payroll results.

Q: What is the aim of schema INLK?

A: The payroll schema INLK aims at facilitating the generation of annual reports and tax computations. During legacy upload, the schema assigs appropriate split indicators for the wage types entred through table T558C. The rules of the schema also try to evaluate approximate values for certain required wage types.

Q: Does the legacy transfer process support retro processing?

A: The earliest retrospective date for payments or deductions in legacy upload process is limited to the start date of the go-live period. Retro processing beyond the go-live period is not supported.

Q: Where to find the information?

Information regarding legacy data transfer process can be found at media centre in SAP service market place for India -  'service.sap.comhrin'. You can download the documents from this web site to access the updated versions.

Q: What utilities are provided for data uploading?

A: Report program 'HINUULK0' and excel template 'HR Template Payroll.xls' are provided to assist in handling data during legacy data transfer. The excel template has two sheets '558b' and '558c'. Data to be uploaded into the payroll accounts tables T558B and T558C have to be entred through the respective sheets of the template. The macro provided in the template enables you to save data as tab delimited local files 558B.txt  and 558C.txt on your system. The report program makes use of these files to upload the data into SAP system.

Q: What date format should be used while uploading data?

A: The utility program HINUULK0 has different versions existing in release 46B and release 46C. The following date formats have to
   be used while entering data through the excel template.

     Release      Date format
      46B             dd.mm.yyyy
      46C            yyyymmdd

Q: What reports are supported by legacy data transfer process?

A: The annual legal reports like Form16 , Form24 , Form12BA , Annual PF report - Form3A and Form6A , Annual Pension Report -
 Form7 and Form8 are supported. Monthly reports for the pre go-live periods are not supported.

Q: How to process loan data for pre go-live periods?

A: The loan data can be transferred for the legacy period using The payment type 'Transfer loan balance'. Please refer to the
   note 360011. Also refer to the SAP on-line help at the following path
   'Payroll->Payroll Other Countries->Deductions->Loans->

Company Loans' for additional information on loan infotype 0045. For the payroll run of the go-live period, to consider the perk values for all the loan types imported from legacy, you can have a wage type which has the consolidated perk value. The wage type characteristics of this wage type should be such that its gets cumulated into /127- Annual perk. You need to take care that this cumulation into /127 continues even in the subsequent payroll periods of the financial year.

Q: What schema customization are required?

A: Payroll schema INLK has rules which are defined for model wage types provided by SAP. These rules need to be redefined for customer specific wage types. To do this, copy the standard rule and modify it according to your requirements. Make a copy of the schema INLK in customer name range and substitute the standard rule with your rule. Given below are the list of rules which might have to be modified at customer end.

Rule Description
INKD Rule defined for TPD - model wage type MLIC
INK3 Rule defined for PF - standard wage types /3F1
and /3F2
INKA Rule defined for standard wage type /3F1
INKB Rule defined for standard wage type /3F3
INKC Rule defined for standard wage type /3F4
INKE Rule defined for CEA - model wage type M260
and M270
INKO Rule defined for CCO - model wage type M220
INKR Rule defined for HRA - model wage type M230

Q: Execution of payroll schema with driver program HINCALC0  resuls in error?

A: Ensure the following

1) The control records for the relevant payroll areas are
      created
2) The payroll periods for all relevant payroll areas are
      generated
3) The customization w.r.t to the wage type characteristics
      are present
4) Certain rules in the schema are based on model wage types
      provided by SAP. Verify that the rules are
      modified/redefined for customer specific wage types
5) The data entred in tables T558B and T558C are correct
6) That you are using the latest version of the schema INLK

Q: How to upload data for split periods?

A: There are two possibilities :

1) The legacy system provides data relevant for individual splits in the period
      Under such circumstances, its recommended that values
      entered in table T558C are as per the split. Use the date
      field of the table to assign the values to the repspective
      part periods. The following schema customization should be
      done in order to avoid any built in default proration.

          i) Comment the step for rule INK2 in the schema.
         ii) Comment the step for rule INKO in the schema.
        iii) Comment the step for rule INKQ in the schema.
        iv) Modify the rule INKR defined for *//114 as below

VarKey  NL T Operation Operation Operation Operation Operation
          D ADDWT *   TABLE IHRAVARGBACCOM
*
1          D VARGBMETRO
1 *          ELIMI *   RESET R   ADDWT /3R4AMT=S M230ADDWT /3R2
1 1          ELIMI *   RESET R  ADDWT /3R3AMT=S M230ADDWT /3R1

2) The legacy system doesn't provide you details of split, but provides only consolidated values for the period. Note that even under such circumstances, the statutory deductions like PF and profession tax etc..have to entered for the split values. The schema INLK will be able to prorate other relevant wage types. The values thus calculated are approximations.

Q: Housing exemption/perk in go-live period doesn't consider the pre go-live periods?

A: The schema INLK generates only relevant wage types during the legacy data transfer process. The wage types thus generated are based on the status of the infotype record while transferring the payroll results. Its mandatory that housing infotype record is available while transferring the legacy payroll results for the system to consider the exemption/perk in go-live periods.

Q: You are going for a Mid-year Go-Live. You have uploaded the data for the pre-go live periods using INLK schema making use of the data as the created in the payroll accounts table T558B,T558C.You find that payroll clusters have been correctly wagetypes /3F1, /3F2, /3F3, /3P1, /3E1 etc.
However, when you generate the statutory reports like Form 3A, 6A, 7 & 10, the reports does not display data for pre-go live periods.

A: The Statutory reports like Form 3A, 6A, 7 & 10 work based on the country-specific split indicators. The country-specific split indicators gets populated    ONLY if you maintain the  'Key date' in view Table T558C.

The Payroll Function TRANS (Transfer of wage types from T558C to IT) checks for this key date while generating the country-specific split indicators. Customers are recommended to set key date, re-run the payroll with INLK Payroll Schema and check for CNTR1.

 


Related Articles