Escolar Documentos
Profissional Documentos
Cultura Documentos
R/3 System
Instructor
Guide
Level 3
Release 4.0
March 1998
(C) SAP AG
ISG.HR
1-1
Contents Page:
Hints on Preparing This Course......................................................................................................... 6
Daily Plan.....................................................................................................................7
Day One............................................................................................................................................. 8
Unit: Introduction........................................................................................................8
Topic: Welcome, introduction, organizational notes...........................................................................9
Topic: Aim of the course and training content.....................................................................................9
Topic: Integration model and contents of the course........................................................................10
ISG.HR
1-2
(C) SAP AG
ISG.HR
1-3
(C) SAP AG
ISG.HR
1-4
Course Details
As with any course, the content and duration will vary with the class size and expertise.
All courses should be started with introductions and setting expectations. There are always some students
who have not taken the suggested prerequisites.
Duration
3 days
Course Materials and other Materials (Training Manual)
Training Manual
Other Media - You can use all the available media (pinboards, flipcharts, and so on) for presenting and explaining the
material.
Country-Specific Units
This course is a country-specific course.
Course Instructor Profiles
The instructor should have a very good knowledge of HR master data. He/she should also have at least an
overview of Payroll Accounting as well as of the organizational structures in Organizational Management.
The instructor should also be familiar with the Customizing tools in the IMG. He/she should be able to
create projects and views using project management in the IMG and then be able to maintain and call these
up. He/she should also be familiar with view maintenance using the IMG. This involves the various
methods for creating new entries.
Level of Knowledge Required
Good knowledge of HR master data and infotypes
Able to create and maintain projects and views using project management in the IMG with the various
methods for creating new entries.
(C) SAP AG
ISG.HR
1-5
Creating projects simultaneously can lead to longer runtimes. This is also the case, when the Participants
create Personnel Subareas and Employee Subgroups.
Goals and Objectives
The training course HR305 shows the participants how to make settings for master data using a project they
have compiled themselves.
(C) SAP AG
ISG.HR
1-6
Course Schedule:
Daily Plan
Topics:
Welcome, introduction, organizational notes
Aim of the course and training content
Integration model and courses
1. Administrator in the CAB Company
2. Customizing
Aims of Customizing
IMG
Creating a project exercise
General view maintenance
Discussion of the exercise
3. Company structure
Overview
Levels: Client, company code, personnel area, personnel subarea
(C) SAP AG
ISG.HR
1-7
40 Minutes
Chapter 0: Introduction
Course overview
60 Minutes
Chapter 1:
Theory
45 Minutes
45 Minutes
Chapter 2:
Theory
25 Minutes
70 Minutes
Chapter 3:
Theory
15 Minutes
Additional notes:
Unit: Introduction
40 minutes
Topics:
Welcome, introduction, organizational notes
Aim of the course and training content
Integration model and courses
Logging on to the System
(C) SAP AG
ISG.HR
1-8
Introductions: the Instructor explaining her/his background and experience and then
each student doing the same. Have students fill out the Introduction Questionnaire
handout (at the end of this guide) which you will collect and use to make notes
during the class if students have questions or comments.
Have them state what other SAP classes they have taken and if they have taken the
prerequisites. It is also important to have them state their objectives for taking the
course which should be recorded on a flip-chart. After the introductions, review each
objective and cross off any objectives that are not appropriate to the content of the
class and tell the students why those items will not be covered. In addition, those
items that will be covered should be checked off to reinforce the content of the class.
This helps to adjust their expectations.
Course Objectives
The training course HR305 shows the participants how to make settings for master
data using a project they have compiled themselves.
It teaches them to use the customizing tools in the IMG.
(C) SAP AG
ISG.HR
1-9
ISG.HR
1-10
(C) SAP AG
ISG.HR
1-11
It gives them an overview about the HR course structure, the integration model and the content of the
course.
It is important to stimulate class participation by asking questions.
Hire an employee
ISG.HR
1-12
information relating to one rate of pay. This information is contained in wage types.
Wage types represent different types of earnings or deductions, such as standard pay,
holiday bonus, union dues or company car.
Do not get into discussion of country-specific infotypes! It will get the class
distracted from the main point.
A New Employees HR Master Data Sheet (1).
A New Employees HR Master Data Sheet (2).
Here are examples of some of the information that might be supplied on an
employee that then needs to get into the SAP system. The first page represents
information the employee might supply while the second page represents
information the hiring manager might supply.
Using a Personnel Action to Hire an Employee.
A personnel action (formerly known as Event) is a group of infotypes that are
presented in a particular order to record data on an employee. Complex activities
such as hiring, transfer or terminations require a series of infotypes to be completed.
Actions are used to ensure consistent information is being collected and stored on
employees when activities have taken place that affect their personnel data. Which
infotypes and in what order they are presented is defined in configuration by the user
based on their companys requirements. Show them the personnel action set-up in
the training system.
Activity:
Go into the system and show them the actions that have been defined in the training system.
Menu Path: Human resources Personnel management Administration [Personnel
actions]. Solicit their conversation as to why these activities might require an Action type.
ISG.HR
1-13
is important to point out to them that they should always try to use the IMG to make
any changes (versus accessing a table directly) because an entry in the IMG may
affect more than one table entry.
(C) SAP AG
ISG.HR
1-14
(C) SAP AG
ISG.HR
1-15
(C) SAP AG
ISG.HR
ISG.HR
easier.
The Implementation guide is in a hierarchy order. Under Personnel Management are
the steps and tables necessary to configure the Personnel Management module.
Under the Payroll Accounting, there are country-specific task lists.
Show how to get to the IMG. Have the students write down the menu path. First
show them what to look for, then how to find it.
The menu paths are in the Solutions.
Show the IMG:
Show them the connection between the Infotype and the IMG.
See the infotypes listed under Personnel Administration > Personal Data (list of
infotypes)
Show Payroll Data. Basic Pay, etc. See Payscale Groups and Levels.
Implementation Guide IMG
This diagram represents the four major icons in the IMG
1) The sheet of paper with the corner folded over. - Clicking on this icon will
display SAP documentation.
2) The red clock with the green check-mark - Clicking on this icon will display the
executable function for this task (take you to the table that can be configured).
3) the blue check-mark with the red pencil - Clicking on this icon will take you to
the change status screen where project status information can be recorded (such
as start/finished projected/actual dates, assigned resources, degree of processing,
and a status code.
4) The yellow quote bubble with the red pencil - allows for project documentation
(node maintenance) by recording notes with WinWord or SAPscript. These
same items are represented in the procedure model by the four boxes within each
work package that say Text - Act - Stat - Node. (Show them the work package
Establish Global Settings. Double click on the Act box and it will take you to
the IMG where Global settings are configured.)
Explain the types of documentation in the IMG
Explain the icons in detail. The Project IMG documentation is for storing technical
information for other project team members.
Explain what is under the Information menu > Title and IMG Info > Activity
Important and Critical Activities (do not rely on this. Use it as a guide to what should
be discussed by the implementation team)
Project IMG. System picks out what is important for your project.
After creating a Project IMG, show them that task groups other than those they
selected are created automatically in the IMG.
Implementation Guide /IMG
Every task in the project has been classified as to its activity importance and
criticality. Each task is either mandatory, optional or non-required. In addition each
task is also either critical or non-critical. The meanings are as follows: Mandatory:
activities which must be carried out (values that need to be changed such as
company code). Optional: delivered values will work and may not need to be
changed. Non-required: delivered values are very good and should not be changed
unless there has been a statutory change. Critical: activities which require special
(C) SAP AG
ISG.HR
care because an incorrect value may have very far-reaching consequences. Noncritical activities: have little or no consequences if not changed. Tasks can be
Mandatory, Optional or Non-required. If they are Mandatory they can also be
Critical or Non-critical. If they are Optional, they can also be Non-critical or
Critical. If they are Non-required/Non-critical, the delivered values should be used.
Making the following drawing gives a clearer picture:
Mandatory
Critical
Optional
Non-critical
Non-required
In additon each task can be displayed as to the country for which they are relevant.
Implementation Guides.
There are four different types of IMG:
SAP Reference IMG which is the Master that is delivered with the system and
contains all the steps for all modules for all countries.
From this IMG you create an Enterprise IMG which will contain all the modules
you have purchased from SAP and plan to implement now or in the near future.
From the Enterprise IMG you create multiple Project IMGs which can be as large
or small as you choose such as a project just for HR and another one just for FI.
Within each of these projects you can have different views, the standard being 1)
optional, 2) mandatory, 3) critical and 4) non-critical, or you can create any type of
view which makes sense to you such as only the tasks one person will be working
on.
Various areas are copied automatically during project generation, without you having to
choose them explicitly.
The implementation guide is valid systemwide, which means you can use it in any client.
There is only one Enterprise IMG for each system for all the different clients. Project IMGs
are also client-independent.
ISG.HR
Generate Project IMG Country and application components. Your country only.
Now the system selects all those things relevant to the chosen country.
New components. List appears. You decide what is relevant to your project IMG.
Mark all then deselect all. Select only the ones you want.
Highlight the connection between master data in the infotypes and Customizing
settings.
Show them an example of the link between Master Data and Customizing by calling
up an Infotype 0002 and showing the selection options for F.O.address and then
showing them the table setup in the IMG for Create forms of address. Make sure
they understand that within the same client more than one project may be accessing
the same tables, such as the FI project will have a task for creating company codes
and the HR project will have the same task but if both projects are being
implemented at the same time, only the FI team would create the company codes.
This is why it is important to assign responsibility for each task.
Customizing Tables: Key and Function Fields.
In a view entry, the items which are considered the key fields will be shaded. When
you select an entry and click on the copy icon, the complete record is displayed for
you to make changes to, the key fields are not blank and you need to be aware of
which fields are considered keys and be sure to replace new values in those fields
before you save your entry or you will receive an error message. Function fields
define the entries and may be the same for more than one set of key fields.
Customizing Tables: Create-Copy
When working in the IMG, there are two ways to make entries within tables. The
first would be selecting the create function in which all entry field are presented with
blank values. The second would be selecting the copy function by first selecting an
entry that already exists and then clicking on the copy iconthis will present all the
values that exist on the entry that is being copied. As explained on the previous slide,
key fields will need to be changed in order for the system to accept the new entry.
(C) SAP AG
ISG.HR
Show going from infotype 2 to the IMG save area to where Forms of address are
configured
First view
Then create. When you overwrite an entry in a key field (gray) the system creates a
new entry.
When you overwrite an entry in a function field (white) you just change the
description.
Show error message that appears when you create a new entry with the same number
as an existing key field. Create Prof (professor) with key field 1 and you will get
an error message, then change it to key field 7 which is unique (therefore no error
message).
(C) SAP AG
ISG.HR
Show how an error message saying that there is missing data leads you to specify
a project number (where you enter your project IMG number) and then takes you to
the relevant part of the IMG. You cant use this functionality in a productive system,
because you cannot configure in a productive system. If this entry is not in your
Project IMG, it will tell you.
Customizing Settings from the Application (2).
And this slide is showing you that even if a field already has valid entries established
in configuration, by pressing F5, you can still jump directly to the IMG to configure
additional information.
Also Right mouse button click jumps you to the right part of the IMG.
The next slide is showing you that even if a field already has valid entries
established in configuration, by pressing F5, you can still jump directly to the IMG
to configure additional information. Show by using the example of basic pay
(infotype 0008) how existing Customizing settings can be enhanced. Go into the list
of pay scale groups that have been possible up to now, press the right mouse button
or F5 and show how you are guided by the system to the correct place in the project
IMG.
Additional Information about Instances and the Transporting System
We also have a customizing workbench tool called the Transport System that helps
manage the movement of information (customization/table changes) from one
version or client to another.
Instances
Develop
Test
Clients:
Clients:
000
Production
Clients:
000
001
001
001
801 (Dev)
801
801
copy
802 (Test)
802
802
803 (Quality)
803
803
transport
An instance is a complete install of the R/3 system (above is a Develop, Test and
Production instance), these could be located on three different pieces of hardware or
all on the same machine. You may have as few as two instances and as many as you
want, however be aware that your contract with SAP normally calls for a limit of
three instances and any more than that would require contract negotiations with SAP.
Within each instance are different clients (the highest level in SAP, remember you
cannot even log onto the system without a client number). You would have one client
just for development, another test, another for training and finally one for
production. You would configure your tables in development, copy the development
client to test, conduct various test scenarios, perhaps go back to development and
make additional changes, then recopy this information down to test. When this
(C) SAP AG
ISG.HR
process had been repeated over and over to where things looked good, development
would be copied down to training and production. At this point test, training and
production would be transported to the Test environment (instance) and stress testing
and User Acceptance testing would be conducted. At some point in this cycle, the
transport system would be turned on and any changes to configuration would be
recorded and tracked. If there were any changes to configuration to be made, it
would be done in development and recopied and transported to be re-tested. When
everything was signed-off, the final transport would be made into production. The
reason for three instances would be to have tested the process of transporting from
one instance to another prior to making the transport for production. When
configuration from one client is sent to another client this is called client copy but
when information is moved from one instance to another instance this is called a
transport. There are some tables which are Client-Independent; hence, they will
affect all clients within an instance. Example: status types, selection fields,
resources, and note types used when creating a project.
Exercise for Buying a Bicycle Manufacturing Company
Approximate Duration: 20 minutes
The participants create their own project in Customizing using the specified attributes. They
practice how to call up this project and navigate in it.
Longer response times can occur during this exercise because several projects are being
generated at the same time.
Be sure to point out to them that when they created a project consisting just of HR
components, the system was smart enough to extract all the other components that would be
necessary to make HR work. I.E. such as a legal set of books from FI. Also ask if anyone
verified that a shared folder was set up automatically when they created their project.
Go over the business scenarios with them and remind them if they get stuck, they
can look at the solutions for the menu paths.
Solution for Unit: Buying a Bicycle Manufacturing Company
Approximate Duration: 15 minutes
Walk them through the solution, getting them to comment on the activity importance
and the three different categories.
Summarize what they have learned in the unit.
(C) SAP AG
ISG.HR
(C) SAP AG
Company code
Personnel Area
Personnel Subarea
Employee group
Employee subgroup
set up the new company and personnel structures using the IMG.
ISG.HR
Now go into the IMG and show them where these steps are configured. Because the
CAB company has never done manufacturing before, it will require setup to handle
the new types of employees and to include the new organizational units within the
enterprise structure.
Overview: SAP Enterprise Structure
The Organizational Structure is made up of these four levels.
Ask: What is a Client? Right, the highest level in SAP, you cannot log onto the
system without a client number. And what do we do with client 000 and 001?
(Nothing! You never touch them, because they have the standard configuration that
works correctly, and if during implementation you want to check a table or file to see
what has been changed, you can do a compare with client 001 and if you want you
can always copy the original table back to your customer client.) What is a company
code? (Legal entity.) And what is the minimum number you can have? (One per
country because the currency and statutory reporting will be different for each
country.) What is the Personnel Area? (A subdivision of the company code, an
organizational unit used by HR, it could be geographic areas, physical locations,
reporting groupings.) And what is a Personnel Subarea? (Just a subdivision of the
personnel area.)
Enterprise Structure: Client
Highest independent organizational level in the SAP system. Remember there is no
exchange of data between clients. If you set an employee up in one client, you will
not be able to access that information from another client. So this means if you have
an employee who is going to transfer from one client to another, they will have to be
terminated and rehired with a new employee number because clients do not talk to
each other. User authorization is set up by client, if you need to access more than one
client, you will need to have your authorization set up independently in each client.
Enterprise Structure: Company Code
Company code equates to a legal entitya complete set of books, used for external
reporting. They are established and controlled in FI. The Client and the Company
Code are the two structures that each and every SAP module must use. Remember
when you created your project and the system included all kinds of components that
you didnt selectwell one of them was company code, lets look at it. Show them
Tools Business Engineering Customizing select project Make sure you have
two sessions open because well be going in and out of the IMG all day and this way
you can just keep one session open to your IMG. Now, expand Enterprise Structure
Definition Financial Accounting Define, copy, delete Company Codes. This
is where you would set up a new company code and you can see you have to specify
(C) SAP AG
ISG.HR
(C) SAP AG
Specifying the country grouping; this controls the dialog for entering
country-specific personnel data and the setting up and processing of
wage types and pay scale groups;
Generating of default values for pay scale types and areas for an
employee's basic pay;
(C) SAP AG
ISG.HR
(C) SAP AG
ISG.HR
To make the relationship to FI, the personnel area is attached to the company code
and the country grouping. Show them the menu path for this connection.
(C) SAP AG
ISG.HR
Organizational plan
Organizational unit
Jobs
Positions
Set up the link between the organizational structure and the new company
(enterprise) structure.
Organizational Plan
The organizational plan includes units, jobs, positions, workplaces and persons.
Organizational Units
Give examples and ask for examples.
Any type of organizational entity such as a department, cost center, line of business
or project team.
Jobs
Give examples and ask for examples.
A general classification of tasks an individual performs. An object type C cuts
across organizational units, such as manager, administrator, consultant.
(C) SAP AG
ISG.HR
Positions
Give examples and ask for examples.
A specific employee placement within an organization unit. An object type S, a
position inherits the attributes and properties of a job, such as manager of payroll or
supervisor of accounting.
CAB Company Organizational Structure (1)
Review the organizational unit and job structure shown.
(C) SAP AG
ISG.HR
(C) SAP AG
ISG.HR
ISG.HR
Payroll Accounting Area has two important functions: 1) it combines the personnel
numbers that are to be accounted into the same payroll run; and 2) it defines the
exact date of the payroll run by linking to a Period Parameter. Usually there is a
correlation between Employee Group\Subgroup and the Payroll Account Area, in
which case you can use a SAP tool (feature) to default the correct Payroll Account
Area on Infotype 0001 (next unit).
Personnel Control Record for Payroll
This step sets up the system control records for payroll accounting functions.
Infotype 0003 is usually created by the system and is used to determine the current
settings for payroll and locks Master & Time data. The last payroll accounting period
for each payroll accounting area is maintained by the system in a control record. The
next time the payroll is run, the system will use this information to determine the
current payroll accounting period, define retroactive accounting, lock master & time
data during the payroll run and define the earliest retroactive accounting period. It is
important that they note that each payroll accounting area must have its own control
record. If you show them: HR Payroll Payroll, they will see that this graphic
shows the standard payroll steps. How this information is used is covered in detail in
the HR390 Introduction to Payroll.
(C) SAP AG
ISG.HR
Employee Attributes
We have defined employee groups and subgroups, now we are going to assign
attributes to them that will attach different types of status indicators to them. In the
IMG go to PM PA Org Data Org Assignment Define Employee
Attributes. These status codes are used for national and international statistical
reporting and only the values defined by SAP should be used.
Exercise for Additional Organizational Assignment
<Approximate Duration>
The participants create an administrator for their personnel area.
Additional Organizational Assignment: Summary
Summarize what the students have learned in this unit.
(C) SAP AG
ISG.HR
Personal Data
Addresses
Bank Details
(C) SAP AG
ISG.HR
Default Values
Features are objects which query different data structure fields to determine a certain
value which is then used as a default value in another field or used as a control for
certain system processes. You might think of them as little mini programs that have
been preconfigured in the system and are just waiting for the user to plug in their
desired values to customize their usage.
Maintaining Features
Features can be maintained using transaction PE03. From this transaction you can
view documentation that tells you about each feature and how it is used. After
making changes to a feature it must be saved and generated. Features also need to be
regenerated after being transported from one instance to another.
Default Values for Payroll accounting area
This slide shows you the basic elements of a feature.
The first column is made up of consecutive numbers that increase in 10s. These
represent line numbers which tell the computer in what order the instructions are to
be carried out. They are numbers in sets of 10 to make it easy to add additional lines
of code at a future date. The second column is the variable key field, well come
back to that later. The third column is the continuation indicator and is used in
complex features where there is more than one line of code relating to the same
operation. The forth column usually has a D in it, indication that a decision is
taking place. The last column tells the system what kind of decision to perform or
what field is to be taken into consideration to determine the default value. In this
example, were telling the system to look at the TCLAS or transaction code and if
it finds any value, indicated by the asterisk *, it is then to look for the MOLGA
or country grouping indicator. In the Variable key field the entry is defined by the
size of the field which was defined in the operation on the previous line. Since
TCLAS is one digit long the asterisk * takes up one space and then there is a blank
indicating a break in field length and then a double asterisk ** that represents the
any MOLGA code. The &ABKRS=D2 tells the system to default in the value D2
in the payroll accounting area. Explain this feature in detail. Go baby step by baby
step. Show them the Utilities Structure graphics to view the decision tree and
(C) SAP AG
ISG.HR
(C) SAP AG
ISG.HR
(C) SAP AG
ISG.HR
(C) SAP AG
ISG.HR
Exempt
Exempt- Non
Emp Subgroup:
E1
Exec
N1
Hrly Union
E2
Salary Mgmt
N2
Hrly Non-Union
E3
Salary Staff
N3
Hrly Part-Time
E4
Interns
N4
Sprvrs Union
E5
Salary PT
N5
Sprvrs Non-Union
CAP
PCR
2 = monthly wage
earner
3 = Salaried
N1
1 = Hourly
N1
N2
N2
N3
N3
N4
2 = Monthly
N5
E1
N4
N5
3 = Salaried
E1
E2
E2
E3
E3
E4
E4
E5
E5
Exercise for Connection between Planned Working Time and Basic Pay
<Approximate Duration>
(C) SAP AG
ISG.HR
ISG.HR
The I indicates Indirect Valuation which draws the amount from a table. When you make
direct entries, it overwrites the number and the I disappears.
None of the countries in Europe use annual salaries. Salaries are calculated monthly and tax
is calculated and deducted monthly. There is a yearly tax balancing for refunds. The SAP
system was originally designed to meet European requirements and has to be set up to
produce annual wage to meet US requirements. For this purpose the A column indicates if
the wage type is used in the calculation of the Annual Salary.
(C) SAP AG
ISG.HR
PSGroup
Levels
( dates)
amount
GR00
01
dates
14.00
GR00
02
dates
15.00
GR00
03
dates
16.00
GR00
04
dates
17.00
A specific pay scale group is only valid in a specific country grouping, pay scale type
(C) SAP AG
ISG.HR
and pay scale area which are specified before entering this table.
(C) SAP AG
ISG.HR
Using report RPDLGA20 (in the payroll menu), you can request an overview of all wage
types.
There are some basic questions you want to ask which will help separate your employees
into different groupings. Who will use which wage types might be related to their
employee subgroup such as industrial vs. salaried. What kind of valuation, such as direct
vs. indirect might be related to tables (like the ones we built in the last unit)? How often?
You may have some wage types which are associated with a one-time usage such as a
Christmas bonus or they could be recurring such as 401K deductions. Wage type
permissibility can be linked to company code, personnel areas, employee groups (or in
(C) SAP AG
ISG.HR
Primary wage types and secondary wage types. Primary wage types are wage and salary
types that the user can enter when maintaining personnel data. Also known as dialog
wage types. The group, primary wage types, includes wage and salary types that are
automatically generated based on conditions specified by the user. Wage types that can be
used for dialog entry, must be defined as such in the system. If the wage type is to be used
as a default value for basic pay, it must be included in a basic wage type model. These
models are assigned depending on the organizational assignment of an employee (i.e.
company code, personnel area, employee group, employee subgroup). A wage type
model appears as a default value. To ensure that your wage type is evaluated during
payroll accounting, you must create an interface between dialog wage type entry and
payroll processing. Wage types have the following functions: a) wage and salary type
permissibility check (per company code and personnel area, per employee group and
subgroup & per infotype); b) infotypes which have a wage type as a subtype, a time
constraint is applied to the wage type controlling how often it may be available at any
given time; c) define whether a wage type is a payment or deduction (by use of the
operation indicator); d) controlling whether a wage type can be entered with or without
amounts, with volume specifications or a unit of time or measurement. Indirect wage
type valuation is possible by indicating a module name or variant as well as the
corresponding rounding preference. The amount is then calculated using tables and not
entered in the infotype Basic Pay (0008). Secondary wage types are those wage types
with interpretable wage type keys. For example, the wage type /001 can not be entered
directly (in dialog). Secondary wage types are created during the payroll run or derived
and made available on the basis of specific factors. They may also refer to a cumulation
of several wage types or a way to store interim results which are used by the program on
a temporary basis.
Setting up Wage Types
Dialog Characteristics
ISG.HR
ALLOWED to use transaction SM31 (table maintenance) for copying wage types, this would cause
the wage types to not appear in some of the necessary views (table T512W).
ISG.HR
online as well as in how they behave in payroll accounting. For these wage types, SAP recommends
the following procedure which compared to copying and coding all wage types is considerably
quicker:
First you make a copy of one wage type of each kind as a "prototype" and make all of the required
specifications. Then you can use the prototype as a template for all the other wage types that have
the same characteristics and codes. Once you have given characteristics to the prototype, create all
the other wage types of this kind by copying the prototype.
Example
In your enterprise you need different wage types for bonuses for hazardous or unpleasant work.
These wage types are identical with regard to their dialog characteristics and how they behave in
payroll accounting. They only differ in how they are used, that is, in the amount of the bonus to be
paid and in the reason that causes the bonus to be paid. The standard SAP system contains model
wage types for bonuses for hazardous or unpleasant work. Copy these wage types and make the
specifications for your online and payroll characteristics - this is your prototype wage type. Then
copy the prototype and if necessary, make the specific changes to the individual copies.
Recommendation
Note: you can only carry out the procedure described above if you have detailed knowledge of the
Personnel Administration and Payroll component. Before you create prototypes, you need to know
how they are to be used and processed in the system.
Keep an exact record of all the settings defined for your prototype. You can use the
implementation guide's note function, this will help you to quickly identify any errors.
Note: customer wage types MUST begin with a number. All SAP model wage types begin with a
letter or a symbol, DO NOT use a letter or a symbol when you create/copy new wage types! Before
you copy the wage types for the individual infotypes, you should determine which wage types are to
be copied to which number ranges. How you actually create your own customer wage types by
copying the relevant prototypes is described in the step Copy prototype wage types . Because you
have to enter the individual prototype wage types manually, you should make a note of your
prototypes using the implementation guide note function.
Procedure
1. Define all the wage types that will be needed.
2. Determine which wage types are to be created using the procedure described above, that is,
which of your wage types are identical with regard to their dialog and payroll characteristics.
3. Work through the sections entitled "Wage Types" in this implementation guide. In these sections,
create your prototypes for each infotype and make the specifications for these in your dialog
characteristics.
4. If you have implemented the Payroll Accounting component, code the prototypes in the relevant
implementation guides with regard to how they are processed in payroll accounting.
5. Once you have created and configured all of your prototypes, create the remaining wage types by
copying the respective prototypes in the step "Create user-specific wage types " contained in the
implementation guide.
Transaction code PU95 allows you to see the connection between Wage Type Group and View.
There is a way to assign things manually here as well as being able to use
PU95 to set up Wage Type Groups which have Views (This is covered in the HR400 class.)
Table T511Z is where you can remove the model SAP wage types from each infotype.
(C) SAP AG
ISG.HR
This course deals with how to deal with wage types through dialog. It starts with simple concepts.
Customers have to understand these first. When customers present difficult situations, ask them to
diagram their issues.
Example II shows the recurring payments and deductions, and also specifies how often a
wage type may be assigned.
WT Perm. For Several Infotypes
To use a wage type in 5 different Infotypes, you would have to go into every related step in the
IMG: Basic Pay, Recurring Payments and Deductions, ..and include the wage type.
Infotype
EE subgroup
Personnel subarea
0015
0014
2010
Input Frequency for WT in Infotypes
Wage types other than basic pay can be assigned a recurring indicator or flagged as only
being able to use it once. Go to a different part of the IMG and show them a deduction
wage type that has the radio buttons for only once or several.
Checking Wage Type Characterisitics
Explain the wage type characteristics apart from indirect valuation, because this will be presented
later. Show the wage type characteristics, but not the block of indirect valuation.
Important: either you group all the personnel subareas together or none at all.
Wage Type Perm. Per Pers. Subarea and EE Subgroup
Determine the eligibility according to employee subgroup or personnel subarea.
These two sets of groupings (employee subgroup grouping for PWT and the personnel
subarea grouping) is now associated with a permissibility indicator.
(C) SAP AG
ISG.HR
ISG.HR
Base WT Valuation
Define valuation of base wage types
Wage types can be calculated as a percentage from one or more wage types.
Section in Customizing: Personnel administration -> Payroll data > Basic pay > Define
valuation of base wage types
Note: the view is displayed in the middle, in other words moved to the right. The base
wage type is at the front instead of the valuated wage type. Caution, because this also leads
to incorrect entries.
Indirect Valuation Using Module: PRZNT
Module PRZNT
Copy the infotype 0008 for your personnel number. Wage types 0010 and 0020 should be
there, enter 0030 and enter 10 (%). 10% of 0010 and 10% of 0020 is calculated.
Delete 0010, 0020; 0030 remains without amount.
Show in the IMG under Wage type catalog -> Check wage type characteristics.
Explain using the definition of 0030: Module PRZNT with variant D means: wage types
that are used as a basis for calculating should be in the infotype. The percentage level is
entered manually in the infotype.
Variant D: Base wage types have to be present in the infotype 0008
Variant I: Base wage types do not have to be present in the infotype 0008
Indirect Valuation Module: SUMME
Module SUMME
bonus that is directly standard
Like PRZNT, this module requires the specification of the base wage types that are used as a
valuation basis. There are also the variants D and I here.
For the module SUMME, the percentage rate for calculating the wage type amount has already been
determined during base evaluation. Percentages are not entered manually in infotype 0008, they are
a fixed part of their wage type.
Demo how to create a wage type with indirect valuation using the SUMME method.
Create a wage type that is 6% of another wage type
(C) SAP AG
ISG.HR
(C) SAP AG
ISG.HR
Defining a WT Model
Explain the decision tree for the return value of the wage type model in the IMG. You should also
show the feature as a structural graphic because this form of display is often easier to comprehend.
Show "Determine proposal wage types" in the IMG. The wage type model (return value) is
extracted from the decision tree and given one or more wage types which should be proposed in
infotype 0008. You also determine here whether or not the proposal wage types may be overwritten
in the infotype 0008.
Defining Default WT
Proposal wage types for infotype 0008.
Wage types which should be proposed in basic pay are listed in a wage type model. Such wage type
models in the infotype 0008 can be proposed on the basis of the organizational assignment of
employees.
<Approximate Duration>
(C) SAP AG
ISG.HR
ISG.HR
1-1
the demonstration personnel number, run the batch input session and display the
effects in master data.
Batch Input Processing
Explain and show how to use a batch input session.
Pay Scale Reclassification Based on Hours Worked
Point out to the participants that they must check whether the date agrees with the
reclassification rule that has been set up.
Standard Pay Increase
Within the standard pay increase they have two options: either a) simple (as
described on the previous graphic) - where an increase is based on an effective date
and and the T510 table for reclassification but no infotype 0008 is created; or b)
enhanced or extended pay increase - which will create a new infotype 0008. The next
two graphics walk through the steps involved.
Performing a Simple Pay Increase
No new record of infotype 0008 is created for a simple standard pay increase, in contrast to
the extended standard pay increase.
Important: Simple standard pay increase does not trigger retroactive accounting
automatically, however if you then run the report RPITRF00, retroactive accounting is
initiated by creating new basic pay records.
Note: The report RPURET00 sets a retroactive accounting flag (in infotype 0003) when the
table is changed.
You can obtain an overview of reassignment, pay scale group membership among
other things using report RPLTRF00.
Basically you run RPU51000 to change the pay scale groups and levels based on key dates
(all part of T510). Only used with indirect valuation and does not perform retroactive
accounting. To force the creation of a new infotype 0008, also run RPITRF00 (this will also
generate retroactive accounting).
Show simple standard pay increase using the report RPU51000. The report is not in the IMG,
you have to call it up separately. You should specify the date, the pay scale groups, the
increase and so on. The report creates a new entry in the table. No additional record of
infotype 0008 is created. Start the report, then call up infotype 0008 for Personnel number (if
affected). Enter date of standard pay increase below in the field indirect valuation. The
wage type is valuated indirectly in the infotype.
(C) SAP AG
ISG.HR
1-2
EE Leaves Company
For this and the following slides, see the notes in the participants' manual.
Exercise for EE Leaves Company
<Approximate Duration>
Reentry into Company
(C) SAP AG
ISG.HR
1-3
(C) SAP AG
ISG.HR
1-4
1. Name:
2. Company:
3. Positions (role on the project):
4. SAP modules:
5. Live date/Release:
6. Have you used an IMG before:
7. Expectations:
(C) SAP AG
ISG.HR
1-5
(C) SAP AG
ISG.HR
1-6