SAP HR Configuration Pack

Organization Management

Published by Team of SAP

Consultants at SAPTOPJOBS Visit us at www.sap-topjobs.com

Copyright 2008-10@SAPTOPJOBS

All rights reserved. No part of this publication may be reproduced, stored in a

retrieval system, or transmitted in any form, or by any means electronic or mechanical including photocopying, recording or any information storage and retrieval system

without permission in writing from SAPTOPJOBS.

INDEX

1. INTRODUCTION 3

2. BUSINESS MODEL FOR CONFIGURATION 4

3. SETUP NUMBER ASSIGNMENT FOR ALL PLAN VERSIONS 8

3.1 Maintain Object Type 11

3.2 Maintain Info types 15

3.3 Maintain Subtypes 20

3.4 Maintain Country-Specific Info types 24

3.5 Relationship Maintenance 27

3.6 Maintain Evaluation Paths 32

3.7 Maintain Personnel Actions 34

4. ACTIVATE INHERITANCE OF ACCOUNT ASSIGNMENT FEATURES 37

5. SETUP TRANSPORT CONNECTION 38

6. SETUP INTEGRATION WITH PERSONNEL ADMINISTRATION 40

7. TRANSFER DATA FROM PERSONNEL ADMINISTRATION 43

8. PREPARE INTEGRATION WITH PERSONNEL ADMINISTRATION 46

9. TRANSFER DATA TO PERSONNEL ADMINISTRATION 48

10. CHECK INTEGRATION CONSISTENCY 50

11. SET UP INTEGRATION WITH COST ACCOUNTING 52

12. SET UP INTEGRATION FOR COST DISTRIBUTION 53

1. Introduction

This document explains configuration steps in Organizational Management covering configurations of

Object Types,

Info types

Relationships

Evaluation Paths

In order to carry out various business and human resources related transactions, it is mandatory to have an organizational plan.

Organizational plan is a functional structure representing any enterprise based on tasks. It can be used for

Evaluation

Activating Business workflow

Planning any department structure

Organizational Management is the base to use the following HR components

Personnel Development

Recruitment

Compensation Management

Personnel Cost Planning

Training and Event Management

Manager's Desktop

2. Business model for configuration

Before we go to the configuration, it is important that we must have an idea of what is the business model or requirement. Let us assume the required organizational structure to be of with following main objects:

Organizational Units

Jobs

Positions

Let us try to understand one by one.

Organizational Units (Object Type 0): - Organizational units will be used to represent the various Divisions and Departments. The following relationships and related object types will be assigned to organizational units:

• A/B 002

Represents the ‘Reports / is line supervisor of’ relationship. This relationship is assigned to the organizational unit which reports to another organizational unit.

• A/B 003

Represents the ‘Belongs to / incorporates’ relationship. This relationship assigns a position to the organizational unit.

For this relationship, the percentage functionality will be added in configuration to allow the assignment of one position to more than one organizational unit with different assignment of percentages.

• A/B 012 (Chief)

Represents the ‘Manages / is managed by’ relationship. This relationship is assigned to a position and it marks the head of the particular organizational unit.

The following records will be created for organizational units:

• Account Assignment Features (IT1008)

This is where the company code for the organizational unit will be stored for reporting purposes.

JOBS (OBJECT TYPE C)

Jobs will be created based on requirement. The following relationship and related object type will be assigned to jobs:

o A/B 007 Represents the ‘Describes / Is described by’ relationship. This relationship assigns jobs to

the related positions.

The following additional records will be created for jobs

o Planned Compensation (Infotype 1005) The jobs pay grade will be assigned in this screen for Compensation Management purposes.

o Composite Survey Result (Infotype 1271)

This is a new screen for Enterprise Compensation Management. If required, this screen will be used to store the salary survey results for jobs/positions

POSITIONS (OBJECT TYPE S) Positions will be created and assigned to organizational units. The following relationships and related object types will be assigned to positions:

o A/B 002 Represents the ‘Reports / is line supervisor of’ relationship. This relationship is assigned to the position which reports to another position at a higher level.

o A/B 003

Represents the ‘Belongs to / incorporates’ relationship. This relationship assigns a position to the organizational unit.

o A008 Represents the ‘Holder’ relationship. This relationship is created when a person is assigned to the position.

o A/B 012 Represents the ‘Manages / is managed by’ relationship. This relationship is assigned to a position and it marks the head of the particular organizational unit.

o A011 Represents the ‘Cost centre assignment’ relationship. This relationship assigns a cost centre to the position. As a basic rule, cost centers will be assigned at organizational unit level. They will only be maintained at position level when there are deviations from this rule.

The following additional records will be created for positions:

o Vacancy (Infotype 1007)

Each vacant position will automatically be assigned an ‘open’ flag. This enables the system to generate a list of vacant positions.

3. Setup Number assignment for all plan versions

BACKGROUND In this step, you specify whether number assignment is plan version- specific or plan version-independent, in other words, valid for all plan versions. This decision is important since it affects the kind of subgroups (number intervals) you may use. If you decide not to work with number assignment valid for all plan versions, you must create individual number intervals per plan version (and possibly also per object type). If you decide to use plan version- independent number assignment, you create number intervals that are valid for all plan versions. In this case, there is no danger of parallel number intervals occurring i.e. the same number interval for one object in one plan version and for a different object in another plan version.

SCENARIO Discuss number range assignment for all plan versions.

INSTRUCTIONS Follow the Menu Path: IMG Personnel Management Organizational Management Basic Settings Maintain Number Ranges Set Up Number Assignment for All Plan Versions Steps: 1. Enter 'X' in the field Value abbr. to activate number assignment for all plan versions. Leave the field Value abbr. blank to deactivate this function.

2. Save your entries.

3.1 Maintain Object Type

BACKGROUND This configuration setting enables to define the object type and to change the existing object type.

SCENARIO Create object type.

INSTRUCTION Follow the Menu Path: IMG Personnel Management

Organizational Management Basic Settings Data Model Enhancement > Maintain Object Type

To create New Object for Example Job Family Select the existing object types from which it is required to be copied

Click Maintain the object type. E.g. ZC in place of C

Click

Click

Click

Click

3.2 Maintain Info types

BACKGROUND In this step, you can make the changes to the infotypes. An infotype is a logical or a business related characteristics of an object.

SCENARIO The standard SAP delivered Infotype are used .Don’t change any settings unless needed 1. Change the name of the infotype, if required. 2. Check and, if necessary, change the time constraint of the info types or subtypes. 3. Assign the info types to object types. (Don’t delete any objects unless needed)

INSTRUCTIONS Follow the Menu Path: IMG Personnel Management Organizational Management Basic Settings Data Model Enhancement Infotype Maintenance Maintain Infotypes Click Select the desired info type. E.g. 1000

Infotype 1000 – Object Double click Maintain time constraint. E.g.1 to indicate without gaps. Other available entries are

Double click Note: - Tick in the check box will not allow to maintain the info type through basic transaction.

Click Click Infotype 1001 – Relationships Select infotype 1001

Double click to maintain time constraint Double click to maintain Alt. screen and maintenance control. Below few more info types are discussed for understanding.

Infotype 1005 – Planned Compensation

3.3 Maintain Subtypes

BACKGROUND This configuration setting enables to maintain subtypes. In either case, you have to assign a time constraint to both subtypes and info types. In this step, you maintain the settings necessary for creating subtypes for info types. You can create new subtypes for standard infotypes or for customer- specific info types

SCENARIO Steps: SAP Standard settings are maintained 1. Create further subtypes for infotype if required. 2. Append a time constraint to each subtype. Example: - Infotype Subtype 1001 Relationships A003 Belongs to 1001 Relationships B003 Incorporates 1050 Job Evaluation Results Job evaluation 1 1050 Job Evaluation Results National Evaluation 1 1050 Job Evaluation Results National Evaluation 2

INSTRUCTIONS Follow the Menu Path: IMG Personnel Management Organizational Management Basic Settings Data Model Enhancement Infotype Maintenance Maintain Subtypes Click

Select the desired row Double click

Maintain the time constraint Time Constraint

Field that contains the time constraint for each infotype or subtype. The time constraint determines how often records can be present at the same time. The system uses time constraints internally to ensure data integrity.

The values have the following meaning: Time Constraint 0 (May only exist once): Indicates, may only be present once. A maximum of one infotype record of the same type for the same object at the same time. No changes to the record are allowed. Time Constraint 1(without gaps): - It indicates

• A maximum of one infotype record of the same type for the same object at the same time.

• No gaps in time between valid records. • Changes to the record

Example: an object must always have a short name. This information must always be present, without gaps, but it can be changed. Time Constraint 2(with gaps): -

• A maximum of one infotype record of the same type for the same object at the same time.

• Gaps in time between valid records Example: a position can only have one Vacancy infotype record at a time. Time Constraint 3(Unlimited): -

• Several infotype records of the same type for the same object at the same time

• Gaps in time between valid records Example: all subtypes of infotype 1001 (Relationships) with the relationship direction top down (when delivered). For example, the Sales department can be related to several positions at the same time. Click

3.4 Maintain Country-Specific Info types

BACKGROUND In this activity, you specify that an infotype is only relevant for a particular country or countries, in other words, a country-specific Infotype. This determines whether an infotype is displayed via Country settings in basic transactions.

SCENARIO Steps: 1. Choose New Entries. 2. Enter an infotype. For Example for Enter US for IT 1610 3. Select the country indicator of the country you want to assign the infotype to. 4. Save your entries.

INSTRUCTIONS Follow the Menu Path: IMG Personnel Management Organizational Management Infotype Maintenance Maintain Country –Specific Info types Click

Click

Click to maintain new country specific info types.

Click Click

Impact of this configuration in Master Data / Transaction Country specific Infotypes are shown in PP01 respective countries only.

3.5 Relationship Maintenance

BACKGROUND In this step, you make the settings that are required for creating relationships. By creating relationships between objects, you can display all the structures that exist in Personnel Management. Relationships are special subtypes of infotype 1001. Each relationship has two relationship types, indicated by A and B. For each relationship created (A or B), the corresponding inverse relationship is automatically set up.

SCENARIO Discuss relationship maintenance

INSTRUCTIONS Follow the Menu Path: IMG Personnel Management Organizational Management Basic Settings Data Model Enhancement Relationship Maintenance Maintain Relationship Click

Select the identical one to Create Custom Relation. E.g. 006

Click Maintain the entries as shown below as required by the business.

Click

It will copy all relationships and Objects link to relation ship link to 003 Select the newly created relationship ZAA Double click To Custom Object ZC (Job family) to the relate to C(Job) Select the job C Click

Maintain the entries as shown below

Click

Click

Click

3.6 Maintain Evaluation Paths

BACKGROUND In this step, you create the evaluation paths you require. An evaluation path is an instruction to the system which determines which object types and relationship(s) are to be included in an evaluation of your organizational plan. One or more relationships are then used as "Navigation paths" for evaluating structural information in your organizational plan (relating to the organizational or reporting structures) or matrix organization. The sequence of the relationships included in the evaluation path is decisive in how the results of the evaluation are displayed.

SCENARIO Example: - Evaluation path "Staff assignments along organizational structure" (SBESX): No Object

Type A/B Relationship Priority Type Rel.Object

skip 010 O B * S x 020 S A * P 030 O B * O First of all in this evaluation path, the positions assigned (S) to an organizational unit (O) are determined, then, the holder (P) assigned to each position is determined. As well as this, the next organizational unit down in the organizational structure is determined; the above procedure then takes place for this organizational unit. This procedure is repeated for all further subordinate organizational units.

INSTRUCTIONS Follow the Menu Path: IMG Personnel Management Organizational Management Basic Settings Maintain Evaluation Paths Click

Impact of this configuration in Master Data / Transaction Various organizational structure reports are generated through evaluation paths

3.7 Maintain Personnel Actions

BACKGROUND In this step, you make the system settings necessary for setting up a personnel action. A personnel action is a collection of several logically connected infotypes in the systems which, in an exact sequence, is used for processing and are used for a particular system activity (see "Create Organizational Unit", for example). Personnel actions are identified by a key.

SCENARIO Assign the following to each step of a personnel action:

A plan version An object type An infotype or subtype A status Default values for screen entry

Discuss the standard setting

INSTRUCTIONS Follow the Menu Path: IMG Personnel Administration Organizational Management Basic Settings Maintain Personnel Actions Click Select the desired row. E.g. O Double click

This action is necessary to create Positions The Info types 1000, 1002, 1003, and 1001 with relationship A011 with object types O, K are used for This Action

Double click Press page down to scroll down the screen and note the details.

Impact of this configuration in Master Data / Transaction PQ10 uses action “O” to create Organizational units.

4. Activate Inheritance of Account Assignment Features

BACKGROUND In this step, you can determine that account assignment features (controlling area, company code and business area) of organizational units are to be inherited by subordinate positions.

SCENARIO To activate inheritance, enter an 'X'

INSTRUCTIONS Follow the Menu Path: IMG Personnel Administration Organizational Management Basic Settings Activate Inheritance of account assignment features Click

Click

Impact of this configuration in Master Data / Transaction Infotype 008 will defaults controlling area

5. Setup Transport Connection

BACKGROUND In this step, you specify which type of transport connection you wish to use to transport Personnel Planning objects from the Customizing client. There are three possible transport options (Option 3 recommended) Automatic transport connection ( “ “ Blank) With the automatic transport connection, a dialog box always appears after you create, change, or delete objects asking you to assign the object to a transport request or to create a new request. Transport via object lock (repair flag) (T ) If you decide to use the object lock option, there is no automatic query regarding a transport request. However, you can use the report RHMOVE50 (Transport of objects using object lock) to transport any objects that were changed. No automatic transport connection (automatic transport connection is deactivated) (“X”) If you decide not to use the automatic transport connection, there is no automatic query regarding a transport request when you create, change or delete an object. This means that you have transport the changed objects yourself. You do so with the report RHMOVE30 (Manual Transport)

You have to enter the objects to be transported yourself, which means that you have to ensure that all changed objects have been transported.

SCENARIO Discuss the setup transport connection

INSTRUCTIONS Follow the Menu Path: IMG Personnel Administration Organizational Management Basic Settings Setup Transport Connection Click

Click

6. Setup Integration with Personnel Administration

BACKGROUND In this step, you activate integration between Organizational Management and HR Master Data in Personnel Administration. This guarantees data consistency between the two components. (Press F1 to read SAP help)

SCENARIO Discuss the integration with personnel administration setup.

INSTRUCTIONS Follow the Menu Path: IMG Personnel Administration Organizational Management Basic Settings Integration Setup Integration with Personnel Administration Click

In the standard system, the switch &PLOGI is set to "X" (all).

Impact of this configuration in Master Data / Transaction T77S0 is major table for OM/PA integration. In hiring process if employee doesn’t have position the action defaults 99999999

7. Transfer Data from Personnel Administration

BACKGROUND In this step, you can copy the objects and relationships set up in Personnel Administration into Organizational Management using the report RHINTE00. This program reads the objects of infotype 0001 "Organizational Assignment" which were created in Personnel Administration. On this basis, the following records are created in Organizational Management. As a prerequisite, you must have selected the "Create objects" or "Create objects" and "Create relationships" parameters in report RHINTE00.

SCENARIO Discuss the data transfer in PA

INSTRUCTIONS Follow the Menu Path: IMG Personnel Administration Organizational Management Basic Settings>Integration Transfer Data from Personnel Administration Click Perform the following Steps: 1. Start the program WITHOUT creating a batch input session. 2. If personnel numbers were found that are not assigned to a position, correct these by

a) Deactivating the integration switch in the Set Up Integration with Personnel Administration step (entry PLOGI ORGA). b) Correcting the data for the persons concerned.

Make sure that all persons are assigned to a position or to a work center.

3. Activate integration again (see 2.a). 4. Start the program RHINTE00 again, this time WITH creation of a batch input session. This session can be started automatically or manually

Impact of this configuration in Master Data / Transaction RHITE00 is major report transfer data PA to OM

8. Prepare Integration with Personnel Administration

BACKGROUND In this step, you can transfer objects created in Organizational Management into Personnel Administration tables using report RHINTE10. In doing this, you fulfil the prerequisite for writing data from Personnel Administration tables to the "Organizational Assignment" infotype using report RHINTE30.

SCENARIO The following object types are relevant for integration: Organizational Management Personnel Administration Work centre (Object type A) Tables T528B, T528T Job (Object type C) Tables T513, T513S Position (Object type S) Tables T528B, T528T Org.unit (Object type O) Table T527X

INSTRUCTIONS Follow the Menu Path: IMG Personnel Administration Organizational Management Basic Settings Integration Prepare Integration with Personnel Administration

Impact of this configuration in Master Data / Transaction RHITE10 is major report populate OM data into PA Tables

9. Transfer Data to Personnel Administration

BACKGROUND In this step, you can use report RHINTE30 to update the "Organizational Assignment" infotype (0001) for the personnel number you have selected with the data generated in previous Organizational Management actions. The report creates a batch input folder for the personnel number, which is updated from the "Organizational Assignment" infotype for the person. The organizational assignment determined in Organizational Management using organizational objects, positions, jobs, work centers and cost centers is transferred into infotype 0001.

SCENARIO Discuss the data transfer to PA

INSTRUCTIONS Follow the Menu Path: IMG Personnel Administration Organizational Management Basic Settings Integration Transfer Data to Personnel Administration

Impact of this configuration in Master Data / Transaction RHINTE30 is major report which will update IT0001 with OM data like Cost center, Position, Job, Org unit

10. Check Integration Consistency

BACKGROUND In this step, you use report RHINTE20 to determine whether data for objects relevant to integration is available in both Personnel Administration and Organizational Management. Entries in the following tables (Personnel Administration) are compared to the corresponding objects created in file HR Plan in the integration plan version (Organizational Management).

SCENARIO Discuss the process of integration consistency

INSTRUCTIONS Follow the Menu Path: IMG Personnel Administration Organizational Management Basic Settings Integration Check Integration Consistency Click

11. Set Up Integration with Cost Accounting

BACKGROUND In this step, you set the controlling area that is used as a default value for Cost Accounting. If you create relationships between cost centers and positions or organizational units, the system asks you to assign the cost center to a controlling area (cost centers are always assigned to a controlling area). In such cases, the value you define in this step is used as the default

SCENARIO Discuss the integration with cost accounting setup

INSTRUCTIONS Follow the Menu Path: IMG Personnel Administration Organizational Management Basic Settings Set Up Integration with Cost Accounting Click

Impact of this configuration in Master Data / Transaction Controlling area will defaults in IT1008 and Inherit down the Org. Structure

12. Set Up Integration for Cost Distribution

BACKGROUND The PLOGI COSTD entry enables you to activate integration between Organizational Management and Personnel Administration for Cost Distribution.

SCENARIO Discuss the standard settings.

INSTRUCTIONS Follow the Menu Path: IMG Personnel Administration Organizational Management Basic Settings Integration Set Up Integration for Cost Distribution

Impact of this configuration in Master Data / Transaction It will activate IT0027& 1018 if the value X.

SAP HR Configuration Pack

Organization Management

Published by Team of SAP

Consultants at SAPTOPJOBS Visit us at www.sap-topjobs.com

Copyright 2008-10@SAPTOPJOBS

All rights reserved. No part of this publication may be reproduced, stored in a

retrieval system, or transmitted in any form, or by any means electronic or mechanical including photocopying, recording or any information storage and retrieval system

without permission in writing from SAPTOPJOBS.