Professional Documents
Culture Documents
"Now 6000 Real-Time Screen Shots With Ten Country Payrolls With Real-Time SAP Blueprint" For Demo Click Here
"Now 6000 Real-Time Screen Shots With Ten Country Payrolls With Real-Time SAP Blueprint" For Demo Click Here
com
om
.c
ew
Fo
ru
Real-time Employees from Top MNC's will teach & answers your
queries everyday.
Real-time Scenarios
Real-time System screen shots step by step configuration total
6000+ screen shots
With two country payrolls (You can choice according your Location)
and real-time Business Blueprint.
Post training support like Resume building & Interview tips with
exact requirement, we will provide top companies HR email ID's and
every day Hot vacancy list.
ik
.W
iN
Example SAP HR : Special Topics apart from general topics which no one dare to teach
.W
ik
iN
ew
Fo
ru
.c
om
om
SAP America is a subsidiary of SAP AG, the recognized leader in providing collaborative, interenterprise software and e-business solutions. A truly global software provider, SAP AG has more
than 1000 partners, 22 industry solutions and 10 million users at 30,000 installations around the
world. SAP America has contributed significantly to this leadership position and it is the foremost
provider of e-business and enterprise software in the United States.
.c
SAP software was developed to be modular, scaleable, open and flexible, allowing companies to
tailor it specifically to their needs. SAP calls this approach to implementing software "configure to
order" because each implementation will be different according to each customer's needs.
Fo
ru
But SAP solutions don't stop there. Information integration is a major tenet of the SAP philosophy,
and SAP places great emphasis on the creation of tools that facilitate it. SAP provides integration
tools and methods for linking legacy and distributed systems as well as a host of third party
software solutions, to get your information into the right hands, internally and externally.
iN
ew
Traditional Information technology systems used by many business today have been developed
to accomplish some specific task and provide reports and analysis of events that have already
taken place. Examples are accounting general ledger systems. Occasionally, some systems
operate in a "real-time" mode that is, have up to date information in them and can be used to
actually control events. A typical company has many separate systems to manage different
processes like production, sales and accounting. Each of these systems has its own databases
and seldom passes information to other systems in a timely manner.
.W
ik
SAP takes a different approach. There is only one information system in an enterprise, SAP. All
applications access common data. Real events in the business initiate transactions. Accounting is
done automatically by events in sales and production. Sales can see when products can be
delivered. Production schedules are driven by sales. The whole system is designed to be realtime and not historical.
SAP structure embodies what are considered the "best business practices". A company
implementing SAP adapts it operations to it to achieve its efficiencies and power.
Flexibility
Customers can customize business modules to realize best business practices
System provides necessary interfaces to incorporate external software.
Scalability, accommodates acquisitions and growth
System can be configured the way you want to do business in the future
Allows customized screens processing and reports
System runs on multiple hardware platforms
om
ru
.c
Enterprise-Wide Integration
Enterprise-wide integration is the main functionality of SAP R/3 System. No other application
software offers the breadth of open systems, client/server functionality, functional links between
processes that multiply the power of each person's work. The R/3 System's components are fully
integrated. Once you enter data, it resides in the central database shared by all R/3 components.
Transaction-related process chains trigger the next activity as needed from engineering to
production planning to sales and distribution. The R/3 System's full integration pulls your
enterprise together, promoting data access, flexibility, and productivity.
Architecture
ew
Fo
Real-Time Information
SAP provides up-to-the-minute, real-time information.
iN
SAP R/3 system is based on Client/Server architecture that is comprised of three tiers:
Presentation server: Your local PC that has SAPGUI.
.W
ik
Application server: The application server is used to run the business application programs in
the R/3 client/server concept. The application modules are loaded from the data base server to
the application server as required. Thus the application server requires only storage capacity to
accommodate UNIX, Swapping and the SAP runtime environment.
Database server: The data base server stores the SAP application programs and data in the R/3
client/server concept. It also handles the SAP update program and batch jobs.
SAP Glossary
GUI (Graphic User Interface)
A graphical interface used by SAP environment as part of the three tiers. Also known as frontend.
IMG (Implementation Management Guide)
It is a hierarchical structure that reflects the R/3 component hierarchy and contains every
configuration activity. Released from version 3.0 onwards
Instance
It means application server and each one has its own set of work processes.
om
SysID
A set of three letters or number that identify a system. Some sets are not allowed because they
are used by SAP. They are informed when the system is installed.
.c
ru
Fo
ew
Archiving SAPs terminology for the functionality that purges transactions and master data
from the SAP database. The SAP literature states that archived data can be restored to the
production system. For practical purposes however, this is not recommended.
iN
DART An acronym for Data Archiving and Retention Tool. This is SAP functionality which
allows you to periodically extract and retain data from your R/3 system. The data is extracted into
a sequential file. DART provides tools for viewing the retained data in different ways.
.W
ik
Legal Data As used in this document, this refers to the requirements imposed by the IRS, State tax
authorities and other tax authorities for the long-term retention of business data to support taxes paid and
other legal requirements.
Operational Data As used in this document, this refers to the requests from customers, vendors or
employees for business data.
Management Data As used in this document, this refers to data that is used by management for business
decisions.
.W
ik
iN
ew
Fo
ru
.c
om
ASAP Methodology
.W
ik
iN
ew
Fo
ru
.c
om
.W
ik
iN
ew
Fo
ru
.c
om
.W
ik
iN
ew
Fo
ru
.c
om
.W
ik
iN
ew
Fo
ru
.c
om
.W
ik
iN
ew
Fo
ru
.c
om
.W
ik
iN
ew
Fo
ru
.c
om
om
.c
.W
ik
ew
iN
Fo
ru
Components of PA:
Use
Recording employee data for administrative, time recording, and payroll purposes is of primary
importance for master data administration in HR. In the SAP System, the information units used
to enter master data are called infotypes.
Infotypes are used to group related data fields together. They provide information with a structure,
facilitate data entry, and enable you to store data for specific periods.
Structure
Infotype Structure
Data Entry
Time-Dependent Storage of Infotype Data
.c
om
Time Constraints
ru
Time constraints guarantee that exactly the data the system needs to be able to correctly process
the employee data, handle personnel administration processes and run payroll for an employee is
available in the system. Time constraints keep you from storing mutually incompatible data and
prevent gaps from occurring in the data history.
iN
ew
Fo
Use
You use time constraints to define the following:
Whether an infotype record must exist for an employee in the system
Whether further records of the same infotypes may exist
Whether these records can overlap in the validity period.
For certain infotypes, you can also assign different time constraints in relation to the infotypes
subtype.
When you enter infotypes, the system automatically checks if your input satisfies the time
constraints conditions, and reacts by automatically delimiting data records or issuing error
messages.
.W
ik
Structure
Time Constraint 1
For the entire time that the employee works at the enterprise, exactly one valid infotype
record must exist. The validity periods of the individual records must not overlap. When you
create a new record, the system automatically uses the start date of the new record as the
delimitation date of the old record. Gaps are only allowed between the employees entry
date and the start date of the first record.
Time constraint 1 must be used for all of the infotypes containing information that must be
available at all times. This is particularly true of personal and organizational assignment
data.
An Organizational Assignment infotype record (0001) must exist for all active or
inactive employees in the SAP System. The system needs the data stored in this
infotype for all business processes.
In addition, this data must be unique, in other words, the system must know
precisely to which organizational units the employee belongs. Thats why only one
record may exist at the same time.
Time Constraint 2
No more than one valid record can exist at any one time. Records with constraint 2 must
not overlap. Their existence is not obligatory. When you create a new record, the system
delimits the previous record, if one exists. If the system delimits a record because of time
constraint 2, it issues an appropriate message.
Time Constraint 3
Any number of valid records can exist at any one time. The individual records do not
conflict with each other.
ew
Fo
ru
.c
om
In the Powers of Attorney infotype (0030), you can store different powers of
attorney. Thats why any number of records for this infotype can exist at the same
time. Since not every employee in your company has powers of attorney, a record
for this infotype does not have to exist in the system.
Time Constraint A
Infotypes with time constraint A must have no more than one record. The system
automatically assigns the record a validity period from January 01, 1800 through
December 31, 9999. This validity period cannot be subdivided.
Infotype records with time constraint A cannot be deleted.
Time Constraint B
Infotypes with time constraint B must have no more than one record. The system
automatically assigns the record a validity period from January 01, 1800 through
December 31, 9999. This validity period cannot be subdivided.
Infotype records with time constraint B can be deleted.
Time Constraint T
Infotype records with time constraint T depend on the subtype.
.W
ik
iN
For the Addresses infotype (0030), you can assign a different time constraint for
each subtype. In this way, you can make sure that a main address always exists for
the employee and you can also enter temporary residences, if necessary.
Time Constraint Z
The infotypes you use for entering working and absence time have a special time
constraint behavior. For more information, see Time Constraints in Time Management.
.W
ik
iN
ew
Fo
ru
.c
om
.c
om
ru
Important Infotypes
Fo
Infotype Name
Actions
0001
Organizational Assignment
0002
Personal Data
0003
Payroll Status
Addresses
ik
0007
iN
0006
ew
0000
Basic Pay
0009
Bank Details
.W
0008
0011
0014
Recur. Payments/Deds.
0015
Additional Payments
0016
Contract Elements
0017
Travel Priviledges
Monitoring of Dates
0021
Family/Related Person
0022
Education
0023
Other/Previous ERs
0024
Qualifications
0025
Appraisals
0027
Cost Distribution
0028
0029
Workers' Compensation
0030
Power of Attorney
0031
0032
Internal Control
0033
Statistics
0034
Corporate Function
0035
Company Instructions
0037
Insurance
0040
Objects on Loan
0041
Date Specifications
0045
Company Loans
0050
0052
Wage Maintenance
0054
Works Councils
0057
Membership Fees
0065
Tax Data - GB
0069
National Insurance GB
0070
Court Orders GB
0071
Pension Funds GB
0077
0078
Loan Payments
0081
m
ru
Fo
ew
ik
0082
iN
0080
.c
0019
om
Leave Compensation
0084
SSP Control GB
0085
0086
SSP/SMP Exclusions GB
0087
0088
Maternity GB
.W
0083
Residence Status
0105
Communication
0121
RefPerNo Priority
0128
Notifications
0130
Test Procedures
0131
Garnishment/Cession
0139
0165
Deduction Limits
0167
Health Plans
0168
Insurance Plans
0169
Savings Plans
0183
Awards
0185
0198
0199
0207
0208
0209
Unemployment State
0216
Garnish. Adjustment
0302
Additional Actions
0416
Quota Compensation
ru
.c
0094
om
Infotype
Infotype Name
Object
1001
Relationships
1008
1011
Department/Staff
ik
1015
Description
iN
1003
ew
1000
1002
Work schedule
Cost planning
Standard profiles
1017
PD profiles
.W
1016
1027
Site-dependent information
1028
Address
1032
Mail address
1037
Billing/allocation information
Fo
Shift group
1208
2002
Attendances
2003
Substitutions
2004
Availability
2005
Overtime
2006
Absence Quotas
2007
Attendance Quotas
2010
EE Remuneration Info
2011
Time Events
2012
2013
Quota Corrections
2050
Annual Calendar
2051
Monthly Calendar
2052
Weekly Calendar
.c
2001
om
Infotype
Infotype
Infotype Name
Applicant Actions
4001
Applications
4002
Vacancy Assignment
Applicant Activities
Applicant's Pers.No.
.W
ik
iN
4005
ew
4004
Fo
4000
4003
ru
.W
ik
iN
ew
Fo
ru
.c
om
.W
ik
iN
ew
Fo
ru
.c
om
.c
om
.W
ik
iN
ew
Fo
ru
.W
ik
iN
ew
Fo
ru
.c
om
.W
ik
iN
ew
Fo
ru
.c
om
.W
ik
iN
ew
Fo
ru
.c
om
.W
ik
iN
ew
Fo
ru
.c
om
.W
ik
iN
ew
Fo
ru
.c
om
.W
ik
iN
ew
Fo
ru
.c
om
.W
ik
iN
ew
Fo
ru
.c
om
.W
ik
iN
ew
Fo
ru
.c
om
.W
ik
iN
ew
Fo
ru
.c
om
iN
ew
Fo
ru
.c
om
The client is used to separate data within a SAP system; clients are always numbers.
Usually the only time you will refer to a client is when you first log into SAP. Here we
see the login screen which asks for the client number:
ik
Configuration and data belong to the client. So if you log into client 200, you may see
different employees and customizing settings to those in say, client 300. Some projects
will use a different SAP system altogether for different data.
.W
The client numbers will be decided on your project. For example, client 200 may be a
play client, 300 for configuration and testing and 400 for training.
Technically, you are actually logging into the same database. Behind the scenes SAP
will fetch the correct data and display it for you. The client is usually the primary key of
database tables in SAP.
Fo
ru
.c
om
The Company code is an independent company with its own accounting unit, that is, a
company that draws up its own balance sheet.
.W
ik
iN
Personnel Subarea
ew
om
Employee Group
.c
The employee is used to classify employees in general terms. It defines the position of a
person within the company's workforce.
.W
ik
iN
ew
Fo
ru
Employee Subgroup
Employee groups are divided into employee subgroups. Employees in the active workforce are
distinguished according to their status - trainee, hourly-paid employee, salaried employee, etc.
Germany
Switzerland
Austria
Spain
Netherlands
France
Canada
Great Britain
Denmark
USA
Saudi Arabia
Singapore
India
om
01
02
03
04
05
06
07
08
09
10
24
25
40
.c
The Personnel Structure is split by Company Code, Personnel Area and Personnel
Subareas. There are other structures including employee groups/subgroups and the
pay scale structure, but in this section its Pers Areas and subareas which are the topic
to be covered.
iN
ew
Fo
ru
An implementation with one company, in one country, with various factories/sites may
look like this:
.W
ik
This is a typical example. The company code is easily defined, as it represents a legal
entity so you have to set them up exactly as they are. This is a function of the Finance
configuration and is not covered here.
The Personnel Area
A Personnel Area is attached to a company code, so you will always have at least one
area per company code. Generally, it represents a high level of the business. Quite
often it represents a country as shown in the example above.
om
If you have just one site, the personnel subarea may be used to represent different splits
of employee, maybe factory vs staff; but generally it represents a physical location.
.c
The public holiday calendar is attached to the personnel subarea, so if you have plants
with different holiday calendars, you must have different subareas for each.
Some points to consider for Personnel Subareas:
ru
.W
ik
iN
ew
Fo
ik
iN
ew
Fo
ru
.c
om
.W
Make sure your company code (4 Digits) doesnt exist in the table already and click on
New Entries shown below.
.c
om
.W
ik
iN
ew
Fo
ru
Enter the company code details as shown in above, and also enter all the address details
of company code as shown below.
om
as
ew
Fo
ru
.c
When we go to this screen we will get a blank screen, Click on the copy option
shown below.
.W
ik
iN
Here we are coping our company code from SAP standard company code for US the
standard company code is 3000
.c
om
When we click above Ok, we will get the below information message click on Yes here
as highlighted.
iN
ew
Fo
ru
If we say Yes for below message we will get standard G/L accounts copied to our new
company code from standard 3000
.W
ik
Once we say Yes for Second Information Message system prompts one more
confirmation, do u want to allocate different currency for a target company code, as we
are coping from standard company code i.e., 3000 which already contained USD as
currency we can say No here, which make ABCL company code to there USD.
om
to move further.
ew
button to move further and keep on the clicking until you reach the
.W
ik
iN
Fo
ru
.c
om
Below are the Couple of FI/CO setting, these settings are not mandatory up to ECC 5.0
and these steps become mandatory in ECC 6.0, if we wont perform the FI/CO setting
implication are as below
.c
If it is 5.0 Error message on hiring an employee in Infotype 0001, but by pressing Enter
you can move further.
Fo
ru
If it is 6.0 Error message on hiring an employee in Infotype 0001, You cant move
further until you complete the below configuration.
.W
ik
iN
ew
Enter the highlighted values, you can use the same values for your company code also,
Here we are using Chart of Accounts as CAUS and Fisal Year Variant as K4.
.W
ik
iN
ew
Fo
ru
.c
om
Chart of Account = Set of General Ledgers are nothing but chart of Accounts.
Fiscal Year Variant K4 represents four quarter for the financial year.
ew
Fo
ru
.c
om
In the Basic Data Navigation area we have to define Controlling area, In a realtime
project these will be created by FI/CO Consultants.
.W
ik
iN
Once you enter in to the table click on New entries button as shown below, when you
click on new entries the following screen will appear.
ik
iN
ew
Fo
ru
.c
om
.W
Click on Save button we will get the following information message, Please click on Yes
button.
By doing the above activity we created a Controlling area for our company code.
Fo
ru
.c
om
.W
ik
iN
ew
Then Click on new entries and your company code there as shown below.
iN
ew
Fo
ru
.c
om
.W
ik
With this we are done with the mandatory FI/CO Configuration for ECC 6.0 Version.
ew
Fo
ru
.c
om
SPRO> SAP Reference IMG (F5)> Enterprise Structure> Definition > Human Resource
Management> Personnel Areas > Personnel Areas > New Entries
.W
ik
iN
.c
om
ru
Click on Create Request option and create your own transport, We just need to enter the
description the transport like what we are trying to perform, System will automatically
generate the Transport number.
Fo
.W
ik
iN
ew
SPRO> SAP Reference IMG (F5)> Enterprise Structure> Definition > Human Resource
Management> Personnel Sub areas > Create Personnel Subareas > New Entries
om
Click on New entries and Make enter 4 digits (maximum) Alphanumeric key for
Personnel Subareas as below
iN
ew
Fo
ru
.c
SPRO> SAP Reference IMG (F5)> Enterprise Structure> Definition > Human Resource
Management> Employee Groups > New Entries
.W
ik
.c
om
SPRO> SAP Reference IMG (F5)> Enterprise Structure> Definition > Human Resource
Management> Employee Subgroups > Define Employee Subgroups> New Entries
iN
ew
Fo
ru
.W
ik
By doing the above activities we are done with creation of Enterprise and Personnel
Structure, now we need to perform the assignment activity.
om
SPRO> SAP Reference IMG (F5)> Enterprise Structure> Assignment > Human
Resource Management> Assign Personnel Area to Company Code
Fo
ru
.c
Select your Personnel Area, Assign your company code and Country Code for personnel
Area, This Country grouping Controls the Master data maintenance and Wagetypes,
Please refer the below screenshot for the same.
ew
.W
ik
iN
SPRO> SAP Reference IMG (F5)> Enterprise Structure> Assignment > Human
Resource Management> Assignment of Employee Subgroup to Employee Group
Fo
ru
.c
om
Note: It is possible to assign more than one MOLGA for same Employee Group and
Employee Subgroup.
.W
ik
iN
ew
.W
ik
iN
ew
Fo
ru
.c
om
Click on
, You will get message box as Parameters Created for USA. Click on
and Make Sure Parameters Created as below highlighted.
om
ik
iN
ew
Fo
ru
.c
number,
, Click on
.W
Finally Click on
om
You can configure the feature by using Create button and you can call the decision
operation based on the requirement, Finally you have to Assign a return value for the
iN
ew
Fo
ru
.c
, All
decision operation (Ex: 06 in the Previous Screen) and Click on Activate Icon
the features need to be activate, Features doesnt give any affect until activate them.
ik
.W
In this table we have to maintain Activity Status, Employment Status and Training Status
for all our EEs and ESGs, In the above 3 status Activity Status is mandatory
Select the MOLGA and Click on enter
ru
.W
ik
iN
ew
Fo
.c
om
ru
.c
om
Fo
The above mentioned Configuration is mandatory to hire an employee for Our own
Company Code.
.W
ik
iN
ew
With the above configuration you can hire an employee and Test whether every
thing is working fine or not for given company code.
.c
om
.W
ik
iN
ew
Fo
ru
Select the User group dependency on menus and Infogroups option as shown below
om
Step 2:
.W
ik
iN
ew
Fo
ru
.c
Now go back (F3) and Select the Infotype Menu option and Enter the Infotype Menu
which was create in the above step i.e., A1, A2 and A3, Select the Infotype A1 and enter
the Infotypes under that menu, repeat the same activity for all other Infotype menus.
.W
ik
iN
ew
Fo
ru
.c
om
Enter the required IT under the A1 menu. In the User Group column enter the user group
number as Reference user group, the both should be one and same. In the No Column
Enter the Serial no of Infotypes. If we leave as blank in the Screen Column system will
pick the Standard Screen. If there any custom screen number enter that number in the
column.
(F2)
In this table we shouldnt create any new entries, In Simple we have to change the
reference user group to our own user which was assigned in our user parameters for 01
HR Master Data Menu.
ru
.c
om
In the given example we are following 78 as reference user group, with this we changed
the reference group as 78 for 01 Menu as shown below.
Fo
Step 4:
ew
In this Step we need to our Infotype Menus (A1, A2, A3) to 01 HR Master Data
Catalog.
SPRO> Personnel Management > Personnel Administration > Customizing
Procedures> Infotype Menus> Determine choice of Infotype menus> Infotype
(F2)
.W
ik
iN
Menus>
.c
om
Note: Before making entries please make sure about the S.No. Just Check how many
S.No are used under the reference user group, If there are preexisting entries under that
User group, we have continue with a different S.No, else we will get a error message as
An entry already existed with same Key
Step 5:
ik
iN
ew
Fo
ru
Goto User Profile (SU3 is T-code) and change the UGR as 78 instead of 10 and
save, as shown below and click on
.W
Goto PA30 and check the customer specific infotype menus got created or not.
In Order to Define the Personnel Actions, First we have to identify what all the action
type the customer is performing on their employees. Once We Identify the action we
have to determine are there any action which falls under same Infogroup. By doing the
above exercise we can come out with a list of Infogroups required for the client.
Here we will configure Hiring action and configuration is steps are same for all the other
action types.
Step1: Define the Infogroups for action
SPRO> Personnel Management > Personnel Administration > Customizing
Procedures> Actions> Define Infogroups> User group dependency on menus and
Info groups >
ew
Fo
ru
.c
om
iN
In the above mentioned table we have to create the relevant Infogroups for actions, we
may have 1:1 or 1:many combination for Infogroups vs Action. In the above example I
created different Infogroups for each action
Step2: Add the Infotypes to Infogroup with relevant operation
ik
.W
(F2)> Give
Procedures> Actions> Define Infogroups> Info group >
your Infogroup which was defined in the previous table as shown below
iN
ew
Fo
ru
.c
om
.W
ik
As we are creating Hiring action, Meaning we dont have any data relevant to that
employee in our system. So we have to create all the data for the PERNR. That is the
reason we have to INS operation for Hiring.
om
In the same way we have to create the Infogroups for Change of Position or Separation.
ru
.c
For Change of Position we can call relevant Infotypes we can user Operation as COP
or MOD
Fo
.W
ik
iN
ew
In the T529A, SAP delivered some standard personnel action, We can select those
actions which are relevant for us as shown below.
om
.W
ik
iN
ew
Fo
ru
.c
Click on Copy Icon ( ) and Change Action Code and Description along with our own
Icon
Infogroups, as shown below and click on
iN
ew
Fo
ru
.c
om
Infotype 0001:
.W
ik
Below configuration is important for Infotype 0001, If we need any changes to the above
highlighted fields input in IT -0001 screen, the below is the work area in SPRO. The
highlighted box is important in all nodes.
.c
om
.W
ik
iN
ew
Fo
ru
ew
Fo
ru
.c
om
.W
ik
iN
This infotype will be created internally by SAP, we dont require any configuration for
this infotype,
.W
ik
iN
ew
Fo
ru
.c
om
om
.c
Below configuration is important for Infotype 0006, If we need any changes to the above
highlighted fields input in IT -0006 screen, the below is the work area in SPRO. The
highlighted box is important in all nodes.
.W
ik
iN
ew
Fo
ru
.c
om
ru
Below configuration is important for Infotype 0009, If we need any changes to the above
highlighted fields input in IT -0009 screen, the below is the work area in SPRO. The
highlighted box is important in all nodes.
.W
ik
iN
ew
Fo
om
.c
Below configuration is important for Infotype 0021, If we need any changes to the above
highlighted fields input in IT -0021 screen, the below is the work area in SPRO. The
highlighted box is important in all nodes.
.W
ik
iN
ew
Fo
ru
.c
om
ru
Below configuration is important for Infotype 0185, If we need any changes to the above
highlighted fields input in IT -0185 screen, the below is the work area in SPRO. The
highlighted box is important in all nodes.
.W
ik
iN
ew
Fo
.c
om
Fo
ru
Below configuration is important for Infotype 0016, If we need any changes to the above
highlighted fields input in IT -0016 screen, the below is the work area in SPRO. The
highlighted box is important in all nodes.
.W
ik
iN
ew
.c
om
ru
Below configuration is important for Infotype 0040, If we need any changes to the above
highlighted fields input in IT -0040 screen, the below is the work area in SPRO. The
highlighted box is important in all nodes.
.W
ik
iN
ew
Fo
.c
om
ru
Below configuration is important for Infotype 0019, If we need any changes to the above
highlighted fields input in IT -0019 screen, the below is the work area in SPRO. The
highlighted box is important in all nodes.
.W
ik
iN
ew
Fo
om
.c
Below configuration is important for Infotype 0041, If we need any changes to the above
highlighted fields input in IT -0041 screen, the below is the work area in SPRO. The
highlighted box is important in all nodes.
Note: This Important is very important; This Infotype can be used for calculation in the
Benefits, Compensation, ECM and Payroll Calculation also. In the below node we can
create new Date Types and we can modify DATAR feature.
.W
ik
iN
ew
Fo
ru
.c
om
Below configuration is important for Infotype 0022, If we need any changes to the above
highlighted fields input in IT -0022 screen, the below is the work area in SPRO. The
highlighted box is important in all nodes.
.W
ik
iN
ew
Fo
ru
om
.c
Below configuration is important for Infotype 0023, If we need any changes to the above
highlighted fields input in IT -0023 screen, the below is the work area in SPRO. The
highlighted box is important in all nodes.
.W
ik
iN
ew
Fo
ru
om
Below configuration is important for Infotype 0105, If we need any changes to the above
highlighted fields input in IT-0105 screen, the below is the work area in SPRO. The
highlighted box is important in all nodes.
ik
iN
ew
Fo
ru
.c
.W
Note: Though IT 0007, IT 0008, IT 0014, IT 0015 required configuration under PA,
we are going to talk about them under respective modules.
.W
ik
iN
ew
Fo
ru
.c
om
Organisation Management
.W
ik
iN
ew
Fo
ru
.c
om
.W
ik
iN
ew
Fo
ru
.c
om
.W
ik
iN
ew
Fo
ru
.c
om
.W
ik
iN
ew
Fo
ru
.c
om
.W
ik
iN
ew
Fo
ru
.c
om
.W
ik
iN
ew
Fo
ru
.c
om
.W
ik
iN
ew
Fo
ru
.c
om
.W
ik
iN
ew
Fo
ru
.c
om
Relationships
.W
ik
iN
ew
Fo
ru
.c
om
.W
ik
iN
ew
Fo
ru
.c
om
.c
om
.W
ik
iN
ew
Fo
ru
A position can be held by more than one person or user and a person can hold more than
one position. However, a one-to-one ratio is the ideal.
.W
ik
iN
ew
Fo
ru
.c
om
om
.c
iN
ew
Fo
ru
Real-time Employees from Top MNC's will teach & answers your
queries everyday.
Real-time Scenarios
Real-time System screen shots step by step configuration total
6000+ screen shots
With two country payrolls (You can choice according your Location)
and real-time Business Blueprint.
Post training support like Resume building & Interview tips with
exact requirement, we will provide top companies HR email ID's and
every day Hot vacancy list.
.W
ik
Example SAP HR : Special Topics apart from general topics which no one dare to teach
.W
ik
iN
ew
Fo
ru
.c
om