Post on 30-Oct-2015
description
7/15/2019 QP Mobile Pass V1.0 12April 13
http://slidepdf.com/reader/full/qp-mobile-pass-v10-12april-13 1/30
EHP5 for SAP ERP 6.0
September 2011
English
Maintain Company
OrganizationalStructures (560)
SAP AGDietmar-Hopp-Allee 1669190 Walldorf Germany
Business Process Documentation
7/15/2019 QP Mobile Pass V1.0 12April 13
http://slidepdf.com/reader/full/qp-mobile-pass-v10-12april-13 2/30
SAP Best Practices Maintain Company Organizational Structures (560): BPD
Copyright
© 2011 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed
without prior notice. Some software products marketed by SAP AG and its distributors contain proprietarysoftware components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, Systemz10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390,OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6,POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS,HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner,WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of
Adobe Systems Incorporated in the United States and/or other countries.
Oracle and Java are registered trademarks of Oracle.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide WebConsortium, Massachusetts Institute of Technology.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAPHANA, and other SAP products and services mentioned herein as well as their respective logos are trademarksor registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, WebIntelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objectsis an SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and servicesmentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc.Sybase is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Datacontained in this document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated
companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, andSAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAPGroup products and services are those that are set forth in the express warranty statements accompanyingsuch products and services, if any. Nothing herein should be construed as constituting an additional warranty.
© SAP AG Page 2 of 30
7/15/2019 QP Mobile Pass V1.0 12April 13
http://slidepdf.com/reader/full/qp-mobile-pass-v10-12april-13 3/30
SAP Best Practices Maintain Company Organizational Structures (560): BPD
Icons
Icon Meaning
Caution
Example
Note
Recommendation
Syntax
External Process
Business Process Alternative/Decision Choice
Typographic Conventions
Type Style Description
Example text Words or characters that appear on the screen. These include field names,screen titles, pushbuttons as well as menu names, paths, and options.
Cross-references to other documentation.
Exampletext
Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLETEXT
Names of elements in the system. These include report names, programnames, transaction codes, table names, and individual key words of aprogramming language, when surrounded by body text, for example, SELECTand INCLUDE.
Example
textScreen output. This includes file and directory names and their paths,messages, source code, names of variables and parameters as well as names
of installation, upgrade and database tools.
EXAMPLE TEXTKeys on the keyboard, for example, function keys (such as F2) or the ENTER key.
Example
textExact user entry. These are words or characters that you enter in the systemexactly as they appear in the documentation.
<Example
text> Variable user entry. Pointed brackets indicate that you replace these words andcharacters with appropriate entries.
© SAP AG Page 3 of 30
7/15/2019 QP Mobile Pass V1.0 12April 13
http://slidepdf.com/reader/full/qp-mobile-pass-v10-12april-13 4/30
SAP Best Practices Maintain Company Organizational Structures (560): BPD
Contents
Maintain Company Organization Structures...................................................................................... .5
1 Purpose ........................................................................................................................................... 5
2 Prerequisites.....................................................................................................................................5
2.1 Master Data and Organizational Data........................................................................................ 5
2.2 Business Conditions ..................................................................................................................6
2.3 Preliminary Steps....................................................................................................................... 7
2.4 Roles.......................................................................................................................................... 7
3 Process Overview............................................................................................................................. 9
4 Process Steps.................................................................................................................................10
4.1 Create Organizational Unit (via Actions).................................................................................. 10
4.2 Create Job (via Actions)........................................................................................................... 14
4.3 Create Position (via Actions)....................................................................................................17
4.4 Maintain Organizational Unit (Expert Mode).............................................................................21
4.5 Maintain Job (Expert Mode)..................................................................................................... 22
4.6 Maintain Position (Expert Mode).............................................................................................. 23
4.7 Change Organization and Staffing........................................................................................... 24
© SAP AG Page 4 of 30
7/15/2019 QP Mobile Pass V1.0 12April 13
http://slidepdf.com/reader/full/qp-mobile-pass-v10-12april-13 5/30
SAP Best Practices Maintain Company Organizational Structures (560): BPD
Maintain Company Organization Structures
1 PurposeThis scenario describes the typical processes used when updating the organizational structure, for example, creating new position for hiring or change of position from one organizational unit toanother for transfer.
2 Prerequisites
2.1 Master Data and Organizational Data
You have entered the master data required to go through the procedures of this scenario. Ensure
that the following scenario-specific master data exists before you test this scenario:
Organizationentity
Value Description
OrganizationalUnits
O 10001000 -10001010
US organizational units created as part of master data load
Jobs C 10002000 -10002043
US jobs created as part of master data load
Positions S 10003000 -10003031
US jobs created as part of master data load
To run through this scenario, the organizational unit and the reporting structure of the organizationalunits and positions must be created.
Use existing sample data to execute the creation of a new position and change of position. Thenumber ranges are set to allow users to search and find positions, jobs, org. units, and so on, easier.
When working with the SAP Best Practices for HCM, an enterprise structure is predefined as follows:
• The Enterprise Structure is designed to support one of two types of companies (that
is, personnel structures): Functional based and Region/Location based.
• In the first structure (1001-1003 series) the company consists of a main
Headquarters group and two lines of business. This structure is primarily for thosecompanies who wish to group employees for reporting purposes based on functionwithin the company.
Personnel Area Personnel Subarea
1001 Headquarters 1002 Human Resources
1003 Finance
1006 Operations
1007 Manufacturing
© SAP AG Page 5 of 30
7/15/2019 QP Mobile Pass V1.0 12April 13
http://slidepdf.com/reader/full/qp-mobile-pass-v10-12april-13 6/30
SAP Best Practices Maintain Company Organizational Structures (560): BPD
Personnel Area Personnel Subarea
1008 Sales/Marketing
1009 Research & Dev.
1011 Field Support
1012 Inform Tech
1002 Product ‘A’ 1006 Operations
1007 Manufacturing
1008 Sales/Marketing
1009 Research & Dev.
1003 Product ‘B’ 1013 Plant ‘A’
1014 Plant ‘B’
The second structure (1004-1008 series) is for those companies who wish to group employeesbased on location.
Personnel Area Personnel Subarea
1004 Region – North 1010 City 1
1015 Union A
1020 City 2
1005 Region – South 1015 Union A
1110 City 3
1120 City 41006 Region - East 1015 Union A
1016 New York
1017 Washington D.C.
1007 Region - Central 1015 Union A
1018 Chicago
1019 New Orleans
1008 Region - West 1015 Union A
1021 San Francisco
1022 Denver Site
2.2 Business Conditions
The business process described in this Business Process Procedure is part of a bigger chain of integrated business processes. Completion and receipt of a Personnel Change Request and/or budget approval is typically required before changes to existing organizational structure.
© SAP AG Page 6 of 30
7/15/2019 QP Mobile Pass V1.0 12April 13
http://slidepdf.com/reader/full/qp-mobile-pass-v10-12april-13 7/30
SAP Best Practices Maintain Company Organizational Structures (560): BPD
2.3 Preliminary Steps
Certain infotypes within Organizational Management are country-specific. This section describes thenecessary steps to ensure those infotypes, specific to your country, are able to be maintained or displayed.
2.3.1 Enabling Country-Specific Infotypes
Use
In this step, you define the settings to display or maintain country-specific infotypes related to theJob object. These same steps can be followed to enable country-specific infotypes for theOrganizational Unit and Position objects using transaction codes PO10 and PO13 respectively.
Procedure
1. Access the transaction using the following navigation options:
SAP Graphical User Interface (SAP GUI)
SAP menu Human Resources Organizational Management Expert Mode
Job
Transactioncode
PO03
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
Business role Administrator (HCM) (SAP_NBPR_ADMIN_HCM_M)
Business rolemenu
Human Resources Organizational Structure Maintain Job
(PO03)
2. From the More Actions menu, choose Settings → Country-Specific Infotypes.
3. Choose the For the following countries button.
4. Enter the specific country codes (for example US for USA).
5. Choose Transfer (Enter).
Result
The list of US country-specific infotypes should now be displayed.
2.4 Roles
Use
The following roles must have already been installed to test this scenario in the SAP NetWeaver Business Client (NWBC). The roles in this Business Process Procedure must be assigned to theuser or users testing this scenario. You only need these roles if you are using the NWBC interface.You do not need these roles if you are using the standard SAP GUI.
Prerequisites
The business roles have been assigned to the user who is testing this scenario.
© SAP AG Page 7 of 30
7/15/2019 QP Mobile Pass V1.0 12April 13
http://slidepdf.com/reader/full/qp-mobile-pass-v10-12april-13 8/30
SAP Best Practices Maintain Company Organizational Structures (560): BPD
Business role Technical name Process step
Administrator (HCM) SAP_NBPR_ADMIN_HCM_M All
© SAP AG Page 8 of 30
7/15/2019 QP Mobile Pass V1.0 12April 13
http://slidepdf.com/reader/full/qp-mobile-pass-v10-12april-13 9/30
SAP Best Practices Maintain Company Organizational Structures (560): BPD
3 Process Overview
Process step Externalprocessreference
Business condition Businessrole
Trans-actioncode
Expectedresults
CreateOrganizationalUnit (via
Actions)
_ Request for newDepartment/OrganizationalUnit
Administrator (HCM)
PQ10 OrganizationalUnit objectandassociatedinfotypes arecreated.
Create Job (via Actions)
_ Request for new Jobcategory
Administrator (HCM)
PQ03 Job object andassociatedinfotypes are
created.
Create Position(via Actions)
_ Request for new Position Administrator (HCM)
PQ13 Position objectandassociatedinfotypes arecreated.
Create/MaintainOrganizationalUnit (ExpertMode)
_ Request for newDepartment/OrganizationalUnit
Administrator (HCM)
PO10 OrganizationalUnit object iscreated.
Create/Maintain
Job (ExpertMode)
_ Request for new Job
category
Administrato
r (HCM)
PO03 Job object is
created.
Create/MaintainPosition (ExpertMode)
_ Request for new Position Administrator (HCM)
PO13 Position objectis created.
ChangeOrganizationand Staffing
_ Request for changes toOrganizational Structure or Staffing
Administrator (HCM)
PPOME Changes toexistingorganizationalhierarchy andstaffing arecomplete.
© SAP AG Page 9 of 30
7/15/2019 QP Mobile Pass V1.0 12April 13
http://slidepdf.com/reader/full/qp-mobile-pass-v10-12april-13 10/30
SAP Best Practices Maintain Company Organizational Structures (560): BPD
4 Process Steps
4.1 Create Organizational Unit (via Actions)
Use
In this activity, you request a new Department/Organizational Unit.
Prerequisites
If the newly-created Organization Unit reports to another Organizational Unit within the structure, thereports to Organizational Unit must already exist.
If defining a cost center to the Organizational Unit, the cost center must already have been createdwithin the FI/CO modules.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC Menu Human Resource Organizational Management Tools Object
Actions
Transactioncode
PP03 or PQ10
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
Business role Administrator (HCM) (SAP_NBPR_ADMIN_HCM_M)
Business rolemenu
Human Resources Organizational Structure Maintain Plan Data
(Action-Based) or Actions for Organizational Unit
2. On the Actions for Organizational Unit screen, make the following entries:
Field name Description User action and values
Plan Version Plan version Defaults to 01
Object Type Object type Field appears only when usingtransaction PP03.
Enter O – Organizational Unit
Object ID or
Organizational Unit
Object number of the
organizational unit
Leave blank, system automatically
assigns a new object idPlanning or InfotypeStatus
Planning status of theorganizational unit
Defaults to Active
Validity Validity dates of the object Enter the begin and end dates of the object
Action Action code Enter YO – Create OrganizationalUnits
© SAP AG Page 10 of 30
7/15/2019 QP Mobile Pass V1.0 12April 13
http://slidepdf.com/reader/full/qp-mobile-pass-v10-12april-13 11/30
SAP Best Practices Maintain Company Organizational Structures (560): BPD
3. Choose the Execute button to proceed to the first Infotype 1000 Create Object.
4. On the Create Object (Infotype 1000) screen, enter the following data:
Field name Description User action and values
OrganizationalUnit Abbreviated name of theorganizational unit Field is blank when creating an object
Planning Status Planning status of organizational unit
Defaults to Active
Valid from Validity dates of the object Defaults to dates defined on theprevious screen, but can be changed
Object Abbreviation
Abbreviated name of theorganizational unit
Enter the abbreviated name of theorganizational unit
Object Name Full name of theorganizational unit
Enter the full name of the organizationalunit
Language Key Language Defaults to EN - English
5. Save your entries. The system accepts the data, assigns an object ID, and advances you to thenext infotype in the Action: Essential relationship Relationships (I1001).
6. On the Essential relationship Relationships (Infotype 1001) screen, enter the following data:
Field name Description User action and values
Organizational Unit Abbreviated name of theorganizational unit
Defaults abbreviatedname of the organizationalunit
Planning Status Planning status of organizational unit Defaults to Active
Valid from Validity dates of the object Defaults to dates defined
on the previous screen,but can be changed
RelationshipType/Relationship
A code that represents a particular type of a relationship.
Defaults to A002
Type of relatedobject
Object type of the related object Defaults to OrganizationalUnit
ID of related object Object ID of the related object Object id of theorganizational unit thisorg. unit reports to
Abbreviation Abbreviated object name Leave blank, defaultsbased on the related
object idName Full object name Leave blank, defaults
based on the relatedobject id
Priority Optional field used to determine thesequence in which objects arepresented in Simple Maintenance andStructural Graphics
Optional
© SAP AG Page 11 of 30
7/15/2019 QP Mobile Pass V1.0 12April 13
http://slidepdf.com/reader/full/qp-mobile-pass-v10-12april-13 12/30
SAP Best Practices Maintain Company Organizational Structures (560): BPD
7. Save your entries. The system accepts the data and advances you to the next infotype in the Action: Create Description (I1002).
8. On the Create Description (Infotype 1002) screen, enter the following data:
Field name Description User action and values
OrganizationalUnit
Abbreviated name of theorganizational unit
Defaults abbreviated name of theorganizational unit
Planning Status Planning status of organizational unit
Defaults to Active
Valid from Validity dates of the object Defaults to dates defined on theprevious screen, but can be changed
Subtype A code that represents aparticular type of description
Defaults to General Description
Language Language of the description Defaults to English
Description Description of the object Enter the detailed description of the
object
9. Save your entries. The system accepts the data and advances you to the next infotype in the Action: Create Relationships (I1001).
10. On the Create Relationships (Infotype 1001) screen, enter the following data:
Field name Description User action and values
Organizational Unit Abbreviated name of theorganizational unit
Defaults abbreviatedname of theorganizational unit
Planning Status Planning status of organizational unit Defaults to Active
Valid from Validity dates of the object Defaults to dates definedon the previous screen,but can be changed
RelationshipType/Relationship
A code that represents a particular type of a relationship.
Defaults to A011 – Costcenter assignment
Type of relatedobject
Object type of the related object Defaults to - Cost Center
ID of related object Object ID of the related object Select the responsiblecost center number for this org. unit
Abbreviation Abbreviated object name Leave blank, defaultsbased on the relatedobject id
Name Full object name Leave blank, defaultsbased on the relatedobject id
Priority Optional field used to determine thesequence in which objects arepresented in Simple Maintenance andStructural Graphics
Optional
© SAP AG Page 12 of 30
7/15/2019 QP Mobile Pass V1.0 12April 13
http://slidepdf.com/reader/full/qp-mobile-pass-v10-12april-13 13/30
SAP Best Practices Maintain Company Organizational Structures (560): BPD
Weighting A percentage that is used to weightthe assignment of one or moreobjects
Field appears only whenusing transaction PP03.
Enter 100
11. Save your entries. The system accepts the data and advances you to the next infotype in the
Action: Create Relationships (I1001).
12. On the Create Relationships (Infotype 1001) screen, enter the following data:
Field name Description User action and values
OrganizationalUnit
Abbreviated name of theorganizational unit
Defaults abbreviated name of theorganizational unit
Planning Status Planning status of organizational unit
Defaults to Active
Valid from Validity dates of the object Defaults to dates defined on theprevious screen, but can be changed
Cost Center Cost center Defaults based on cost center definedon previous screen
13. Save your entries.
14. Make the following entry:
Field name Description User action and values
CO Area Controlling area of the cost center Enter 1000
15. Save your entries. The system accepts the data and advances you to the next infotype in the Action: New Entries: Details of Added Entries (I1612).
16. On the New Entries: Details of Added Entries (Infotype 1612) screen, enter the following data:
Field name Description User action and values
Organizational Unit Object number of theorganizational unit
Defaults object id of theorganizational unit
Periods Validity periods for thisinfotype
<begin and end dates for workerscompensation>
Workers’Compensation State
Workers’ CompensationState
<state>
Workers’Compensation Code
Workers’ CompensationCode
<compensation code>
17. Save your entries. The system accepts the data.
18. Choose the Cancel button. The system advances you to the next infotype in the Action: WC:Definition of WC to Organizational Unit Overview (I1612).
19. Choose the Cancel button. The system returns you to the start of the PQ10 transaction. Exitfrom here or create another Organizational Unit.
Result
Organizational Unit object and associated infotypes are created.
© SAP AG Page 13 of 30
7/15/2019 QP Mobile Pass V1.0 12April 13
http://slidepdf.com/reader/full/qp-mobile-pass-v10-12april-13 14/30
SAP Best Practices Maintain Company Organizational Structures (560): BPD
4.2 Create Job (via Actions)
Use
In this activity, you request a new Job object.
Prerequisites
If the Planned Compensation infotype (1005) is created for the job, pay scale/grade information mustbe configured before creating the Planned Compensation infotype.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC Menu Human Resource Organizational Management Tools Object
Actions
Transactioncode
PP03 or PQ03
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
Business role Administrator (HCM) (SAP_NBPR_ADMIN_HCM_M)
Business rolemenu
Human Resources Organizational Structure Maintain Plan Data
(Action-Based) or Actions for job
2. On the Actions for Job screen, make the following entries:
Field name Description User action and values
Plan Version Plan version Defaults to 01
Object Type Object type Field appears only when using transactionPP03.
Enter C - Job
Object ID or Job Object number of the job
Leave blank, system automatically assignsa new object id
Object Name Name of job Leave blank
Planning or InfotypeStatus
Planning status of the job
Defaults to 1 - Active
Validity Validity dates of theobject
Enter the begin and end dates of theobject
Action Action code Select value YC from the dropdown list
3. Choose the Execute button to proceed to the first Infotype 1000 Create Object.
4. On the Create Object (Infotype 1000) screen, enter the following data:
Field name Description User action and values
Job Abbreviated name of the job
Field is blank when creating an object
© SAP AG Page 14 of 30
7/15/2019 QP Mobile Pass V1.0 12April 13
http://slidepdf.com/reader/full/qp-mobile-pass-v10-12april-13 15/30
SAP Best Practices Maintain Company Organizational Structures (560): BPD
Planning Status Planning status of the job
Defaults to Active
Valid from Validity dates of theobject
Defaults to dates defined on the previousscreen, but can be changed
Object Abbreviation
Abbreviated name of the job
Enter the abbreviated name of the job
Object Name Full name of the job Enter the full name of the job
Language Key Language Defaults to - English
5. Save your entries. The system accepts the data, assigns an object ID, and advances you to thenext infotype in the Action: Create Planned Compensation (I1005).
6. On the Planned Compensation (Infotype 1005) screen, enter the following data:
Fieldname
Description User action and values
Job Abbreviated name of the job Defaults abbreviated name of the job
PlanningStatus
Planning status of organizational unit Defaults to Active
Valid from Validity dates of the object Defaults to dates defined onthe previous screen, but canbe changed
Pay Grade:
Use this tab when defining annual salariesto a job
CountryGrouping
Identifies the country code of the pay gradeinformation
Select USA
Pay GradeType
Distinguishes between the different typesof pay grade structures
<pay grade type>
Pay Grade Area
Distinguishes logical regions within a salarystructure
<pay grade area>
Valid values are:01,02,05,06,09 or 10
Pay Grade Groups similar jobs for employeecompensation
<pay grade>
Pay GradeLevel
Defines the salary range within the paygrade. Each level has a minimum and amaximum amount
<pay grade level>
Key Datefor Display
Date for display salary amounts effectiveon a specific date
Defaults to system date, butcan be overwritten
Pay Scale: Use this tab when defining hourly rates of pay to a job
CountryGrouping
Identifies the country code of the pay gradeinformation
USA
Pay ScaleType
Distinguishes between the different typesof pay scale structures
<pay scale type>
© SAP AG Page 15 of 30
7/15/2019 QP Mobile Pass V1.0 12April 13
http://slidepdf.com/reader/full/qp-mobile-pass-v10-12april-13 16/30
SAP Best Practices Maintain Company Organizational Structures (560): BPD
Pay Scale Area
Distinguishes logical regions within a payrate structure
<pay scale area>
Use values01,02,05,06,07,08,09 or 10.
ESG for CAP
An employee subgroup grouping for collective agreement provisions combinessubgroups that are governed by the samevalid collective agreement provisions
<employee subgroup>
Pay ScaleGroup
Criterion used for grading job evaluation. Apay scale group is divided up into severalpay scale levels
<pay scale group>
Pay ScaleLevel
Criterion for job evaluation within the payscale group
<pay scale level>
Key Datefor Display
Date for display hourly rates effective on aspecific date
Defaults to system date, butcan be overwritten
Time Unit Determines which unit of time is used tocalculate/display amounts in compensationadministration
<time unit>
Direct: Use this tab when defining specificrates/amounts of pay to a job
CurrencyKey
Currency code USD
Amount Specific range of amounts per time unit <minimum and maximumamounts>
Time unit Determines which unit of time is used tocalculate/display amounts in compensationadministration
<time unit>
7. Save your entries. The system accepts the data and advances you to the next infotype in the Action: Infotype 1610: US Job Attributes: Details (I1610).
8. On the Infotype 1610: US Job Attributes: Details (Infotype 1610) screen, enter the following data:
Fieldname
Description User action and values
Job Object ID and abbreviated name of the job
Defaults abbreviated name andID of the job
Periods Validity dates of the job attributes Dates default based on theperiod start and end date of the
job object
EEOCategory
Holds the code that corresponds to aparticular job category
Select the EEO Category
AAPCategory
Contains the Affirmative Action Planningcategory to be assigned to a job
Select the AAP Category if applicable
OCC Holds the Occupational Classification Leave blank
© SAP AG Page 16 of 30
7/15/2019 QP Mobile Pass V1.0 12April 13
http://slidepdf.com/reader/full/qp-mobile-pass-v10-12april-13 17/30
SAP Best Practices Maintain Company Organizational Structures (560): BPD
Category Code that can be assigned to an EEOcategory
FLSAIndicator
Classifies a job as being exempt or non-exempt
Select Exempt or Non-Exemptbutton
9. Save your entries. The system accepts the data.
10. Choose the Cancel button. The system advances you to the next infotype in the Action:Infotype 1610: US Job Attributes: Overview (I1610).
11. Choose the Cancel button. The system returns you to the start of the PQ03 transaction. Exitfrom here or create another Job.
Result
Job object and associated infotypes are created.
4.3 Create Position (via Actions)
Use
In this activity, you request a new position.
Prerequisites
To create the Account Assignment Features infotype (1008) and/or the Employee Group/Subgroupinfotype (1013), the Enterprise Structure must have been configured.
If any Job object is associated with a Position, the Job must exist before creating this relationship.
The Organizational Unit to which this position reports must exist.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC Menu Human Resource Organizational Management Tools Object
Actions
Transactioncode
PP03 or PQ13
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
Business role Administrator (HCM) (SAP_NBPR_ADMIN_HCM_M)
Business rolemenu
Human Resources Organizational Structure Maintain Plan Data
(Action-Based) or Actions for Position
2. On the Actions for Job screen, make the following entries:
Field name Description User action and values
Plan Version Plan version Defaults to 01
Object Type Object type Field appears when using transactionPP03 or via NWBC
© SAP AG Page 17 of 30
7/15/2019 QP Mobile Pass V1.0 12April 13
http://slidepdf.com/reader/full/qp-mobile-pass-v10-12april-13 18/30
SAP Best Practices Maintain Company Organizational Structures (560): BPD
Enter S - Position
Object ID or Position
Object number of theposition
Leave blank, system automaticallyassigns a new object id
Object Name Name of position Leave blank
Planning or InfotypeStatus
Planning status of theposition
Defaults to 1 - Active
Validity Validity dates of theobject
Enter the begin and end dates of theobject
Action Action code Select value YS from the dropdown list
3. Choose the Execute button to proceed to the first Infotype 1000 Create Object.
4. On the Create Object (Infotype 1000) screen, enter the following data:
Field name Description User action and values
Position Abbreviated name of
the position
Field is blank when creating an object
Planning Status Planning status of theposition
Defaults to Active
Valid from Validity dates of theobject
Defaults to dates defined on the previousscreen, but can be changed
Object Abbreviation
Abbreviated name of the position
Enter the abbreviated name of the position
Object Name Full name of theposition
Enter the full name of the position
Language Key Language Defaults to English
5. Save your entries. The system accepts the data, assigns an object ID, and advances you to thenext infotype in the Action: Essential relationship Relationships (I1001).
6. On the Essential relationship Relationships (Infotype 1001) screen, enter the following data:
Field name Description User action and values
Position Abbreviated name of the position Defaults abbreviatedname of the position
Planning Status Planning status of position Defaults to Active
Valid from Validity dates of the object Defaults to dates definedon the previous screen,but can be changed
RelationshipType/Relationship
A code that represents a particular type of a relationship.
Defaults to A003
Type of relatedobject
Object type of the related object Defaults to OrganizationalUnit
ID of related object Object ID of the related object Object id of theorganizational unit thisposition belongs to
© SAP AG Page 18 of 30
7/15/2019 QP Mobile Pass V1.0 12April 13
http://slidepdf.com/reader/full/qp-mobile-pass-v10-12april-13 19/30
SAP Best Practices Maintain Company Organizational Structures (560): BPD
Abbreviation Abbreviated object name Leave blank, defaultsbased on the relatedobject id
Name Full object name Leave blank, defaults
based on the relatedobject id
Priority Optional field used to determine thesequence in which objects arepresented in Simple Maintenanceand Structural Graphics
Optional
7. Save your entries. The system accepts the data and advances you to the next infotype in the Action: Create Description (I1002).
8. On the Create Description (Infotype 1002) screen, enter the following data:
Field name Description User action and values
Position Abbreviated name of theposition
Defaults abbreviated name of theposition
PlanningStatus
Planning status of position Defaults to Active
Valid from Validity dates of the object Defaults to dates defined on theprevious screen, but can be changed
Subtype A code that represents aparticular type of description
Defaults to General Description
Language Language of the description Defaults to - English
Description Description of the object Enter the detailed description of theobject
9. Save your entries. The system accepts the data and advances you to the next infotype in the Action: Create Relationships (I1001).
10. On the Create Relationships (Infotype 1001) screen, enter the following data:
Field name Description User action and values
Position Abbreviated name of the position Defaults abbreviatedname of the position
Planning Status Planning status of position Defaults to Active
Valid from Validity dates of the object Defaults to dates definedon the previous screen,but can be changed
RelationshipType/Relationship
A code that represents a particular type of a relationship.
Defaults to B007 – isdescribed by
Type of relatedobject
Object type of the related object Defaults to Job
ID of related object Object ID of the related object Job ID that describes thisposition.
Abbreviation Abbreviated object name Leave blank, defaults
© SAP AG Page 19 of 30
7/15/2019 QP Mobile Pass V1.0 12April 13
http://slidepdf.com/reader/full/qp-mobile-pass-v10-12april-13 20/30
SAP Best Practices Maintain Company Organizational Structures (560): BPD
based on the relatedobject id
Name Full object name Leave blank, defaultsbased on the related
object idPriority Optional field used to determine the
sequence in which objects arepresented in Simple Maintenance andStructural Graphics
Optional
Weighting A percentage that is used to weightthe assignment of one or more objects
Enter 100
11. Save your entries. The system accepts the data and advances you to the next infotype in the Action: Create Account Assignment Features (I1008).
12. On the Create Account Assignment Features (Infotype 1008) screen, enter the following data:
Field name Description User action and values
Position Abbreviated name of the position
Defaults abbreviated name of the position
PlanningStatus
Planning status of position
Defaults to Active
Valid from Validity dates of theobject
Defaults to dates defined on the previousscreen, but can be changed
CompanyCode
Company code Select value from dropdown list
Business Area Business area Leave blank
Personnel Area Personnel area Select value from dropdown list
PersonnelSubarea
Personnel Subarea Select value from dropdown list.
13. Save your entries. The system accepts the data and advances you to the next infotype in the Action: Create Employee Group/Subgroup (I1013).
14. On the Create Employee Group/Subgroup (Infotype 1013) screen, enter the following data:
Field name Description User action and values
Position Abbreviated name of the position
Defaults abbreviated name of the position
Planning Status Planning status of position
Defaults to Active
Valid from Validity dates of theobject
Defaults to dates defined on the previousscreen, but can be changed
EmployeeGroup
Employee group Select value from dropdown list
EmployeeSubgroup
Employee subgroup Select value from dropdown list. Select avalue that begins with a “Y”.
© SAP AG Page 20 of 30
7/15/2019 QP Mobile Pass V1.0 12April 13
http://slidepdf.com/reader/full/qp-mobile-pass-v10-12april-13 21/30
SAP Best Practices Maintain Company Organizational Structures (560): BPD
15. Save your entries. The system accepts the data and returns you to the start of the PQ13transaction. Exit or create another position.
ResultPosition object and associated infotypes are created.
4.4 Maintain Organizational Unit (Expert Mode)
Use
In this activity, you request a new Department/Organizational Unit.
Prerequisites
If the newly created Organization Unit reports to another Organizational Unit within the structure, thereports to Organizational Unit must already exist.
If defining a cost center to the Organizational Unit, the cost center must already have been createdwithin the FI/CO modules.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC Menu Human Resources Organizational Management Expert Mode
Organizational Unit
Transactioncode
PO10
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
Business role Administrator (HCM) (SAP_NBPR_ADMIN_HCM_M)
Business rolemenu
Human Resources Organizational Structure Maintain
Organizational Unit
2. On the Maintain Organizational Unit screen, make the following entries:
Field name Description User action and values
Plan Version Plan version Defaults to Current Plan
OrganizationalUnit
Object ID of theorganizational unit
Object ID of the organizational unit
Abbreviation Abbreviated name of the organizationalunit
Defaults abbreviated name of the organizationalunit
InfotypesName
List of infotypes tomaintain
Select an infotype and choose the Display,Copy, Change, or Delete button depending onthe requirements. Maintain the fields specific to
© SAP AG Page 21 of 30
7/15/2019 QP Mobile Pass V1.0 12April 13
http://slidepdf.com/reader/full/qp-mobile-pass-v10-12april-13 22/30
SAP Best Practices Maintain Company Organizational Structures (560): BPD
Field name Description User action and values
each infotype.
3. Save your entries.
Result
Organizational Unit object is created.
4.5 Maintain Job (Expert Mode)
Use
In this activity, you request a new Job object.
PrerequisitesIf the Planned Compensation infotype (1005) is created for the job, pay scale/grade information mustbe configured before creating the Planned Compensation infotype.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC Menu Human Resources Organizational Management Expert Mode Job
Transaction
code
PO03
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
Business role Administrator (HCM) (SAP_NBPR_ADMIN_HCM_M)
Business role menu Human Resources Organizational Structure Maintain Job
2. On the Maintain Job screen, make the following entries:
Field name Description User action and values
Plan Version Plan version Defaults to Current Plan
Job Object ID of the job
Object ID of the job
Abbreviation Abbreviatedname of the job
Defaults abbreviated name of the job
InfotypesName
List of infotypesto maintain
Select an infotype and choose the display, copy,change, or delete button depending on therequirements. Maintain the fields specific to eachinfotype.
© SAP AG Page 22 of 30
7/15/2019 QP Mobile Pass V1.0 12April 13
http://slidepdf.com/reader/full/qp-mobile-pass-v10-12april-13 23/30
SAP Best Practices Maintain Company Organizational Structures (560): BPD
If the Worker’s Compensation information must be defined on a Job, make sure that youcreate IT1613 (WC Attributes for JOB).
3. Save your entries.
Result
The job object is created.
4.6 Maintain Position (Expert Mode)
Use
In this activity, you request a new Position.
Prerequisites
To create the Account Assignment Features infotype (1008) and/or the Employee Group/Subgroupinfotype (1013), the Enterprise Structure must be configured.
If any Job object is associated with a Position, the Job must exist before creating this relationship.
The Organizational Unit to which this position reports must exist.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC Menu Human Resources Organizational Management Expert Mode
Position
Transactioncode
PO13
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
Business role Administrator (HCM) (SAP_NBPR_ADMIN_HCM_M)
Business rolemenu
Human Resources Organizational Structure Maintain
Position
2. On the Maintain Position screen, make the following entries:
Field name Description User action and valuesPlan Version Plan version Defaults to Current Plan
Position Object ID of theposition
Object ID of the position
Abbreviation Abbreviated nameof the position
Defaults abbreviated name of the position
Infotypes List of infotypes to Select an infotype and choose the display, copy,
© SAP AG Page 23 of 30
7/15/2019 QP Mobile Pass V1.0 12April 13
http://slidepdf.com/reader/full/qp-mobile-pass-v10-12april-13 24/30
SAP Best Practices Maintain Company Organizational Structures (560): BPD
Field name Description User action and values
Name maintain change, or delete button depending on therequirements. Maintain the fields specific to eachinfotype.
3. Save your entries.
Result
Position object is created.
4.7 Change Organization and Staffing
4.7.1 Create New Position
UseCreation of a new position is used when increasing the headcount of a department to hire newemployees to cover the relevant tasks within the department.
This process is best used for maintaining areas of the organizational structure as opposed tocreating new objects. The OM Actions described above are best used for creating new objects asthey guide the user through the creation of the essential infotypes on each of the object types.
Prerequisites
Use the Organizational Structure provided by SAP Best Practices for HCM U.S.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECCmenu
Human Resources Organizational Management Organizational
Plan Organization and Staffing Change
Transactioncode
PPOME
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
Business role Administrator (HCM) (SAP_NBPR_ADMIN_HCM_M)
Business role
menu
Human Resources Organizational Structure Change
Organization and Staffing
2. The Object Manager on the left side contains a search area and a selection area. Use onesearch option under Organizational unit to go to the root Organizational Unit Best PracticeCompany displayed in the selection area below. Try to find out your favorite search method.
3. Select the Organizational Unit Best Practice Company so it is displayed in the work area on the
right side. Choose the button to enter the date and preview period.
© SAP AG Page 24 of 30
7/15/2019 QP Mobile Pass V1.0 12April 13
http://slidepdf.com/reader/full/qp-mobile-pass-v10-12april-13 25/30
SAP Best Practices Maintain Company Organizational Structures (560): BPD
4. Select the department where you would like to create the new position and choose theCreate button to choose the relationship Incorporates Position.
5. In the detail area, maintain the object attributes for the position created starting on the Basic Data tab, enter the following data:
Field name Description User action andvalues
Object Abbreviation
The abbreviation represents, or identifies, aspecific object (for example, an organizationalunit).
Enter anabbreviation of upto 12 characters.
Object Name Contains a brief description of an object (for example, an organizational unit).
Enter a descriptionof up to 40characters.
Job The job object assigned to this position Select value fromdropdown list
Head of OrganizationalUnit
The position becomes the chief position of theorganizational unit that it belongs to
Flag this field
Staffing Status Vacancy open means that the position is vacant,in other words, a person (employee) is to befound for it. The position is marked as vacant inthe Recruitment component.
Vacancy occupied or put on hold means that theposition is vacant, but presently no person(employee) is being sought to fill it.
Obsolete means that the position is not requiredin the future.
<staffing status>
Indicator for Staff Position
A staff flag indicates that a position or organizational unit is not part of the normalreporting structure, but rather reports directly toa high-level position or organizational unit.
Flag this field if needed
If you selected a job for which the Planned Compensation infotype (1005) has alreadybeen created, then you could skip the following section for maintaining the planned compensation. If integration is activated the data of the Planned Compensation infotype(1005) of the job are inherited onto position level and defaults in personneladministration, Basic Pay (IT0008).
6. Maintain the object attributes for the position created starting on the Account assignment tab,enter the following data:
Field name Description User action and values
Controlling Area
The controlling area is the highestorganizational unit in Controlling.
Controlling Area 1000 isset
CompanyCode
The company code is an organizational unitwithin financial accounting.
Enter 1000
Personnel A personnel area is an organizational entity Select an appropriate
© SAP AG Page 25 of 30
7/15/2019 QP Mobile Pass V1.0 12April 13
http://slidepdf.com/reader/full/qp-mobile-pass-v10-12april-13 26/30
SAP Best Practices Maintain Company Organizational Structures (560): BPD
area representing an area within an enterprisedefined by specific aspects of personneladministration, time management, and payroll.
Personnel Area; see themaster data sectionabove
Pers.
subarea
A personnel subarea is an organizational entity
that represents part of a personnel areacharacterized by personnel administration, timemanagement, and payroll criteria.
Select an appropriate
Personnel Subarea; seethe master data sectionabove
7. Maintain the object attributes for the position created starting on the Work Schedule tab, enter the following data:
Field name Description User action and values
EmployeeGroup
The employee group is anorganizational entity that isgoverned by specific personnelregulations.
Select an appropriate Employee group,for example, Employee
Employee
Subgroup
An employee subgroup is an
organizational entity within anemployee group.
Select an appropriate Employee
subgroup, for example, Y1 Exempt/Salariedt. Select a value thatbegins with a Y .
8. Choose the Continue (Enter) button. The system accepts the data and automatically entersthe planned working time. Adjust approval percentage if needed.
9. Choose the Undo Change button if there are entries that should not be saved.
10. Save your entries.
Result
The position is created within the according department and becomes effective on the date entered.
4.7.2 Maintain Planned Compensation
Use
After creation of a new position, the values for the planned compensation must be maintained tocreate a proposal for an employee’s pay rate that is linked to this position.
The Planned Compensation infotype (1005) has also been defined for salaried (exemptand non-exempt) and hourly jobs. This includes the pay scale/grade type, area, grade,and level. If integration is activated, this information defaults in personnel administration,
Basic Pay (IT0008). When you maintain the planned compensation additionally onposition level, then these values overwrite the data inherited from the job assignment.
Prerequisites
Use the Organizational Structure provided by SAP Best Practices for HCM U.S.
Procedure
1. Access the transaction choosing one of the following navigation options:
© SAP AG Page 26 of 30
7/15/2019 QP Mobile Pass V1.0 12April 13
http://slidepdf.com/reader/full/qp-mobile-pass-v10-12april-13 27/30
SAP Best Practices Maintain Company Organizational Structures (560): BPD
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECCmenu
Human Resources Organizational Management Organizational
Plan Organization and Staffing Change
Transaction
code
PPOME
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
Business role Administrator (HCM) (SAP_NBPR_ADMIN_HCM_M)
Business rolemenu
Human Resources Organizational Structure Change
Organization and Staffing
2. The Object Manager on the left side contains a search area and a selection area. Use onesearch option under Organizational unit to obtain the root Organizational Unit Best PracticeCompany displayed in the selection area below. Try to find out your favorite search method.
3. Select the organizational unit Best Practice Company so it is displayed in the work area on theright side. To enter the date (for example, 1st January of the current year) and the preview
period, choose the button.4. Select the department for which you would like to manage the Planned Compensation for the
positions.
5. Double-click the position for which you would like to maintain the planned compensation.
6. From the More menu, choose Goto Detailed object Enhanced object Description to get tothe Infotype maintenance.
7. Select the Planned Compensation checkbox and choose the Create button. Select one entryfrom each block in the table below then save your entries.
Fieldname
Description User action and values
Pay Grade:
Use this tab when defining annual salariesto a job
CountryGrouping
Identifies the country code of the paygrade information
Select value USA
Pay GradeType
Distinguishes between the different typesof pay grade structures
Select value from dropdownlist
Pay Grade Area
Distinguishes logical regions within asalary structure
Select value from dropdownlist
Valid values are:01,02,05,06,09 or 10
Pay Grade Groups similar jobs for employeecompensation
Select value from dropdownlist
Pay GradeLevel
Defines the salary range within the paygrade. Each level has a minimum and amaximum amount
Select value from dropdownlist for the minimum andmaximum amounts
Key Date Date for display salary amounts effective Defaults to system date, but
© SAP AG Page 27 of 30
7/15/2019 QP Mobile Pass V1.0 12April 13
http://slidepdf.com/reader/full/qp-mobile-pass-v10-12april-13 28/30
SAP Best Practices Maintain Company Organizational Structures (560): BPD
for Display on a specific date can be overwritten
Pay Scale: Use this tab when defining hourly rates of pay to a job
CountryGrouping
Identifies the country code of the paygrade information
Select value USA
Pay ScaleType
Distinguishes between the different typesof pay scale structures
Select value from dropdownlist
Pay Scale Area
Distinguishes logical regions within a payrate structure
Select value from dropdownlist
Use values01,02,05,06,07,08,09 or 10.
ESG for CAP
An employee subgroup grouping for collective agreement provisions combinessubgroups that are governed by the samevalid collective agreement provisions
Select value from dropdownlist
Pay ScaleGroup
Criterion used for grading job evaluation. Apay scale group is divided up into severalpay scale levels
Select value from dropdownlist
Pay ScaleLevel
Criterion for job evaluation within the payscale group
Select value from dropdownlist for the minimum andmaximum rates
Key Datefor Display
Date for display hourly rates effective on aspecific date
Defaults to system date, butcan be overwritten
Time Unit Determines which unit of time is used tocalculate/display amounts in compensationadministration
Select value from dropdownlist
Direct: Use this tab when defining specificrates/amounts of pay to a job
CurrencyKey
Currency code Select or enter currency code,example USD for USA
Amount Specific range of amounts per time unit Enter the minimum andmaximum amount
Time unit Determines which unit of time is used tocalculate/display amounts in compensationadministration
Select value from dropdownlist
The table above is used for defining Planned Compensation infotype (1005) has alsobeen defined for salaried (exempt and nonexempt) jobs. This includes the pay gradetype, area, grade, and level.
© SAP AG Page 28 of 30
7/15/2019 QP Mobile Pass V1.0 12April 13
http://slidepdf.com/reader/full/qp-mobile-pass-v10-12april-13 29/30
SAP Best Practices Maintain Company Organizational Structures (560): BPD
4.7.3 Create New Position by Copying
Use
Copy for creating a new position is used when increasing the headcount of a department to hire new
employees to cover the relevant tasks within the department and a similar position already existswithin the department.
The new position then has the same attributes such as object description job assigned, accountinginformation, and working schedules inherited from the copied position.
Prerequisites
Use the Organizational Structure provided by SAP Best Practices for HCM U.S.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECCmenu
Human Resources Organizational Management Organizational
Plan Organization and Staffing Change
Transactioncode
PPOME
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
Business role Administrator (HCM) (SAP_NBPR_ADMIN_HCM_M)
Business rolemenu
Human Resources Organizational Structure Change
Organization and Staffing
2. The Object Manager on the left side contains a search area and a selection area. Use one
search option under Organizational unit to get the root Organizational Unit Best PracticeCompany displayed in the selection area below. Try to find out your favorite search method.
3. Select the Organizational Unit Best Practice Company so it is displayed in the work area on the
right side. Enter the date and preview period choosing the button.
4. Select a similar position within the department where you would like to create the new position
and choose the Copy button. Adjust the number of new positions to be created and thevalidity date and the object name and abbreviation if needed.
5. Choose the Undo Change button for entries that should not be saved.
6. Save your entries.
Result
The position is created within the according department and becomes effective on the date entered.
4.7.4 Update Organizational Structure (Change Position)
Use
© SAP AG Page 29 of 30
7/15/2019 QP Mobile Pass V1.0 12April 13
http://slidepdf.com/reader/full/qp-mobile-pass-v10-12april-13 30/30
SAP Best Practices Maintain Company Organizational Structures (560): BPD
The Change Position is used when reorganization experiences a change in reporting lines. In somecases, a change of the position may result in a change in payroll relevant assignments and the
Account Assignment information. If the positions’ attributes are not affected, simply copy the positionusing drag and drop from one department to another.
This action should be used if the reorganization is approved because the person holdingthe position is affected by this change.
Prerequisites
Use the Organizational Structure provided by SAP Best Practices for HCM U.S.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECCmenu
Human Resources Organizational Management Organizational
Plan Organization and Staffing Change
Transactioncode
PPOME
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
Business role Administrator (HCM) (SAP_NBPR_ADMIN_HCM_M)
Business rolemenu
Human Resources Organizational Structure Change
Organization and Staffing
2. The Object Manager on the left side contains a search area and a selection area. Use onesearch option under Organizational unit to get the root Organizational Unit Best Practice
Company displayed in the selection area below. Try to find out your favorite search method.
3. Select the Organizational Unit Best Practice Company so it is displayed in the work area on the
right side. Enter the date and preview period choosing the button.
4. Select one or more positions within one or more departments that you would like to bereorganized. Use the CTRL key for multiple selections. Drag & Drop the selected position ontothe organizational unit/department to that the positions should now report to.
The validity date of the change of the position to the new department starts with the day
that is entered in date and preview period choosing the button. If the date should bechanged, select the relevant position and then from the menu bar, choose Goto
Detail Object Enhanced object description
for detailed object maintenance of therelationships.
Result
The change in position becomes effective on the date entered in date and preview period choosing
the button.