EHP3 for SAP ERP 6.

0
June 2009
English













Engineering Change
Management (666)







SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
Building Block Configuration Guide

SAP Best Practices Engineering Change Management (666): Configuration Guide
SAP AG Page 2 of 10
Copyright

Copyright 2009 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 proprietary software components
of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,
OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z,
System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5,
POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

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 Web
Consortium, 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 invented
and implemented by Netscape.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and
other SAP products and services mentioned herein as well as their respective logos are trademarks or
registered trademarks of SAP AG in Germany and in several other countries all over the world. 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 Best Practices Engineering Change Management (666): Configuration Guide
SAP AG Page 3 of 10
Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax


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.
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 key words 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 as names
of installation, upgrade and database tools.
EXAMPLE TEXT
Keys on the keyboard, for example, function keys (such as F2) or the ENTER
key.
Example
text
Exact user entry. These are words or characters that you enter in the system
exactly as they appear in the documentation.
<Example
text>
Variable user entry. Pointed brackets indicate that you replace these words
and characters with appropriate entries.
SAP Best Practices Engineering Change Management (666): Configuration Guide
SAP AG Page 4 of 10
Contents
Engineering Change Management: Configuration Guide.............................................................. 5
1 Purpose ............................................................................................................................... 5
2 Preparation .......................................................................................................................... 5
2.1 Prerequisites .............................................................................................................. 5
2.1.1 Building Blocks ....................................................................................................... 5
3 Configuration ........................................................................................................................ 5
3.1 Define Authorization Groups for Digital Signatures ...................................................... 5
3.2 Define Single Signature .............................................................................................. 6
3.3 Define Signature Strategy ........................................................................................... 7
3.4 Defining Signature Network for Change Master Records ............................................. 8
3.5 Defining Change Types for Change Master Records ................................................... 9
3.6 Maintaining Change Profiles ..................................................................................... 10
SAP Best Practices Engineering Change Management (666): Configuration Guide
SAP AG Page 5 of 10
Engineering Change Management: Configuration
Guide
1 Purpose
This configuration guide provides the information you need to set up the configuration of this
building block manually.
2 Preparation
2.1 Prerequisites
2.1.1 Building Blocks
Before you start installing this building block, you must install prerequisite building blocks. For
more information, see the Building Block Prerequisite Matrix for SAP Best Practices for
Electronics and Component Manufacturing. The matrix (an Excel file) is linked on the solution's
DVD/website in one of the following two locations:
Content Library
Site Map


Authorization object C_STUE_NOH lets you maintain a BOM that has a history
requirement without a change number. The authorization object contains field NOHIS
(authorization to change BOMs without a change number). To assign this
authorization, enter X.

3 Configuration
3.1 Define Authorization Groups for Digital Signatures
Use
This activity creates the necessary authorization groups for digital signatures requested for the
engineering change management process.
You can use the authorization groups to help you restrict the authorizations for approving
ECR/ECOs as follows:
You define different authorization groups for users who work in different task
areas.
SAP Best Practices Engineering Change Management (666): Configuration Guide
SAP AG Page 6 of 10
In the user master record, allocate each user with the correct authorization for
the authorization group that corresponds to his/her task area (authorization
object: C_SIGN_BGR).
Define single signatures that must be entered by users in a specific user group
and are used in the signature strategies for the change types of an ECR/ECO.
The authorization groups are not taken into account if, in the ECR/ECO, a single signature
suffices to approve which system status is set and a signature strategy is not required.
Procedure
1. Access the activity using the following navigation options:
IMG Menu Logistics General Engineering Change Management Change
Type Approval Define Authorization Group
Transaction
Code
SPRO
2. On the Change View Authorization Group for Digital Signatures: Overview screen, choose
New Entries.
3. On the New Entries: Overview of Added Entries screen, make the following entries:
Field name Description User action and
values
Notes
AGrpDigSig Authorization Group / Role for
Digital Signatures
YQ_ECM01
Authorization group f.
digital signature
Production
Manager

4. Save your entries.
Result
Authorization groups for digital signatures are created.

3.2 Define Single Signature
Use
This activity defines individual signatures for users in a specific authorization group.
You can then use these single signatures as individual steps in a signature strategy when a
status in the ECR/ECO is approved.
If a single signature suffices to approve the status that is set in the ECR/ECO and no signature
strategy is required, you do not have to define the single signatures.
Prerequisites
Authorization groups for digital signatures must be already defined.
Procedure
SAP Best Practices Engineering Change Management (666): Configuration Guide
SAP AG Page 7 of 10
1. Access the activity using the following navigation options:
IMG Menu Logistics General Engineering Change Management Change
Type Approval Define Single Signature
Transaction
Code
SPRO
2. On the Change View Individual Signature: Overview screen, choose New Entries.
3. On the New Entries: Overview of Added Entries screen, make the following entries:
Field name Description User action and values Notes
Individual Signature YQ_ECM01
AGrpDigSig YQ_ECM01
Indiv. Signature Description Production Manager
4. Save your entries.
Result
Individual signatures are defined.

3.3 Define Signature Strategy
Use
This activity defines all required signature strategies.
Prerequisites
Individual signatures must be defined already.
Procedure
1. Access the activity using the following navigation options:
IMG Menu Logistic General Engineering Change Management Change
Type Approval Define Signature Strategy
Transaction
Code
SPRO
2. On the Change View Define Signature Strategy: Overview screen, choose New Entries.
3. On the New Entries: Overview of Added Entries screen, make the following entries:
Field name Description User action and values Notes
SigStrat Signature
Strategy
YQ_ECM01
Signature Strategy
Description
Release of BOM changes
Signature Method R (System Signature with authorization
by ECC User ID/Password)

SAP Best Practices Engineering Change Management (666): Configuration Guide
SAP AG Page 8 of 10
Field name Description User action and values Notes
Display Document Possible
Display Remark Possible
Display Comment Possible
4. Select your added entry and choose Assign Individual Signatures.
5. On the Change View Assign Individual Signatures: Overview screen, choose New Entries.
6. On the New Entries: Overview of Added Entries screen, make the following entries:
Field name Description User action and values Notes
Indiv Sig Individual Signature YQ_ECM01
7. Save your entries.
Result
Signature strategies are defined.

3.4 Defining Signature Network for Change Master
Records
Use
This activity defines signature networks in which you allocate one signature strategy to the
individual system statuses of the ECR/ECO. When you set the system status in the ECR/ECO
(change header), the allocated signature process is started.

This step is required if you are using Digital Signatures.
Prerequisites
Signature strategies must be defined already.
Procedure
1. Access the activity using the following navigation options:
IMG Menu Logistics General Engineering Change Management Change
Type Approval Define signature network for change master record
Transaction
Code
SPRO
2. On the Change View Signature network for ECR/ECO: Details screen, choose New Entries.
3. On the New Entries: Details of Added Entries screen, make the following entries:
Field name Description User action and values Notes
Signature Network ECR/ECO YQ_ECM01
SAP Best Practices Engineering Change Management (666): Configuration Guide
SAP AG Page 9 of 10
Descriptions Release of BOM changes
Convert ECR YQ_ECM01
Release ECO YQ_ECM01
4. Save your entries.
Result
Signature networks for change master records are defined.

3.5 Defining Change Types for Change Master Records
Use
This activity defines all needed change types for change master records.
Prerequisites
Signature networks must be defined already.
Procedure
1. Access the activity using the following navigation options:
IMG Menu Logistics General Engineering Change Management Change
Type Define change types for change master record
Transaction
Code
OS56
2. On the Change View Change Types Overviews screen, choose New Entries.
3. On the New Entries: Overview of Added Entries screen, make the following entries:
Field
name
Description User action and values Notes
ChgTyp Change Type 901
Description Changes in approved
recipes/BOMs

Sig.NetWk Signature Network
ECR/ECO
YQ_ECM01
4. Save your entries.
Result
Change Type for Master Record is defined.

SAP Best Practices Engineering Change Management (666): Configuration Guide
SAP AG Page 10 of 10
3.6 Maintaining Change Profiles
Use
This activity defines the profiles for default values and settings when you create a change master
record.
The information in a profile is standard information that you must enter frequently in a similar
combination in change master records. The profile makes it easier to enter and manage change
data.
Procedure
1. Access the activity using the following navigation options:
IMG Menu Logistics General Engineering Change Management Maintain
Profile
Transaction
Code
SPRO
2. On the Change View Change master record profile: Details screen, choose New Entries.
3. On the New Entries: Details of Added Entries screen, make the following entries:
Field name Description User action and values Notes
Profile YQ_ECM01
Change Number Status 1
4. Select your settings and choose Object type profile (Overview).
5. On the Change View: Object type profile (overview): Overview screen, make the following
entries:
Field name Description User action and values Notes
OT Profile YQ_ECM01
6. Select your settings and choose Object type profile (detail).
7. On the Change View: Object type profile (detail): Overview screen, make the following
entries:
Field name Description User action and values Notes
Object Type 02
Object Type Active X
Object X
Object Type 41
Object Type Active X
Object X
8. Save your entries.
Result
The change profile is maintained.