155_bpd_20_en_xx
TRANSCRIPT
7/29/2019 155_BPD_20_EN_XX
http://slidepdf.com/reader/full/155bpd20enxx 1/7
EHP5 for SAP ERP6.0
December 2010
English
Maintain Capacity (155.20)
SAP AGDietmar-Hopp-Allee 1669190 Walldorf Germany
Master Data Procedure
7/29/2019 155_BPD_20_EN_XX
http://slidepdf.com/reader/full/155bpd20enxx 2/7
SAP Best Practices Maintain Capacity (155.20): MDP
Copyright
© 2010 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without theexpress 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 proprietary software componentsof 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,System z10, 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, SystemStorage, 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 is a registered trademark of Oracle Corporation.
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.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology inventedand implemented by Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjectsExplorer, and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions,Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP France in the United States and inother countries.
All other product and service names mentioned are the trademarks of their respective companies. Data
contained 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, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only
warranties for SAP Group products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as
constituting an additional warranty.
© SAP AG Page 2 of 7
7/29/2019 155_BPD_20_EN_XX
http://slidepdf.com/reader/full/155bpd20enxx 3/7
SAP Best Practices Maintain Capacity (155.20): MDP
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 fieldnames, screen titles, pushbuttons as well as menu names, paths andoptions.
Cross-references to other documentation.
Example text Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT Names of elements in the system. These include report names,program names, transaction codes, table names, and individual keywords of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.
Example text Screen output. This includes file and directory names and their paths,
messages, source code, names of variables and parameters as well asnames of installation, upgrade and database tools.
EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or theENTER key.
Example text Exact user entry. These are words or characters that you enter in thesystem exactly as they appear in the documentation.
<Example text> Variable user entry. Pointed brackets indicate that you replace thesewords and characters with appropriate entries.
© SAP AG Page 3 of 7
7/29/2019 155_BPD_20_EN_XX
http://slidepdf.com/reader/full/155bpd20enxx 4/7
SAP Best Practices Maintain Capacity (155.20): MDP
Contents
1 Purpose ......................................................................................................................................5
2 Prerequisites ...............................................................................................................................5
2.1 Roles ....................................................................................................................................5
3 Process Steps .............................................................................................................................5
3.1 Creating Capacity .................................................................................................................5
4 Follow-Up Processes ..................................................................................................................7
4.1 Creating Work Center ...........................................................................................................7
4.2 Creating Resources for Process Industry .............................................................................7
5 Appendix .....................................................................................................................................7
5.1 Reversal of Process Steps ...................................................................................................7
© SAP AG Page 4 of 7
7/29/2019 155_BPD_20_EN_XX
http://slidepdf.com/reader/full/155bpd20enxx 5/7
SAP Best Practices Maintain Capacity (155.20): MDP
Maintain Capacity
1 PurposeIn this document, you can maintain capacity.
2 Prerequisites
2.1 Roles
Use
The following roles must have been installed to allow the relevant activities to be carried out in
the SAP NetWeaver Business Client (NWBC). In addition, they must be assigned to the user or users who will perform the process steps described in this document. You do not need theseroles if you are not using the NWBC interface, but the standard SAP GUI.
Prerequisites
The business roles have been assigned to the user(s) who will perform the process stepsdescribed in this document.
Business role Technical name Process step
Employee(Professional User)
SAP_NBPR_EMPLOYEE_S Assignment of this role is necessary for basic functionality.
EngineeringSpecialist
SAP_NBPR_ENGINEER_S Create Capacity
3 Process Steps
3.1 Creating Capacity
The creation of capacities is not in scope of this release. The capacity is maintainedduring the creation of the work centers.
If you do not want to work with capacities which may later be referenced to the workcenter capacity header you can skip the following steps and proceed with thecreation of work centers.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI):
SAP ECC menu Logistics Production Master Data Work Centers Capacity Create
Transaction code CR11
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
© SAP AG Page 5 of 7
7/29/2019 155_BPD_20_EN_XX
http://slidepdf.com/reader/full/155bpd20enxx 6/7
SAP Best Practices Maintain Capacity (155.20): MDP
Business role Engineering Specialist
(SAP_NBPR_ENGINEER_S)
Business role menu Engineering →Master Data→Work Centers→Create Capacity
2. On the Initial screen make following entries:
Field name Description User action and values Comment
Plant 1000
Capacity enter capacity
Capacity category
001
002
Machine
Person
3. On the second screen, make the following entries:
Field name Description User action and values Comment
Description Enter a description (optional)
Capacity Planner group
A / B / C Select from list
Base unit of measure
Choose Unit of measure e.g.MIN for minutes
Start 08:00:00 for 8 am
Finish 17:00:00 for 5 pm
Length of breaks 01:00:00 for 1 hour
Capacity utilization 100 for 100%
No. of indiv. cap. 1
Relevant for finitescheduling
X Select checkbox
Long term Planning X Select checkbox
Can be used by several operations
X Select checkbox
4. Choose Save.
Result
Capacity is created.
© SAP AG Page 6 of 7
7/29/2019 155_BPD_20_EN_XX
http://slidepdf.com/reader/full/155bpd20enxx 7/7
SAP Best Practices Maintain Capacity (155.20): MDP
4 Follow-Up Processes
4.1 Creating Work Center
Use
This activity will create work center.
Procedure
To execute this activity, run the Create Work Center (155.21) scenario.
4.2 Creating Resources for Process Industry
Use
This activity will create the resource.
Procedure
To execute this activity, run the Create Resources for Process Industry (155.23)scenario.
5 Appendix
5.1 Reversal of Process Steps
In the following section, you can find the most common reversal steps, which you can take toreverse some of the activities described in this document.
Create capacity
Transaction code (SAP GUI) CR11
Reversal: Change Capacity
Transaction code (SAP GUI) CR12
Business role Engineering Specialist
Business role menu Engineering Master DataWork Centers Changecapacity
Comment In transaction CR12 choose : Capacity Delete
© SAP AG Page 7 of 7