Professional Documents
Culture Documents
TRAINING MANUAL
FOR
Druk Green Power Corporation Limited
Druk Holdings and Investments Limited
Wipro Ltd.
Date: 13.12.2010
Version 1.0
Table of Contents
1.
1.1.
Object Types.....................................................................................................................................2
1.2.
Methodology ....................................................................................................................................2
1.3.
1.4.
Position ............................................................................................................................................3
1.5.
Job ....................................................................................................................................................4
1.6.
Cost Centre.......................................................................................................................................4
1.7.
1.8.
1.9.
2.
Getting Started.....................................................................................................................................7
2.1.
2.2.
2.3.
2.4.
2.5.
3.
3.1.
3.2.
3.2.1.
3.2.1.1.
3.2.1.2.
3.2.1.3.
4.
OM History ........................................................................................................................................ 26
Page 1
1. Master Data
Master data contains data records that are stored in the database for a long period of time. These are stored
centrally and used and processed on a cross-application basis. This prevents multiple storage (redundancy)
of data.
When you create purchasing documents, the R/3 System facilitates data entry by copying the data from
existing master records as default values into the purchasing documents. It also copies data such as units of
measure and material short texts from the material master record. The data in the vendor master record
includes addresses and payment data. You can store data for a particular material (for example, delivery
time and purchase price) on a vendor basis in info records.
1.1.
Object Types
1.2.
Methodology
Organizational management is based on the concept that each element in an organization represents a
stand-alone object (object-oriented design) with individual characteristics. These objects are created and
maintained individually. They are then linked together through relationships (shown below) to form a
network which has the flexibility to perform human resources planning, forecasting and reporting.
Objects:
Relationships:
Characteristics:
OM is based on
organizational
objects
Page 2
Object Type
Organizational Unit
Job
Position
Cost centre
Person
K
P
1.3.
Object Icon
Person
Organization Unit
Represent a functional unit in your enterprise, marketing department, for example. This field defines the
Department / Section within the Organizational structure in which the employee is working. You depict the
functional units of your enterprise with
organizational units. You create an organizational structure by
assigning these organizational units to each other. The highest organizational unit in an organizational
structure is the root organizational unit. The organizational structure* is the basis for the creation of an
organizational plan.
1.4.
Position
Page 3
1.5.
Job
It is defined as Resource for creating positions. Positions are concrete and can are held by persons in an
enterprise (purchasing administrator, for example). Jobs, in contrast, are classifications of functions in an
enterprise (administrator, for example), which are defined by the assignment of characteristics. When
creating a new position (purchasing administrator, for example), you can relate it to a
job that already
exists (administrator, for example). The position then automatically inherits the tasks and characteristics of
the job.
1.6.
Cost Centre
Object type key K is used for object type Cost Centre. Cost centers are maintained in Financial Accounting
and are linked to either organizational units or positions. Cost center assignments are inherited along the
organizational structure.
1.7.
Object Relationships
All relationships are stored in infotype 1001(HRP1001 database). The objective is to explain the connection
between object relationships, evaluation paths, and the organizational plan.
Data Model:
Object
Types
Meaning
Page 4
OO
A/B 003
Belongs to/Includes
OS
A/B 008
Holder/Holder
SP
A/B 002
S-S
Position to Position
1.8.
If a job describes a position, then the position, in turn, will be described by the job. The direction of these
relationships is distinguished using the identification A or B. It is therefore, necessary to create a relationship
in only one direction. The inverse relationship will be created automatically by the system. This is the
concept of inverse relationship in SAP. As the name indicates, when a relationship is maintained between 2
objects, then there is automatic creation of inverse relationship. For instance if there is created a
relationship A003 (position belongs to) between Position and Organizational Unit then by default the inverse
relationship B003 (Incorporates) is created between Organizational Unit and Position inversely.
A relationship can also be one-sided. Relationships to objects of an external object (cost centre in
controlling, for example) are often one-sided, that is, they go only in 1 direction.
The relationships between the basic objects result in the following structures:
Organizational Structure
Reporting Structure
Staff Assignments
Page 5
ORGANIZATIONAL
UNIT
COST CENTER
Belongs to A003
Cost center allocation A011
POSITION
Person is assigned as the holder A008
Is described by B007
Describes A007
Holder B008
JOB
1.9.
PERSON
Number Range
Page 6
2. Getting Started
Switch ON your PC. A screen similar to the one shown below will flash on your PC:
Page 7
2.1.
In this window, The System Head can configure the SAP Logon for you.
To Logon to SAP:
OR
To open Logon Window:
Page 8
2.2.
To Logon to SAP
Double click on the small icon in the Description column, in the SAP logon-pad window.
After a brief delay, following window shall open on your screen:
2.3.
Page 9
The user menu contains only those items such as transactions, reports, and Web Addresses you need to
perform your daily tasks. If your system Head has defined a user menu, it is displayed when you log on to
the system.
If you have not been assigned a user menu, or you need to access items that are not contained in your user
menu:
Open the SAP standard menu by choosing Menu SAP standard menu. You now have a complete
overview of the SAP System you are currently working with. Use the workplace menu to navigate to the
items you need.
Page 10
2.4.
Standard toolbar
Name
Function
Enter
Command field
Save
Back
Exit
Cancel
Find
Find next
First page
Page 11
2.5.
Previous page
Next page
Last page
Create session
Create shortcut
F1 Help
Layout menu
Application toolbar
Name
Function
Create
Change
Display
Copy
Page 12
Delete
Overview
Execute
Page 13
3. Business Processes
3.1.
Organization Structure
Organization Structure is the representation of the reporting structure and the distribution of tasks using
organization units (depts.) in an enterprise. The highest organization unit in the organization structure is the
root organization unit. E.g. CMD Organizational structure is the representation of the task related,
functional structure of the company.
Page 14
3.2.
Page 15
3.2.1.
SIMPLE MAINTAINANCE
Menu Path
Transaction Code
PPOC_OLD
Either, one can follow the path or by using the transaction code
OR
Page 16
Command Field
Mandatory
field
Create
button
Validity Start
Date
Page 17
System
generate 8
Digit code
Page 18
Click on Staff
Assignment
Click on
Position
Page 19
Note: From the same screen you can create the different number of positions.
Create
Click
Page 20
NOTE: On the same window you can create the multiple Divisions/Units.
As and when you will press SAVE button following new screen will appear with entered values:
Dept
created
Page 21
Click on Staff
Assignment
Click
Click on
Position
Page 22
Note: From the same screen you can create the different number of positions and create realtionsips.
Now, all the created Positions are assigned to Organization Unit.
MDDGPC
Head
HRA
Page 23
1. Directly from employee master data: Click on the Assign Holder button from the screen and
following screen will come. Firstly mark to where one want to assign the holder- e.g. Recruitment
Division under HR&A Dept, then click Assign Holder assign holder screen will appear either
type his name or personnel Identity number and save it.
Assign
Holder
Page 24
Holder
assigned
For example: We have assigned the holder for position Assistant manager-RD directly while hiring. After
assigning the holder, one can assign the chief position if the person is holding the chief position of the
department/division/unit.
Page 25
Assigned
Click
The hat symbol shows the head of the Dept/Division/ Units and below one show that they are reporting to
the head.
4. OM History
As and when any record will be created in the SAP HCM system under OM module that record will be saved
in the system with particular start and end dates. If due to any reason some position or organization unit or
job is not required in the OM structure of the company and co. decided to obsolete those positions or
departments then just change the End Date of that particular object type, changing the End Date of any
object type is called Object Delimit concept in SAP.
No need to delete the particular object type because after deletion History of the particular object is not
possible to retrieve.
Page 26
Page 27
Page 28