SAP HR Interview Questions and Answers

Q1: What is SAP HR?

Ans: SAP HR records the data from the hiring an employee to its final termination in organization. It store the employee data such as designation, role, salary details, working shifts, address and so on

Q2: What is SAP HCM?

Ans: SAP HCM is an on-premises system that services HR functions such as compliance, payroll, personnel files and benefits administration. In December 2011, SAP announced its acquisition of Success Factors, signaling SAP's commitment to the cloud while maintaining its commitment to its HCM products.

Q3: Which are the sub-modules in SAP HR?

Ans:Following are the modules in SAP-HR —

• Recruitment -Personnel Administration
• Organization Management
• Personnel Development
• Training and Event Management
• Compensation Management
• Personnel Time Management
• Payroll
• MSS – Manager Self Service
• ESS – Employee Self Service

Q4: Describe the various structures in SAP – HR?

Ans: Structures are required to represent statutory, regional, and organizational conditions in an organization. Following are three structures in SAP HR.

• Enterprise Structure – gives Information about the location of work on an employee. It comprises of Client, Company Code, Personnel Area, and Personnel Sub-area
• Personnel Structure – gives information about the employees job function. It comprises of Employee Group and Employee Subgroup
• Organizational Structure – gives relations between employee and his corresponding departments or business unit. It comprises of organizational plan, which includes Job, position, organizational unit etc.

Q5: What is an Infotype?

Ans: Individual Information such as last name, first name, DOB etc is defined in data fields. Data fields are grouped into information units according to their content, these information units are called Infotypes. Infotypes have names and 4 digit keys.

For Ex. Infotype 0002 is for Personal Data, which stores Employees Full Name, Date of Birth, etc.

An Infotype can have a sub-type.

Infotypes are classified as follows

• 1000 – 1999 == OM related
• 2000 – 2999 == Time related
• 9000 and above Customer Specific

Q6: What Time Constraint 1 on an Infotype ?

Ans: Infotype with Time Constraint 1(TC 1) must be unique, i.e. only one valid record can exist for a given period. There can be no gaps between the records. When we add a new record to an Infotype with TC1, the system delimits the overlapping record on the key date and adds new record

Q7: How can you maintain information for an Infotype?

Ans: To maintain information in an Infotype you could use –

PA30 – Personal Administration Maintenance

PA40 – Personal Actions

Alternatively, Fast Entry Screen.

Q8: Which Personal Actions have you performed on an employee?

Hire

Ans:

• Change Organizational Unit/Position
• Change of Pay
• Transfer
• Terminate
• Retirement
• etc.

Q9: Where are payroll results stored?

Ans: Payroll results are store in PCL2 cluster, which can be accessed using the transaction pc_payresult

Q10: What is Matchcode W?

Ans: Match Code W provides a list of all personnel numbers in the selected payroll area that have been rejected by the payroll run because of incorrect data. This means that the payroll has not run for them successfully. Personnel numbers are also included in Matchcode W if personnel data is changed in the correction phase of the payroll run.

Q11: List the Time Related Infotypes that you have used?

Ans:

• 2001 – Absences
• 2002 – Attendances
• 2003 – Substitutions
• 2007- Time Quotas
• 0007- Personnel Work Schedule

Q12: How would record time in your SAP HR system?

Ans: We can record time using one of the following methods

• Online by time administrators
• Separate time recording systems
• Cross-Application Time Sheet (CATS)
• Employee Self-Service (ESS) applications
• Customer systems with an interface to the R/3 System

Q13: What is PROCESSING CLASS, where we do them and why?

Ans: Wage type characteristic that determines how processing is conducted during the payroll run.

Q14: What is EVALUTION PATH, where do we do it and why?

Ans: A chain of relationships between objects in a hierarchical structure. for eg. O-S-P(Organization->Position->Person).

Q15: What is INTERNAL PAYROLL PROCESS?

Ans: Payroll process(program) is run at a specific point in time, not only to calculate an employee’s basic remuneration but also any special payments, overtime payments or bonuses that must be effected for the period in question.

Q16: What is meant by payscale structure? How did you configure pay scale structure? (I said I created various payroll areas and defaulted them using the feature ABKRS. Seemed he was expecting more than this from me.)

Ans: Pay Scale Structure means creation of Payroll area , Pay scale type,area, group and levels with EmpSub group grouping for PCR & CAP’s.

Q17: How do you import pay scale data from non SAP to SAP? (Somebody told me that there’s a tool called LEGACY to transfer non SAP data to SAP. I said the same. Is it the same for payroll also? He wanted a clearer explanation of how I did it.

Ans: Yes you have to say from which transaction code you are transferring data from Non SAP in to sap.

Q18: What is meant by a schema? (I said I’m only aware that it is a set of rules which is copied and renamed, but never worked on that.)

Ans: No, you have to say him that schema is a set of instructions ( Programs )  modified as per requirements and its process is to collect the data as from all the defined instructions with sub schemas and PCR’s. As I was not authorised to work on them I know just the process of schemas only, (you should have said like this.)

Q19: How do you restrict the data to be entered in payroll area?

Ans: No, data is entered in a payroll area , but the employees are defined depending on their payscale structure. If you are restricting any data to be entered for pay strcs this is for indirectly for payroll area.

Q20: What is meant by authorization? Did you ever work on it?

Ans: Authorisations are the transactions given to the end users or the developers for only some areas to work, infotyopes, transaction codes, org units and others depending on the requirement of the client or the developing enterprise.