What are the general tasks required to implement Payroll?

[Former Member]

Hi All,

Does anyone of you have any document which will guide the process of Implenting the Payroll in SAP?

Also, any kind of Blue Print for the project will be helpful.

If so pls let me know.

Thanks

TSS

[Former Member · Accepted solution]

hai..

The steps are identical for Attendances also.

The Configuration for Payroll:

The Configuration of payroll needs to be done at different places in IMG. They can be divided into 6 main steps for ease of handling.

They are

o Configuring Payroll area

o Basic Pay

o Wage types

o Pay roll organization

o infotypes

o Payroll run

1.Configuration of Payroll Area

o Create Payroll Area

o Create Control record

o Default Payroll Area.

2.Configuration of Basic Pay:

o Define EE subgroup grouping for PCR and CAP.

o Check Payscale Type .

o Check Payscale Area.

o Check Assignment of Payscale structure to Enterprise Structure.

o Modify feature TARIF.

o Create Payscale groups and levels

o Define pay scale salary ranges

3.Configuration of Wage types:

o Create a Basic pay wage type

o Check the wage type group “Basic Pay”

o Check entry permissibility per infotype

o Check Wage type characteristics

o Define Employee subgroup grouping for primary wage type

o Define Personnel Subarea grouping for primary wage type

o Define Wage type permissibility per PS and ESG.

o Define Enterprise structure for wage type models.

o Revise Default wage types

o Define valuation of base wage types.

4.Configuration of Pay roll Organisation:

o View the period modifiers

o View the existing Date modifiers

o Generate the Pay roll periods

5.Configuration of Infotypes

o Create the necessary infotypes through PA 40/PA30.

6.Payroll Run:

SAP Easy Access->Human Resources->Payroll-> Americas->USA->Payroll-> Simulation.

PATHS

Assigning Personnel Calculation Rules to Employee subgroups

IMG: Personnel Management  Personnel Administration  Payroll Data  Basic Pay  Define EE Subgroup Grouping for PCR and Coll.Agrmt Prov.

Defining the Collective Agreement Provision for Employee Subgroups

IMG: Personnel Management  Personnel Administration  Payroll Data  Basic Pay  Define EE Subgroup Grouping for PCR and Coll.Agrmt Prov.

Defining Pay Scale Types and Areas

IMG: Personnel Management  Personnel Administration  Payroll Data  Basic Pay  Check Pay Scale Type

IMG: Personnel Management  Personnel Administration  Payroll Data  Basic Pay  Check Pay Scale Area

Assigning Pay Scale Types and Areas to Personnel Subareas

IMG: Personnel Management  Personnel Administration  Payroll Data  Basic Pay  Check Assignment of Pay Scale Structure to Enterprise Structure.

Defining Pay Scale Groups and Levels

IMG: Personnel Management  Personnel Administration  Payroll Data  Basic Pay  Revise Pay Scale Groups and Levels

TARIF Feature

IMG: Personnel Management  Personnel Administration  Payroll Data  Basic Pay  Determine Default for Pay Scale Data

Wage Type Copy Function

IMG: Personnel Management  Personnel Administration  Payroll Data  Basic Pay  Wage Types  Create Wage Type Catalog

Checking the Wage Type Group for Basic Pay

IMG: Personnel Management  Personnel Administration  Payroll Data  Basic Pay  Wage Types  Check Wage Type Group ‘Basic Pay’

Checking the Permissibility of Wage Types

IMG: Personnel Management  Personnel Administration  Payroll Data  Basic Pay  Wage Types  Check Wage Type Catalog  Check Entry Permissibility per Infotype

Checking Wage Type Characteristics

IMG: Personnel Management  Personnel Administration  Payroll Data  Basic Pay  Wage Types  Check Wage Type Characteristics

Employee Subgroup Groupings for Primary Wage Types

IMG: Personnel Management  Personnel Administration  Payroll Data  Basic Pay  Wage Types  Employee Subgroups for Primary Wage Type

Personnel Subarea Groupings for Primary Wage Types

IMG: Personnel Management  Personnel Administration  Payroll Data  Basic Pay  Wage Types  Personnel Subareas for Primary Wage Type

Wage Type Permissibility per Personnel Subarea and Employee Subgroup

IMG: Personnel Management  Personnel Administration  Payroll Data  Basic Pay  Wage Types  Define Wage Type Permissibility for each PS and ESG

Defining Default Values for Wage Types and the Wage Type Model

IMG: Personnel Management  Personnel Administration  Payroll Data  Basic Pay  Wage Types  Revise Default Wage Types

IMG: Personnel Management  Personnel Administration  Payroll Data  Basic Pay  Wage Types  Enterprise Structure for Wage Type Model

Defining Valuation of Base Wage Types

IMG: Personnel Management  Personnel Administration  Payroll Data  Basic Pay  Wage Types  Define Valuation of Base Wage Types

Assigning Bonus Wage Types (Module Name TARIF, VARIANT B-D) to Pay Scale Groups and Levels

IMG: Personnel Management  Personnel Administration  Payroll Data  Basic Pay  Pay Scale Groups and Levels

Defining Annual Salaries (if this is relevant for your country)

IMG: Personnel Management  Personnel Administration  Payroll Data  Basic Pay  Define Annual Salary

The above steps will be usefull till Gross Part of the payroll

[Former Member · Accepted solution]

Thanks Ram...Your answer was really helpful.

i really appreciate. Pls let me know if you have any documention for the Project Planning and implementation.

Points rewared

Thanks

Shyam

[Former Member · Accepted solution]

Hai...

ASAP Methodology

Accelerated SAP

Accelerators are used for implementation in order to speed up the implementation.

A step by step phased implementation where the project deliverables can be measured in each phase.

1. Project preparation

a) Define project goals & objectives

What you are expecting from the project & what u want your SAP system to perform?

b) Define scope of the project

1) What modules u want to implement?

2) Within the modules what are the functionalities you want to implement?

3) Whether you want all modules to implement at a time (or) phased implementation [Big Bong (or) phased]?

4) Whether it is a phased (or) Big Bong will be mentioned in EASD (Enterprise Area Scope Document)?

An EASD enables to define which modules are in scope and which functionally in each module is in scope.

5) Formation of project organization and steering committee.

6) Sizing of the development servers (not mandatory).

7) Training the SAP personnel (if required).

😎 Establishing the SAP standards such as documentation standards, reporting standards, communication between the team members.

9) OSS access to the consultant.

10) Establish procedure that every member of the project team should follow to use management request.

11) Organize a kick – off meeting where you invite all project team members and members of the steering committee and declare all convey the goals and objectives and scope of the project.

12) Concept check tool is provided by SAP which can be used for performing quality checks on the deliverables for the phase1 and phase2.

The tool offers a series of questions which changes dynamically to sec on the answers you give. The tool will generate a report which can be used for optimizing and system performance.

Outcome

Tools

1) EASD, can be generated using the project estimator. This EASD is linked to Q & A data base which is used in phase2 to determine the detailed process and development requirement.

EASD----

---

Q & A data base

Phase1 phase2

2) Concept check list

2. Business blue print

A business blue print is a document that specifies all the business process requirements within the scope of the project.

1) AS – IS study.

2) Re – engineering techniques are applied (not mandatory, only if required).

3) TO – BE process requirements are identified and documented. These requirements are what you want your R/3 system to perform.

4) A last chance to make slight changes in the project scope.

5) Conducting and organizing work shops for gathering information and suggestions to frame the requirements.

TOOL – Q & A data base.

6) A Q & A data base tool is used, which is generated from EASD scope document. Depending on the scope the Q & A data base with change. Example: If you do not have PS module you do not have PS module related questions

a) A Q & A data base also contains ISSUE data base which can be logged and resolved from project management.

b) A Q & A data base also can be used to generate reports on all information that you log into data base

c) Reports can be generated based on the answers the users give and the solutions given by the consultants for the possible requirements.

d) You can generate answer reports which contain only answers that have been entered in data base.

e) You can generate business print when the consultants enter their analysis of the requirements.

7) AS – IS study is done and analyzed if any gap is found which is not supported in SAP. Gap analysis is done (not mandatory).

😎 If the initial development of system was not set up that it has to set up in the phase with necessary user logins.

9) Technical architecture has to set up.

(Data base – Application – Presentation)

10) Transport request management has to set up.

11) Release strategy.

12) Remote connection to SAP has to set up.

[A tool where we can access in to user server (production)].

13) The desktops should be should be connected to LAN with SAP login.

14) One of the important deliverable of this phase is to develop the training strategy of the team.

3. Realization

This phase is sub divided into:

1) Base line configuration

2) Final configuration

3) Unit testing

4) Integration testing

1) Base line configuration, all critical and regular processes are configured in SAP R/3 system. Once this is configured it offers a foundation for the forthcoming final configuration phase. In base line configuration – 80% would be completed. Those business requirements that are not considered in baseline configuration must be defined final configuration. Any problems/errors that are found in base line configuration must be faced at final configuration.

2) Establishment of production system.

3) Unit and integration testing.

4) Stress test and tests on any interfaces.

5) Technical team need to work on system authorizations and end users for the production system.

6) Start preparing the end user documentation.

7) End user training and desktops duly configured.

4. Final preparation

1) Finalize entire system configuration and environment, including tests, user training, and productive system setup from the functional and technical point of view.

2) Need to develop a cut over plan – include both manual conversion and conversions through programs.

3) Provide end user training to end users with the training material that you developed in previous phase.

4) End users should have hands on experience on SAP R/3 system so that they can work from day one after Go – live.

5) Setup of 1 and 2 level help desk i.e., if not solved by level1 then g\it goes to level2.

5) Finally start converting data from your legacy system to the SAP R/3. You can use conversion programs (or) manual conversion.

5. Go – live & support

1) Go productive with production system (SAP R/3).

2) Dismantle the existing system.

3) Regular transactions in SAP R/3 system.

4) End users may require more support in the initial phase. Hence more support be given.

Continuous change to improve the capability of production system.

Might be Helpfull..

[Former Member]

Hi

Please go through the documentation links provided in the below thread.

If this helps, pl do reward.

Thanks

Narasimha