DAY 1:

SAP Landscape :

Arrangement of server

DEV : Development server is also known as sand box client. It is the server where consultants do new configuration
write new program as per the business requirement, it has 3 clients

A} Sand box : Sand box client is the place where all the system design work taken place.

B} Customizing client : After configuration in the sand box if everything is good then they recreate the same
configuration in client.

TEST : This client is used for unit testing in some projects integration testing also in the client

QAS : It is the same we test the new customization or changes …etc

PRD : Production client is also known as golden client it has the server where real time business operations taken
place.

Request flow from Transport request DEV->QAS->PRD

Ways of login to SAP:

1. SAP logon ( SAPGUI Program)

2. SAP Web based.

SAP ERP Versions ECC 6.0, 7.0, EHP 8…etc

SAP T.code Commands:

/n : Close current session

/o : Keep the current page & go to another page

/Nex : Exit without any prompt

/Nend : Exit after display prompt

Transaction code (T.code) : Shotcut to an application it can be accessible in sap command prompt.

PA40 : Personnel Actions

PA30 : Maintain the Master Data

PA20 : Display of Master Data

 PA41 : Correct the Hire/ Leaving date

PA42 : Fast Entry of Actions

PA70 : Fast entry Payroll Data

PA71 : Fast entry of Time Data

PU00 : Delete Personnel Number

PU01 : Delete the Payroll Results

PU03 : Change the Payroll Status

LSMW : Legacy system migration work bench

SPRO : SAP Program Reference Object

Types Of Data in SAP HR

1. Configuration Data (SPRO ) : Organization specific data

Ex: Company
2. Master Data (PA30 ): Data which can be maintained in the records
Ex: EE Details ( Name, Address, DOB…etc)
3. Transactional Data ( Infotypes Master Data ) : Day to day transactional data , the data which changes
frequently.

DAY 2:
Types of Projects in SAP HR

SAP Implementation Project.

SAP Support Project.

SAP Roll-Out Project.

SAP Enhancement Project.

SAP Upgradation Project.

SAP Migration Project.

SAP Acquisition/Merger Project.

IMPLEMENTATION PROJECT:

IMPLEMENTATION means implementing Business Processes. After purchasing the SAP (ERP), Companies do Study
the Methodologies and various process and case studies.

In Implementation, Several People works on various functional modules listed below (can be considered as SAP BI
ARCHITECTS, DESIGNERS, SAP CONSULTANTS)

Every Module has its Importance and is linked to other module in one or many ways (SAP is all Tables and Table
Relations)

1. 1. Function Modules: Ex: FI CO Consultant, SD Consultant etc.

2. 2. Technical Module ABAP Programmer.
3. 3. Basis & security Administration
4. 4. Others

Function Modules:

 Financial Accounting (FI)

 Financial Supply Chain Management (FSCM)
 Controlling (CO)
 Materials Management (MM)
 Sales and Distribution (SD)
 Logistics Execution (LE)
 Production Planning (PP)
 Quality Management (QM)
 Plant Maintenance (PM)
 Project System (PS)
 Human Resources (HR)

Technical Module:

 SAP Technical (ABAP Programmers)

Basis & Security Consultants:

OTHERS

1. BIW (BI or BW) – Business Information Warehouse

2. CRM – Customer Relationship Management
3. IDES – International Demonstration and Education System
4. KW – Knowledge Warehouse
5. MDM – Master Data Management

You can easily find the different SAP Types in diagram as follows:
Companies follow 5 Step/Stages ASAP Methodology to Implement a Project.

A. Project Preparation
B. Business Blueprint
C. Realization
D. Final Preparation
E. Go-Live & Support

ROLLOUT PROJECT:

Rollout exactly means, expanding the business after Implementation.

An Organization which is started in one country, expanding their services to other countries, follows Rollout.

Exactly in Rollout we can find that the Organization works accordingly to Government there in other countries like

Taxation: As the taxation will be different in other countries. Ex: Some allowances, Income Tax, etc.

Master Data: As the new employees join the organization

So many modifications should be done according to Country.

So Rollout is little tough but effective after completion.

SUPPORT PROJECT: (AMS )

After implementation of SAP modules customer/business need assistance of consultants in their day to day
business operations using SAP software. The end user raise their concerns, issues, errors etc through a ticket
handling tool. A ticket handing tool is must for a support project, it helps to track the status of tickets. Basically
there is no phases in it. Roles of a consultant Accept /Acknowledge the tickets, analysis the issue, document
it ,solve, provide solutions to client, Get confirmation from the user & close the ticket.

Change request and service request is the main roles in support projects.

*We use Remedy/service Now/TMS as a Ticketing tool for tracking the issues/tickets/calls*

SAP UPGRADE PROJECT:

SAP Upgrade means upgrading the software with a latest version which has got more advantages (i.e. Bugs fixed
compared to previous version)

Example: Company migrating from older versions like 4.5,4.6b, 4.6c to ECC 5.0 / ECC 6.0 . SAP HR EHP3 to SAP HR
EHP 5

SAP Testing

SAP Testing Phases/Methodology

Three phases in SAP methodology are

1.Test Preparation:
1) Identification of business process
2) Development of manual test cases and automated cases.
3) Creation of test plans & review
4) Set up of test system(Dev, Quality, Pre production system)
5) Creation of test data.

2.Test execution Phase:

1) Test execution using test tools such as Solution Manager, HP Quality Center ,HP ALM.
2) Test status reporting & defect handling.

3.Test Evaluation Phase:

1) Detailed assessment of all test plans
2) Defect Analysis
3) Documentation of the testing process

Types Of Testing In a Sap HR Implementation Project

Sap recommends 3 system Landscapes

-DEV
-QAS
-PRE PRD-Optional
-PRD

Following are types of SAP R/3 testing

1. Development Unit Testing

2. Configuration testing
3. Interface Testing
4. Batch Testing
5. Security Testing
6. Regression Testing
7. Integration Testing
8. Parallel Testing
9. Performance and Load Testing
10. User Acceptance Testing

1.Development Unit Testing

This is done by developer .Unit test is executed in development system. This tests alone pieces of functionality. For
example PA40 Actions,PA30 Maintain master data ,Infotypes, reports .

2.Configuration testing

To check if the configuration is correct . This testing is to make sure that all the business requirements are
properly configured and verified.

3. Interface Testing

It includes the testing of the SAP interface program, testing of middleware settings, data transfer requirements
between the system.
Ex: If you have two development systems SAP ECC & Non SAP system . Run SAP interface program to sent data to
Non SAP system & can use it.
In interface testing system triggering file to other system ,data transfer is successful, and the receiver is able to
accept & process the data received from SAP.

4. Batch Testing
Batch test includes testing of all batch scheduled jobs .It also test the performance of batch schedules jobs .Tivoli
Workload scheduler(TWS) is used to schedule the jobs of multiple platforms.

5. Security Testing
Security testing ensures the SAP security roles and authorization roles provided based on the requirements. Test
IDs will be created of different job roles and used to both confirm what a user can do and what a user cannot do.
The tester will perform both Positive and Negative testing of the of job roles that are assigned to user test ids.

6.Regression Testing
Regression testing ensures that new introduced /configured changes will not adversely affect by the existing
system. Test will test all existing T codes ,report s etc to make sure that nothing is impacted.

7. Integration Testing
In a multiple plat form environment integration testing is mandatory .All integrated areas need to test by a tester.
It is testing of SAP transactions (for example hire-to- termination- to rehire) , data conversion ,security roles and
workflow.

8.Parallel Testing
During parallel testing all the existing data in the legacy system will transfer to SAP system & perform same
process in both systems. A successful Parallel test shows identical results when both the legacy system and new
system results are compared.
Tester will run the programs / transaction repeatedly in both system , resolve issues with the help of other team if
any issues, continue perform tests till gets the identical results in both.
Example : Parallel payroll process. Run payrolls in SAP & legacy system for 2-3 months & analyze the payroll
results

9.Performance and Load Testing

Performance testing is to find out the performance of various programs/reports . The objective is to validate the
reaction time of the transactions under different conditions.
If there a program to upload files contains some records .During performance test , the tester will note down the
time taken to complete the process & compare with previous results.

10.User Acceptance Testing(UAT)

User Acceptance testing is conducted in by a group of business end users to validate that the new developed SAP
system meets all requirements. During User acceptance testing the system end users separately execute test cases
& find out the results are as expected. The test team will guide the UAT team in their testing activities.
UAT will ensure that the system is acceptable from the users perspective, performing as per the requirement & if
the users are satisfied they provide a sign off.

SAP HR Infotypes :

Refer in excel sheet Infotypes list

DAY 3:

Configuration of Enterprise structure

1. Create Company code

2. Create Personnel Area
3. Create Personnel Subareas for each personnel area
4. Assign Company code and Country grouping to each personnel area

Personnel Structure

1. Creation of EE Groups
2. Creation of EE Subgroups
3. Assign the EE group to EE subgroup

Company code Created by the FICO consultant

Personnel Area : Personnel Area is sub category of company code mostly based on the geographical location. It is
4-digit alphanumeric code.
EX: BA42 or 1000

Personnel Subarea is further classification of personnel area, it is 4-digit alphanumeric code

Ex : HI42 or 1001

Personnel Structure:

It is a two-level (EG & ESG) categorization of employee based on employment type ( Permanent, Contract,
Trainee ) and based on payment frequency ( Monthly, weekly, Bi-weekly ) and working frequency ( Full time, Part
time), Nature of work ( Managers, Engineers, workers)

1. Employee Group (EG) : It is represented by single digit character (C), Permanent, Contract, Trainee

2. Employee Subgroup (ESG): It is represented by a 2-digit alphanumeric code , (Monthly, hourly)

DAY4:

1. Assign the personnel areas to company code and EE groups to EE subgroups

2. Maintain the EE Group Attributes
3. Personnel Number Ranges
4. Features & Technical Field Names
5. User Parameters

Personnel Number Ranges or EE ID / PERNR : ( Max 8 digit Numeric ID)

1. Internal ID : Automatically generated by the system when EE is hired

2. External ID : Manually give the number

T.Code : PA04

P1 70000000 79999999 P
Z1 60000000 69999999 Q
Z3 50000000 59999999 R

Features : It is a Max 5 digit character it has T.Code PE03

Feature Purpose :

1. Used to default the values in infotypes fields

2. Specify the conditions and validations
3. Control the display of infotype screens these are used in screen modifications

Number Ranges feature : NUMKR

Technical Field Names:

BUKRS : Company Code

WERKS : Personnel Area
BTRTL : Personnel subarea
MOLGA : Country grouping
LAND1 : Country Key
PERSG : EE Group
PERSK : EE Subgroup
PERNR : Number ranges EE ID
BEGDA : Start date
ENDDA : End date

User Parameters used to maintain the default values in certain fields, It has T.Code : SU3
Frequently used parameters in HR,

MOL : Country Grouping 40 or 10

USG : User Grouping 40 or 10 or Custom Numeric NN
KOS : Cost Center
PER : Personnel No
PON : Org Unit
CVR : Time sheet Profile
ABK : Payroll Area

DAY 5:

1. Infotypes list and their time constraints

2. IT0001 Configuration

Cost Center : It is a 10 digit character code, it has T.code KS01.... KOSTL is Technical name. It is a cost accounting
object. ( Configuration is from FICO)

Business Area : It is used for Finance reporting this is further classification of company code. it is a cost accounting
object. ( Configuration is from FICO)

Contract : This field through we can know employee belongs to which union or association , third party apart from
company.

IT0001 Features to Default the value in Organization Assignment

NUMKR : Default the Number Ranges

PLOGI : Integration b/w OM & PA
ABKRS : Default the Payroll Area
VDSK1 : Default the Organization key
PINCH : For Administrator Groups

DAY 06:

1. Payroll Area Configuration

2. Control Record Configuration

DAY 07:

IT0001, Organizational Plan

Org unit, Position, Job ( PA without OM )
Organization Key
IT0001, Administrator Groups
Org unit: Organizational units are units of your company that perform a function. These units can be departments,
groups or project teams, for

Example: You create the organizational structure of your company by relating organizational units to one another.
The organizational structure is the basis for the creation of an organizational plan.

Job: Job is not a concrete, it is General holding various task to perform.(Eg: Manager, GM).

Position: Position is concrete and specific which are occupied by Persons. (Eg: Manager – Hr, GM – Hr).

Tables:

Org unit: V_T527X

Job: T513, V_T513S

Position: T528B, V_T528T

Organization Key: Organizational key is used for setting up additional authorizations to HR administrators who
maintain employee master data. It is a 14 character to be made up of the fields from IT0001 to be defaulted using
feature VDSK1. Authorization object P_ORGIN

There are two types of Authorizations:

1. General Authorizations
 Transaction codes
 Tables
 Programs
 Infotypes

2. Structural Authorizations
 Making restriction on the data based on Org structure, Personnel Structure, Enterprise
structure.
Admin Groups:

Administrator will responsible for maintain the master data for assigned employees.

DAY 08 :

IT0006 Overview
IT0009 Configuration

DAY 09 & 10:

PA Infotypes Overview & Configuration

IT0016, IT0019, IT0021, IT0022, IT0023, IT0032, IT0041, IT0128, IT0105, IT0185
IT0016 Syntax:

001: Hours
010: Days
011: Weeks
012: Months
030: Percentage

001/012: Continued Pay

060/010: Sickpay Supplement period
003/012: Probationary period
R2: Notice Period for EE
1E: EE Notice Period T547T
T2: Contract Type T547V
IC: Limited ( 1 Month, 60Days, 3Months)

ER Notice Period: R2- ER- 3Months

EE Notice Period: R3- EE- 3Months

CONTR Feature Return Value: 001/012-060/010-006/012-R2-R3-T2

DAY 11:

Personnel Actions:

Personnel Actions are the events of an employee's employment history within the organization beginning from
hiring an employee to termination of the employee. Each of these events need specific information to be captured.
This is achieved by grouping together infotypes called as infogroup which appear one after another in sequence to
capture/change information in the infotypes whenever the personnel action is executed. Personnel Actions are
executed by transaction PA40.

Example of Actions:

1.Hiring

2.Promition

3.Change Organizational Unit/Position

4.Change of Pay

4.Transfer

6.Seperation/Termination

7.Retirement ............etc.
Configuration of Personnel Actions:

1. Create Infogroup

2. Assign Infotypes to infogroup with maintenance type (Copy, Modify, Delete)

3. Create Action type & Assign infogroup and maintain default status

4. Create reasons for action type

5. Display Action type in action menu (PA40) depending on user group (India-40, USA-10)

User Group is used to group the users for going to use same set of infotypes for action

1. Select user-dependent tick box if the user group is used for the info group
2. Specify a reference user group that should be used if no user group is defined in the parameters of the system
user

DAY 12:

Dynamic Actions:

Dynamic Actions are performed automatically by the system depending on the certain conditions are in table
V_T588Z , if we are maintaining one infotype has an effect of another infotype, the system automatically display
the second infotype record for processing

Dynamic actions configuration you need to go to SM30->V_T588Z ,

You have to specify the infotype number for which you need to trigger the dynamic action inside the dynamic
action there are various columns. conditions can be based on infotype, subtype and field level.

Example:

1.IT0002 personnel data whenever the married field is updated once you save the infotype in next moment IT0021
family members spouse details will trigger.

2. IT0016 Contract elements is saved the next IT0019 will trigger

Dynamic Action Customization as per client requirement:

Employees who are working in manufacturing unit should go for Eye vision test mandatory for every 02 months ..
record maintain in IT0028 is save the next IT0019 should trigger as reminder type as vision test.

Base Infotype is IT0028 Subtype 0022

Target Infotype IT0019 Subtype R1

DAY 13:

Screen Modifications

Screen Header Modifications

DAY 14:

Procedure for Adhoc Query :

1. Set Query Area

2. Creating a user group

3. Creating Infoset

4. Create Query & Execute

T.code: SQ01,SQ02,SQ03

Set Query Area

There are two types of queries, standard area which is client dependent and Global area which is client
independent

In Dev we would be using Global area, it requires transport request to create any object in global area means no
separate process for transport

If any changes is required in any component in future it can be done in development client and then moved along
the landscape (DEV->QAS->PRD)

Ensure all the queries under the infoset created in global area

Logical Data bases:

PA: PNP, PNPCE

OM: PCH

For Infotypes data dump, PA infotypes start with PANNNN, OM infotypes HRPNNNN

Go to T.code: SE16N-> PA0001, HRP1000

EE data report T.code: PAR1, PAR2, PAAH

DAY 15:

1. Legacy System Migration Workbench (LSMW)

The Legacy System Migration Workbench (LSMW) is a tool to transfer data from legacy systems into an R/3
System. LSMW supports a step-by-step procedure, if one step is executed and saved then next step automatically
follows. Apart from creation of project/ subproject/ object and recording, there are 14 basic steps included in
LSMW

DAY 16:

1. LSMW Export and Import from one Server to another Server

2. Creation Of Transport Request

3. Additional Actions

Types of Transport Requests:

A) Workbench Request: Workbench requests are cross-client. Changes done in one client are
automatically reflected in all other clients.
B) Customizing Request: Customizing requests are client specific. The changes will not be reflected in other
clients. For e. g a change done in ECC Dev system will not be reflected in other clients in the same ECC Dev
system. We have to do a client copy using T-code SCC1. You can see the client number next to this type of request.

Transport Request Move from DEV->TES->QAS

->PRD (TR Will move by Basis team)

T.Code : SE09 - Transport Organizer

Actions & Additional actions

As Hiring action is Time Constraint “1”, another actions like Transfer, Termination, and Promotion Not Possible on
the same Day for the same “PERNR”.
However there will be instances like Transfer, Termination, and Promotion for the employee on the joining date.
This is possible through info type “0302”.Howver we don’t maintain this infotype manually. The additional actions
will be recorded in “0302”.Through “additional actions” we can run the two actions on the same date. For example
we can transfer the employee or promote the employee on the same day of hiring.

We can't perform more than one action on the same day, unless we change employment Status of an employee".
1) Is the above statement true ?
2) What is the relationship between Infotype 0000 (Actions) & 0302 (Additional Actions) ?
3) How to access the infotype 0302 (Additional Actions)?
1) Is the above statement true ?
Yes, it is true. But, SAP has provided with the option of additional actions to enable performing multiple actions on
the same day.

2) What is the relationship between Infotype 0000 (Actions) & 0302 (Additional Actions) ?

Action infotype captures the first personnel action run on the day. If additional actions is enabled than the
following action run on the same day is captured in IT 0302 additional actions.

3) How to access the infotype 0302 (Additional Actions)?

In Actions Infotype 0000 below you can see window box with Addition action detail and T.Code: PA30

PA10 also can be view 0302

DAY 17:

Infotype Menu Configuration