LO 980 engineering change mgmt

262

Click here to load reader

description

SAP 4.6 LO980 engineering change mgmt

Transcript of LO 980 engineering change mgmt

Page 1: LO 980 engineering change mgmt

SAP AG 1999

LO980 Engineering Change Management

/2���/2���(QJLQHHULQJ�&KDQJH0DQDJHPHQW(QJLQHHULQJ�&KDQJH0DQDJHPHQW

n R/3 System

n Release 4.6C

n November 2000

n Material Number 5004 1897

Page 2: LO 980 engineering change mgmt

SAP AG 1999

&RS\ULJKW������6$3�$*���$OO�ULJKWV�UHVHUYHG�1HLWKHU�WKLV�WUDLQLQJ�PDQXDO�QRU�DQ\�SDUW�WKHUHRI�PD\EH�FRSLHG�RU�UHSURGXFHG�LQ�DQ\�IRUP�RU�E\�DQ\�PHDQV�RU�WUDQVODWHG�LQWR�DQRWKHU�ODQJXDJH��ZLWKRXW�WKH�SULRUFRQVHQW�RI�6$3�$*��7KH�LQIRUPDWLRQ�FRQWDLQHG�LQ�WKLVGRFXPHQW�LV�VXEMHFW�WR�FKDQJH�DQG�VXSSOHPHQW�ZLWKRXW�SULRUQRWLFH�$OO�ULJKWV�UHVHUYHG�

&RS\ULJKW

7UDGHPDUNV:n Some software products marketed by SAP AG and its distributors contain proprietary software

components of other software vendors.n Microsoft®, WINDOWS®, NT®, EXCEL®, Word® and SQL Server® are registered trademarks of

Microsoft Corporation.n IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®,

AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.n ORACLE® is a registered trademark of ORACLE Corporation, California, USA.n INFORMIX®-OnLine for SAP and Informix® Dynamic ServerTM are registered trademarks of

Informix Software Incorporated.n UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of The Open Group.n HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide

Web Consortium, Laboratory for Computer Science NE43-358, Massachusetts Institute ofTechnology, 545 Technology Square, Cambridge, MA 02139.

n JAVA® is a registered trademark of Sun Microsystems, Inc. , 901 San Antonio Road, Palo Alto, CA94303 USA.

n JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license fortechnology invented and implemented by Netscape.

n SAP, SAP Logo, mySAP.com, mySAP.com Marketplace, mySAP.com Workplace, mySAP.comBusiness Scenarios, mySAP.com Application Hosting, WebFlow, R/2, R/3, RIVA, ABAP™, SAPBusiness Workflow, SAP EarlyWatch, SAP ArchiveLink, BAPI, SAPPHIRE, Management Cockpit,SEM, are trademarks or registered trademarks of SAP AG in Germany and in several other countriesall over the world. All other products mentioned are trademarks or registered trademarks of theirrespective companies.

n Design: SAP Communications Media

Page 3: LO 980 engineering change mgmt

SAP AG 1999

3URGXFW�/LIHF\FOH�0DQDJHPHQW��3/0�

Product LifecycleManagement

���������3 days

/HYHO�� /HYHO��

Basic Data forDiscrete Manufacturing

�������3 days

DocumentManagement System

�������3 days

Engineering ChangeManagement

���������3 days

Variant ConfigurationPart 1

��������5 days

Classification

��������3 days

Variant ConfigurationPart 2

�������� 3 days

Page 4: LO 980 engineering change mgmt

SAP AG 1999

3URGXFWLRQ�3ODQQLQJ/HYHO�� /HYHO��

ManufacturingPlanning &Execution forDiscrete & Repetitive

��������5 days

EngineeringChangeManagement

���������3 days

BatchManagement

������3 days

KANBAN

��������2 days

Classification

��������3 days

Special Features ofLIS in Production

��������2 days

Logistics InfoPlanning

��������2 days

CAP Calculation ofStandard Values

���������2 days

RepetitiveManufacturing

��������3 days

Capacity Planning

���������5 days

LogisticsInformationSystem (LIS)Reporting

���������2 days

Basic DataPart 2

���������3 days

Basic Data forDiscreteManufacturing

��������3 days

ProductionOrders

������ �5 days

ProductionPlanning

������ ��5 days

VariantConfiguration Part 1

���������5 days

VariantConfiguration Part 2

�������� 3 days

Page 5: LO 980 engineering change mgmt

SAP AG 1999

&RXUVH�3UHUHTXLVLWHV

l 5HTXLUHG�l /2��� - PDM Overview or

l /2��� – Manufacturing Planning & Execution _Discrete and Repetitive

l Basic business knowledge of production planning andcontrol, as well as ECM within a company

l $OVR�UHFRPPHQGHG�l /2��� - Production Orders

Page 6: LO 980 engineering change mgmt

SAP AG 1999

l 3DUWLFLSDQWV�� 3URMHFW�WHDP�PHPEHUV��&RQVXOWDQWV��2UJDQL]HUV���ZKR

DUH�UHVSRQVLEOH�IRU�WKH�LPSOHPHQWDWLRQ�RI�5���6\VWHPVROXWLRQV�IRU�WKH�(&0�RI�PDVWHU�GDWD�DQG�SURGXFWLRQRUGHUV��3URGXFWLRQ��

� 7HDP�OHDGHUV�DQG�HPSOR\HHV�WKDW�KDYH�WR�ZRUN�ZLWK(QJLQHHULQJ�&KDQJH�0DQDJHPHQW��GHVLJQ�HQJLQHHUV�SURGXFWLRQ�VFKHGXOHUV�DQG�VR�RQ��

7DUJHW�*URXS

l 'XUDWLRQ����GD\V

1RWHV�WR�WKH�XVHUn The training materials are not teach-yourself programs. They complement the course instructor’s

explanations. On the sheets, there is space for you to write down additional information.

Page 7: LO 980 engineering change mgmt

© SAP AG LO980 1-1

SAP AG 1999

l &RXUVH�*RDOVl &RXUVH�2EMHFWLYHVl &RXUVH�&RQWHQWl &RXUVH�2YHUYLHZ�'LDJUDPl 0DLQ�%XVLQHVV�6FHQDULR

&RQWHQWV�

&RXUVH�2YHUYLHZ

Page 8: LO 980 engineering change mgmt

© SAP AG LO980 1-2

SAP AG 1999

7KLV�FRXUVH�ZLOO�SUHSDUH�\RX�WR�

&RXUVH�*RDOV

Use the functions and work methods of R/3 changemanagement for basic data and production orders.

Page 9: LO 980 engineering change mgmt

© SAP AG LO980 1-3

SAP AG 1999

&RXUVH�2EMHFWLYHV

$W�WKH�FRQFOXVLRQ�RI�WKLV�FRXUVH�l You can recognize the interaction of changes on

documents, material masters, BOMs, and routings.l Support the change process using the standard

workflow for Engineering Change Managementl Change production orders in a controlled manner with

the help of Engineering Change Management andOrder Change Management

Page 10: LO 980 engineering change mgmt

© SAP AG LO980 1-4

SAP AG 1999

l Change master record

l Special features of object changes

l Reporting

l ECR/ECO

l Standard Workflow in Engineering Change Management

l Effectivity parameter, change hierarchies, release key

digital signature

l Order Change Management

&RXUVH�7RSLFV

7KH�IROORZLQJ�WRSLFV�DUH�FRYHUHG�LQ�WKLV�FRXUVH�

Page 11: LO 980 engineering change mgmt

© SAP AG LO980 1-5

SAP AG 1999

Unit 1 &RXUVH�2YHUYLHZUnit 2 &KDQJH�0DVWHU�5HFRUGVUnit 3 2EMHFW�&KDQJHVUnit 4 5HSRUWLQJUnit 5 (&5�(&2Unit 6 3URFHVVLQJ�&KDQJHV

ZLWK�:RUNIORZ

3UHIDFH

$SSHQGL[

&RXUVH�&RQWHQW

Unit 7 &KDQJH�+LHUDUFKLHV�5HOHDVH�.H\�3DUDPHWHU�(IIHFWLYLW\

Unit 8 2UGHU�&KDQJH0DQDJHPHQW��2&0�

Unit 9 &RQFOXVLRQ

Page 12: LO 980 engineering change mgmt

© SAP AG LO980 1-6

SAP AG 1999

&RXUVH�2YHUYLHZ�'LDJUDP

2EMHFW�&KDQJHV2EMHFW�&KDQJHV ��

5HSRUWLQJ5HSRUWLQJ �� 6XPPDU\6XPPDU\ ��

2UGHU�&KDQJH�2UGHU�&KDQJH�0DQDJHPHQW��2&0�0DQDJHPHQW��2&0� ��

�� &KDQJH�+LHUDUFK\��&KDQJH�+LHUDUFK\��5HOHDVH�.H\�5HOHDVH�.H\�«« ��&KDQJH�0DVWHU�5HFRUG&KDQJH�0DVWHU�5HFRUG

3URFHVVLQJ�&KDQJHV�3URFHVVLQJ�&KDQJHV�ZLWK�:RUNIORZZLWK�:RUNIORZ ��&RXUVH�2YHUYLHZ&RXUVH�2YHUYLHZ ��

(&5���(&2(&5���(&2 ��

Page 13: LO 980 engineering change mgmt

© SAP AG LO980 1-7

SAP AG 1999

1HZ�GHYHORSPHQW�DQG�FKDQJHV�WR�UHOHYDQW�SURGXFWVDUH�WKH�GDLO\�WDVNV�RI�D�FRPSDQ\��7KH\�SRVH�DW�OHDVWRQH�RI�WKH�IROORZLQJ�UHTXLUHPHQWV�l 7KH\�QHHG�GHWDLOHG�PRQLWRULQJ�DQG�GRFXPHQWDWLRQ

RI�WKH�FKDQJH�SURFHVV�l &KDQJHV�KDYH�WR�EH�DEOH�WR�EH�SODQQHG�DQG�WHVWHG

DQG�EH�GHILQHG�DV�FRQYHUWLEOH�l 7KH\�UHTXLUH�VHYHUDO�FKDQJH�VWDWXVHV�IRU�DQ

REMHFW�l 7KH\�ZDQW�WR�VWUXFWXUH�FKDQJHV�l 3URGXFWLRQ�RUGHUV�VKRXOG�DOVR�DOZD\V�EH

FRQWUROOHG�DV�FKDQJHDEOH�

0DLQ�%XVLQHVV�6FHQDULR

Page 14: LO 980 engineering change mgmt

© SAP AG LO980 2-1

SAP AG 1999

&RQWHQWV�l ,QWHJUDWLRQ�LQ�WKH�5���6\VWHPl &KDQJHV�ZLWK�+LVWRU\l /LQNHG�2EMHFWVl 6WUXFWXUH�DQG�)XQFWLRQV�RI�WKH�&KDQJH�0DVWHU�5HFRUGl 2EMHFW�PDQDJHPHQW�UHFRUGVl $OWHUQDWLYH�GDWHVl 3URGXFW�6WUXFWXUH

&KDQJH�0DVWHU�5HFRUG

Page 15: LO 980 engineering change mgmt

© SAP AG LO980 2-2

SAP AG 1999

$W�WKH�FRQFOXVLRQ�RI�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�l (VWDEOLVK�WKH�RSWLRQV�DQG�WKH�XVH�RI�(QJLQHHULQJ

&KDQJH�0DQDJHPHQW�IRU�\RXU�FRPSDQ\l &UHDWH�DQG�XVH�WKH�FKDQJH�PDVWHU�UHFRUG�ZLWK�LWV

VWUXFWXUH�DQG�LWV�IXQFWLRQDOLW\� Change header� Object management record� Alternative dates

l 6HOHFW�DQG�FRS\�REMHFWV�IRU�(QJLQHHULQJ�&KDQJH0DQDJHPHQW�ZLWK�WKH�KHOS�RI�WKH�SURGXFW�VWUXFWXUH

&KDQJH�0DVWHU�5HFRUG��7RSLF�2EMHFWLYHV

Page 16: LO 980 engineering change mgmt

© SAP AG LO980 2-3

SAP AG 1999

&RXUVH�2YHUYLHZ�'LDJUDP

2EMHFW�&KDQJHV2EMHFW�&KDQJHV ��5HSRUWLQJ5HSRUWLQJ ��

�� &KDQJH�+LHUDUFK\��&KDQJH�+LHUDUFK\��5HOHDVH�.H\�5HOHDVH�.H\�«« ��

3URFHVVLQJ�&KDQJHV�3URFHVVLQJ�&KDQJHV�ZLWK�:RUNIORZZLWK�:RUNIORZ ��&RXUVH�2YHUYLHZ&RXUVH�2YHUYLHZ ��

(&5���(&2(&5���(&2 ��

&KDQJH�0DVWHU�5HFRUG&KDQJH�0DVWHU�5HFRUG

6XPPDU\6XPPDU\ ��

2UGHU�&KDQJH�2UGHU�&KDQJH�0DQDJHPHQW��2&0�0DQDJHPHQW��2&0� ��

Page 17: LO 980 engineering change mgmt

© SAP AG LO980 2-4

SAP AG 1999

&KDQJH�0DVWHU�5HFRUG��%XVLQHVV�6HQDULR

l 7KH�FHQWUDO�(QJLQHHULQJ�&KDQJH�0DQDJHPHQWOHDUQV�WKH�IXQFWLRQV�DQG�WKH�VWUXFWXUH�RI�WKHFKDQJH�PDVWHUV�

l )RU�H[DPSOH�D�%20�LV�FKDQJHG�ZLWK�WKH�KHOS�RI�WKHSURGXFW�VWUXFWXUH�DQG�WKH�HIIHFWV�GLVSOD\HG�

Page 18: LO 980 engineering change mgmt

© SAP AG LO980 2-5

SAP AG 1999

(QJLQHHULQJ�&KDQJH�0DQDJHPHQW��3DUW�RI�3'0

&ODVVLILFDWLRQ&ODVVLILFDWLRQ

3URMHFW3URMHFW6\VWHP6\VWHP

'RFXPHQW'RFXPHQWPDQDJHPHQWPDQDJHPHQW

9DULDQW9DULDQWFRQILJXUDWLRQFRQILJXUDWLRQ

0DVWHU�GDWD0DVWHU�GDWD

��������� � �

������������������������������

&$'�LQWHUIDFH&$'�LQWHUIDFH(QJLQHHULQJ

&KDQJH0DQDJHPHQW

é Engineering Change Management is a central, integral part of Product Data Management (PDM) inthe SAP R/3 System.

é Other components are:

• Master data management (material master records, BOMs, routings)

• Document Management System

• Classification

• CAD interface

• Workflow

• Project System

• Variant Configuration

Page 19: LO 980 engineering change mgmt

© SAP AG LO980 2-6

SAP AG 1999

IRU�GLIIHUHQW�REMHFWVIRU�GLIIHUHQW�REMHFWVIRU�WKH�VDPH�RU�GLIIHUHQWIRU�WKH�VDPH�RU�GLIIHUHQWSRLQWV�LQ�WLPHSRLQWV�LQ�WLPHZLWK�VSHFLDO�FRPSUHKHQVLYH�ZLWK�VSHFLDO�FRPSUHKHQVLYH�GRFXPHQWDWLRQGRFXPHQWDWLRQ

:K\�0DNH�&KDQJHV�ZLWK�(QJLQHHULQJ�&KDQJH0DQDJHPHQW"

0RQLWRULQJ�DQG�GRFXPHQWDWLRQ�RI�FKDQJHV

&XPXODWLRQ�RI�UHODWHG�FKDQJHV�LQ�D�FKDQJH�PDVWHU�UHFRUG

3ODQQLQJ�DQG�FRQYHUVLRQ�IRU�GHILQHG�HIIHFWLYLWLHV

6DYLQJ�VHYHUDO�FKDQJH�VWDWXVHV�RI�DQ�REMHFW

,QWHJUDWLRQ�LQ�WKH�ORJLVWLFV�SURFHVV�FKDLQ

Page 20: LO 980 engineering change mgmt

© SAP AG LO980 2-7

SAP AG 1999

���

���! "$# %'&)(�* &+",".-/* &)( ��"!- 0�* 1+"

2�3 -41!5+�,#)* &,(2 -76!8 3 1$9:* 6�&; �!&!&<* &)(

2 -76!8 3 1$9:* 6�&

= 3 �! * 9?>@ �<&+�)(A")BC"!&+9 2 -76ED7",1$9

@ �!&,�A(A".BF"!&+9

7UDQVIHU�LQWR�2SHUDWLYH�$UHDV

(&0 2&0

n ECM (Engineering Change Management) = Process for the master data changes

n In the daily process, it can happen that sales orders or projects that are already scheduled in theproduction and converted in the production orders, have to be changed. For this, you use the R/3System 2UGHU�&KDQJH�0DQDJHPHQW�(OCM). It enables product structures to be converted intoproduction structures and processes at the earliest time necessary using MRP and also for them to bechanged at the last possible moment. It is also possible to adapt processed production orders to thechanged product structure. The changes can either be initiated by a changed customer requirement orby a design change using a change master record.

Page 21: LO 980 engineering change mgmt

© SAP AG LO980 2-8

SAP AG 1999

:LWK�KLVWRU\:LWK�KLVWRU\

G

:LWKRXW�KLVWRU\:LWKRXW�KLVWRU\

H � I

J �!K

H �LI

J ��K

H � I

J �!K

MON � J�P �I HQR'S � J �/T

GMON � J P �

I HQ R'S � J �/T

&KDQJH�'RFXPHQWV�DQG�+LVWRU\

:LWKRXW�KLVWRU\:LWKRXW�KLVWRU\EXWEXWZLWKZLWK

FKDQJH�GRFXPHQWVFKDQJH�GRFXPHQWV

n You can perform object changes (for example, BOM and routing changes) in the SAP R/3 Systemeither ZLWK or ZLWKRXW KLVWRU\. However, you should be aware that WKH�V\VWHP�JHQHUDWHV�FKDQJHGRFXPHQWV�HYHQ�IRU�FKDQJHV�ZLWKRXW�KLVWRU\��EXW�WKH�FKDQJH�VWDWXVHV�DUH�QRW�VDYHG�

n &KDQJHV�ZLWKRXW�KLVWRU\These are changes that do not have to be documented because they take place during thedevelopment stage of the product, for example.The status of the object before the change is not saved. You can only find out about the status of theobject before the change by using change documents.

n &KDQJHV�ZLWK�KLVWRU\These are changes that must be documented because they take place during production, for example.Both the status before and after the change is saved. The system generates change documents. Thesechange documents differ for some objects from those generated for changes without history.Engineering Change Management in the SAP R/3 System enables you to document changescompletely. Some of these changes may be needed for product liability purposes, for example.

Page 22: LO 980 engineering change mgmt

© SAP AG LO980 2-9

SAP AG 1999

&KDQJHV�ZLWK�+LVWRU\

6WDWXV�DIWHU�WKH�FKDQJH"&KDQJH�RQ���������6WDWXV�EHIRUH�WKH�FKDQJH"

6WDWXV�DIWHUDIWHU�WKH�FKDQJH"

&KDQJH�RQ���������&KDQJH�RQ���������6WDWXV�EHIRUHEHIRUH�WKH�FKDQJH"

:KHQ�GRHV�WKH�FKDQJH�WDNH�SODFH":KHQ:KHQ�GRHV�WKH�FKDQJH�WDNH�SODFH"

���������%20��������������������IURP,WHP��&RPS��WR��������[����������������������������������������������

���������%20��������������������IURP,WHP��&RPS��WR��������[����������������������������������������������

���������%20��������������������IURP,WHP��&RPS��WR��������[����������������������������������������������

���������%20��������������������IURP,WHP��&RPS��WR��������[����������������������������������������������

:K\:K\�GRHV�WKH�FKDQJH�WDNH�SODFH"

"U�UVU�UVUU�UVU�UVUU�UVU�UVU

Page 23: LO 980 engineering change mgmt

© SAP AG LO980 2-10

SAP AG 1999

&KDQJLQJ�D�%20�8VLQJ�D�&KDQJH�0DVWHU�5HFRUG

WX5+�.&A(!"BY�E#,9?".-'-?",1,6<-78

Z\[ L�]� � Q �VT J'PZ\[ L�:� � Q �<T J�P Z\N �<^��ZCN �<^��

_ R'S [_ R'S [

�� `aK N ��� �� � `bK N �V��

Z\[ L�:� � Q ��T J�PZF[ L�:�� Q �<Tc J�P ZFN ��^d�Z\N ��^��

_ R'S [fe_ R'S [fe

� � `aK N ��� � e�� `aK N ���c� e

n If you change a BOM using the change master record, the system saves both the status before andafter the change.

Page 24: LO 980 engineering change mgmt

© SAP AG LO980 2-11

SAP AG 1999

7DVN�OLVWVg � HhR �i J�Pg �j�<^/� �]� J�Q � H [ � �:���i HhJ T����g �j�<^/� �]� J�Q �k�:�V���l� HhR �m J'Pgon J T [ � Q �m HpJ [ � � Jghqhr R [ S � J ��:�VTsa�4 T��g �t�<TV����X�]� Q [ �g u � J ��/�� S � J �:� J � J�Q �

%20Vg �v���:� �� � �Vwx�t�vTgFy HQ'R'S � J �cT��z� R�Q � R �]�gFqor R [ S � J �XwX�a�g � RJ�Q �z HhJ ���� HcQ ���i H{J wj�t�g Z �� ��T H �]I � �jwj���

0DVWHU�PDVWHUV

&KDUDFWHULVWLFV�&KDUDFWHULVWLFV�RI�FODVV

&ODVVLILFDWLRQ

'RFXPHQWV

&RQILJXUDWLRQ�SURILOH2EMHFW�GHSHQGHQFLHV

9DULDQW�WDEOH

|~}i�7� � �/�|z}m�7� � ����?�?�4��� � �L���d� �/�?��,�� � ��� � � � �L� �� �� �

�6XEVWDQFH�3KUDVH�'DQJHURXV�JRRGV

/LQNHG�2EMHFW�7\SHV

&KDQJHPDVWHU�UHFRUG

Page 25: LO 980 engineering change mgmt

© SAP AG LO980 2-12

SAP AG 1999

5HDVRQ�IRU�FKDQJH9DOLG�IURP6WDWXV

&KDQJH�KHDGHU&KDQJH�KHDGHU

0DWHULDO�PDVWHU�UHFRUG%20V5RXWLQJV������

2EMHFW�PJPW�UHFRUGV2EMHFW�PJPW�UHFRUGV

$OWHUQDWLYH�GDWHV$OWHUQDWLYH�GDWHV

$FFRPSDQ\LQJ�GRFXPHQWV$FFRPSDQ\LQJ�GRFXPHQWV

2EMHFW�W\SHV2EMHFW�W\SHV

&ODVVLILFDWLRQ&ODVVLILFDWLRQ

0DWHULDO��3����%20��3�����������7DVN�OLVW��1�����������������

6WUXFWXUH�RI�WKH�&KDQJH�0DVWHU�5HFRUG

n The change header contains a short description of the change, the valid-from date, and the changestatus.

n You determine which objects can be changed with the change master record by selecting the objecttypes.

n One of the functions of the object management record is to enable you to document changes to aspecific object, for example: material BOM for pump P-100.

n Alternative dates allow you to control the valid-from date of individual objects more precisely.

n You can assign accompanying documents to the change master record.

n You can use classification to search for change master records.

Page 26: LO 980 engineering change mgmt

© SAP AG LO980 2-13

SAP AG 1999

'HVFULSWLRQ��&KDQJH�QXPEHU���ORQJ�WH[W

9DOLG�IURP�GDWH���HIIHFWLYLW\

&KDQJH�QXPEHU�VWDWXV���UHOHDVH�NH\

�$XWKRUL]DWLRQ�JURXS

�5HDVRQ�IRU�FKDQJH���DFFRPSDQ\LQJ�GRFXPHQWV��������d��������d��������d�

�$GPLQLVWUDWLYH�GDWD

&KDQJH�KHDGHU&KDQJH�KHDGHU

&KDQJH�+HDGHU�'DWD

Page 27: LO 980 engineering change mgmt

© SAP AG LO980 2-14

SAP AG 1999

2EMHFW�7\SH�,QGLFDWRUV

$FWLYH2EMHFW�W\SH

;%LOO�RI�PDWHULDO;7DVN�OLVW;'RFXPHQW;0DWHULDO

&KDUDFWHULVWLF

���&ODVV ;

2EMHFW

;

�;�

/RFN

;

*HQ�GLDO*HQ�QHZ0JW5HF�

;;

; ;

The following indicators control processing with the change number for the individual object types:

n $FWLYH� �REMHFW�W\SH�IRU�WKH�FKDQJH�QXPEHU�LV�DFWLYH� You must set this indicator if you want toprocess objects of the object type concerned with the change number.

n 2EMHFW� �DQ�REMHFW�PDQDJHPHQW�UHFRUG�LV�UHTXLUHG�IRU�HDFK�REMHFW: If you set this indicator, thenyou can only make a change to an object of the object type concerned if you create an objectmanagement record for the object first.

n 0JW5HF�� �REMHFW�PDQDJHPHQW�UHFRUG�LV�JHQHUDWHG� If you set this indicator, the system generatesan object management record automatically when you process (create or change) an object of theobject type concerned with the change number. If you set this indicator, you can make changes to allobjects of the object type with the change number.

n *HQ��QHZ� �REMHFW�PDQDJHPHQW�UHFRUG�LV�RQO\�JHQHUDWHG�DXWRPDWLFDOO\�ZKHQ�\RX�FUHDWH�DQREMHFW�IRU�WKH�ILUVW�WLPH� If you set this indicator, an object management record is only createdautomatically when you create an object of the object type concerned. If you want to process anexisting object with the change number, create an object management record manually first.

n *HQ'LDO� �REMHFW�PDQDJHPHQW�UHFRUG�LV�RQO\�JHQHUDWHG�DXWRPDWLFDOO\�ZKHQ�\RX�FUHDWH�DQREMHFW�PDQDJHPHQW�UHFRUG�LQ�GLDORJ� When the object management record is generatedautomatically, the system branches to a dialog screen where you can enter object-specificdocumentation (exception: (Exception: Sales order BOM)

n /RFN� �REMHFW�W\SH�ORFNHG�IRU�FKDQJHV� You can lock and unlock the object type as required.

Page 28: LO 980 engineering change mgmt

© SAP AG LO980 2-15

SAP AG 1999

&KDQJH�PDVWHU�UHFRUG

2EMHFW�W\SH�2EMHFW�W\SH�������

2EMHFW�� @ �+9?".-/* �! 2��4�+�) 

2EMHFW�� ¡'¢ @£2��d ��,�+¤) E�+�,�+¤! 

2EMHFWPJPW�UHFRUG2EMHFW��0DWHULDO�3����

2EMHFW�� @ �+97")-/* �! 2!�/ ¥�,�2EMHFWPJPW�UHFRUG2EMHFW��0DWHULDO�3����

2EMHFW�PDQDJHPHQW�UHFRUG

2EMHFW���������������

����������

+HDGHU+HDGHU

2EMHFW�W\SH�2EMHFW�W\SH���0DWHULDO0DWHULDO

2EMHFW�W\SH�2EMHFW�W\SH���%20%20

$VVLJQPHQW�DQG�'DWD�IRU�WKH�2EMHFW�0JPW�5HFRUGV

¦ "$#A1)-/* ; 9/* 6�&¨§�©)6<&)(ª97"�«A9¬ �! * 8 �L­ -76<B®8!�$9?"¯§° 97".-�&A�$9/* 0A"F8!��9d"©)6!1.±° 8�Bv* &.* #+9/-?�$9/* 0,"C8!��97��.­ 6�-<6�²�D�",1$9<BY(<BF9'-?",1,6�-d8�.­ 6�-<6�²�D�",1$9!1!5+�<&+(!"

° #,#!* (�&A",8O6�²zD�",1$9

n The object management record is an independent master record in the SAP R/3 System. However,you can only create one in connection with a change master record (or ECR/ECO). It is thereforechange number-specific.

n When you enter objects in the object overview of the change master record, an object managementrecord is created in the background. You can create any number of object management records for achange master record. You can only create object management records for materials, BOMs,routings, and documents.

n $VVLJQHG�REMHFW��This contains the key fields that uniquely identify the assigned object (forexample, material number).

n 2EMHFW�PDQDJHPHQW�UHFRUG�GHVFULSWLRQ��You describe the change or reason for the change. Youcan also enter a long text.

n 9DOLG�IURP�GDWH���DVVLJQPHQW�RI�DOWHUQDWLYH�GDWHV��The change made to the assigned object withreference to the change number becomes effective from this date. This date comes from the changeheader or from the assignment of the alternative date.

n /RFN��If you set this indicator, you can temporarily lock the assigned object against eventualchanges with reference to a change number.

n $GPLQLVWUDWLYH�GDWD�IRU�REMHFW�PDQDJHPHQW�UHFRUG�DQG�IRU�FKDQJHV�WR�DVVLJQHG�REMHFWV�Changedate, last person to make the change...

Page 29: LO 980 engineering change mgmt

© SAP AG LO980 2-16

SAP AG 1999

W$ +HDGHU %

&KDQJH�PDVWHU�UHFRUG

0DWHULDO�3����%20�3�������������

0DWHULDO�3����%20�3�������������

2EMHFW�W\SH�2EMHFW�W\SH���0DWHULDO0DWHULDO

2EMHFW�W\SH�2EMHFW�W\SH���%LOO�RI�PDWHULDO%LOO�RI�PDWHULDO

+HDGHU+HDGHU

2EMHFW��0DWHULDO�3����2EMHFW��0DWHULDO�3����

2EMHFW��%20�3�������������2EMHFW��%20�3�������������

$OWHUQDWLYH�GDWH�$$OWHUQDWLYH�GDWH�$

$OWHUQDWLYH�GDWH�%$OWHUQDWLYH�GDWH�%

$OWHUQDWLYH�'DWHV

n The valid-from date in the change header determines when the changes made with reference to thechange number become effective. If you want to override this for an object, then you must createalternative dates. The alternative date only exists within the change master record. You then assignthese alternative dates to one or more object management records.

n As soon as an alternative date is assigned to at least one object management record, the system setsthe object assignments indicator for this alternative date.

Page 30: LO 980 engineering change mgmt

© SAP AG LO980 2-17

SAP AG 1999

6HOHFWLQJ�2EMHFWV�IURP�WKH�3URGXFW�6WUXFWXUHYLD�������*RWR�������2EMHFW�VHOHFWLRQ��&WUO����)���\RX�JRWR�

³~´ µz¶~·i¸/¹~º/¹ ´ ·m¸/¹ ·z´ » ¼�½zµ�´ ¹m¹ »�¾]¹³~·z¿'À

ÁCÂ¥Ã,Ä�Å�Æ ÇxÄ!È7ÄVÅ�Æ7É7Ê'ËhÌ�ÍxÎ~ÊÏÐoÅ�Æ'ÇxÆ7Î¥ÐÅVÆ�Ð�Υļ�»]Ñ »]¸/¹ Ò.ÓiÔmÓ]Õz» ¼¥Ó�Öz»

× ½zÓ]ÔmÕ�»�Ôz·m¿'Øm»i´ ÙE»]º]¸i´ Ú À:¹ Ú µ~ÔÒ.Ó/¹ »i´ Ú Ó]ÑiÛEÜ!Ò)ºÝ~Þ�·mÚ À�¿�»mÔ]¹EÛ¥Ü!Ò)ºÙ�µ�¸]·z¿�»iÔ]¹�º:¹ ´ ·m¸�¹ ·�´ »:ºßm·zÔz¸�¹ Ú µ~ÔmÓiÑ:Ñ µz¸:Ó:¹ Ú µ~Ô'ÛEÜ.Ò)ºÙ�µ�¸]·z¿�»iÔ]¹ ºÒ.Ó/¹ »i´ Ú Ó]Ñ º

àE»/ÖzÚ ºmÚ µzÔ'Ñ »/Öm»iÑ ºÙEµz¸m·m¿V»iÔ]¹ ºÝ~Þ�·�Ú Àz¿�»]Ôi¹× ½mÓmÔiÕz»�Ôz·�¿VØz»i´ º× Ñ Ó:º]ºmÚ á Ú ¸iÓ/¹ Ú µ�ÔÛEÜ!Ò)º

â{½m»i´ »]ã ·iºi»]¶'Ñ Ú º/¹

¼~¹ ÓiÔm¶zÓi´ ¶'À�·m¿�Àmº¼~¹ ÓiÔm¶zÓi´ ¶'À�·m¿�Àmº¼~¹ ÓiÔm¶zÓi´ ¶'À�·m¿�Àmº¼~¹ ÓiÔm¶zÓi´ ¶'À�·m¿�Àmº¼~¹ ÓiÔm¶zÓi´ ¶'À�·m¿�Àmº

n One of the functions of a change master record is to group together changes to related objects. Toselect these objects quickly and easily, you can create object management records from the productstructure browser.

n You can open the product structure browser with any material master or document for example.Once in the product structure browser (for example, product structure for a material master), you cannavigate through the BOMs on several different levels.

n You can only select an object if the change master record contains the appropriate indicators for thecorresponding product structure browser.

n Furthermore, the product structure browser enables you to display and change all relevant objectsboth in the selection and by directly calling up (transaction CC04).

Page 31: LO 980 engineering change mgmt

© SAP AG LO980 2-18

SAP AG 1999

l 1HZ�LQLWLDO�REMHFW� &RQILJXUDWLRQ�0DQDJHPHQWl 1HZ�VHOHFWDEOH�REMHFWV� 5RXWLQJVl 5HODWLRQVKLSV�IRU�URXWLQJV� 6HTXHQFH

0DWHULDOV&ODVVLILFDWLRQ

l 2WKHU�REMHFWV� 5HIHUHQFH�RSHUDWLRQ�VHW,QVSHFWLRQ�SODQ0DWHULDO�VSHFLILFDWLRQ��40�&KHFN�DQG�PDVWHU�FKHFN�FKDUDFWHULVWLFV��40�

l (QKDQFHG�ILOWHU�VHWWLQJV

1HZ�IRU�6HOHFWLRQ�IURP�WKH�3URGXFW�6WUXFWXUH

���&

Page 32: LO 980 engineering change mgmt

© SAP AG LO980 2-19

SAP AG 1999

<RX�DUH�QRZ�DEOH�WR�l (VWDEOLVK�WKH�RSWLRQV�DQG�WKH�XVH�RI

(QJLQHHULQJ�&KDQJH�0DQDJHPHQW�IRU�WKHFRPSDQ\

l &UHDWH�DQG�XVH�WKH�FKDQJH�PDVWHU�UHFRUGZLWK�LWV�VWUXFWXUH�DQG�LWV�IXQFWLRQDOLW\u &KDQJH�KHDGHUu 2EMHFW�PDQDJHPHQW�UHFRUGu $OWHUQDWLYH�GDWHV

l 6HOHFW�DQG�FRS\�REMHFWV�IRU�(QJLQHHULQJ&KDQJH�0DQDJHPHQW�ZLWK�WKH�KHOS�RI�WKHSURGXFW�VWUXFWXUH

&KDQJH�0DVWHU�5HFRUG��8QLW�6XPPDU\

n You can use Engineering Change Management to control and document changes made with historyin the system.

n Changes with history become effective on a key date. The object status both before and after thechange is saved.

n The change master record controls and documents SAP object changes that belong together.

n The system can generate an object management record for certain object types. This record enablesyou to control and document changes to specific objects more precisely.

n You can use alternative dates to set the effectivity date (when changes become effective) for objectmanagement records.

n You can select objects that you want to change by using the product structure.

Page 33: LO 980 engineering change mgmt

© SAP AG LO980 2-20

([HUFLVH([SODQDWLRQ�RI�WKH�6\PEROV�XVHG�LQ�WKH�([HUFLVHV�DQG�6ROXWLRQV

([HUFLVHV

6ROXWLRQV

&RXUVH�2EMHFWLYHV

%XVLQHVV�VFHQDULR

7LSV��7ULFNV

:DUQLQJ�RU�SRLQW�RI�FDXWLRQ

'DWD�XVHG�LQ�WKH�([HUFLVHV'DWD 'DWD�LQ�WKH�7UDLQLQJ

6\VWHPMaterial with BOM

T-F1## T-F100

T-F2## T-F100

T-B1## T-B100

T-B2## T-B200

T-B3## T-B300

T-B4## T-B400

Material

100-130 100-130

T-T1## T-T100

T-T2## T-T200

T-T3## T-T300

T-T0## T-T000

T-T4## T-T400

T-T5## T-T500

Page 34: LO 980 engineering change mgmt

© SAP AG LO980 2-21

Document

T-F1## DRW 000 00 T-F100 DRW 000 00

T-F2## DRW 000 00 T-F200 DRW 000 00

T-F3## DRW 000 00 T-F300 DRW 000 00

T-F4## DRW 000 00 T-F400 DRW 000 00

Class

(001) LO980-## (001) LO980-00

'DWD 'DWD�LQ�WKH�,'(66\VWHP

Material with BOM

T-F1## P-100

T-F2## P-100

T-B1## 100-100

T-B2## 100-200

T-B3## 100-300

T-B4## 100-400

Material

100-130 100-130

T-T1## 100-110

T-T2## 100-120

T-T3## 100-130

T-T0## 100-210

T-T4## 100-310

T-T5## 100-410

Document

T-F1## DRW 000 00 P-100 DRW 000 00

T-F2## DRW 000 00 P-100 DRW 000 00

T-F3## DRW 000 00 P-100 DRW 000 00

T-F4## DRW 000 00 P-100 DRW 000 00

Class

(001)LO980-## (001)100

Page 35: LO 980 engineering change mgmt

© SAP AG LO980 2-22

�([HUFLVHV

8QLW��&KDQJH�0DVWHU�5HFRUG7RSLF��6WUXFWXUH�RI�WKH�&KDQJH�0DVWHU�5HFRUG

At the conclusion of this exercise, you will be able to:

• Create change master records with which you can changeBOMs and material master records

• Assign the meaning of the object management records

As a result of technical problems, pump T-F1## has to bechanged. Therefore, change the BOM with and without history.

The following abbreviations and conditions apply for DOO�exercises

��� �*URXS�QXPEHUsuch as T-F1##T-F101 for group 01

Plant: ����BOM usage: �

1 Changes with and without history:

1-1 The BOM for the pump 7�)��� is reworked.The following change should first be carried out ZLWKRXW history:

In the general data for the spiral casing7�%��� enter a component scrap of���.

Save the changes.

Page 36: LO 980 engineering change mgmt

© SAP AG LO980 2-23

1-2 The BOM is reworked again.The changes should now be made ZLWK history:

In a second session create a change master record for that with the followingdata:

– Change no.: &����Text: 7HFKQ��XSGDWLQJ�SDUW��Valid-from: 7RGD\¶V�GDWH�����PRQWKStatus: $FWLYH

– Object types:BOMs and such that the object management recordshave to be maintained manually.Materials and such that the object management

recordsare generated automatically.

– Object:BOM for material 7�)���in plant ����,Usage �Description: µ,WHP�FKDQJH�QHFHVVDU\¶

Save.

Now carry out (in your first session) the changes to your pump 7�)��� withthe help of the change master record C##-1 ZLWK history.

Replace the flywheel 7�%��� with the flywheel �������.

Save the changes.

1-3 Change the BOM 7�%��� with thechange master record &����. Give a reason for the system message.

_____________________________________________________

_____________________________________________________

_____________________________________________________

_____________________________________________________

Page 37: LO 980 engineering change mgmt

© SAP AG LO980 2-24

([HUFLVHV8QLW��&KDQJH�0DVWHU�5HFRUG7RSLF��6HOHFWLQJ�2EMHFWV�IURP�WKH�3URGXFW�6WUXFWXUH

At the conclusion of this exercise, you will be able to:

• Select objects for Engineering Change Management with thehelp of the product structure

• Use alternative dates.

As a result of technical problems, pump T-F1## has to bechanged again. Therefore, change BOMs for your BOM structurewith history.

2-1 In a second session create another change master record for that with the followingdata:

Change no.: &����Text: 7HFKQ��XSGDWLQJ�SDUW��Valid-from: 7RGD\¶V�GDWH�����PRQWKVStatus: Insufficient consistencyStatus: DFWLYHLong text: Techn. updating part 2, Problems after 1000 operating hours: Oil leak from the casing.

Object types: BOMs and such that the object management recordshave to be maintained manually.Materials and such that the object management records is generatedautomatically.Task lists and such that the object management records is generatedautomatically and a dialog box appears giving a reason for thechange.

Object:Switch to the object selection and access with material T-F1##:

In the product structure on the left, open the folder ‘BOMs’ and then:- the BOM T-F1##, 1000, 1- Items- Item 10 L T-B1##- Material- T-B1##- BOMs.

Page 38: LO 980 engineering change mgmt

© SAP AG LO980 2-25

Generate object management records for the BOMsT-F1## 1000 1 andT-B1## 1000 1.This is done by selecting the BOM from the left-hand side and moving it using‘Drag & Drop’ to the object type column on the right hand side of the screen.

Copy the reserved objects by clicking ‘Copy objects’.

As a description, enter: “Change assembly” or “Change pump”.

In the $OWHUQDWLYH�GDWH�view (using the button) create a alternative date *5�� withthe valid-from date 7RGD\¶V�GDWH�����PRQWKV.

Select the alternative date and assign is to the object management record of theBOM for the pump 7�)���.Save your change master record.

2-2 Now make the following changes ZLWK the change master record�&����.

In the BOM for the pump 7�)����increase the component quantity of the shaft 7�%��� from � to � pieces.Also, change the alternative text in the BOM header to �3XPS *U���.Save the changes.

OptionalIn the BOM for the spiral casing 7�%��� replace the seals 7�7��� with the gasket�������. Save.

2-3 Display your pump 7�)��� for the following times. (First goto the item overview):

Yesterday

How high is the component scrap of the spiral casing 7�%��� (in the general datafor the component)?Why ?

In six weeksIn three monthsEntire lifetimeBranch to the header!

2-4 Display the change document for the pump 7�)���:

Selection date: Current date

Select 'Overview documents'!How many change documents do you see?

Display the documents in detail.What information is contained in the documents?What can you conclude from this?

Page 39: LO 980 engineering change mgmt

© SAP AG LO980 2-26

�6ROXWLRQV

8QLW��&KDQJH�0DVWHU�5HFRUG7RSLF��6WUXFWXUH�RI�WKH�&KDQJH�0DVWHU�5HFRUG

In this course, theactivity group 6$3B&$B3'0B'(6,*1(5³&$�±�3URGXFW�'DWD�0DQDJHPHQW��'HVLJQ�(QJLQHHU´is used. This is configured for you. The menu paths in the solutions relateto your user menu.

You can find the menu paths relating to the SAP menu, in the appendix.

1 Choose

%LOO�RI�PDWHULDO�→�0DWHULDO�%20�→�&KDQJH1-1 In the initial screen enter:

Material: T-F1##Plant: 1000Usage: 1Valid from: Current date

The item overview appears. Select the item 0010 and choose the button³,WHP� �)�” .In the basic data screen, enter the component scrap of 10% and save thischange.

1-2 Open a second session by clicking µ&UHDWH�D�QHZ�VHVVLRQ¶ or 6\VWHP�→&UHDWH�VHVVLRQ. Choose

8VHU�PHQX�→�(QJLQHHULQJ�&KDQJH�0DQDJHPHQW→�&KDQJH�QXPEHU�→&UHDWH

In the initial screen enter:

Change no.: &����Do not change the other settings, namely:Type: Change master recordFunction: Without release keyThe rest remain blank

The change header appears. Here, enter:Text,Valid-from date andStatus.

The date release in the object types overview appears. Select:in the line %LOO�RI�PDWHULDO� the fields $FWLYH�and 2EMHFW�andin the line 0DWHULDO the fields $FWLYH��and��0JW5HF��.

Page 40: LO 980 engineering change mgmt

© SAP AG LO980 2-27

For material masters, the field “ Object” is automatically set when youset “ Active” .

By clicking on �2EMHFWV� �)���the object overview appears.Select the tab page “ Mater. BOM” and enter your BOM here:

Material: 7�)���Plant: 1000Usage: 1 and the description

Save your change master record.

Switch to your first session.

In the initial screen enter the BOM change:

Material: 7�)���Plant: 1000Usage: �Change number: &����Valid-from: (ignore) is determined by the system

The item overview appears. In item 0020 overwrite your component T-B2##with the component 100-200 and save the change.

1-3 Access the initial screen of the BOM change analogous to above withmaterial T-B1##:

The change master is only planned for changes to the BOMT-F1##. For changes to other BOMs, the corresponding object managementrecords have to be created in the change master C##-1.

Page 41: LO 980 engineering change mgmt

© SAP AG LO980 2-28

6ROXWLRQV8QLW��&KDQJH�0DVWHU�5HFRUG7RSLF��6HOHFWLQJ�2EMHFWV�IURP�WKH�3URGXFW�6WUXFWXUH

2-1 Click %DFN� �)� to switch to the user menu and choose(QJLQ��FKDQJH�PJPW�→�&KDQJH�QXPEHU�→�&UHDWH�In the initial screen, enter:

Change no.: &����Do not change the other settings, namely:Type: Change master recordFunction: Without release keyThe rest remain blank

The change header appears. Enter hereText,Long text (Click ³&KDQJH�KHDGHU�ORQJ�WH[W´� �6KLIW���)�)Save long text! and go backenter valid-from date andstatus.

By clicking on �2EMHFW�W\SHV��the object types overview appears. Select:in the line %LOO�RI�PDWHULDO� the fields $FWLYH, 2EMHFW¶in the line 7DVN�OLVW the fields $FWLYH��2EMHFW� 0JW5HF��and�*HQ�'LDO andin the line 0DWHULDO the fields $FWLYH��and��0JW5HF��.Switch to the object selection by clicking

5HOHDVH����&� &OLFN�2EMHFW�2YHUYLHZ� �$OO�2EMHFWV� �)�5HO�����%� *RWR�→�6HOHFW�REMHFW� �&WUO���)�or using the corresponding button in the object overview on the tab pages

Continue as described in the exercise:

(Access with the material 7�)����In the product structure on the left, open the folder ‘BOMs’ and then:

- the BOM T-F1## 1000 1- Items- Item 10 L T-B1##- Material- T-B1##- BOMs.

Page 42: LO 980 engineering change mgmt

© SAP AG LO980 2-29

Generate object management records for the BOMsT-F1## 1000 1 andT-B1## 1000 1.This is done by selecting the BOM from the left-hand side and moving it using

‘Drag & Drop’ to the object type column on the right hand side of the screen.Copy the reserved objects by clicking µ&RS\�REMHFWV¶� �6KLIW.���)��In the detail screen of the object management record, enhance the description.

Click ³$OWHUQDWLYH�GDWHV� �)�´ or

*RWR�→�$OWHUQDWLYH�GDWH�→�$OWHUQDWLYH�GDWHV

Create an alternative date *5�� with the valid-from date 7RGD\¶V�GDWH����PRQWKV.Select the alternative date and click ³2EMHFW�DVVLJQ�´. Select the object managementrecord of the pump T-F1## and click ³$VVLJQ�DOW��GDWH´�Save the change master record.

2-2 In the initial screen of the BOM change (8VHU�PHQX�→�%LOO�RI�PDWHULDO�→0DWHULDO�%20�→�&KDQJH), enter:

Material: 7�)���Plant: 1000Usage: �Change number: &����Valid-from: (ignore) is determined by the system

The item overview appears. In item 0030 overwrite the quantity '1' with quantity '2'.

Click on “+HDGHU� �)�” to switch to the header overview and change thealternative text.

Save the changes.

Page 43: LO 980 engineering change mgmt

© SAP AG LO980 2-30

2-3 Choose 0DWHULDO�%20�→�'LVSOD\.

In the initial screen enter:Material: 7�)���Plant: 1000Usage: 1Valid from: YesterdayValid-to: Yesterday

The item overview appears.Select item 0010 and click “ ,WHP� �)�” to go to the detail screen.Í The component scrap equals 10%, because the changes

were made with the current date, but not historically.

Valid-from and valid-to: today’ s date + six weeksÍ Changes with C##-1 taken into account

Valid-from and valid-to: today’ s date + three monthsÍ Changes with C##-1 and C##-2 taken into account

Valid from: blank (or today’ s date)Valid-to: blank (or today’ s date + three months)Using the corresponding button, branch to the header.Í 2 Header data records.

2-4 From the user menu select5HO�����&��%LOO�RI�0DWHULDO�→�5HSRUWLQJ�→ &KDQJH�'RFXPHQW�→�0DWHULDO�%205HO�����%��(QJLQHHULQJ�&KDQJH�0DQDJHPHQW�→ 5HSRUWLQJ�→�&KDQJH�'RFXPHQW→�0DWHULDO�%20.or from any BOM transaction(QYLURQPHQW�→�&KDQJH�'RFXPHQWIn the initial screen enter:Material: 7�)���Plant: 1000Usage: 1Selection date: Today’ s date (that means changes today or later)

Select ''RFXPHQW�RYHUYLHZ�'In Rel. 4.6B you see four change documents and in Rel. 4.6C you see five.

Move the cursor to the document line and select 'LVSOD\�GRFXPHQW.

In the first document, you see your first non-historic changes (increase componentscrap).

In the second document, you find 3 entries created.A new item was created andfor the new and the old item, a new information selection was stored.

In the third document there is a note saying that the BOM has first been changedhistorically. In Rel. 4.6C the last change number was also changed to C##-1.

Page 44: LO 980 engineering change mgmt

© SAP AG LO980 2-31

In the fourth document, you find 4 entries created.Three entries relate, analogously to above, to the changed BOM item. The fourthentry provides information about the BOM header.

Only in Rel. 4.6C do you find in the fifth document that the change number hasbeen changed to C##-2.

Page 45: LO 980 engineering change mgmt

© SAP AG LO980 3-1

SAP AG 1999

2EMHFW�&KDQJHV

l &KDQJHV�WR�PDWHULDO�PDVWHU�UHFRUGVl &KDQJHV�WR�GRFXPHQWVl &KDQJHV�WR�%20Vl &KDQJHV�WR�URXWLQJVl &KDQJHV�WR�FODVVHV��FKDUDFWHULVWLF�DVVLJQPHQWV�WR

FODVVHV�DQG�FODVVLILFDWLRQl &KDQJHV�WR�REMHFW�GHSHQGHQFLHV��FRQILJXUDWLRQ�SURILOHV

DQG�YDULDQW�WDEOHV

&RQWHQWV�

Page 46: LO 980 engineering change mgmt

© SAP AG LO980 3-2

SAP AG 1999

2EMHFW�&KDQJHV��7RSLF�2EMHFWLYHV

$W�WKH�FRQFOXVLRQ�RI�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�l $VVLJQ�UHYLVLRQ�VWDWXVHV�DQG�XVH�WKHP�WR�VHOHFW

GHYHORSPHQW�VWDWXVHVl 3URFHVV�WKH�YDULRXV�REMHFWV�ZLWK�UHIHUHQFH�WR�D

FKDQJH�QXPEHUl 1DPH�WKH�GLIIHUHQFHV�DQG�WKH�VSHFLDO�IHDWXUHV

RI�PDLQWDLQLQJ�REMHFW�W\SHV�ZLWK�D�FKDQJHPDVWHU�UHFRUG�

l :RUN�ZLWK�DOWHUQDWLYH�GDWHV�DQG�GDWH�VKLIWV

Page 47: LO 980 engineering change mgmt

© SAP AG LO980 3-3

SAP AG 1999

��

5HSRUWLQJ5HSRUWLQJ ��

�� &KDQJH�+LHUDUFK\��&KDQJH�+LHUDUFK\��5HOHDVH�.H\�5HOHDVH�.H\�«« ��&KDQJH�0DVWHU�5HFRUG&KDQJH�0DVWHU�5HFRUG

3URFHVVLQJ�&KDQJHV�3URFHVVLQJ�&KDQJHV�ZLWK�:RUNIORZZLWK�:RUNIORZ ��&RXUVH�2YHUYLHZ&RXUVH�2YHUYLHZ ��

(&5���(&2(&5���(&2 ��

2EMHFW�&KDQJHV2EMHFW�&KDQJHV

6XPPDU\6XPPDU\ ��

2UGHU�&KDQJH�2UGHU�&KDQJH�0DQDJHPHQW��2&0�0DQDJHPHQW��2&0� ��

&RXUVH�2YHUYLHZ�'LDJUDP

Page 48: LO 980 engineering change mgmt

© SAP AG LO980 3-4

SAP AG 1999

l 6DOHV�ZRXOG�OLNH�WR�VHOO�D�QHZ�SXPS�W\SH��7KHFHQWUDO�FKDQJH�GHSDUWPHQW�LV�DVNHG�WR�DUUDQJHDQG�H[HFXWH�WKH�QHFHVVDU\�FKDQJHV�

l $OO�UHODWHG�REMHFWV�DUH�FKDQJHG�

2EMHFW�&KDQJHV��%XVLQHVV�6FHQDULR

Page 49: LO 980 engineering change mgmt

© SAP AG LO980 3-5

SAP AG 1999

0DWHULDO�&KDQJHV�DQG�7KHLU�(IIHFWV

&KDQJH�WKH�VKDIW&KDQJH�WKH�VKDIW&KDQJH�&KDQJH�WKH�URXWLQJWKH�URXWLQJ&KDQJH&KDQJH

WKH�%20WKH�%20

&KDQJH&KDQJHWKH�GRFXPHQWWKH�GRFXPHQW ���

&KDQJHPDVWHU�UHFRUG1��

n You can change any number of objects with a change number.

n The object type indicators control which objects you can process with a change number.

n There are some special features for the different change objects.

Page 50: LO 980 engineering change mgmt

© SAP AG LO980 3-6

SAP AG 1999

0DWHULDO�0DVWHU�5HFRUG���&KDQJH�,PPHGLDWHO\

W����������� ������ ��������������������������� �!"�$#"��%&'� �)(*�����+��� ���,�

0DWHULDO�PDVWHUUHFRUG

053�FRQWUROOHU�����

�-�+������"�.� �'/01�2�01�2 3�0&0�0

&KDQJH�GRFXPHQW

053�FRQWUROOHU�����

,PPHG�

&KDQJH

&KDQJH�GRFXPHQW

053�FRQWUROOHU�����

,PPHG�

&KDQJH

$1��465�7 465�7 894�4�4

�%1��4:597 49;67 8�4�4�4

���

n If you want to change materials with the function�&KDQJH -> ,PPHGLDWHO\, you can only change themwith reference to a change number if the YDOLG�IURP date is the FXUUHQW date or if it is in the SDVW.

n No new data records are created for material changes with reference to a change number. The systemsaves the changes in FKDQJH�GRFXPHQWV. The changes that you last saved - regardless of the YDOLG�IURP date of the change master record - are always taken as the current status. In this example, thedata from the second change is the current status (MRP controller 055).

n There is QR�KLVWRU\�UHTXLUHPHQW for material changes. You can process materials at a later datewithout reference to a change number even if you have previously processed them with reference toa change number. You would still have complete documentation because change documents aresaved for all material changes - regardless of whether you made the changes with or without achange number.

n 2EMHFW�PDQDJHPHQW�UHFRUGV are required by material master records for changes with changenumbers. The relevant indicator in the object type overview is set automatically. However, you haveto ensure that a relevant object management record exists or is automatically created.

Page 51: LO 980 engineering change mgmt

© SAP AG LO980 3-7

SAP AG 1999

0DWHULDO�0DVWHU�5HFRUG���6FKHGXOHG�&KDQJH

0DWHULDO�PDVWHUUHFRUG

<>=@?("� ����+� ��� ����/ 1A0�1

�-�+������*�B� � /01�2 0DC�2 3&0�0�0 6FKHGXOH

&KDQJH

�$FWLYDWLRQ0�1�2 0�1�2 01

EGFIH�JIKDLM�NDOAPRQ LAJTS

UWV'XORN JTS�Y N&Z Z LRY�[ \T\I]

'RF�

WCreated on9DOLG�IURP�GDWH�LQ�WKH�IXWXUH

'RF�

6FKHGXOH

&KDQJH

$FWLYDWLRQ0�^*2�01�2 0�3

EGFTHAJRKDLM�N_ODPRQ LAJTS

U`V�XOIN JTS�Y N&Z Z LAY�[ \T\a]

1��4�5�7 4:5�7 8�4�4�5

1��465�7 465�7 8�494�8

n If you want to change materials with the function &KDQJH -> 6FKHGXOH, you can only change themwith reference to a change number if the valid-from date is in the IXWXUH.

n A change that is planned for a specific date in the future is stored in the form of a change document.The date is stored in the document header of the change document. The planned changes must beactivated on a specific date if they are to become effective. When you activate the changes, thesystem only takes into account those changes that are to become effective on the given date.

n For technical reasons, the current status is always displayed for the following data, even if you'LVSOD\�RQ�NH\�GDWH:• All types of long text (for example: purchase order text)• Document data• Co-products• Average plant stock• Revision level• Conditions of sale, customs tariff preferences, export licenses• Assignment to configurable material and variant configuration values• QM inspection data• Production versions• Consumption values and forecast values and execution of the forecast• Classification

n 2EMHFW�PDQDJHPHQW�UHFRUGV are required by material master records for changes with changenumbers. The relevant indicator in the object type overview is set automatically. However, you haveto ensure that a relevant object management record exists or is automatically created.

Page 52: LO 980 engineering change mgmt

© SAP AG LO980 3-8

SAP AG 1999

&UHDWH�ZLWK�FKDQJH�PDVWHU�

3XPS3XPS

6KDIW��6KDIW��&DVLQJ��&DVLQJ��

([DPSOH�

���&KDQJH�ZLWKFKDQJH�PDVWHU�

3XPS3XPS

���&KDQJH�ZLWKFKDQJH�PDVWHU�

3XPS3XPS

���&KDQJH�ZLWKFKDQJH�PDVWHU�

3XPS3XPS

&KDQJH�QR�������

�W���b#&� �"����%*(���# / 1_0"c

&KDQJH�QR�������5HYLVLRQ�OHYHO��� ��

&KDQJH�QR�������5HYLVLRQ�OHYHO� ���

&KDQJH�QR�������5HYLVLRQ�OHYHO� ���

6KDIW��6KDIW��&DVLQJ��&DVLQJ�� &DVLQJ��&DVLQJ�� 6KDIW��6KDIW�� &DVLQJ��&DVLQJ�� 6KDIW��6KDIW��

7KH�5HYLVLRQ�/HYHO���2YHUYLHZ

n If you make changes to material masters or documents with reference to a change number, you canassign a revision level to a specific change status. You can either assign a new revision level to everychange with reference to a change number, or you can use revision levels for particular changes (forexample, for larger, more important changes).

n This means that you can process the objects concerned at a later date either with reference to achange number or with reference to the revision level.

n You can only assign one revision level per change number. An object management record must existbefore you can assign a revision level.

n You can assign and display a revision level in several different ways.

n This is described in detail in this unit.

n Processing with revision levels PXVW�EH�DFWLYDWHG in Customizing. You also define the sequence ofthe UHYLVLRQ�OHYHO�QXPEHUV in Customizing.

Page 53: LO 980 engineering change mgmt

© SAP AG LO980 3-9

SAP AG 1999

5HYLVLRQ�6WDWXV�$VVLJQPHQW�IRU�0DWHULDO�0DVWHU5HFRUGV

U HIS�LAY�d H ZaQ HIeaS�L�YU HIS�LAY�d H ZaQ HTeIS�LDY

PDLQWHQDQFHPDLQWHQDQFHf*ghUfgiU

PDLQWHQDQFHPDLQWHQDQFH 7UDQVDFWLRQ7UDQVDFWLRQ

5HYLVLRQ�OHYHO5HYLVLRQ�OHYHO ����������'LVSOD\HG�LQ�'LVSOD\HG�LQ���������0DW��PDVWHU�PDLQWHQDQFH��0DW��PDVWHU�PDLQWHQDQFH��������%20�H[SORVLRQ��%20�H[SORVLRQ��������2EMHFW�PJPW�UHFRUGV��2EMHFW�PJPW�UHFRUGV��������3XUFKDVH�UHTXLVLWLRQ��3XUFKDVH�UHTXLVLWLRQ��������3XUFKDVH�RUGHU��3XUFKDVH�RUGHU��������:RUN�RUGHU��:RUN�RUGHU

DVVLJQVDVVLJQV

��������8VDEOH�LQ�WKH�PDLQWHQDQFH�RI�8VDEOH�LQ�WKH�PDLQWHQDQFH�RI���������0DWHULDO�PDVWHU�UHFRUG��0DWHULDO�PDVWHU�UHFRUG��������%LOO�RI�PDWHULDO��%LOO�RI�PDWHULDO��������5RXWLQJ��5RXWLQJ

n You can identify special change statuses of a material by using a UHYLVLRQ�OHYHO.As a rule, when you process a material BOM you give new the new, changed BOM a new revisionlevel. This revision level is assigned to the header material of the changed BOM. You can also referto the revision level when you process routings for the material.

n Revision levels require object management records for the material master records.

Page 54: LO 980 engineering change mgmt

© SAP AG LO980 3-10

SAP AG 1999

&KDQJLQJ�'RFXPHQWV�ZLWK�(&0

UHVHUYHGUHVHUYHG

UHVHUYHGUHVHUYHG DVVLJQHG

UHVHUYHGUHVHUYHG

'RFXPHQWYHUVLRQ���

&KDQJH�QR�����������1��

&KDQJH�PDVWHU�UHFRUG1��

&KDQJH�PDVWHU�UHFRUG1��

&KDQJH�PDVWHU�UHFRUG

1��

n 1R new data record is created when you change a document.

n You can save the history of a document by using YHUVLRQ�PDQDJHPHQW. If you want to preserve acertain processing status, create a new version.

n The change number links the document to all other R/3 objects that are affected by a certain change(for example: BOM or task list).

n You can enter a change number in the basic data for a document. This creates a validity period thatstarts on the YDOLG�IURP date.

n You can UHVHUYH a document for more than one change number. To do this, you create an objectmanagement record for the document in each of the change master records. If you change thedocument, all the change numbers for which the document is reserved are displayed.

n You can process the document with reference to a FKDQJH�QXPEHU. As soon as you have entered achange number from the reservation list in the document, you can no longer change the changenumber. This also applies if you enter a change number directly in a document that is not reservedfor a change number.

n If you want to create a reference to another change number, create a new version.

Page 55: LO 980 engineering change mgmt

© SAP AG LO980 3-11

SAP AG 1999

5HYLVLRQ�/HYHO�$VVLJQPHQW�IRU�'RFXPHQWV

:LWKRXW�UHIHUHQFH�WR�D�FKDQJH�QXPEHU

releasedreleased

&KDQJHPDVWHU�UHFRUG1��

&KDQJHPDVWHU�UHFRUG1��

'RFXPHQWYHUVLRQ���

&KDQJH�QR�����������1��

'RFXPHQWYHUVLRQ���

'RFXPHQWYHUVLRQ���

&KDQJH�QR�����������1��

'�'�

5HYLVLRQ�OHYHO

n The revision level serves as an identification number for an important document version. You canonly assign a revision level in document processing functions.

n If a change number has been entered in the document and you release the document version for thefirst time, the system automatically assigns the revision level.

n When you process the document structure, you can display the revision level but you cannot assign arevision level.

n You make settings for revision levels for documents in Customizing for 'RFXPHQW�0DQDJHPHQW.n Under 'HILQH�GRFXPHQW�W\SHV you define whether you can assign a revision level to documents of

each document type (indicator 'RFXPHQW�ZLWK�UHYLVLRQ�OHYHO).n Under 'HILQH�GRFXPHQW�VWDWXV you set the release indicator for the status that defines the document

as released.

n There are functions for changing and displaying revision levels in the (QJLQHHULQJ�&KDQJH0DQDJHPHQW menu.

Page 56: LO 980 engineering change mgmt

© SAP AG LO980 3-12

SAP AG 1999

%20���+HDGHU�'DWD

6WDWXVQHZ�YDOXH���

�������� �������� �������� ����������D

E

&KDQJH�QXPEHU1�������0DWHULDO�3����

W

&UHDWH

%DVH�TXDQWLW\QHZ�YDOXH���

F

&KDQJH�QXPEHU1�������0DWHULDO�3����

%20%20+HDGHU�RYHUYLHZ

%20�KHDGHUV9DOLG�IURP����9DOLG�WR�����&KJ��QU��������������������������1���������������������������1������������������������

n When you change header data with reference to a change number, the system saves both the old andthe new BOM header status of a BOM header in header records (independent of item effectivity).

n The validity periods of a header record are determined by the YDOLG�IURP and the YDOLG�WR dates. Thesystem determines the YDOLG�IURP date from the change master record.

n The validity periods end with the YDOLG�WR date. This date is automatically determined by the system.31.12.9999 is the maximum 9DOLG�WR date. The 9DOLG�WR date is not explicitly saved with this.If you process the BOM header more than once with reference to different change numbers, then theYDOLG�IURP date of the following change number is the YDOLG�WR date of the previous data record.

n Some header data is QRW stored with history. The old values are overwritten by the new values whenyou make a change and no new header record is created.This is the case for the following header data:

• BOM text• External BOM number• Lot-size range (multiple BOMs)• Name of the BOM group

Page 57: LO 980 engineering change mgmt

© SAP AG LO980 3-13

SAP AG 1999

%20���,WHP�'DWD

F

2SHUDWLRQ�VFUDSQHZ�YDOXH���

D

E

,WHP�TXDQWLW\�QHZ�YDOXH������

&KDQJH�QXPEHU1��&RPSRQHQW��������

&KDQJH�QXPEHU1��&RPSRQHQW��������

3�j*2k1�1�2 0�0 1A3*2�1D3*2 0�0 31�2 0�^*2 0�1 l1�2�1_3*2 m"m"m�mW

&UHDWH

%20%20

n When you change item data with reference to a change number, the system saves both the old andthe new BOM item status as complete item data records.

n The item data record is not duplicated if you make and cancel the the change in one transaction. Fortechnical reasons, the system creates a new item record for the following item data, even if youcancel the change in the same transaction:

• Sub-item data• Object dependencies• Long text

n The validity periods of an item record are determined by the YDOLG�IURP and the YDOLG�WR dates. Thesystem determines the YDOLG�IURP date from the change master record.

n The effectivity period ends with the 9DOLG�WR date that the system determines dynamically. The9DOLG�WR�date is not explicitly saved with this.. The last possible YDOLG�WR date is 12/31/9999.

n If you process the item more than once with reference to different change numbers, then the YDOLG�IURP date of the following change number is the YDOLG�WR date of the previous item record.

Page 58: LO 980 engineering change mgmt

© SAP AG LO980 3-14

SAP AG 1999

%20���(IIHFWLYLW\�3HULRG

l1�2k1_3*2 m�m&m�m

9DOLG9DOLGIURPIURP

&KDQJHQXPEHU

1��

01�2 0�1�2 0�1�2 0�32 01�2 0"l*2 01�2 0�C�2

$

$

$ 1�� 1��

1��

$,WHP�%,WHP�%

,WHP�$,WHP�$

,WHP�&,WHP�&

%20%20

9DOLG9DOLGIURPIURP

&KDQJHQXPEHU

1��9DOLG9DOLGIURPIURP

&KDQJH&KDQJHQXPEHUQXPEHU

1��1��

1��

1��

%20�KHDGHU%20�KHDGHU

"

n If you process the BOM with reference to a change number, the system determines the valid headerrecord and also the valid item records for the YDOLG�IURP date. In this example, there are two validitems for the YDOLG�IURP date of change number N-1 (item A and item C).

n Item B can be created

• without ECM by a change valid-from 1.3 or• with a change number such as N-4 with the relevant date or• with one of the change numbers and alternative dates above.

n You define the settings for processing BOMs with Engineering Change Management when youconfigure your BOM management system (in Customizing). Under 'HILQH�PRGLILFDWLRQ�SDUDPHWHUVyou can make basic settings. For example, you can activate Engineering Change Management forBOM processing. If you do this, then there is a history requirement for BOMs. You can also specifywhether you must enter a change number when you create a BOM. In Customizing (Set historyrequirement) you can define for a BOM usage (for example, production) that you must use a changenumber to change a BOM that has a certain status - even if you have not worked with a changenumber until then.

n In exceptional cases, you can allow a BOM change without a change number for BOMs with historyrequirement by using authorization object C_STUE_NOH. Please note that, in this case, the changesare not documented completely.

Page 59: LO 980 engineering change mgmt

© SAP AG LO980 3-15

SAP AG 1999

5RXWLQJV

l�1�2�1A32 m�m�m"m

.H\�GDWH.H\�GDWH

7DVN�OLVW�7DVN�OLVW�KHDGHUKHDGHU

6HTXHQFH6HTXHQFH

2SHUDWLRQ��2SHUDWLRQ��

2SHUDWLRQ��2SHUDWLRQ���-!&���&n��po>� �!&� ��(!"���&n�.���*�rq"��

n When you process the following WDVN�OLVW�REMHFWV with reference to a change number, the systemsaves both the old and the new status:

• Header, operation, sequence, assignment of production resource/tool to operation• Inspection characteristics• Assignment of material components to operation

n The key date determines the start of the validity period for a task list object. The system assigns theYDOLG�IURP date from the change master record.

n The validity periods end with the YDOLG�WR date. This date is automatically determined by the system.The last possible YDOLG�WR date is 12/31/9999.If you process the task list object more than once with reference to different change numbers, thenthe YDOLG�IURP date of the following change number is the�YDOLG�WR date of the previous data record. Ifyou process the task list on a specific date, the system determines all task list objects that are valid onthat date.

n Task list objects can be processed without reference to a change number, even if you have previouslyprocessed them with reference to a change number. In this case, however, you will be left with anincomplete history. In the above example, operation 2 was created with reference to a changenumber and then changed without a change number. No new validity period exists. The new value(for example, base quantity) is valid from the YDOLG�IURP date of the change number.

Page 60: LO 980 engineering change mgmt

© SAP AG LO980 3-16

SAP AG 1999

l�1�2�1A32 m�m�m"m9DOLG�IURP9DOLG�IURP

&KDQJH�QXPEHU�1��

3URFHVVLQJ�RI�FKDUDFWHULVWLFV &ODVVLILFDWLRQé�&KDUDFWHULVWLFV��FKDUDFWHULVWLF�YDOXHV é�$VVLJQPHQW�FODVV���REMHFWé�7H[WV�IRU�FKDUDFWHULVWLFV�DQG� é�9DOXHV���&KDUDFWHULVWLF�YDOXHVé�&KDUDFWHULVWLF�DVVLJQPHQW�LQ�FODVV�PDLQWHQDQFH

GHOHWHG&KDUDFWHULVWLF�&KDUDFWHULVWLF�

YDOXHVYDOXHV���"�q��s�*�n ���"���o>!�� ��

2EMHFWV�LQ�WKH�&ODVVLILFDWLRQ�6\VWHP

n There is a KLVWRU\�UHTXLUHPHQW for all objects in the classification system that you have processedwith reference to a change number.

n The system saves both the old and the new status of the objects in the classification system that youchange with reference to a change number.

n 2EMHFW�PDQDJHPHQW�UHFRUGV are QRW supported for objects in the classification system. This meansthat you cannot, for example, select an alternative YDOLG�IURP date for a classification system object.

n The validity periods of an object are determined by the YDOLG�IURP and YDOLG�WR dates.There are no limitations for the YDOLG�IURP date. If you process an object with reference to a changenumber, the system determines the YDOLG�IURP date from the change master record.

n The validity period ends with the YDOLG�WR date. This date is automatically determined by the system.The last possible YDOLG�WR date is 12/31/9999.If you process the object more than once with reference to different change numbers, then the YDOLG�IURP date of the following change number is the�YDOLG�WR date of the previous data record.

n In Customizing for &ODVVHV you can define for each class type whether (QJLQHHULQJ�&KDQJH0DQDJHPHQW can be used for changing classification system objects.

Page 61: LO 980 engineering change mgmt

© SAP AG LO980 3-17

SAP AG 1999

2EMHFW�2EMHFW�GHSHQGHQFLHVGHSHQGHQFLHV &RQILJXUDWLRQ�SURILOH�IRU�

FRQILJXUDEOH�REMHFWV

%DVLF�GDWD%DVLF�GDWD 6RXUFH�FRGH6RXUFH�FRGHMaterial

master recordStd network

PM ECRModel specs

�&tp#�#���� (����� � �vu � �Do�%�wG���:��%�&tW%�%'� n �*�$���

�s�",�������&(��x���%�� n ��wi��k:���&n*%�&tW%�%'� n �*�$���)(*� ��%&%

� qRy+�"(� ��#"���&����*(*� ��%����&�B����A�*:!"��

#"��+�&�B������%

�"tv#�#���� (������� �vu�� ��o�%�*wi������%�"t`%�%�� n �*�B���

����������,�&(��>��"%�� n ��*wh��,����&n*%�"t`%�%�� n �*�B���'(� ��%"%

� qRy��*(D'���#"���&����&(� ��%

9DULDQW�&RQILJXUDWLRQ�2EMHFWV

RQO\��YLHZ

VHYHUDOYLHZV

9DULDQW�WDEOHV9DULDQW�WDEOHV

7DEOH�7DEOH�FRQWHQWVFRQWHQWV

n You can maintain both a VLQJOH�GHSHQGHQF\ and a GHSHQGHQF\�QHWZRUN with reference to a changenumber. When you change the basic data or the source code with reference to a change number, thesystem saves both the old and the new object statuses.

n You define how the configuration profile for a material or a standard network, and so on, isprocessed in Customizing for 9DULDQW�&RQILJXUDWLRQ.

Under 0DLQWDLQ�VWDWXV you determine for each configurable object whether changes to configurationprofiles with a certain status (for example, UHOHDVHG) are stored with history.

Several views exist for the configuration object 0DWHULDO. For the other configuration objects onlyone view exists.

n The table contents of a variant table can also be changed historically, however, the table structure cannot.

n There is a KLVWRU\�UHTXLUHPHQW for all variant configuration objects that you have processed withreference to a change number.

Page 62: LO 980 engineering change mgmt

© SAP AG LO980 3-18

SAP AG 1999

X

2EMHFW 1HZGDWD�UHFRUGV

+LVWRU\UHTPW

2EMHFWPJPW�UHFRUG

$FWLYLWLHVLQ

&XVWRPL]LQJ%LOO�RI�PDWHULDO7DVN�OLVW'RFXPHQW0DWHULDO2EMHFWV�IURPFODVVLILFDWLRQ2EMHFW�IRUYDULDQWFRQILJXUDWLRQ

; ; ; ;; �;�EWB ; �� � ; ;�Status

� � ; �; � for class type

; ; �Status forconfigurableobjects

2YHUYLHZ�RI�&KDQJH�2EMHFWV

;

Mod.parameterStatus

n As a rule, both the old and the new status are saved in different data records when you make achange with history to a change object.Exceptions: Changes to materials are stored in change documents.Version management represents the important change statuses of a document. Versions obtain avalidity period from the change number.

n There is a history requirement for BOMs, documents, objects in the classification system, variantconfiguration objects, and partly for routings (EWB).As soon as you have released a document version with reference to a change number, followingversions can also only be released with reference to a change number. You can, however, process theobject without reference to a change number up to its release.You can process materials and partial routings (not for the EWB) without reference to a changenumber, even if you have previously made changes with reference to a change number.

n To control changes to individual objects, you can create object management records for BOMs, tasklists, documents, and materials.

n You must make settings in Customizing for BOMs, documents, and class types. For BOMs andconfiguration profiles you can define status-dependent history requirements.

Page 63: LO 980 engineering change mgmt

© SAP AG LO980 3-19

SAP AG 1999

'DWH�6KLIW�:LWKRXW�&KDQJLQJ�WKH�(IIHFWLYLW\�3HULRG

0DWHULDO0DWHULDO

%20%20

��5RXWLQJ5RXWLQJ

'RFXPHQW'RFXPHQW

������������������������

W1�� 1�� 1�� 1��

&KDQJH�PDVWHUUHFRUG� ����� ������������������'/ 1��

n As long as there are no changes to objects, you can enter a new valid-from date. However, the statusof the change master record must allow you to change the date. As soon as there is at least one objectchange, you must perform a date shift.

n When you try to perform a date shift, the system checks the settings in Customizing. If the datecheck is activated, then you can only perform a date shift to a date outside the "protected timeperiod".

n As long as the date shift does not lead to inconsistencies in any of the objects that have already beenchanged with the change number (for example, two changes to a BOM header on the same date) andit does not lead to a change in the sequence of the validity period, then you can perform this dateshift for any object type.

Page 64: LO 980 engineering change mgmt

© SAP AG LO980 3-20

SAP AG 1999

'DWH�6KLIW�&KDQJLQJ�WKH�(IIHFWLYLW\�3HULRG

0DWHULDO0DWHULDO

%20%20

�5RXWLQJ5RXWLQJ

'RFXPHQW'RFXPHQW

������������������������

W1R�� 1R�� 1R�� 1R��1R��

&KDQJH�PDVWHUUHFRUG� ���� �'�����+���z������/1��

Page 65: LO 980 engineering change mgmt

© SAP AG LO980 3-21

SAP AG 1999

2EMHFW�&KDQJHV��8QLW�6XPPDU\

<RX�DUH�QRZ�DEOH�WR�l $VVLJQ�UHYLVLRQ�VWDWXVHV�DQG�XVH�WKHP�WR

VHOHFW�GHYHORSPHQW�VWDWXVHVl 3URFHVV�WKH�YDULRXV�REMHFWV�ZLWK�UHIHUHQFH�WR�D

FKDQJH�QXPEHUl 1DPH�WKH�GLIIHUHQFHV�DQG�WKH�VSHFLDO�IHDWXUHV

RI�PDLQWDLQLQJ�REMHFW�W\SHV�ZLWK�D�FKDQJHPDVWHU�UHFRUG�

l :RUN�ZLWK�DOWHUQDWLYH�GDWHV�DQG�GDWH�VKLIWV

n Change statuses can be assigned a revision level.

n You can make material changes immediately, or you can schedule them.

n You can use version management to administer document changes with history.

n You can only perform date shifts that change the effectivity period for BOMs and routings.

Page 66: LO 980 engineering change mgmt

© SAP AG LO980 3-22

([HUFLVHV

8QLW��2EMHFW�&KDQJHV7RSLF��%DVLF�GDWD�REMHFW�FKDQJHV

At the conclusion of this exercise, you will be able to:

• Change the various objects with Engineering ChangeManagement.

• Assign a revision level and be able to work with this.

• Use date shifting and know the control options of this process.

Due to a sales requirement changes also have to be made todrawings, BOMs, routings, material masters and objects in theclassification system and variant configuration.

1-1 :LWK the change master record &����� change the routing for the spiral casing 7�%���.

For this use the Engineering Workbench.

In operation 0010 replace work center ���� with ����.

Save the changes.

Display your routing for material 7�%��� at the following times:

- Today

- Today’s date + 4 months

- Interval: From today til today + 4 months

1-2 Create another change master record with the following data:

Change no.: &����View: Change Header:Text: 7HFKQ��XSGDWLQJ�SDUW��Valid-from: 7RGD\¶V�GDWH����PRQWKVStatus: ActiveReason for change: Further complicationsLong text: Techn. updating part 3Problems after 1000 operating hours: Break of hexagonal head screws.

View: Object types:BOM: active; object management records (manual)

Page 67: LO 980 engineering change mgmt

© SAP AG LO980 3-23

Task list: active; object management records (automatically generated,dialog box for the reasons for change)

Document: active; object management records (manual)

Material: active; object management records (manual)

Characteristic activeCharacteristics of the class: activeClassification: Active

Object dependencies: activeConfiguration profile: activeVariant table: Active

View: Object:Switch to the product structure (= Select object = Ctrl. + F6) and enter with theDOCUMENT:

Document: 7�)���Document type: DRWDocument part: 000Document version: ��

Copy the document T-F1## DRW 000 00 using ‘Drag & Drop’.

Open the folders Object links, Material master.Copy the material 7�)���In the right hand area of the screen you see the transferred document and thematerial master.

Open the material T-F1##, from there, open the BOM folder and copy the BOM to7�)���.

�2QO\�LQ�5HOHDVH����&��Open the routing folder and copy the first routing: 1��«���������Click �&RS\�REMHFWV�Save your change master record.

Page 68: LO 980 engineering change mgmt

© SAP AG LO980 3-24

1-3 Now make the following changes with the FKDQJH�PDVWHU�UHFRUG�&����:

1-3-1 In the BOM for pump 7��)��� enter the sort string ‘Gray (cast) iron’ for theVSLUDO�FDVLQJ�7�%���.

Create a stockable BOM item 70 with 8 hexagonal head screws �������.( 2 items relating to the same material can, for example, be necessary, toassign the screws of various operations in the routing as components.)

Then assign a new revision level and save. What number does the revisionlevel have? Revision level:______________

1-3-2 In the material master 7�)��� enter a VFKHGXOHG change. In the Basic Data1 view, alter the old material number to ‘*5��¶ (##=Group number) andsave.

1-3-3 In the document 7�)��� '5:���������Fhange the status of &+ to 5/. Inso doing, copy the reserved change number. Enter something of your choicein the log field and save.What revision status is assigned? Revision level:______________

1-3-4 Classify your material master 7�)��� in the class /2������ (class type001) historically.(Go to the classification menu using the corresponding menu path.)Valuate at least the pump height.

(A prerequisite for this exercise is that the class type 001 for EngineeringChange Management (time) is set in Customizing.)

2SWLRQDO

1-4 Create another change master record with the following data:

Change no.: &����with profile 35(&0��If necessary, enhance the:Header:Text: 7HFKQ��XSGDWLQJ�SDUW��Valid-from: 7RGD\¶V�GDWH����PRQWKVStatus: Active

Object types:

BOM: Active; object management records (generated automatically)material: Active; object management records (generated automatically).

In the pump BOM 7�)��� delete the previously created item for the hexagonalhead screw with this change number.

Display the BOM over the interval from today up to 5 months in the future.

The changes to the change master &���� are first valid two months later. Carry outa date shift.

Display the BOM again over the interval from today up to 5 months in the future.

Page 69: LO 980 engineering change mgmt

© SAP AG LO980 3-25

6ROXWLRQV

8QLW��2EMHFW�&KDQJHV7RSLF��%DVLF�GDWD�REMHFW�FKDQJHV

1-1 From the user menu go directly into the Engineering Workbench.

Select the working area ‘3B$//(6’. Copy this as the default working area.

The selection criteria for headers screen appears. You process:with change number &����with selection period: WRGD\ WR WRGD\�����PRQWKVMaterial: 7�%���Plant: ����.Execute the selection (button or F8).

The task list header appears. Select these then choose7DVN�OLVWV�→�2SHUDWLRQV

The operation overview appears. Select 2SHUDWLRQ����and process it (Button:“Change/Lock = F6”). Ignore possible queries about the alternative dates or defaultvalues.

In operation 10, overwrite work center ���� with ������and save the changes.

Use the validity window to display the routing.If above, you did not enter the Engineering Workbench with the appropriateselection period, call it up again, but this time enter the selection period as today totoday + 4 months.

1. today left, set key date to todayright, change the effectivity window to key date

2. today + 4 months left, set key date to today + 4 monthsright, change the effectivity window to key date

3. Interval right, change the effectivity window toselection period

Page 70: LO 980 engineering change mgmt

© SAP AG LO980 3-26

1-2 Choose→ (QJLQ��FKDQJH�PJPW�→�&KDQJH�QXPEHU�→�&UHDWH,and in the initial screen enter:

Change no.: C##-3

The change header appears.Here, enter theLong text: ‘Techn. updating part 3

Problems after 1000 operating hours:Break of hexagonal head screws’6DYH�WKH�ORQJ�WH[W�DQG�JR�EDFN,

Valid-from date: Today’s date + 3 monthsStatus active.

By clicking on �2EMHFW�W\SHV��the object types overview appears. Select in theline:%20� the fields $FWLYH, 2EMHFW¶7DVN�OLVW the fields $FWLYH��2EMHFW� 0JW5HF��and�*HQ�'LDO'RFXPHQW the fields $FWLYH��2EMHFW0DWHULDO the fields $FWLYH��and��0JW5HF��&KDUDFWHULVWLFV��FKDUDFWHULVWLFV�RI�D�FODVV��FODVVLILFDWLRQ��REMHFW�GHSHQGHQFLHV�FRQILJXUDWLRQ�SURILOH��YDULDQW�WDEOH

the field $FWLYH�Switch to the object selection(Rel. 4.6c 'All Objects' = F7)

→ *RWR�→�6HOHFW�REMHFWAccess with the following DOCUMENT:

Document: 7�)���Document type: DRWDocument part: 000Document version: ��

Copy the document T-F1## DRW 000 00 using ‘Drag & Drop’.

Open the folders Object links, Material master.Copy the material 7�)���

Open the material T-F1##, and from there, open the BOM folder and copy theBOM to 7�)���.

Open the routing folder and copy the first routing 1��«�����������Click �&RS\�REMHFWV��= Shift + F7.

Save your change master record.

Page 71: LO 980 engineering change mgmt

© SAP AG LO980 3-27

1-3 Now make the following changes with the FKDQJH�PDVWHU�UHFRUG�&����:

1-3-1 Start from the user menu:→ %LOOV�RI�PDWHULDO�→�0DWHULDO�%20�→�&KDQJHIn the initial screen enter:

Material: 7�)���Plant: 1000Usage: �Change number: &����Valid-from: ignore (is determined by the system)

The item overview appears.In item 0010 enter the sort string ‘Grey iron’ (navigate to the right).

In the first free line, enter item category L component 100-130, quantity 8

Then select ([WUDV�→�1HZ�UHYLVLRQ�OHYHO�The UHYLVLRQ�OHYHO�01 is assigned.

Save the changes.

1-3-2 Start from the user menu:→ 0DWHULDO�→�&KDQJH�→�6FKHGXOHIn the initial screen enter:

Material: T-F1��Change number: &����Change schedule for: ignore (is determined by the system)

Select the Basic Data 1 view and choose “Continue”.

In the Basic Data view, change the old material number to ‘*5��¶ and savethe changes.

1-3-3 Start from the user menu:→ 'RFXPHQW�→�&KDQJHIn the initial screen enter:

Document: 7�)���Document type: DRWDocument part: 000Document version: 00.

Release the data (Enter)

Copy (Enter) the reserved change number C��-3.Change the status from CH to RL, enter something of your choice in the logfield and save.

The UHYLVLRQ�OHYHO�01 is assigned.

Page 72: LO 980 engineering change mgmt

© SAP AG LO980 3-28

1-3-4 Start from the user menu:5HO�����E�→ &ODVVLILFDWLRQ�→�$VVLJQPHQW→�&ODVV�WR�2EMHFWV5HO�����F → &ODVVLILFDWLRQ�→�$VVLJQPHQW→�$VVLJQ�2EMHFWV��&ODVVHV�WR�D�&ODVVIn the initial screen enter:

Class: LO980-##Class type: ���Change number: C##-3

The overview appears, from here, click’New Assignments’ and then select ’Material’.

Assign your material master 7�)���. After, data release appears under thevalue assignment screen.

Valuate the pump height (using the F4 help) with 10 m.

2SWLRQDO

1-4 Choose(QJLQ��FKDQJH�PJPW�→�&KDQJH�QXPEHU�→�&UHDWH,and in the initial screen enter:

Change no.: &����3URILOH� 35(&0�� (Rest remains unchanged)

The change header appears.Enhance the:Text: ‘Techn. updating part 4’ ,Valid-from date: Today’ s date + 4 months

Because of the change profile, the object types have to be predefined as requested.Save the data.

Start from the user menu:→ %LOOV�RI�PDWHULDO�→�0DWHULDO�%20�→�&KDQJHIn the initial screen enter:

Material: 7�)���Plant: 1000Usage: �Change number: &����Valid-from: ignore (is determined by the system)

Select the last item and delete the item by clicking “Delete item” = Shift + F2”.

Save the changes.

Start from the user menu:→ %LOO�RI�PDWHULDO�→�0DWHULDO�%20�→�'LVSOD\Material: 7�)���Plant: 1000Usage: 1

Page 73: LO 980 engineering change mgmt

© SAP AG LO980 3-29

Valid from: TodayValid-to: Today +5 months

Among other things, you are told that item 70 is valid for one month from today +3months. Reference point is the change number C##-3.

Choose(QJLQ��FKDQJH�PJPW�→�&KDQJH�QXPEHU�→�&KDQJH,and in the initial screen enter:

Change no.: &����(GLW�→�0RUH����→�6KLIW�GDWHEnter a date two months in the future, confirm the warning message, copy the dateand save.

Start from the user menu:%LOO�RI�PDWHULDO�→�0DWHULDO�%20�→�'LVSOD\Material: 7�)���Plant: 1000Usage: 1Valid from: TodayValid-to: Today +5 months

You do not get item 70.

Page 74: LO 980 engineering change mgmt

© SAP AG LO980 4-1

SAP AG 1999

&RQWHQWV�l (YDOXDWLQJ�REMHFW�FKDQJHV�IRU�PRUH�WKDQ

RQH�FKDQJH�PDVWHU�UHFRUGl (YDOXDWLQJ�REMHFW�FKDQJHV�LQ�RQH�FKDQJH

PDVWHU�UHFRUGl &KDQJH�GRFXPHQWV�LQ�WKH�PDVWHU�UHFRUG

IRU�WKH�FKDQJH�REMHFW

5HSRUWLQJ

Page 75: LO 980 engineering change mgmt

© SAP AG LO980 4-2

SAP AG 1999

$W�WKH�FRQFOXVLRQ�RI�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�l (YDOXDWH�D�FKDQJH�RYHUYLHZ�RI�VHYHUDO�FKDQJH

PDVWHUH�UHFRUGVl 'LVSOD\�DQG�HYDOXDWH�WKH�REMHFW�FKDQJHV�LQ�D

FKRVHQ�FKDQJH�PDVWHU�UHFRUG�WKDW�KDYH�EHHQ�PDGHZLWK�UHIHUHQFH�WR�WKH�FKDQJH�QXPEHU

l (YDOXDWH�WKH�FKDQJHV�WR�D�FKDQJH�PDVWHU�UHFRUG�LQWKH�UHOHYDQW�FKDQJH�GRFXPHQWV

5HSRUWLQJ��7RSLF�2EMHFWLYHV

Page 76: LO 980 engineering change mgmt

© SAP AG LO980 4-3

SAP AG 1999

2EMHFW�&KDQJHV2EMHFW�&KDQJHV ��

��

�� &KDQJH�+LHUDUFK\��&KDQJH�+LHUDUFK\��5HOHDVH�.H\�5HOHDVH�.H\�«« ��&KDQJH�0DVWHU�5HFRUG&KDQJH�0DVWHU�5HFRUG

3URFHVVLQJ�&KDQJHV�3URFHVVLQJ�&KDQJHV�ZLWK�:RUNIORZZLWK�:RUNIORZ ��&RXUVH�2YHUYLHZ&RXUVH�2YHUYLHZ ��

(&5���(&2(&5���(&2 ��

5HSRUWLQJ5HSRUWLQJ 6XPPDU\6XPPDU\ ��

2UGHU�&KDQJH�2UGHU�&KDQJH�0DQDJHPHQW��2&0�0DQDJHPHQW��2&0� ��

&RXUVH�2YHUYLHZ�'LDJUDP

Page 77: LO 980 engineering change mgmt

© SAP AG LO980 4-4

SAP AG 1999

5HSRUWLQJ���%XVLQHVV�6FHQDULR

l <RX�ZDQW�WR�DQDO\]H��ZKLFK�UHSRUWLQJ�IXQFWLRQV�WKHH[LVWLQJ�WRRO�RIIHUV�DV�VWDQGDUG�

l 7KLV�IRUPV�WKH�EDVLV�IRU�WKH�GRFXPHQWDWLRQ�DQGUHSRUWV�WR�EH�FUHDWHG����,Q�VRPH�FDVHV��WKHVH�DUHFRPSOHWHG�E\�D�UHSRUW�

Page 78: LO 980 engineering change mgmt

© SAP AG LO980 4-5

SAP AG 1999

5RXWLQJ�FKDQJH

'RFXPHQW��SURFHVVLQJ

%20�FKDQJH

%20�FKDQJH 5RXWLQJ�

FKDQJH

&KDQJH�RYHUYLHZRI

VHYHUDO�FKDQJH�QXPEHUV&KDQJHPDVWHU�UHFRUG

1��

&KDQJH�PDVWHU�UHFRUG

1��

&KDQJH�2YHUYLHZ

n You can call up the &KDQJH�RYHUYLHZ from the (QJLQHHULQJ�&KDQJH�0DQDJHPHQW menu under5HSRUWLQJ.

n The change overview provides information on all changes that have been made with one or morechange master records or ECRs/ECOs.

Page 79: LO 980 engineering change mgmt

© SAP AG LO980 4-6

SAP AG 1999

6DYH�DV�EDVLF�VHWWLQJV

•��&KDQJH�QXPEHU•��&UHDWHG�E\•��9DOLG�IURP�GDWH•��6WDWXV�FKDQJH�QXPEHU•��&KDQJH�W\SH�����IRU�(&5�(&2�•��$XWKRUL]DWLRQ�JURXS•��'HOHWLRQ�IODJ

•��'LVSOD\�REMHFW�PJPW�UHFRUGV•��'LVSOD\�REMHFW�W\SHV•��'LVSOD\�DOWHUQDWLYH�GDWHV•��'LVSOD\�ORQJ�WH[W•��6\VWHP�DQG�XVHU�VWDWXV�����FKDQJH�QXPEHU�����REMHFW�PDQDJHPHQW�•��'LVSOD\�DFWLYH�VWDWXV�RQO\

&KDQJH�2YHUYLHZ

6HOHFWLRQ�FULWHULD6HOHFWLRQ�FULWHULD 2XWSXW�SDUDPHWHUV2XWSXW�SDUDPHWHUV

2SWLRQV�IRU�&KDQJH�2YHUYLHZ

n You can limit the range of change numbers by using VHOHFWLRQ�FULWHULD. For example, you can chooseonly to evaluate change numbers that have an DFWLYH�status.

n You determine the amount of information shown in the change overview by using RXWSXWSDUDPHWHUV:é Display object management: All object managment records for the change numbers are displayed�é Display object types: The object types that are active for the change number are displayed (for

example, BOM). An object type that has object management records is accounted for under 2EMHFWPDQDJHPHQW.

é Display change number or object management status: If a system or user status is maintained forthe change master record or the object management record, then the status is displayed.

é Display active status only: This indicator controls which statuses are displayed. If you only wantthe overview to contain the active statuses, then set this indicator. By active statuses we mean thestatuses that have already been set manually (for example, $OO�REMHFWV�FKHFNHG) and those that areset now (for example, &KDQJH�RUGHU�LQFRPSOHWH).If you want the overview to contain statuses that have been set or deleted by the system, then donot set this indicator.

Page 80: LO 980 engineering change mgmt

© SAP AG LO980 4-7

SAP AG 1999

&KDQJH�QXPEHU�1���������9DOLG�IURP�������'HVFULSWLRQ������6WDWXV�«�',G

&KDQJH�QXPEHU���

2EMHFW�W\SHV�������������������$FWLYH�������������/RFN������2EMHFW0DWHULDO�%20���������������������;������������������������������������;����2EMHFW�W\SH�IRU�FKDQJH�REMHFWV���������������2EMHFW�QXPEHU$OWHUQDWLYH�GDWHV�����������������9DOLG�IURP���������������������������������'HVFULSWLRQ�0DWHULDO�%20�����������������������������������������3���������������������

�������� 3XPS6KDIW�FKDQJH

� � �

� � �2EMHFW�W\SH�IRU�FKDQJH�REMHFWV ���$OWHUQDWLYH�GDWHV ���5RXWLQJ ���

&KDQJH�QXPEHU�1���������9DOLG�IURP�������'HVFULSWLRQ������6WDWXV�«�',G

SOXVJRHV�WRLQ�WKHFKDQJHPDVWHU

�'RXEOHFOLFN�

&KDQJH�2YHUYLHZ�6WUXFWXUH

n You can decide whether you want to evaluate the changes with reference to one or more than onechange number on the initial screen (6HOHFWLRQ�RSWLRQV).é If you want to evaluate LQGLYLGXDO change numbers, enter the change numbers in 6LQJOH�YDOXHVHOHFWLRQ�

é If you want to evaluate more than one LQWHUYDO, enter the intervals in ,QWHUYDOV.n An individual data block is created for each change number. This data block is separated by a

dividing line.

é Each block starts with the &KDQJH�QXPEHU, 9DOLG�IURP date, 'HVFULSWLRQ, and 6WDWXV.é Further information is dependent on the output parameters you choose.

n By double-clicking on a chosen field you can display the change master record. You can perform allactive display functions.

Page 81: LO 980 engineering change mgmt

© SAP AG LO980 4-8

SAP AG 1999

5RXWLQJV5RXWLQJV

(YDOXDWLRQ�OLVWV������������IRU����

%20V%20V

'RFXPHQWV'RFXPHQWV

0DWHULDOV0DWHULDOV

9DULDQW�&RQILJXUDWLRQ�2EMHFWV9DULDQW�&RQILJXUDWLRQ�2EMHFWV2EMHFWV�IURP����2EMHFWV�IURP���� 2EMHFWV�LQ�WKH�&ODVVLILFDWLRQ�6\VWHP2EMHFWV�LQ�WKH�&ODVVLILFDWLRQ�6\VWHP

2EMHFW�&KDQJHV�LQ�WKH�&KDQJH�0DVWHU�5HFRUG

&&�� &&��5HSRUWLQJ����&KDQJHPDVWHU�UHFRUG

1��

1HZ�SUHVHQWDWLRQ�RI�WKH�OLVW�1HZ�SUHVHQWDWLRQ�RI�WKH�OLVW�³$OO�FKDQJHV³$OO�FKDQJHV´́���&

n You can display all object changes that you make with reference to a change number while you areprocessing the change master record. You can carry out this evaluation separately for all objecttypes. For example, you can create an evaluation list for the BOM changes.

n 7KH�OLVWV�RI�REMHFW�FKDQJHV�DUH�GLIIHUHQW�IRU�GLIIHUHQW�REMHFW�W\SHV�

Page 82: LO 980 engineering change mgmt

© SAP AG LO980 4-9

SAP AG 1999

'DWD�WKDW�LGHQWLILHV�D�%20��JHQHUDO�%20�FDWHJRU\��%20�QXPEHU��%20�XVDJH��GDWH�$OWHUQDWLYH�%20��!�2EMHFW�QXPEHU����VXFK�DV��PDWHULDO���GHVFULSWLRQ��SODQW

'DWD�IRU�WKH�FKDQJHG�KHDGHU��LI�DYDLODEOH�%DVH�TXDQWLW\��EDVH�XQLW�RI�PHDVXUH��GHVFULSWLRQ��FUHDWHG�E\

'DWD�IRU�WKH�SURFHVVHG�LWHP�;��LI�DYDLODEOH�,WHP�QXPEHU��FRPSRQHQWV��LWHP�W\SH��FRPSRQHQW�TXDQWLW\��FRPSRQHQW�XQLW�RI�PHDVXUH��GHVFULSWLRQ

'DWD�IRU�WKH�SURFHVVHG�LWHP�<��LI�DYDLODEOH����

&KJ

&KJ

&KDQJH�QXPEHU�1�� !�'HVFULSWLRQ�� !�'DWH��

1(:

'DWD�WKDW�LGHQWLILHV�D�%20��JHQHUDO�«

5HSRUWLQJ�/LVW�IRU�%20�&KDQJHV

n When you make an historical change to header or item data, both the old and the new data record issaved (see unit 3, 2EMHFW�&KDQJHV). This data is displayed in several display blocks for each BOM.

é The changed BOM is displayed in the first block.

é The second block displays the BOM header changes, provided that header data with history hasbeen processed with reference to the chosen change number. The block starts with the processingindicator Chg. (Change). A description of the header fields in the list follows.

é The third block lists all items that have been processed with reference to the change number. Theblock starts with the processing indicator Chg. (Change). A description of the item fields in the listfollows.

n Further processing indicators for the header or item records show how the header or the item hasbeen processed.

Page 83: LO 980 engineering change mgmt

© SAP AG LO980 4-10

SAP AG 1999

'DWD�WKDW�LGHQWLILHV�D�WDVN�OLVW�JURXS��JHQHUDO�7DVN�OLVW�W\SH��VXFK�DV�URXWLQJ���WDVN�OLVW�JURXS��YDOLG�IURP�GDWH

'DWD�IRU�WDVN�OLVW�DFFRUGLQJ�WR�JURXS�FRXQWHU��LI�DYDLODEOH�7/*U&RXQWHU���

&KDQJH�QXPEHU�1�� !�'HVFULSWLRQ�� !�'DWH��

« 'DWD�WKDW�LGHQWLILHV�D�WDVN�OLVW�JURXS��JHQHUDO�

7/*U&RXQWHU���

7/*U&RXQWHU���

7DVN�OLVW�KHDGHU�FKDQJHV6HTXHQFH�FKDQJHV 2SHUDWLRQ�FKDQJHV

$VVLJQPHQW�FKDQJHV�0DWHULDO�FRPSRQHQW���2SHUDWLRQ

357���2SHUDWLRQ

5HSRUWLQJ�/LVW�IRU�7DVN�/LVW�&KDQJHV

n Task list groups are sorted according to task list type. After all the task lists of one type have beenevaluated, the task lists of the next type are displayed.

n The task lists of a task list group are displayed in a block.

é The header line contains identifying data for the task list (type, group).

é Below that, the individual task lists in the task list group are listed with their group counter.

é The following task list changes are displayed:

- Changes to task list headers (for example, changes to the usage)

- Changes to the sequence (for example, changing the alignment key)

- Changes to operations or activities (for example, inserting a new activity or operation)

- Changes to material components (for example, changing the assignment of materialcomponents to an operation or activity)

- Changes to production resources/tools (PRTs) (for example, deleting the assignment ofproduction resources/tools to an operation or activity).

n The information contained here is for the most part ZKDW�has�been changed. More details can befound in the change documents in the routing or task list menu.

Page 84: LO 980 engineering change mgmt

© SAP AG LO980 4-11

SAP AG 1999

'RFXPHQW��'RFXPHQW�W\SH���'RFXPHQW�SDUW�����'RFXPHQW�YHUVLRQ�����'HVFULSWLRQ

&KDQJH�QXPEHU�1�� !�'HVFULSWLRQ�� !�'DWH��

���

'RFXPHQW��'RFXPHQW�W\SH���'RFXPHQW�SDUW�����'RFXPHQW�YHUVLRQ�����'HVFULSWLRQ

3ULQW 'LVSOD\

7R�JRWR�GLVSOD\�FKDQJHV

'RFXPHQWYHUVLRQ���

&KDQJH�QR�����������1��

5HSRUWLQJ�/LVW�IRU�'RFXPHQW�&KDQJHV

n Since 'RFXPHQW�0DQDJHPHQW does not use (QJLQHHULQJ�&KDQJH�0DQDJHPHQW to store documentdata with history, you do not obtain any information in this list about changed fields.

n The list contains all documents for which the chosen change number has been entered in thedocument info record.Documents that are only reserved in the change master record are not included in the list. Thereservations are included in the object overview for documents in the change master record.

Page 85: LO 980 engineering change mgmt

© SAP AG LO980 4-12

SAP AG 1999

$FWLYH�FKDQJHV$OO�FKDQJHV�WKDW�KDYH�EHHQ�PDGH�DUH�VKRZQ�

6FKHGXOHG�FKDQJHV$OO�VFKHGXOHG�FKDQJHV�WKDW�KDYH�QRW�\HW�EHHQ�DFWLYDWHG�DUH�VKRZQ�

��������� � ����������� � ��������������� ���

� ���!� �� ������ �"����� �#�$� ��������� ���

���$�!� �� � �������"��� � ��������������� ���

�����!� �� ����� �"���� �#�$����������� ���

'HWDLOV��SRVV��2UJ��OHYHOV�&KDQJH��!�)LHOG�GHVFULSWLRQ��������2OG�YDOXHV� «�����1HZ�YDOXHV� ����

5HSRUWLQJ�/LVW�IRU�0DWHULDO�&KDQJHV

n The list contains all materials that have been processed with reference to a change number. At thisstage, no distinction is made between changes that have already been made and changes that areplanned.

n In a further processing step you can decide whether just the active or the planned changes should bedisplayed.

é Active changes:

- Change that has been made with the function 0DWHULDO -> &KDQJH�-> ,PPHGLDWHO\- Planned change that has already been activated

é Planned change: change that has been made with the function 0DWHULDO -> &KDQJH -> 6FKHGXOH(not yet activated).

Page 86: LO 980 engineering change mgmt

© SAP AG LO980 4-13

SAP AG 1999

&KDUDFWHULVWLFV&KDUDFWHULVWLFV

&ODVVLILFDWLRQ&ODVVLILFDWLRQ

&KDUDFWHULVWLFV�RI�FODVV&KDUDFWHULVWLFV�RI�FODVV

2EMHFW�GHSHQGHQFLHV2EMHFW�GHSHQGHQFLHV

&RQILJXUDWLRQ�SURILOH&RQILJXUDWLRQ�SURILOH

9DULDQW�WDEOH�FRQWHQWV9DULDQW�WDEOH�FRQWHQWV

%UDQFK�WR�WKH�GLVSOD\�WUDQVDFWLRQ�RI�WKH�UHOHYDQW�REMHFW��&KDUDFWHULVWLF��&ODVV��2EMHFW�LQ�FODVV��2EMHFW�GHSHQGHQFLHV��&RQILJXUDWLRQ�SURILOH��1RW�IRU�WKH�YDULDQW�WDEOH

2QO\�IRU�REMHFW�GHSHQGHQFLHV

5HSRUWLQJ�/LVW�IRU�2EMHFWV�IURP�WKH�&ODVVLILFDWLRQ6\VWHP�DQG�9DULDQW�&RQILJXUDWLRQ

n &KDUDFWHULVWLFThis list contains all characteristics that have been processed with reference to a change number. Thecharacteristics are sorted in alphabetical order by characteristic name. There is a block for eachcharacteristic with the data you selected (for example, class) and information on the processing.

n &KDUDFWHULVWLFV�RI�FODVVThis list only contains the classes for which at least one characteristic has been processed withreference to a change number. The characteristics that have been processed with the chosen changenumber are listed directly below the class to which they belong.

n &ODVVLILFDWLRQThis list contains the objects that have been classified with reference to a change number. In theobject line you see the class that the object is classified in. Directly below the object you see thecharacteristics of the class to which you have assigned values with reference to the change number.

n 2EMHFW�GHSHQGHQFLHVThis list displays the object dependencies that have been processed with reference to the changenumber.

n &RQILJXUDWLRQ�SURILOHThis list contains all the configurable objects whose configuration profile has been processed withreference to the change number. There is one block for each object.

Page 87: LO 980 engineering change mgmt

© SAP AG LO980 4-14

SAP AG 1999

&KDQJH�'RFXPHQWV�IRU�&KDQJHV�ZLWK�(&0

%LOO�RI�PDWHULDO5RXWLQJ'RFXPHQW0DWHULDO

&KDUDFWHULVWLF&KDUDFWHULVWLFV�LQ�FODVV&ODVVLILFDWLRQ2EMHFW�GHSHQGHQFLHV&RQILJXUDWLRQ�SURILOH9DULDQW�WDEOH

LQ�WR�REMHFW������6$3�0HQX���WR�WKH�FKDQJH�PDVWHU

;� %'&�(*)�+�,.-�/ 0��;� %213(*)�45+,.-�/�0;� 6767(*)�+�,.-�/ 0

;� %'&289(�: :�:;� %'&2;9(�: :�:�;� 676<(.=

6�6 >?=�:�: :

;����!�JRHV�WR��������������;� �JRHV�WR ;

���

;����!�JRHV�WR;����!�JRHV�WR;����!�JRHV�WR;����!�JRHV�WR;����!�JRHV�WR���������������;�

���

5HSRUW

;� %'@ (A=B+,*-�/ 0;� %DC�(.)E+,*-�/ 0;� %DC�FA=�4'G*%DC$F*F�4%DC�F.(�45+2,.-�/ 0

;� %DH'(*)$GI%JH�F9)@ K�K�L M

;� %DH2=$)�+�N90PORQ.M��

Page 88: LO 980 engineering change mgmt

© SAP AG LO980 4-15

SAP AG 1999

&KDQJH &KDQJH�GRFXPHQWV

&RPSOHWH�GRFXPHQW+HDGHU2EMHFW�W\SHV2EMHFW�PDQDJHPHQW$OWHUQDWLYH�GDWHV

&KDQJHPDVWHU�UHFRUG

1��

&KDQJH�'RFXPHQWV�IRU�WKH�&KDQJH�0DVWHU�5HFRUG

n Important changes to the change master record as well as the creation of change numbers are bothsaved in the change documents.

n Complete documentAll changes are shown (header, object type indicators, object management, and alternative dates).

n HeaderOnly changes to the header data are shown.

n Object typesChanges to the object type indicators are shown.

n Object managementChanges that you make on the object management record screen and changes to assignments to analternative date are shown.

n Alternative datesChanges to the alternative dates are shown. Changes to the assignments to an object are not shown.

Page 89: LO 980 engineering change mgmt

© SAP AG LO980 4-16

SAP AG 1999

3URFHVVLQJ�,QGLFDWRUV�IRU�+HDGHU�DQG�,WHP�5HFRUGV

/RJLFDOO\GHOHWHG

'(/�IRU�LWHP�

,QDFWLYH

,QQ�IRU�LWHP�

,QG

$FWLYH�IRU�KHDGHU�DQG�LWHP�

1(: 2/'

,WHP����FKDQJHG 1(:2/'

&KDQJH�QR��1���

,WHP����GHOHWHG,WHP������� '(/

,WHP����FUHDWHG� ,11&KDQJH�QR��1���

&KDQJH�QR��1���

1����EHIRUH�1����GDWH�VKLIW,WHP����GHOHWHG� ,1'

,WHP����FUHDWHG� ,11

,WHP����FUHDWHG� ,11&KDQJH�QR��1���

&KDQJH�QR��1���

1����DQG�1����ZLWK�WKH�VDPH�GDWH,WHP����GHOHWHG� ,1'

,WHP����FUHDWHG� ,11

n ���%ORFN• First you create item 30 with reference to change number N-02.

• Next you delete item 30 with reference to change number N-03. For the time being, changenumber N-02 has a later valid.from date than N-02.

• Then the valid-from date of change number N-1 is shifted so that it comes before the valid-from date of change number N-2.=> Evaluation DIWHU�the date shift: - &KDQJH�PDVWHU�UHFRUG�1���in this change master record item 30 is flagged as an inactive item that starts (INN) - &KDQJH�PDVWHU�UHFRUG�1����in this change master record item 30 is also flagged as an inactive item that however, finishes (IND).

n ���%ORFN• First you create item 40 with reference to change number N-04.

• Next you delete item 40 with reference to change number N-05. Change numbers N-04 and N-05 have the same YDOLG�IURP date.=> Evaluation - &KDQJH�PDVWHU�UHFRUG�1��� In this change master record item 40 is flagged with the processing status NEW before deletion; after deletion the item record is flagged as inactive INN - &KDQJH�PDVWHU�UHFRUG�1����In this change master record item 40 is also flagged as deleted however, as IND.

Page 90: LO 980 engineering change mgmt

© SAP AG LO980 4-17

SAP AG 1999

<RX�DUH�QRZ�DEOH�WR�l (YDOXDWH�D�FKDQJH�RYHUYLHZ�RI�VHYHUDO�FKDQJH

PDVWHUH�UHFRUGVl 'LVSOD\�DQG�HYDOXDWH�WKH�REMHFW�FKDQJHV�LQ�D

FKRVHQ�FKDQJH�PDVWHU�UHFRUG�WKDW�KDYH�EHHQPDGH�ZLWK�UHIHUHQFH�WR�WKH�FKDQJH�QXPEHU

l (YDOXDWH�WKH�FKDQJHV�WR�D�FKDQJH�PDVWHU�UHFRUG�LQWKH�UHOHYDQW�FKDQJH�GRFXPHQWV

5HSRUWLQJ��8QLW�6XPPDU\

n You can evaluate several change master records in the change overview.

n You can use selection criteria to limit the choice of change numbers. The amount of information thatis displayed in the change overview is determined by output parameters.

n In any chosen change master record, you can display all the object changes that have been made withreference to this change number.

n You can check and document the changes you make to a change master record with changedocuments.

Page 91: LO 980 engineering change mgmt

© SAP AG LO980 4-18

([HUFLVHV

8QLW��5HSRUWLQJ7RSLF��5HSRUWLQJ

At the conclusion of this exercise, you will be able to:

• Evaluate information relating to changes to change masterrecords

• Evaluate information relating to changes made with a changemaster record to BOMs, documents, materials, classificationand routings.

All the changes that have been made up to this point along withthe corresponding change master records will be analyzed.

1-1 Switch to the change overview and, for the change master records &���� to &�����display the object types, the object management data, the long text and thealternative dates.

From the change overview, determine:

1-1-1 For which change master record an alternative date has been created and towhich object it has been assigned?

1-1-2 With which change master record a routing has been changed?

1-1-3 How often the BOM 7�)�������������� has been changed historically?

1-1-4 Why you can not determine from the change overview which object hasbeen classified with the change master record &����?

1-2 Switch to the display of your change master record &���� and display the followingevaluation functions:

1-2-1 BOM changesCompare the old and new item 0010.

Page 92: LO 980 engineering change mgmt

© SAP AG LO980 4-19

(optional - Only if the date shift was carried out in the last exercise)Look at the processing indicator of the BOM items..Which identifier now has the item hexagonal head screws? What does itmean?

1-2-2 Document:Display the document info record and all changes.

1-2-3 Material:Display the planned changes to the material master. Which material masterrecord field has been changed ?

1-2-4 Classification:Which classes did you use for the classification of your pump? Display theclassification.

1-3 Switch to the display of your change master record &���� and display the followingevaluation functions:

1-3-1 Routing changes:Which changes are displayed in the change master record ? Make a note ofthe task list group and the group counter.

____________________ BBBBBBBBBBBBBBBBBBBBB

Note: As of Release 4.6C change documents are also written for changescarried out with the Engineering Workbench. So these changes canonly be displayed in the routing menu of the change documenttransaction as of Release 4.6C.

1-4 2QO\�LQ�5HOHDVH�����DQG�RQO\�RSWLRQDOTry to answer the above questions from the information system:

1-1-2 (left in the tree)

1-1-3 (left in the tree)

1-2-1 Part 2 Double click on C##-3 and right click on the tab page ‘Bill of Material’1-3-1

Page 93: LO 980 engineering change mgmt

© SAP AG LO980 4-20

�6ROXWLRQV

8QLW��5HSRUWLQJ7RSLF��5HSRUWLQJ

1-1 Start on the user menu and goto(QJLQ��FKDQJH�PJPW�→�$QDO\VHV�→�&KDQJH�2YHUYLHZ�

Change no.: &�����WR�&����Output parameters: Object types

Object management dataAlternative datesLong text

Select �([HFXWH� �)��

1-1-1 An alternative data has been created for the change master record C##-2 andassigned to the object management record for BOM 7-B1## / 1000 / 1.

1-1-2 The routing for material T-B100 has been changed with the change masterrecord C##-2.

1-1-3 The BOM T-F1## / 1000 / 1 has been changed historically three times (fourtimes) (if all exercises have been performed C##-1 to C##-4).

1-1-4 For technical reasons no object management record could be created forclassification.

1-2 Start on the user menu and goto(QJLQ��FKDQJH�PJPW�→�&KDQJH�1XPEHU�→�'LVSOD\�Enter the change number in the overview:

Change no.: &����The change header appears.

1-2-1 Select (QYLURQPHQW�→�5HSRUWLQJ�→�%20�&KDQJHV�Compare the new and old item by clicking on �&RPSDUH�2OG�1HZ� �)��.(The cursor position is irrelevant.)

(optional)The BOM item 70 the hexagon head screw has the processing indicator Inn.According to the legend (�'LVSOD\�/HJHQG� �)��� it refers to an inactiveitem that starts with this change number (AEN).

Page 94: LO 980 engineering change mgmt

© SAP AG LO980 4-21

1-2-2 Switch back to the change header.Select (QYLURQPHQW�→�5HSRUWLQJ�→�'RFXPHQWV�Select the document by placing the cursor on the corresponding line andselecting �'LVSOD\� �)��.The document header appears. From the document header select*RWR�→�'LVSOD\�FKDQJHV

1-2-3 Switch back to the change header.Select (QYLURQPHQW�→�5HSRUWLQJ�→�0DWHULDO�Select the material by placing the cursor on the corresponding line andselecting �3ODQQHG�FKDQJHV�.Select the change document by placing the cursor on the corresponding lineand selecting �&KRRVH� �)�”.The material master field “Old material number” has been changed.

1-2-4 Switch back to the change header.Select (QYLURQPHQW�→�5HSRUWLQJ�→�&ODVVLILFDWLRQ�→�&ODVVLILFDWLRQ�The class LO980-## has been used.Select the item and click �&KRRVH� �)��. The already filled out initialscreen of the transaction CL21 appears. By pressing ‘Enter’ you see thevalues.

1-3 Start on the user menu and goto(QJLQ��FKDQJH�PJPW�→�&KDQJH�1XPEHU�→�'LVSOD\�Enter the change number in the overview:

Change no.: &����The change header appears.

1-3-1 Select (QYLURQPHQW�→�5HSRUWLQJ�→�7DVN�/LVW�&KDQJHV�You see in which task list group, by which group counter and to whichoperation a change has been made, but not what has been changed.

It is not possible to branch directly to the change documents.

2QO\�LQ�5HOHDVH����&� For evaluating the change document use thetransaction &$�� from)DYRULWHV���ULJKW�PRXVH�EXWWRQ�→�$GG�WUDQVDFWLRQ

1-4 See the notes in the exercise

Page 95: LO 980 engineering change mgmt

© SAP AG LO980 5-1

SAP AG 1999

&RQWHQWV�l 2YHUYLHZ�RI�WKH�IXQFWLRQV�RI�(&5V�DQG�(&2Vl &RPSDULVRQ��FKDQJH�PDVWHU�UHFRUG� �������(&5���(&2l &KDQJH�W\SHl &KHFN��FRQYHUVLRQ�DQG�UHOHDVH�SURFHGXUHl 6WDWXV�QHWZRUNV�IRU�(&5V��(&2V��DQG�REMHFW

PDQDJHPHQW�UHFRUGVl 6WDWXV�QHWZRUN�GHSHQGHQFLHVl ,QWHJUDWLRQ�RI�XVHU�VWDWXVHVl 'LJLWDO�6LJQDWXUHV

(&5���(&2

Page 96: LO 980 engineering change mgmt

© SAP AG LO980 5-2

SAP AG 1999

$W�WKH�FRQFOXVLRQ�RI�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�l 8VH�WKH�IXQFWLRQDOLW\�RI�WKH�(&5�DQG�(&2l &DUU\�RXW�WKH�FKHFN��FRQYHUVLRQ�DQG�UHOHDVHSURFHGXUH�XVLQJ�WKH�VWDWXV�QHWZRUN�IRU(&5V�(&2V�DQG�REMHFW�PDQDJHPHQW�UHFRUGV�DQGWKH�REMHFW�GHSHQGHQFLHV�WKDW�WKLV�LQFOXGHV

l ,QFOXGH�WKH�XVHU�VWDWXV�LQ�WKLV�ZRUNIORZ�DQG�KRZWR�XVH�LW

l $VVHVV�WKH�GLJLWDO�VLJQDWXUH�RSWLRQV

(&5���(&2��7RSLF�2EMHFWLYHV

Page 97: LO 980 engineering change mgmt

© SAP AG LO980 5-3

SAP AG 1999

2EMHFW�&KDQJHV2EMHFW�&KDQJHV ��

5HSRUWLQJ5HSRUWLQJ ��

�� &KDQJH�+LHUDUFK\��&KDQJH�+LHUDUFK\��5HOHDVH�.H\�5HOHDVH�.H\�«« ��&KDQJH�0DVWHU�5HFRUG&KDQJH�0DVWHU�5HFRUG

3URFHVVLQJ�&KDQJHV�3URFHVVLQJ�&KDQJHV�ZLWK�:RUNIORZZLWK�:RUNIORZ ��&RXUVH�2YHUYLHZ&RXUVH�2YHUYLHZ ��

��(&5���(&2(&5���(&2

6XPPDU\6XPPDU\ ��

2UGHU�&KDQJH�2UGHU�&KDQJH�0DQDJHPHQW��2&0�0DQDJHPHQW��2&0� ��

&RXUVH�2YHUYLHZ�'LDJUDP

Page 98: LO 980 engineering change mgmt

© SAP AG LO980 5-4

SAP AG 1999

l ,W�KDV�EHHQ�GHFLGHG��WR�SURFHVV�FKDQJHV�ZLWK(&5V�(&2V�EHFDXVH�\RX�ZDQW�WR�UHSUHVHQW�WKHFKDQJH�SURFHVV�LQ�GHWDLO�DQG�ZDQW�WR�LQWHJUDWHVHYHUDO�GHSDUWPHQWV�

l 7KH�FHQWUDO�(QJLQHHULQJ�&KDQJH�0DQDJHPHQWRSHQV�DQ�(&5�WKDW�FRQWDLQV�WKH�GHVLUHG�FKDQJHVIURP�6DOHV�

(&5���(&2��%XVLQHVV�6FHQDULR

Page 99: LO 980 engineering change mgmt

© SAP AG LO980 5-5

SAP AG 1999

l 5HSUHVHQW�WKH�FKDQJH�SURFHVV���LPSRUWDQW��6WDWXV�PDQDJHPHQW

l 9DOLG�IURP�GDWHQRW�NQRZQ�DW�WKH�VWDUW

l 1RW�NQRZQ�IURP�WKH�VWDUW�ZKLFK�REMHFWV�DUH�DIIHFWHG�E\�FKDQJHV

l 6HYHUDO�GHSDUWPHQWV�FDQ�ZRUN�WRJHWKHU�ZLWKUHVSHFW�WR�RUJDQL]LQJ�VFKHGXOHG�FKDQJHV

l ,QFOXGLQJ� 8VHU�VWDWXV�� :RUNIORZ��������RU� 'LJLWDO�6LJQDWXUH

�����

�����

:K\�8VH�(&5V���(&2V�"

n The central master record for Engineering Change Management is the change master record. Youcan use the change master record to make changes with history to all related R/3 objects anddocument these changes.

n If you wish to use Engineering Change Management to handle the business process of requesting,checking, releasing and execution of a change, then you can use the change request, which can beconverted to a change order during the change process. 7KH�(&5�(&2�WDNHV�WKH�SODFH�RI�WKHFKDQJH�PDVWHU�UHFRUG�LQ�WKLV�FDVH�

n The ECR/ECO is almost identical to the change master record in terms of its structure andfunctionality. However, the ECR/ECO offers extensive status management, which is the basis forhandling such a business process. Additionally, the status management of the ECR/ECO links SAPBusiness Workflow to Engineering Change Management.

Page 100: LO 980 engineering change mgmt

© SAP AG LO980 5-6

SAP AG 1999

���� ������� ������

�������� ��������� ������

(&5

(&2

5HTXHVW��FKHFN�DQG�UHOHDVH5HTXHVW��FKHFN�DQG�UHOHDVH

6ZLWFK�VWDWXV

RSWLRQDO�ZLWK�:RUNIORZRSWLRQDO�ZLWK�:RUNIORZ

2EMHFWPDQDJHPHQW�UHFRUG2EMHFW��0DWHULDO�3����

2EMHFWPDQDJHPHQW�UHFRUG2EMHFW��%LOO�RIPDWHULDO3�������������

�! �" $#� ��&%�'�

�( �" $#� )�&%�'*

)XQFWLRQ�RI�WKH�(&5���(&2

n If you want to use (QJLQHHULQJ�&KDQJH�0DQDJHPHQW to support the business process of requesting,checking, and releasing a change, then you can do this by using an ECR. The ECR can be convertedto an ECO during the process. 7KH�(&5�(&2�WDNHV�WKH�SODFH�RI�WKH�FKDQJH�PDVWHU�UHFRUG�LQ�WKLVFDVH�

n The ECR/ECO is almost identical to the change master record in terms of its structure andfunctionality. It also contains• an extensive status management,• the prerequisite for the integration of the SAP Business Workflow into change management• as well as other possibilities.

n When you create an ECR/ECO you must define the change type. You can use the change type to linkto GLIIHUHQW�business processes for requesting, checking, and releasing a change.

Page 101: LO 980 engineering change mgmt

© SAP AG LO980 5-7

SAP AG 1999

&RPSDULVRQ�%HWZHHQ�(&5���(&2�DQG�&KDQJH0DVWHU�5HFRUG

&KDQJH�W\SH����������������������������������������������������;��������������������������������������������������6\VWHP�VWDWXV�������������������������������������������������;��������������������������������������������������8VHU�VWDWXV������������������������������������������������������;������������������������������������������������;2EMHFW�PJPW�UHFRUGV�������������������������������������;�������������������������������������������������;$XWRP��JHQHUDWH�REMHFW�PJPW�UHFRUGV������������������������������������������������������������;(QWHU�YDOLG�IURP�GDWH����������������������������EHIRUH�FRQYHUVLRQ� ������LPPHGLDWHO\&KDQJH�REMHFWV��������������������������������������DIWHU�FRQYHUVLRQ������������������������LPPHGLDWHO\

&KDQJHPDVWHU�UHFRUG1��

�����

�����

&KHFN�DQG�UHOHDVH

+�,.- /1032 ,5476�8�+ 9;:=<1->2 ?A@B;:DC5<DE�/A?.-F F F

n The central master record for Engineering Change Management is the change master record. Youcan use the change master record to make changes with history to all related R/3 objects anddocument these changes.

n If you wish to use Engineering Change Management to handle the business process of requesting,checking and releasing a change, then you can use the change request, which can be converted to achange order during the change process. 7KH�(&5�(&2�WDNHV�WKH�SODFH�RI�WKH�FKDQJH�PDVWHUUHFRUG�LQ�WKLV�FDVH�

n 7KH�(&5�(&2�LV�DOPRVW�LGHQWLFDO�WR�WKH�FKDQJH�PDVWHU�UHFRUG�LQ�WHUPV�RI�LWV�VWUXFWXUH�DQGIXQFWLRQDOLW\��+RZHYHU��WKH�(&5�(&2�RIIHUV�H[WHQVLYH�VWDWXV�PDQDJHPHQW��ZKLFK�LV�WKH�EDVLVIRU�KDQGOLQJ�VXFK�D�EXVLQHVV�SURFHVV� Additionally, the status management of the ECR/ECO linksSAP Business Workflow to Engineering Change Management.

Page 102: LO 980 engineering change mgmt

© SAP AG LO980 5-8

SAP AG 1999

2EMHFW�7\SH�,QGLFDWRUV���(&5���(&2

$FWLYH2EMHFW�W\SH

;%LOO�RI�PDWHULDO;7DVN�OLVW;'RFXPHQW;0DWHULDO

&KDUDFWHULVWLF

���&ODVV

2EMHFW

;

;

/RFN*HQ�GLDO*HQ�QHZ0JW5HF�

;

;

8VH�WKH�REMHFW�PDQDJHPHQW�UHFRUG�LI�WKH�REMHFW�W\SH�SHUPLWV�LW8VH�WKH�REMHFW�PDQDJHPHQW�UHFRUG�LI�WKH�REMHFW�W\SH�SHUPLWV�LW

n As object management records CANNOT be generated automatically for an ECR/ECO, thesecolumns are missing in the object type overview. If possible, you have to work with the objectmanagement record.

n Object management records cannot be generated automatically because the ECR/ECO controls thebusiness process of requesting, checking, and releasing changes to H[SOLFLW�REMHFWV. You are notallowed to assign additional objects to an ECR/ECO by changing the object with a change numberbecause the change has not been approved.

n Note: the graphic shows the default settings for the ECR/ECO.

Page 103: LO 980 engineering change mgmt

© SAP AG LO980 5-9

SAP AG 1999

3URFHVV�)ORZ�IRU�DQ�(&5�(&2&KDQJH

QRWLILFDWLRQ7ULJJHU�RI�WKH�FKDQJHG�HJI$K

&KDQJHQRWLILFDWLRQ G�HJI$K

5HTXHVW�(&5

VXFK�DV�FXVWRPHU

DVVLJQ�DIIHFWHGREMHFW�

&RPSOHWLRQ

5HOHDVH�RI�WKH�RUGHU

/RJ�FKHFN�UHVXOWV

$SSURYDO�SURFHVV

LQIRUP�DIIHFWHGGHSDUWPHQWV

5HTXHVW�DIIHFWHGGHSDUWPHQWV�

WR�FDUU\�RXWFKDQJHV

&KHFN�UHVXOWV������������UHODWLQJ�WR�REMHFWV

6WDWXV�UHODWLQJ�WR��������REMHFW�FKDQJHV

Page 104: LO 980 engineering change mgmt

© SAP AG LO980 5-10

SAP AG 1999

(&5(&5 &KDQJH�W\SH

2EMHFWV2EMHFWV

6WDWXV�SURILOH�RIWKH�XVHU�VWDWXV

:RUNIORZ�WDVN

6LJQDWXUHQHWZRUN

5HTXLUHG

2SWLRQDO2SWLRQDO

&KDQJH�W\SH

2SWLRQDO

L

�L�L � M&N�OQP R�S>OJP T

&KDQJH�7\SH

n You must assign a change type to the ECR/ECO. You can assign a change type to the assignedobject management records. The change type controls the change process in the following way:• If you assign a status network (optional), you can complement the predefined system status by

adding a customer-specific user status.• If you assign a Workflow object (optional), you can start a Workflow automatically as soon as a

specific status is set.• If you assign a signature network (optional), you can only carry out the status change after an

enhanced authorization check with the desired status.

n Please note that you can only overwrite the change type that you assign when you create a changemaster record with another change type that has the same status profile, Workflow object andsignature network assigned to it.

Page 105: LO 980 engineering change mgmt

© SAP AG LO980 5-11

SAP AG 1999

:LWKGUDZDSSURYDO

5HMHFW�(&5

5HOHDVH

&RPSOHWH

&KHFN

&KHFNHG

$SSURYH

&RQYHUW (&2FRPSOHWH

(&5�SKDVH(&5�SKDVH

(&2�SKDVH(&2�SKDVH

6\VWHP�6WDWXV�1HWZRUN���(&5���(&2

«�XQORFN

(&2LQFRPSOHWH

/RFN

$W�DQ\�WLPH�l�

l�

l�

l�

l�

l�

(&5�RSHQHG���������������FUHDWH�REMHFW��������������PDQDJHPHQW�UHFRUGV

n There is a predefined, IL[HG��comprehensive status network (flow control) for the ECR/ECO in thestandard system.

n You can only DVVLJQ�REMHFW�PDQDJHPHQW�UHFRUGV to the ECR BEFORE you set the $SSURYH statusand for the ECO when the status is set to (52�LQFRPSOHWH.

n You cannot set the ECR to &KHFNHG, $SSURYHG, and convert it to an ECO until DOO the assigned objectmanagement records have the status &KDQJH�SRVVLEOH or &KDQJH�XQQHFHVVDU\.

n After setting the ECR to &KHFNHG or $SSURYHG, the ECR can be rejected.

n After setting the ECR to $SSURYHG, the approval can be cancelled.

n The ECR must be converted to an ECO if there is at least one object to be changed.

n %HIRUH�\RX�FRQYHUW�WKH�(&5�WR�DQ�(&2��\RX�PXVW�PDLQWDLQ�WKH�YDOLG�IURP�GDWH�RI�WKH�(&5�n After conversion, you can set the request status to ,QFRPSOHWH. In this case, the status must be set to

&RPSOHWH before you can continue the object changes.

n If the ECO and the object management record have been released, you can no longer change theobject.

n You can lock and unlock the ECR/ECO at any time.

n The status network can be complemented by a user status.

Page 106: LO 980 engineering change mgmt

© SAP AG LO980 5-12

SAP AG 1999

&KDQJH�XQQHFHVVDU\

&KDQJH�LPSRVVLEOH

&KDQJH�SRVVLEOH

(UURU�LQ�FKDQJH

(UURU�FRUUHFWHG

&RPSOHWH�FKDQJH

5HOHDVH�FKDQJH

2EMHFW�PJPW�UHFRUGV2EMHFW�PJPW�UHFRUGV

2EMHFW�FKDQJHV

&KHFN

6\VWHP�6WDWXV�1HWZRUN��2EMHFW�0JPW�5HFRUG

n The predefined status network for change objects in the standard system applies to all the objects thatare to be changed from the object types material, document, BOM and task list.

n You can change between statuses &KDQJH�SRVVLEOH, &KDQJH�LPSRVVLEOH and &KDQJH�XQQHFHVDU\ inany sequence.

n You only need to look at the object change and set a further status for the status�&KDQJH�SRVVLEOH. Ifat least one object management record has this status, the ECR must be converted to an ECO.

n The change can be set to (UURU�LQ�FKDQJH after you have set it to &RPSOHWH. In this case, you mustcorrect the error before you can release the change.

n If the ECO and the object management record have been released, you can no longer change theobject.

n The status network can be complemented by a user status.

Page 107: LO 980 engineering change mgmt

© SAP AG LO980 5-13

SAP AG 1999

&KDQJH�SRVVLEOH

&RPSOHWH�FKDQJH

5HOHDVH�FKDQJH5HOHDVH

&RPSOHWH

&KHFN

&KHFNHG

$SSURYH

&RQYHUW 2EMHFW�FKDQJH

(&5�SKDVH(&5�SKDVH

(&2�SKDVH(&2�SKDVH

2EMHFW�PJPW�UHFRUGV2EMHFW�PJPW�UHFRUGV

l�

l�

6\VWHP�6WDWXV�1HWZRUN�'HSHQGHQFLHV��,�

n There are various dependencies between the ECR/ECO status networks and the assigned objectmanagement records.

n You can only DVVLJQ�REMHFW�PDQDJHPHQW�UHFRUGV to the ECR BEFORE you set the $SSURYH statusand for the ECO when the status is set to (52�LQFRPSOHWH.

n The &KDQJH�SRVVLEOH status means that you still need to process the ECR and make changes and soyou can also set further statuses. If at least one object management record has this status, then theECR must be converted to an ECO.

n The &RPSOHWH�FKDQJH status allows you to complete the ECO.

n ([FHSWLRQ�IRU�GRFXPHQWV��7KH�&RPSOHWH�FKDQJH�VWDWXV�LV�VHW�E\�XVLQJ�GRFXPHQW�LQIR�UHFRUGVWDWXV�PDQDJHPHQW�DQG�LV�127�VHW�GLUHFWO\�LQ�WKH�REMHFW�PDQDJHPHQW�UHFRUG��)RU�WKLV�SXUSRVH�\RX�PXVW�VHW�D�VWDWXV�LQ�WKH�GRFXPHQW�LQIR�UHFRUG�WKDW�KDV�WKH�&RPSOHWH�IRU�(QJLQHHULQJ&KDQJH�0DQDJHPHQW�LQGLFDWRU�LQ�&XVWRPL]LQJ�IRU�'RFXPHQW�0DQDJHPHQW� Setting such a statusin the document info record sets the &RPSOHWH�FKDQJH indicator in the object management record.)RU�WKLV�UHDVRQ��\RX�FDQ�RQO\�VHW�VXFK�D�VWDWXV�LQ�WKH�GRFXPHQW�LQIR�UHFRUG�LI�WKH�REMHFWPDQDJHPHQW�UHFRUG�DOORZV�WKH�&RPSOHWH�FKDQJH�VWDWXV�DW�WKDW�WLPH�

Page 108: LO 980 engineering change mgmt

© SAP AG LO980 5-14

SAP AG 1999

6\VWHP�6WDWXV�1HWZRUN�'HSHQGHQFLHV��,,�

&KDQJH�XQQHFHVVDU\

5HOHDVH

&RPSOHWH

&KHFN

&KHFNHG

$SSURYH

&RQYHUW

(&5�SKDVH(&5�SKDVH

(&2�SKDVH(&2�SKDVH

2EMHFW�PJPW�UHFRUGV2EMHFW�PJPW�UHFRUGV

l�

n There are various dependencies between the status networks for ECR/ECOs and the status networksfor assigned object management records.

n You can only DVVLJQ�REMHFW�PDQDJHPHQW�UHFRUGV to the ECR BEFORE you set the $SSURYH statusand for the ECO when the status is set to (52�LQFRPSOHWH.

n The &KDQJH�XQQHFHVVDU\ status allows you to set the &KHFNHG�status for the order, EXW�GRHV�QRWGHPDQG�DQ\�IXUWKHU�DFWLRQ�UHJDUGLQJ�REMHFW�FKDQJHV�RU�WKH�VHWWLQJ�RI�IXUWKHU�VWDWXVHV.�<RXRQO\�KDYH�WR�UH�DQDO\]H�WKH�(&5�DQG�FRQYHUW�LW�WR�DQ�(&2�LI�DW�OHDVW�RQH�RWKHU�DVVLJQHG�REMHFWPDQDJHPHQW�UHFRUG�KDV�WKH�&KDQJH�SRVVLEOH�VWDWXV�

Page 109: LO 980 engineering change mgmt

© SAP AG LO980 5-15

SAP AG 1999

6\VWHP�6WDWXV�1HWZRUN�'HSHQGHQFLHV��,,,�

&KDQJH�LPSRVVLEOH&KHFN

&KHFNHG

(&5�SKDVH(&5�SKDVH 2EMHFW�PJPW�UHFRUGV2EMHFW�PJPW�UHFRUGV

l�

«�XQORFN

/RFN&KDQJHSRVVLEOH

&KDQJH�QRW�QHFHVVDU\

&DVH�

&DVH�

(&2�SKDVH(&2�SKDVH

n There are various dependencies between the status networks for ECR/ECOs and the status networksfor assigned object management records.

n You can only DVVLJQ�REMHFW�PDQDJHPHQW�UHFRUGV to the ECR BEFORE you set the $SSURYH statusand for the ECO when the status is set to (52�LQFRPSOHWH.

n 7KH�&KDQJH�LPSRVVLEOH�VWDWXV�ORFNV�WKH�(&5� As long as the lock remains set, you cannot processthe ECR or any of the assigned objects. Either before (or after) the ECR has been unlocked,eliminate the reasons for the lock and set the object management record to either the &KDQJHSRVVLEOH or &KDQJH�XQQHFHVVDU\ status. <RX�FDQQRW�SURFHVV�WKH�(&5�IXUWKHU�XQWLO�\RX�KDYH�GRQHWKLV�

Page 110: LO 980 engineering change mgmt

© SAP AG LO980 5-16

SAP AG 1999

nn������&RQWUROV�VHTXHQFH�RI�EXVLQHVV������WUDQVDFWLRQVn���,Q�(QJLQHHULQJ�&KDQJH�0DQDJHPHQW��IRU�DQ�(&5���(&2�������DQG�WKH�UHODWHG�REMHFW�PDQDJHPHQW�UHFRUGV

$SSOLFDWLRQ$SSOLFDWLRQ

nn������6\VWHP�VWDWXV n���8VHU�VWDWXV

6WDWXV�W\SHV6WDWXV�W\SHV

6WDWXV�0DQDJHPHQW

n A status can either DOORZ business processes, DOORZ them ZLWK�D�ZDUQLQJ� or GLVDOORZ them.

n If you want to be able to carry out a specific business transaction, at least one active status mustallow the transaction and no active status can disallow it.

n Furthermore, you can use the status to find out about the FXUUHQW�SURFHVVLQJ�VWDWXV of the object.

n The internal, fixed system status can be complemented by a customer-specific user status.

n System status assignment by the system follows a predefined sequence that CANNOT be changed.System statuses cannot be set or deleted by user statuses.

n System statuses can be set by the user for the ECR/ECO and the object management record.However, the system determines which statuses you can set. (In other objects that are linked tocentral status management - for example, production orders - you cannot set the system statusmanually.)

n You can define user statuses in Customizing. If required, you can also define a set sequence in thestatus profile.

n User statuses can be set or deleted automatically by certain business transactions. Otherwise you setor delete the user status manually.

Page 111: LO 980 engineering change mgmt

© SAP AG LO980 5-17

SAP AG 1999

Change possible

Complete change

Release change

Change possible

Complete change

Release change

6\VWHP�VWDWXV 8VHU�VWDWXV

Check

Check

Warehouse stock

Technicalnecessity

Check Usageof parts

Checks Documented

6\VWHP�DQG�8VHU�6WDWXV��2EMHFW�0JPW�5HFRUG������VU������

2EMHFW�PDQDJHPHQW�UHFRUG�W �" *#� X��%�'�

n If required, you can use user statuses to complement the system status management. 7KLV�LV�SRVVLEOHIRU ERWK�WKH�(&5�(&2�DQG�WKH�DVVLJQHG�REMHFW�PDQDJHPHQW�UHFRUGV� You can use GLIIHUHQWstatus profiles for the assigned object management records of DQ�ECR/ECO.

n You can define user statuses in Customizing. If required, you can also define a set sequence in thestatus profile.

n As with a system status, by using a user status you can DOORZ, DOORZ�ZLWK�D�ZDUQLQJ, or GLVDOORZcertain business transactions.

n As with a system status, by setting a user status, you can start a workflow.

n If you want to be able to carry out a specific business transaction, at least one active status mustallow the transaction and no active status can disallow it.

n Furthermore, you can use the status to find out about the FXUUHQW�SURFHVVLQJ�VWDWXV of the object.

n User statuses can be set or deleted automatically by certain business transactions. Otherwise you setor delete the user status manually.

Page 112: LO 980 engineering change mgmt

© SAP AG LO980 5-18

SAP AG 1999

Check

Checked

Approve

Convert

Complete

Release

Check

Checked

Approve

Convert

Complete

Release

6\VWHP�VWDWXV 8VHU�VWDWXV

Check economic feasibility

Checks documented

6\VWHP�DQG�8VHU�6WDWXV��0DVWHU�5HFRUG����Y�ZU������

+HDGHU�OHYHO�W �" *#� X�[%\'�

Page 113: LO 980 engineering change mgmt

© SAP AG LO980 5-19

SAP AG 1999

'LJLWDO�6LJQDWXUHV

6PDUW�FDUG

]�^ _a`=b1c&dfeQgh b5iji5kml;e>n

o1prq�q;s�t3u

vxw1yrz�{�����ZU������

n The ability to effectively use the DP-supported Engineering Change Management in the companysoftware on the one hand and to keep the statutory requirements, approval process documents withthe original signature of the employee for a specific time on the other hand, leads to the importanceof introducing 'LJLWDO�6LJQDWXUH.

n An original signature identifies the person that made this signature. A paper document with anoriginal signature can serve as evidence and forms the basis for business and civil agreements.

n In a company’s change management approval procedure, the employee responsible confirms hisdecisions (such as release, reject, close) with his signature.

n The integration of the digital signature enables you to meet the statutory security requirements ofdifferent control authorities and industry standards (such as Good Manufacturing Practices).

n A prerequisite for the use of the electronic signature is a card reader for smart cards that is deliveredby an external provider and connected to the frontend computer.

Page 114: LO 980 engineering change mgmt

© SAP AG LO980 5-20

SAP AG 1999

HeaderHeader

ObjMgmtRecObjMgmtRec

ObjMgmtRecObjMgmtRec

ObjMgmtRecObjMgmtRec

�����

6WDWXV

6WDWXV

6WDWXV

6WDWXVl 0XOWLSOH�VLJQDWXUH�SULQFLSOHl $XWKRUL]DWLRQ�FRQFHSWl 6HDUFK�DQG�UHSRUWLQJ�IXQFWLRQV

'LJLWDO�6LJQDWXUH��&KDQJH�7\SHl &KDQJH�KHDGHU�DQG�REMHFW

PDQDJHPHQW�UHFRUGl 6HWWLQJV�LQ�&XVWRPL]LQJ�IRU

HDFK�VWDWXV�FKDQJH�(OHFWURQLF�VLJQDWXUH��<HV�1R"

6HWWLQJV�LQ�&XVWRPL]LQJ�W �" $#� ��%�'� |~} #Y " �.���� � ��[�Z�\�1�

4712 3'0B�4711 3'0B�

... ... ...

...

...

CA�5/1C1�C5�A/.CA�C5�5/.C5��/.�CA�D/rCA�x/1�,5�j�50 :A�A/,A�=�50 :A�1/Cr:f?.�1/A0 -C.:�?r�5/A0 -CA4 :D�A/CA4 :5�1/0>/A4 /.,x�1/0>/54 /1,r�1/

�.���r�J�D�&�r�&�

�.���r�J�D�&�r�&�

n For each ECR/ECO or object management record, you can set in Customizing whether an electronicsignature is activated when setting this status in the change process.

n As soon as a status change requires an electronic signature, the user is first asked to enter a passwordin a special dialog box. At this point the user can also enter a comment. The next step is for the userto have his personal smart card checked by the card reader. If the password entered and theinformation on the smart card match, then the next step of the change process can be carried out. Thesystem checks whether the user is entitled to use a particular digital signature according to theauthorization object C_SIGN_BGR.

n Using the available search and reporting functions, all activated signatures can be selected anddisplayed for one or more ECRs/ECOs at any time.

n An important performance feature of the electronic signature in the R/3 System Engineering ChangeManagement is the support of the PXOWLSOH�VLJQDWXUH�SULQFLSOH. Here, you decide from three mainscenarios, which cover all possible cases.• All scheduled employees have to sign.

Example: Three group/department heads from the mechanical, electronic and ergonomic areas• A predefined subquantity of employees have to sign.

Example: at least two employees from the department• It is enough for one or more employees with special permission to sign.

Example: two employees from the department or a department head

Page 115: LO 980 engineering change mgmt

© SAP AG LO980 5-21

SAP AG 1999

&XVWRPL]LQJ��'LJLWDO�6LJQDWXUHV

�$VVLJQVLJQDWXUH�VWUDWHJ\�

WR�WKH�V\VWHP�VWDWXV

�$VVLJQVLJQDWXUH�VWUDWHJ\�

WR�WKH�V\VWHP�VWDWXV $VVLJQ�VLJQDWXUH�QHWZRUN�

WR�WKH�FKDQJH�W\SH$VVLJQ�VLJQDWXUH�QHWZRUN�WR�WKH�FKDQJH�W\SH

&UHDWH�VLJQDWXUH�QHWZRUN�IRU�WKH���(&5���(&2���2EMHFW�PDQDJHPHQW�UHFRUG

DQG�WR�WKLV�WR�WKHDXWKRUL]DWLRQ�REMHFW

&B6,*1B%*5DQG�WR�WKLV�WR�WKH

DXWKRUL]DWLRQ�REMHFW&B6,*1B%*5

&UHDWH�DXWKRUL]DWLRQ�JURXS

$QG�GHWHUPLQH�WKDW�WKHVH�DUH�DVVLJQHG�WR�DXWKRUL]DWLRQ�

JURXSV

$QG�GHWHUPLQH�WKDW�WKHVH�DUH�DVVLJQHG�WR�DXWKRUL]DWLRQ�

JURXSV

&UHDWH�LQGLYLGXDO�VLJQDWXUHV

&UHDWH�VLJQDWXUH�VWUDWHJLHV��������� $VVLJQ�LQGLYLGXDO�VLJQDWXUHV�

DQG�SUHGHFHVVRU�VLJQDWXUHV��������� 'HWHUPLQH�WKH�UHOHDVH�VWDWXV�XVLQJ�WKH

QHFHVVDU\�LQGLYLGXDO�VLJQDWXUH�FRPELQDWLRQV

n 1. Create the authorization groups. In the user master record, you assign this authorization group tothe authorization object C_SIGN_BGR.

n 2. Create the individual signatures. Authorization groups are assigned to these. This determines whois allowed to manage which individual signature.

n 3. Create a�signature strategy. You assign individual signatures to these. You still have to determinethe sequence of these individual signatures. Any network is possible for this. Using the releasestatus, you determine which combination of individual signatures leads to the release of the statussetting .

n 4. Assign this signature strategy to the desired status of the ECR/ECO or the object managementrecord. This takes place in the signature network.

n 5. You assign this signature network when completing the change types.

Page 116: LO 980 engineering change mgmt

© SAP AG LO980 5-22

SAP AG 1999

1HZ�)HDWXUHV�LQ����&��'LJLWDO�6LJQDWXUHV

l 1HZ�VLJQDWXUH�PHWKRGV� 8VHU�VLJQDWXUH�ZLWK�DXWRPDWLF�YHULILFDWLRQ� 6\VWHP�VLJQDWXUH��8VHU�,'��3DVVZRUG�

l 1HZ�GDWD�LQ�VLJQHG�GRFXPHQW� 5HDVRQ�IRU�VLJQDWXUH��XVHU�,'�FRPSOHWH�QDPH�FRPPHQWV��WLPH�RI�VLJQDWXUH

l 1HZ�LQ�WKH�GLDORJ�ER[�IRU�PDQDJLQJ�WKH�VLJQDWXUH� &RPPHQW� 5HDVRQ�IRU�VLJQDWXUH

l 8VHU�ORFN�DIWHU�D�VHW�QXPEHU�RI�LQFRUUHFW�VLJQDWXUH�DWWHPSWVDQG�WKLV�LV�WKHQ�ORJJHG�LQ�WKH�6HFXULW\�$XGLW�/RJ

���&

n You can make these new settings in Customizing Engineering Change Management under Approvalfor new entries -> Maintain basic settings for digital signatures.

Page 117: LO 980 engineering change mgmt

© SAP AG LO980 5-23

SAP AG 1999

1HZ�)HDWXUHV�LQ����&��&KDQJH�1RWLILFDWLRQ

�)UHHO\�IRUPXODWHG�WH[W�XVLQJ�D�VLPSOH�IRUP�LQ�WKH�,QWUDQHW$GYDQWDJHV���� 1R�VSHFLDO�NQRZOHGJH�UHTXLUHG

�� �5���RU�(QJLQHHULQJ�&KDQJH�0DQDJHPHQW��� &DQ�DOZD\V�EH�FUHDWHG�XVLQJ�WKH�,QWUDQHW��LQVWHDG�RIE\�WHOHSKRQH�IRU�H[DPSOH�

�� SRVVLEOH�LQ�6$3�5����7UDQVDFWLRQV�,46��RU�,46����� 3RVVLEOH�RXWVLGH�RI�6$3�5����(DV\�:HE�7UDQVDFWLRQ��� 'LUHFW�WUDQVIHU�LQWR�5��

���� �IRU�H[DPSOH��(QJLQHHULQJ�&KDQJH�0DQDJHPHQW��� &UHDWH�RQH�RU�PRUH�FKDQJH�QXPEHUV�IRU�D�FKDQJHQRWLILFDWLRQ

�� $VVLJQ�FKDQJH�QRWLILFDWLRQ�WR�DQ�H[LVWLQJ�FKDQJH�QXPEHU�� 7KH�QRWLI\LQJ�SHUVRQ�FDQ�DOZD\V�GLVSOD\�WKH�VWDWXV�RIWKH�QRWLILFDWLRQ�DQG�WKH�GRFXPHQW�IORZ��FKDQJH�QXPEHU�

� YLD�WKH�,QWUDQHW

���&

Page 118: LO 980 engineering change mgmt

© SAP AG LO980 5-24

SAP AG 1999

<RX�DUH�QRZ�DEOH�WR�

(&5���(&2��8QLW�6XPPDU\

l 8VH�WKH�IXQFWLRQDOLW\�RI�WKH�(&5�DQG�(&2l &DUU\�RXW�WKH�FKHFN��FRQYHUVLRQ�DQG�UHOHDVH

SURFHGXUH�XVLQJ�WKH�VWDWXV�QHWZRUN�IRU(&5V�(&2V�DQG�REMHFW�PDQDJHPHQW�UHFRUGV�DQGWKH�REMHFW�GHSHQGHQFLHV�WKDW�WKLV�LQFOXGHV

l ,QFOXGH�WKH�XVHU�VWDWXV�LQ�WKLV�:RUNIORZ�DQG�KRZWR�XVH�LW

l $VVHVV�WKH�GLJLWDO�VLJQDWXUH�RSWLRQV

n The ECR / ECO and the assigned object management records with their status management form therequest, check and release procedure in Engineering Change Management.

n You can use a customer-specific user status for the ECR / ECO and the object management recordsto complement the set up defined by the system status.

n You can assign a user status profile, Workflow object and signature network using the change typeof the ECR / ECO or the object management records.

n Status management allows you to trigger Workflows in Engineering Change Management.

Page 119: LO 980 engineering change mgmt

© SAP AG LO980 5-25

�([HUFLVHV

8QLW��(&5���(&27RSLF��(&5���(&2

At the conclusion of this exercise, you will be able to:

• Carry out the process using an ECR and an ECO in the SAPStandard from the point of view of central changemanagement.

• Carry out the process using an ECR and an ECO in the SAPStandard from the point of view of the affectedengineering/design department (BOM and documentmanagement).

In this exercise, you simulate two departments in a company:central change management and an affected engineering/designdepartment. Technically required changes to a BOM anddocument are made with the help of an ECR/ECO.

Open a second session and arrange both sessions on your screen.

1-1 &HQWUDO�&KDQJH�0DQDJHPHQW:Create an ECR with the following data:

Change no.: &����Type: (&5Change type: ���

Rest unchanged

Change Header:Description: 7HFKQ��XSGDWLQJ�SDUW��Status: $FWLYHObject types:BOM: active; object management records (manual)Document: active; object management records (manual)

Objects:BOM: 7�)��������������Document: 7�)����'5:�������Switch back to the header and set the system status “&KHFN�UHTXHVW”. Confirm theinformation for the change type of the object management records and save yourECR.

Page 120: LO 980 engineering change mgmt

© SAP AG LO980 5-26

1-2 Switch to your other screen.

$IIHFWHG�(QJLQHHULQJ�'HVLJQ�'HSDUWPHQW�Goto the change mode in your ECR.

To check the ECR of the affected object display the detail view of the objectmanagement record:

BOM: 7�)��������������Document: 7�)����'5:�������

Maintain any of the descriptions in the object management records.

Since you are of the opinion that the affected objects could be changed, set thesystem status in the affected object management records to µ&KDQJH�SRVVLEOH¶ andthen save the ECR.

1-3 Switch to your other screen.

&HQWUDO�&KDQJH�0DQDJHPHQW�Since you are of the opinion that the ECR should be converted into the scheduledform, switch to the header of the ECR and, one after the other, set the systemstatuses 5HTXHVW�FKHFNHG, $SSURYH�UHTXHVW and &RQYHUW�UHTXHVW.Valid from: Today’s date + 6 monthsSave your ECR.

1-4 Switch to your other screen.

Affected Engineering/Design Department:

Change the affected objects with the change number C##-5:

BOM: 7�)��������������For the component T-B3## enter the sort string 'Steel'.Save the BOM.

Document:7�)����'5:�������Change the status of &+ to 5/. In so doing, copy the reserved change number.Which revision level was assigned when saving? _____

Since you are of the opinion that the affected objects have finally been changed, goto the affected object management record of the change number and set the systemstatus to &ORVH�FKDQJH���5HOHDVH�FKDQJH��In the object management record of the documents the status has already been set to&ORVH�FKDQJH. Why ?____________________________________________________________

____________________________________________________________

Page 121: LO 980 engineering change mgmt

© SAP AG LO980 5-27

1-5 Switch to your other screen.

&HQWUDO�&KDQJH�0DQDJHPHQW�Since you are of the opinion that the ECO is closed, switch to the header ofthe ECR and, one after the other, set the system statuses &ORVH�RUGHU and 5HOHDVHRUGHU.

Page 122: LO 980 engineering change mgmt

© SAP AG LO980 5-28

6ROXWLRQV

8QLW��(&5���(&27RSLF��(&5���(&2

1-1 &HQWUDO�&KDQJH�0DQDJHPHQW:

In the user menu, goto(QJLQ��FKDQJH�PJPW�→�&KDQJH�1XPEHU�→�&UHDWH

In the initial screen enter:

Change no.: &����Type: (&5Change type: ���

Rest unchanged

The change header appears. Enter text and status 01 here. The rest remainsunchanged.

After a data release, or by clicking on ‘2EMHFW�W\SHV’ the object types overviewappears. Copy the recommended selections in the lines BOM and document. Deletethe indicator for the material master record and routing.

By clicking on �2EMHFWV� �)���the object overview appears.

Here you start on the tabpage 'RFXPHQW�and enter the given document.

7�)����'5:�������Switch to the tab page 0DWHULDO�%20 and enter the given BOM.

7�)��������������

Click �+HDGHU� �)�" and switch back to the header and set the system status&KHFN�UHTXHVW, by clicking the �6HW�6WDWXV���3HQFLO�ZLWK�JUHHQ�WLFN��button andselecting the corresponding button in the dialog box. (Quit the warning messagethat object management records exist without change type) and save your ECR.

Page 123: LO 980 engineering change mgmt

© SAP AG LO980 5-29

1-2 Switch to your other screen.

$IIHFWHG�(QJLQHHULQJ�'HVLJQ�'HSDUWPHQW�

In the user menu, goto(QJLQ��FKDQJH�PJPW�→�&KDQJH�1XPEHU�→�&KDQJH

In the initial screen enter:Change no.: &����Go to the object overview. (Click "Objects")

Select the BOM line and goto the details by clicking �'HWDLO�YLHZ� �&WUO����)��(jigsaw piece)

By clicking on �'LVSOD\�� (glasses) you can goto the item overview of the BOMfrom here.

Go back to the detail view of the object management record.Here, maintain the 'HVFULSWLRQand set the V\VWHP�VWDWXV�&KDQJH�SRVVLEOH, in the way described above (Click�6HW�VWDWXV�).

Go back to the overview of the object management records.Select the document line and goto the details by clicking �'HWDLO�YLHZ� �&WUO���)�� (jigsaw piece)

By clicking on �'LVSOD\�'RFXPHQW� (glasses) or µ'LVSOD\�2ULJLQDO¶�(bar chart)you can goto the corresponding display.

Go back to the detail view of the object management record.Here, maintain the 'HVFULSWLRQand set the V\VWHP�VWDWXV�&KDQJH�SRVVLEOH, in the way described above (Click�6HW�VWDWXV�).

Save the ECR.

1-3 Switch to your other screen.

&HQWUDO�&KDQJH�0DQDJHPHQW�I the user menu, goto(QJLQHHULQJ�&KDQJH�0DQDJHPHQW�→�&KDQJH�1XPEHU�→�&KDQJH

In the initial screen enter:

Change no.: C##-5

The change header appears.

Set the system status 5HTXHVW�FKHFNHG, $SSURYH�UHTXHVW and &RQYHUW�UHTXHVW,by clicking on the button with the symbol for 6HW�VWDWXV and selecting thecorresponding button in the dialog box.

After ’Continue’ the Valid-from date becomes a required field. You enhance this inthe header screen.

Save the ECR.

Page 124: LO 980 engineering change mgmt

© SAP AG LO980 5-30

1-4 Switch to your other screen.

$IIHFWHG�(QJLQHHULQJ�'HVLJQ�'HSDUWPHQW�In the user menu, goto%LOO�RI�0DWHULDO�→�0DWHULDO�%20�→�&KDQJHIn the initial screen enter:Material: 7�)���Plant: ����Usage: �Change number: &����Valid-from: (ignore) date from change number

automatically transfer

The item overview appears. In item 0030 enter the sort string (scroll to the right ofthe item overview). Save the changes.

In the user menu, goto'RFXPHQW�→�&KDQJHIn the initial screen enter:

Document: 7�)���Document type: '5:Document part: ���Document version: ��

After the data release, a dialog box appears with the reserved change numbers.Copy the reserved change number &�����by double clicking on the change number.Change the status and save.The UHYLVLRQ�OHYHO��� is assigned.

In the user menu, goto(QJLQ��FKDQJH�PJPW�→�&KDQJH�1XPEHU�→�&KDQJH

In the initial screen enter:

Change no.: &����

The change header appears. Select �2EMHFWV� The object overview appears. Fromthere, first select the object management record of the BOM and using thecorresponding buttons, branch to the corresponding detail screen.

Set the system status &RPSOHWH�FKDQJH, ´5HOHDVH�FKDQJH´.

Return to the object overview and goto the detail screen of the document.

Branch to the status dialog box. The system status &RPSOHWH�FKDQJH is already setbecause for documents, this status is NOT set directly, rather indirectly using thestatus management of the document info record. For this purpose, you must set astatus in the document info record that has the µ&RPSOHWLRQ�PHVVDJH�IRU(QJLQHHULQJ�&KDQJH�0DQDJHPHQW¶�indicator set in Customizing. In the trainingsystem, this is the case for the status µ5/¶. Set the status ´5HOHDVH�FKDQJH´.

Save the ECR.

Page 125: LO 980 engineering change mgmt

© SAP AG LO980 5-31

1-5 Switch to your other screen.

&HQWUDO�&KDQJH�0DQDJHPHQW�I the user menu, goto(QJLQHHULQJ�&KDQJH�0DQDJHPHQW�→�&KDQJH�1XPEHU�→�&KDQJH

In the initial screen enter:

Change no.: C##-5

The change header appears.

Set the system statuses &RPSOHWH�RUGHU, and 5HOHDVH�RUGHU. Confirm the dialogbox with the information that the ECO is released.

Save the ECR.

Page 126: LO 980 engineering change mgmt

© SAP AG LO980 6-1

SAP AG 1999

&RQWHQWV�

3URFHVVLQJ�&KDQJHV�ZLWK�:RUNIORZ

l &RQFHSW�DQG�VWUXFWXUH�RI�WKH�:RUNIORZl 5ROHVl 2UJDQL]DWLRQDO�VWUXFWXUH�DQG�RUJDQL]DWLRQDO�PDQDJHPHQWl :RUNIORZ�7HPSODWHV�IRU�(&0l 6HWWLQJ�XS�WKH�VWDQGDUG�ZRUNIORZ

l &KDQJH�W\SHl 2UJDQL]DWLRQDO�VWUXFWXUHl /LQNVl &XVWRPL]LQJ

Page 127: LO 980 engineering change mgmt

© SAP AG LO980 6-2

SAP AG 1999

l 1DPH�WKH�EDVLF�FRQFHSW�DQG�FRPSRQHQWV�RI�WKH6$3�%XVLQHVV�:RUNIORZ�DQG�KDYH�DQ�LGHD�RI�WKHKRZ�WKH�ZRUN�VWHSV�LQ�(QJLQHHULQJ�&KDQJH0DQDJHPHQW�FDQ�EH�DXWRPDWHG

l 6HW�XS�DQG�XVH�WKH�VWDQGDUG�ZRUNIORZ�RI(QJLQHHULQJ�&KDQJH�0DQDJHPHQW�DQG�NQRZZKLFK�:RUNIORZ�WHPSODWH�WR�XVH�DV�D�EDVLV�IRUFRPSDQ\�VSHFLILF�ZRUNIORZV�LQ�(QJLQHHULQJ&KDQJH�0DQDJHPHQW

l $SSUHFLDWH�WKH�PHDQLQJ�RI�WKH�FKDQJH�W\SH�IRU�WKH:RUNIORZ

l 0DNH�WKH�QHFHVVDU\�VHWWLQJV�LQ�&XVWRPL]LQJ

$W�WKH�FRQFOXVLRQ�RI�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�

3URFHVVLQJ�&KDQJHV�ZLWK�:RUNIORZ�7RSLF�2EMHFWLYHV

Page 128: LO 980 engineering change mgmt

© SAP AG LO980 6-3

SAP AG 1999

&RXUVH�2YHUYLHZ�'LDJUDP

2EMHFW�&KDQJHV2EMHFW�&KDQJHV ��

5HSRUWLQJ5HSRUWLQJ ��

�� &KDQJH�+LHUDUFK\��&KDQJH�+LHUDUFK\��5HOHDVH�.H\�5HOHDVH�.H\�«« ��&KDQJH�0DVWHU�5HFRUG&KDQJH�0DVWHU�5HFRUG

��&RXUVH�2YHUYLHZ&RXUVH�2YHUYLHZ ��

(&5���(&2(&5���(&2 ��

3URFHVVLQJ�&KDQJHV�3URFHVVLQJ�&KDQJHV�ZLWK�:RUNIORZZLWK�:RUNIORZ

6XPPDU\6XPPDU\ ��

2UGHU�&KDQJH�2UGHU�&KDQJH�0DQDJHPHQW��2&0�0DQDJHPHQW��2&0� ��

Page 129: LO 980 engineering change mgmt

© SAP AG LO980 6-4

SAP AG 1999

l 7KH�IORZ�RI�WKH�(&5�(&2�EXVLQHVV�VFHQDULRGHVFULEHG�LQ�WKH�SUHYLRXV�XQLW�VKRXOG�EH�VXSSRUWHGE\�:RUNIORZ�

l <RX�KDYH�WR�DQDO\]H�KRZ�WKH�VWDQGDUG�ZRUNIORZ�RI(QJLQHHULQJ�&KDQJH�0DQDJHPHQW�FDQ�EH�VHW�XSDQG�XVHG��DQG�WR�ZDQW�H[WHQW�FRPSDQ\�VSHFLILFHQKDQFHPHQWV�DUH�UHTXLUHG�

3URFHVVLQJ�&KDQJHV�ZLWK�:RUNIORZ��%XVLQHVV6FHQDULR

Page 130: LO 980 engineering change mgmt

© SAP AG LO980 6-5

SAP AG 1999

:KDW�&DQ�D�:RUNIORZ�0DQDJHPHQW�6\VWHP�'R"

$�ZRUNIORZ�PDQDJHPHQW�V\VWHP�IDFLOLWDWHV�WKH�HOHFWURQLFSURFHVVLQJ�RI�VWUXFWXUHG�SURFHVVHV�ZKLFK�

l LQFOXGH�D�UDQJH�RI�DFWLYLWLHV�l DOZD\V�RFFXU�LQ�D�VLPLODU�RU�LGHQWLFDO�IRUP�l LQYROYH�VHYHUDO�SHRSOH�RU�GHSDUWPHQWV�DQGl UHTXLUH�D�KLJK�GHJUHH�RI�FRRUGLQDWLRQ�

:RUNIORZ�PDQDJHPHQW�V\VWHPV�FRQWURO�SURFHVVHV�DFFRUGLQJ�WRD�SUHGHILQHG�PRGHO�DQG�DUH�HVSHFLDOO\�VXLWHG�WR�VWUXFWXUHGRUJDQL]DWLRQV�WKDW�DUH�EDVHG�RQ�GLYLVLRQ�RI�ODERU�

n A workflow management system coordinates the flow of all types of information by differentactivities.

n Workflow ensures that the correct task is given to the correct person at the correct point in time.

Page 131: LO 980 engineering change mgmt

© SAP AG LO980 6-6

SAP AG 1999

���������� �����

� ����������� ������� � � �� ��� �! #"$�%����&� ��� � �'� �� (�) ��+*,� � �� ���-�.� � � �� �����

/ �&0���1

� �'��2�� �+34��5��� � �����

/ %-� �� 3�������6 � �-�7 ��*&�8$�� ��9 � ��$&�4��� �� ���

::; < = >4?::; < =

Process design

@BA�CEDGFIH�J�K5L�F-DNMPOQ�J�R.R'RR4R'RA-OBQSM FUT�CWV-CK X'Y�C�VEO�Q6OZQ+X'YI[�LPCB\�Q�M�C^]F�H`_ba�L�MPX'\PQ�M C^]cM.OBQIJ6X'Yed-fhgji-k�l�R

m�F�H`OW_na�L M4X�\4Q�M�Co]p]!HqF�r�C�Q�QSM.A�CX4Y�VIXPs�XPV�a+O�L�]!HtF�r�C8Q�Q6OIr�M�XPs�XPM.X C�QEA�O�sCEM FCvu-X'Q-M�OBQ�Q�X.YI[�L�C8\PQ-M Co]wM4O�Q�JBQxX'YbF�HtV�C8HM�F6T�C#X'Y�M5C�[�H&O�M C�VUX'YbM.A�CW_baIL�M�X'\PQ�M C^]M�OBQIJBQ+R

@BA�CyQ�X'YI[�LPC8\�Q�M5Co]zM OBQ�JBQUH{CK|CBH}M�FO�YnF�Tq~^C�r�M�M4�8]�CyO�Y�VUOW_jC�M�A�F�VER4R'R�R

R4R'R�MPA�OIM�CY�O�T�L�C�QUO+r�r�C�Q�QxM�FxC�u-X Q�M'X�YI[d�fGg�K|a+Y�r�M.X F�Y�O�L'X�M ����K|FIH}Cvu-O�_�]�LPCBR

%DVLF�&RQFHSWV��,�

n Workflow Definition

é Made up of individual steps in a modular fashion.

é Establishes which tasks are performed, when, under which conditions and by whom.

n 0XOWL�VWHS�WDVNV��:RUNIORZ�WDVNV�:RUNIORZ�WHPSODWHV�é Each refers to a Workflow definition.

n :RUNIORZ�7HPSODWHVSAP provides executable Workflow templates that can be changed and added to at any time usingthe graphical Workflow editor.

Page 132: LO 980 engineering change mgmt

© SAP AG LO980 6-7

SAP AG 1999

(YHQWV�� 7 ��*��6� 5�I��5� ) 7 ��*��E� 5����5� ) �� � ���I2U�� ) ����� ����2p�� ) ����� �����*&�.����'���� ��+�I*��4��&� ������-�b��� ��� �!����-�n��� �,� ���/ � ������1p1+� � 1��'�4���/ � ������1p1�� � 1��'�����

� � ) �� �� � �+*��b�.� � &�.��2U��I�+��5�� ��*|�n�4� � &�4��2p�B���+������ � *�� 2�2��+*��'��2S�B�I�+�� �� *�� 2�2+�+*,� �I2x��I�+�� ������ �e� $��0������4�I2�� ��3�����+��W��� �b� $��0��Z������2�� ��3P����+� � ����� �W|�e*,%�� � � ����� � ����� ��|�b*�%�� � � �����

( �+�+�� �

/ %�� {� 3�����+�6 � ���

�W����������-���/ �&0��-1

7 ��*,��$�� ��9� �$&�.��� �� ���

� �'��2�� �I34��|�+� � ���8�

��*|2 � ��� � � ,� ��� � ����*�%I�B&%�*5��5��� ��8�B� � ����o���B�o�

���5� ����8� � ����o���8���$FWLYLWLHV$FWLYLWLHV$FWLYLWLHV

%DVLF�&RQFHSWV��,,�

$JHQW�VHDUFKXVLQJUROH�UHVROXWLRQ�

�-%��+0 � ������0 � �+2+�x�-%I�n���+*��%I�+0 � �����G0 � ��2-�6�U���

" %-���'� ��0���1" %����'� ��0���1�B���+���B�+�+��

�Z*�2 � ��� � � �� ��� � ��%��-� ��P�#�

� ���x������ ���x�P���" �I�-� �� ���p� � �

" ��*������E� " �" �+*��+���E� " �

n 5ROH�UHVROXWLRQA customer task/standard task is usually defined fully and in general terms, so that several agents areassigned to it. Roles are used to limit or define more closely the number of possible agents or personsresponsible according to business points of view.Advantages:

é Dynamic restriction of possible agents

é Actual organizational structure need not be known

é Finding of agents up-to-date (role resolution at runtime)

n :RUN�LWHP�WH[WText in the description column of the integrated inbox.

n /RQJ�WH[WDescription of taskNotification text (for notification agent) when task is completeNotification text (for notification agent) when deadline has not been met

n 7ULJJHULQJ�HYHQWVSingle-step tasks are independent, re-usable modules that can also be performed alone as a singlestep.If a single step is to be entered as an event receiver, it must be agreed on as triggering event whenyou define the single-step task.

Page 133: LO 980 engineering change mgmt

© SAP AG LO980 6-8

SAP AG 1999

:RUNIORZ�7HPSODWHV�IRU�(&0

( ��������+����1

7 ��*���$,� �I9�� � * ���1 9 � � ,�'��2

9 � � ��'��2

( �G�*����5���B��I1

( �h�� ��������1

���������+*� ( �h� �-��*|���I� ( �����0��I�I� ( �h�� � ��&*��.��%��� ( �h�j$5��*��+����-*&�.��2p�����|���P�� � ( �h�j��j�����I0����I����1

����� � � ��� ( �y������e�-� ��� ( ���  ��$5� � ����%�������������� � &%��

7 ��*,��$�� ��9$��'��� �-0���17HPSODWH�IRU�(&5�(&2�OHYHOV

7HPSODWH�IRUFKDQJH�REMHFWOHYHOV

n Change process scenarios based on a Workflow template can take place on two levels:ECR / ECO level (Workflow template for object type ECM)Change object level, for example, BOM, document (Workflow template for object type ECO).

n You can use Workflow templates individually (for example, for processing an ECR / ECO), orcombined (for example, additional use of Workflow template for processing BOMs and documents).

n There are three Workflow templates for processing an ECR / ECO:Template WS 00000039 (up to release 3.x)Template WS 00600011 (up to release 3.1)Template WS 20000067 (from release 4.0a).

Page 134: LO 980 engineering change mgmt

© SAP AG LO980 6-9

SAP AG 1999

(&5���(&2

Í GeneralÍ Bill of materialÍ DocumentÍ Recipes

&KDQJH�REMHFWV

Í:6���������

:6���������:6���������:6���������:6���������

:RUNIORZ�7HPSODWHV

n You can display the technical data for all the Workflow templates that are defined for (QJLQHHULQJ&KDQJH�0DQDJHPHQW in the�6$3�%XVLQHVV�:RUNIORZ��'HYHORSPHQW� menu.

n To do this, choose 7DVNV from the 'HILQLWLRQ�WRROV menu.

n The task type for Workflow template is WS.

n If you display the possible entries in the 7DVN field, you see all the Workflow templates for(QJLQHHULQJ�&KDQJH�0DQDJHPHQW.Choose 6WUXFWXUH�VHDUFK. Expand the following entries in the component hierarchy: /RJLVWLFV*HQHUDO�� (QJLQHHULQJ�&KDQJH�0DQDJHPHQW.Following this, you can display the Workflow templates that are defined for &KDQJH�PDVWHU�UHFRUGPDQDJHPHQW and /LQNHG�FKDQJH�REMHFWV separately.

Page 135: LO 980 engineering change mgmt

© SAP AG LO980 6-10

SAP AG 1999

:6���������

3URFHVVLQJ�(&5���(&2

�`�+� � � �I� ( �h�z����-�n��� ��� ( �y��� 7 � ������������¡��  ��$5� � ����%�����������B��� � &%��U� 7 � ������������¡B¢

( ��������+����1

7 ��*���$�� �+9�� � *� ��1 9 � � ��'��2

9 � � ��'��2

( �G�*|���5������1

( ���� �-�I�8��1

������I�+*� ( �h�z� 7 � ������������¡+£ �-��*|���I� ( �y�z� 7 � ������������¡��

��0������ ( �h�z� 7 � ������������¤�¥� � ��&*��4�-%��� ( �h�j$5��*��+����+*,�.��2p�����5���P�U� 7 � ������������¤�¦

� � ( �h�j��n�����I0����I����1S� 7 ��§ ������£�£

7 ��*,��$�� ��9$��'��� �-0���1

:6�������

:6���������

:6���������:6���������

:6���������:6���������

:6���������:6���������

n The Workflow template 3URFHVV�(&5�(&2 (WS 20000067) is defined as a multi-step task. ThisWorkflow consists of a sequence of several subworkflows.

n These work items are taken from the different steps of the Workflow definition, each of whichrelates to a standard task (TS). The following process is controlled with this Workflow (20000067):

n You create the ECR and start the Workflow. You can create individual objects that are affected bythe change.

n If the ECR does not yet have the &KHFN�(&5 system status, the system starts the subworkflow 6HW(&5�WR��7R�EH�FKHFNHG���:6��������

n After you have created the change objects and set the &KHFN�(&5 status, you can distribute therequest to other employees who can, if need be, add further change objects. 'LVWULEXWH�(&5�IRUHQWHULQJ�REMHFWV��:6����������

n After the employees have created the change objects, you can check the feasibility of the change foreach change object &KHFN�(&5��:6��������� and set the system status (&5�FKHFNHG for the changemaster record.

n After the ECR has been checked, you can approve it with $SSURYH�(&5��:6�����������n After the ECR has been approved, you can convert it with &RQYHUW�(&5��:6����������n You can now process the objects (WS20000074) and complete object changes.

n Finally, you can complete the ECO (WS 20000072), and release it (WSW20000073).

Page 136: LO 980 engineering change mgmt

© SAP AG LO980 6-11

SAP AG 1999

1HZ�:RUNIORZV�IRU�(&5V�DQG�2EMHFWV

Ì :RUNIORZ� ����������(&5�(&2

Ì )XUWKHU�GHYHORSPHQW�RI:6������������DOO�SRVVLEOHVWDWXV�FKDQJHV�DUH�WDNHQ�LQWRFRQVLGHUDWLRQ

Í :RUNIORZ� ����������2EMHFW�PDQDJHPHQW�UHFRUG

Í )XUWKHU�GHYHORSPHQW�DQGVXPPDU\�RI�:6�����:6���:6������

Í 3RVVLEOH�WR�MXPS�WR�GLVSOD\DQG�PDLQWHQDQFH�IRU�DOOREMHFW�PDQDJHPHQW�UHFRUGV

���&

Page 137: LO 980 engineering change mgmt

© SAP AG LO980 6-12

SAP AG 1999

2UJDQL]DWLRQDOREMHFW�W\SHV

2UJDQL]DWLRQDOREMHFW�W\SHV

7&&���� Person responsiblefor changes �FKDQJH�PDVWHU�7&&���� Person responsiblefor changes �FKDQJH�PDVWHU�

2UJ��VWUXFWXUH 5ROH�������������IRU�VWDQGDUG�WDVNV

7&&���� Person responsiblefor REMHFW changes

Change typeChange type

Change type(Objects)

,PSRUWDQFH�RI�WKH�&KDQJH�7\SH

0DVWHUUHFRUG

n The change type is defined in Customizing for (QJLQHHULQJ�&KDQJH�0DQDJHPHQW. This change typeforms the link between the change master record or the change object and the organizational unit.The processor of the task is derived from this link.

n The organizational units for (QJLQHHULQJ�&KDQJH�0DQDJHPHQW are represented in the BusinessObject Repository by the SAP organizational object types TCC11 and TCC13.

n You define the organizational responsibility for the changes in the structural organization for yourcompany. Group employees with the same change tasks together by choosing your jobs andorganizational units carefully. By linking each organizational unit to to a specific change type youcan determine the possible processors for the task. For example, you can enter the change type 099&RPSODLQW�(TC11) for the organizational unit &RPSODLQWV�GHSDUWPHQW. All standard tasks in(QJLQHHULQJ�&KDQJH�0DQDJHPHQW are either assigned to the change master record or the changeobject. An attribute for the employee responsible in the organizational unit is maintained for each ofthese object types. Responsibility for processing the standard tasks is determined at the time ofdefinition via the default role 00000138 3HUVRQV�UHVSRQVLEOH�IRU�FKDQJHV�RI�D�FKDQJH�W\SH. Theassignment of the organizational unit to an organizational object type (TC11 or TCC13) is defined inthe data flow definition for this role.

Page 138: LO 980 engineering change mgmt

© SAP AG LO980 6-13

SAP AG 1999

1. Definition of change types (Customizing)

é for the master record Í (TCC11)é for the objects Í (TCC13)

2a. Maintain organizational structureã Processing the organizational object

2b. Task-Specific Customizing

¨�©^ª ���B�«�'¬­^�

¨!©^ª ���B�}�.¬8­��® ¯I°5± ²�³&´ µ,¶

&XVWRPL]LQJ

6HWWLQJV�IRU�(&0

/ � �����**|������*�1

n Before you make any settings, decide how the possible processors of a task are going to bedetermined in your company.

n If you decide to maintain an organizational structure specific to your company to define theorganization of your employees, then you can determine the employees by a default role. In this case,you should note the following in Customizing:

n You must carry out the work steps for the organizational structure.

n You do not need to carry out the work step ([HFXWH�WDVN�VSHFLILF�&XVWRPL]LQJ if the default role is setfor all tasks.

n If you do not want to organize who receives which jobs by using a structural organization, then youmust enter the relevant employee for each task. In this case, please note the following inCustomizing:

n You do not need to carry out the work steps for the organizational structure.

n You must carry out the work step ([HFXWH�WDVN�VSHFLILF�&XVWRPL]LQJ.

Page 139: LO 980 engineering change mgmt

© SAP AG LO980 6-14

SAP AG 1999

Definition of FKDQJH�W\SHV (Customizing)

ã For the master record (TCC11) (;$03/(: &KDQJH�W\SH������IRU�FRPSODLQWV���

ZLWK�:RUNIORZ�7HPSODWH�:6���������

ã for the objects (TCC13) (;$03/(: &KDQJH�W\SH������IRU�%20V���

ZLWK�:RUNIORZ�7HPSODWH�:6���������

���'HILQLQJ�WKH�&KDQJH�7\SH�LQ�&XVWRPL]LQJ¨�©oª ���B���'¬­��0DVWHUUHFRUG

¨!©�ª ���B�}�'¬­��® ¯I°5± ²,³&´ µ,¶

n The change type of a change master record or a change object contains information on whichWorkflow task is carried out.

n You choose the change type in the following processing situations:

é ECR / ECO: Create

é Change object: entering the detail data of an object management record

n You define the change types in Customizing for (QJLQHHULQJ�&KDQJH�0DQDJHPHQW in the followingwork steps:

é Define change types for the master record (for example, 099 for complaints)

é In this workstep you enter the task for processing the change master record (for example, WS00600011 3URFHVV�(&5�(&2).

é Define change types for objects (for example, 001 for processing BOMs)

é In this workstep you enter the task for processing the change object (for example, WS 00000044&KDQJH�REMHFW�%20).

n After you have saved the change type for a change master record or a change object, you can onlyreplace the change type with another change type that has the same Workflow task.

Page 140: LO 980 engineering change mgmt

© SAP AG LO980 6-15

SAP AG 1999

�D��3URFHVVLQJ�WKH�2UJDQL]DWLRQDO�6WUXFWXUH

ã Organizational structure for ECM department

2UJDQL]DWLRQDO�XQLW��2�2UJDQL]DWLRQDO�XQLW��2�

3RVLWLRQ��6� 3HUVRQ��3�3HUVRQ��3�RU�RU�XVHUXVHU

-RE��&�-RE��&�

(;$03/(2UJDQL]DWLRQDO�XQLW�IRUFRPSODLQW

n -RE� A task is linked to one or more jobs. It describes these jobs and determines their activity profile.All positions and position holders that are assigned to a job "inherit" the job activity profile. Tosimplify matters, you can assign a job to one or more application components as well as directlylinking job and tasks:

é All tasks for these application components are then automatically added to the job activity profilewithout an explicit assignment being necessary for each task.

é Authorization profiles are automatically generated for all position holders for the job. Theseauthorization profiles allow access to the functionality of the assigned tasks.

n 3RVLWLRQ� You could also assign tasks on a position level to assign to individual positions a completeactivity profile that differs from the described job.

n 3HUVRQ�UHODWHG�DVVLJQPHQWV� Try to avoid person-related assignments as far as possible when youare at the definition stage. This type of assignment is inflexible and requires you to invest anincreased amount of time in maintaining it. An example�RI�SUREOHPV�ZLWK�WKLV�W\SH�RI�DVVLJQPHQWFRXOG�EH�WKH�WUDQVIHU�RU�DEVHQFH�RI�DQ�HPSOR\HH�

n You maintain your company-specific organizational structure in the %XVLQHVV�:RUNIORZV�menuunder:

'HYHORSPHQW��!�'HILQLWLRQ�WRROV��!�2UJDQL]DWLRQ�PDQDJHPHQW��!�2UJDQL]DWLRQDO�VWUXFWXUH

Page 141: LO 980 engineering change mgmt

© SAP AG LO980 6-16

SAP AG 1999

ã Assignment change type Organizational object

2UJDQL]DWLRQDO�XQLW2UJDQL]DWLRQDO�XQLW([DPSOH��FKDQJH����([DPSOH��FKDQJH����

6WDQGDUG�UROH���������

2UJDQL]DWLRQDO�REMHFW�W\SH�2UJDQL]DWLRQDO�REMHFW�W\SH�([DPSOH��7&&�����([DPSOH��7&&�����&KDQJHV�&KDQJHV�RI�WKLV�FKDQJH�W\SH�RI�WKLV�FKDQJH�W\SH��PDVWHU�UHFRUG��PDVWHU�UHFRUG�

.H\�ILHOG.H\�ILHOG([DPSOH��(&+����([DPSOH��(&+����

�D��3URFHVVLQJ�WKH�2UJDQL]DWLRQDO�2EMHFW

ÌÍ

n First of all, you link the organizational units for (QJLQHHULQJ�&KDQJH�0DQDJHPHQW to one of thefollowing organizational object types so that the system can determine possible processors for thesingle-step tasks in�(QJLQHHULQJ�&KDQJH�0DQDJHPHQW:

n TCC11 - (PSOR\HH�UHVSRQVLEOH�IRU�FKDQJHV�RI�WKLV�FKDQJH�W\SH��PDVWHU�UHFRUG�n TCC13 - (PSOR\HH�UHVSRQVLEOH�IRU�REMHFW�FKDQJHV�RI�WKLV�FKDQJH�W\SHn Next, you enter the special change type for which the organizational unit is responsible, for example:

é Change type 099 for &RPSODLQWV�for an organizational unit with reference to object type TCC11

é Change type 001 for BOM processing for an organizational unit with reference to object typeTCC13

n The standard role 00000138 for the change type determines the appropriate organizational unit andtherefore the appropriate people at runtime.

Page 142: LO 980 engineering change mgmt

© SAP AG LO980 6-17

SAP AG 1999

ã Execute task-specific Customizing

���$VVLJQ�WDVNV�WR�UHVSRQVLEOH�SHUVRQV���'HILQH�JHQHUDO�WDVNV

,PSRUWDQW� /LQNLQJ�RI�HYHQWV�LV�QRW�QHFHVVDU\�

IRU�(QJLQHHULQJ�&KDQJH�0DQDJHPHQW�

ã Activate linking of events

�E��7DVN�6SHFLILF�&XVWRPL]LQJ

&XVWRPL]LQJ

n In Customizing %DVLV��!�%XVLQHVV�0DQDJHPHQW��!��6$3�%XVLQHVV�:RUNIORZ�you only have to carryout the work step $VVLJQ�WDVNV�WR�DJHQW for Engineering Change Management in the 7DVN�6SHFLILF&XVWRPL]LQJ�under�/RJLVWLFV��*HQHUDO��!�(QJLQHHULQJ�&KDQJH�0DQDJHPHQW.

n The default role 138 (3HUVRQV�UHVSRQVLEOH�IRU�FKDQJHV�RI�D�FKDQJH�W\SH) has been entered for allstandard tasks that are used in Workflow templates for (QJLQHHULQJ�&KDQJH�0DQDJHPHQW� Thedefault role is cancelled during the Workflow runtime in order to determine the chosen agent oraddressee (provided that you have maintained the structural organization). You do not need to makesettings in WDVN�VSHFLILF�&XVWRPL]LQJ for these tasks.

n If you do not maintain an organizational structure in your company, then you cannot inform youremployees of their tasks using the default role 138. In this case you must carry out the followingstep: ([HFXWH�WDVN�VSHFLILF�&XVWRPL]LQJé $VVLJQ�WDVNV�WR�DJHQWV

You have to enter the possible employees responsible for each task in order to define borders ofresponsibility clearly.

é 'HILQH�JHQHUDO�WDVNVIf the standard task is not subject to user limitations, then you can classify this task as a generaltask.

n $FWLYDWH�LQVWDQFH�OLQNDJH is not necessary for Workflow in (QJLQHHULQJ�&KDQJH�0DQDJHPHQW sinceall activities that trigger further events are activated directly (status management).

Page 143: LO 980 engineering change mgmt

© SAP AG LO980 6-18

SAP AG 1999

1HZ�6LPSOH�:RUNIORZ�ZLWK�6FKHGXOLQJ

l 6LPSOH�:RUNIORZl +DV�WR�EH�DFWLYDWHG�

,V�WKHQ�DFWLYH�IRUDOO�FKDQJH�QXPEHUV

l &RPSOHWH�SURFHVVLQJ�RI�WKHFKDQJH�QXPEHU�SRVVLEOHYLD�WKH�LQER[

l 'HWHUPLQDWLRQ�DQG�FRQWUROOLQJ�RISURFHVVLQJ�VFKHGXOHV�SRVVLEOHZLWK�WKH�:RUNIORZ�WRROV

l (DV\�IRUZDUGLQJ�WR�RWKHUSURFHVVRUV�SRVVLEOH

���&:6���������

Page 144: LO 980 engineering change mgmt

© SAP AG LO980 6-19

SAP AG 1999

<RX�DUH�QRZ�DEOH�WR�

3URFHVVLQJ�&KDQJHV�ZLWK�:RUNIORZ��8QLW�6XPPDU\

l 1DPH�WKH�EDVLF�FRQFHSW�DQG�FRPSRQHQWV�RI�WKH6$3�%XVLQHVV�:RUNIORZ�DQG�KDYH�DQ�LGHD�RI�WKHKRZ�WKH�ZRUN�VWHSV�LQ�(QJLQHHULQJ�&KDQJH0DQDJHPHQW�FDQ�EH�DXWRPDWHG

l 6HW�XS�DQG�XVH�WKH�VWDQGDUG�ZRUNIORZ�RI(QJLQHHULQJ�&KDQJH�0DQDJHPHQW�DQG�NQRZZKLFK�:RUNIORZ�WHPSODWH�WR�XVH�DV�D�EDVLV�IRUFRPSDQ\�VSHFLILF�ZRUNIORZV�LQ�(QJLQHHULQJ&KDQJH�0DQDJHPHQW

l $SSUHFLDWH�WKH�PHDQLQJ�RI�WKH�FKDQJH�W\SH�IRU�WKH:RUNIORZ

l 0DNH�WKH�QHFHVVDU\�VHWWLQJV�LQ�&XVWRPL]LQJ

n You have learned about Workflow Management as a tool for increasing the productivity andefficiency of office communication and organization.

n You have learned that SAP Business Workflow integrates and supplements the currentcomprehensive business functionality of the R/3 System.SAP Business Workflow belongs in an integration layer "above" the transaction level and uses theexisting transactions and function modules.

n You have learned that the change process can be controlled using a Workflow definition (single ormulti-step task), roles and organizational structures.

n Executable Workflow templates for Engineering Change Management are delivered in the standardsystem. You can adapt these templates to suit company-specific change processes.

n If you want to distribute standard tasks to the responsible persons using the default roles designed forthis purpose, then you must maintain an organizational structure for your company (with reference toa change type).

n You only need to use task-specific Customizing if you do not use the default/standard role forautomatic recipient determination.

n Since triggering events for workflows are directly activated in Engineering Change Management,you do not need to carry out any event linkage in Customizing for Engineering Change Management.

Page 145: LO 980 engineering change mgmt

© SAP AG LO980 6-20

([HUFLVHV

8QLW��3URFHVVLQJ�&KDQJHV�ZLWK�:RUNIORZ7RSLF��6HW�XS�DQG�DSSOLFDWLRQ�RI�WKH�6$3�VWDQGDUGZRUNIORZAt the conclusion of this exercise, you will be able to:

• Process an ECR and ECO in its entire run per standardworkflow.

• Make all the necessary settings for change type and structureof a small organizational structure.

You are responsible for the installation of the standard workflowin your company. You use standard role 138 and anorganizational structure for the conversion.

1-1 Which workflow template is assigned to the change type �� in the�³'HILQH�FKDQJHW\SHV�IRU�FKDQJH�PDVWHU�UHFRUGV´?

_________

1-2 Is there a change type for your group in the ³'HILQH�FKDQJH�W\SHV�IRU�FKDQJHPDVWHU�UHFRUGV´ ?If yes, make a note of the change type. _________

If not, create a change type for your group that uses the WS 20000067 workflow._________

1-3 Which status profile is assigned to the change type ��LQ the�³'HILQH�FKDQJH�W\SHVIRU�REMHFWV´�?_________

1-4 Which change type in the “'HILQH�FKDQJH�W\SHV�IRU�REMHFWV” is created for yourgroup? _________(Compare the descriptions of the group number and the change type fordocuments.)

The following optional part of the exercise is complex and can take sometime. You practice the structure of a simple organizational structure andthe assignment of change types.

You can test the successful structure by creating a ECR and switching toyour inbox. You can now simulate central change centers andengineering/design departments.

Alternatively, the process of the workflow is demonstrated in the nextexercise.

Page 146: LO 980 engineering change mgmt

© SAP AG LO980 6-21

1-5 Create an organizational unit ³&HQWUDO���´. Assign a position ³&HQWUDO��´�to thisorganizational unit��description ³&HQWUDO�JURXS���” and use as the describedposition “3URGXFWLRQ”. Assign your user 3'0��� to the position.Maintain the 6$3�RUJDQL]DWLRQDO�REMHFW for the organizational unit with theorganization object type ³7&&��´�and assign this your change type from part 1-2.

1-6 Create an organizational unit ³/RFDO���´. Likewise, assign a position ³/RFDO��´�tothis organizational unit��description ³(QJLQHHULQJ�GHVLJQ�GHSDUWPHQW�JURXS���”and use as the described position “3URGXFWLRQ”. Assign your user 3'0��� to theposition.Maintain the 6$3�RUJDQL]DWLRQDO�REMHFW for the organizational unit with theorganizational object type ³7&&��´�and assign this your change type from part 1-3.

�RQO\�LQ�5HO�����&�DQG�RQO\�RSWLRQDO��*R�EDFN�WR�&XVWRPL]LQJ�RI�WKH�FKDQJH�W\SHV��&KDQJH�W\SH�IRU�PDVWHU�UHFRUGV��VHH�H[HUFLVH���������FKDQJH�WKH�ZRUNIORZ�WDVN�LQ�:6����������&KDQJH�W\SH�IRU�REMHFW�PDQDJHPHQW�UHFRUGV��VHH�H[HUFLVH���������FKDQJH�WKH�ZRUNIORZ�WDVN�LQ�:6���������

1-7 Create an ECR &����. Assign the change type for your group from part 1-2 (No. 50+ ##) in the header. Maintain any description and set the status active.

Maintain an object management record for the document7�)�����'5:������������Assign the change type for your group from part 1-3 (No.50 + ##) to the object management record in the detail view.

'R�QRW�FKDQJH�DQ\�V\VWHP�VWDWXVHV�Save the ECR.Goto your inbox and start the workflow for your ECR.

If you successfully released the ECR/ECO, you can skip the next task.

:HOO�GRQH�

Page 147: LO 980 engineering change mgmt

© SAP AG LO980 6-22

([HUFLVHV8QLW��3URFHVVLQJ�&KDQJHV�ZLWK�:RUNIORZ7RSLF��$SSOLFDWLRQ�RI�WKH�:RUNIORZ�7HPSODWH

At the conclusion of this exercise, you will be able to:

• Process an ECR and ECO in its entire run per standardworkflow.

In this exercise, the trainer and the participants simulate severaldepartments in a company. The trainer simulates the centralchange management, each participant simulates an affectedengineering/design department.

A prerequisite is that the company department has created anECR.

This exercise is meant as an alternative to parts 1-5 to 1-7 of the previousexercise.

(2-1) The trainer (= the responsible central change department) finds the task of definingthe corresponding objects to this ECR, in his integrated inbox. He assigns documentT-F4## DRW 000 00 and sets the request to &KHFN�UHTXHVW.

Each group is responsible for their document.

2-2 Switch to your integrated inbox!

There, you find the task to check your document 7�)���� that means to check thefeasibility of the changes.

Carry out the task. The corresponding object management record appears. Firstdisplay the document from the object management record.

Since you are of the opinion that the affected document can be changed, set thesystem status to &KDQJH�SRVVLEOH and save.

(2-3) The trainer (= the responsible central change department) now finds the task ofchecking the ECR, in his integrated inbox. In the header of the ECR, he sets thesystem statuses 5HTXHVW�FKHFNHG, $SSURYH�UHTXHVW and &RQYHUW�UHTXHVWdirectly after each other.

Page 148: LO 980 engineering change mgmt

© SAP AG LO980 6-23

2-4 After the trainer has done this (be patient!) you find, in your LQER[��DIWHU�D�UHIUHVK�the task of completing the change to your document 7�)���.

Carry out the task. The corresponding object management record appears. Changethe document from the object management record. Change the status of &+ to 5/.In so doing, copy the reserved change number.Which revision level was assigned when saving? _____________

Make sure that in the object management record, the status &RPSOHWH�FKDQJH hasbeen set, release the changes and save.

(2-5) The trainer (= the responsible central change department) now finds the task ofcompleting the ECR, in his integrated inbox.

Page 149: LO 980 engineering change mgmt

© SAP AG LO980 6-24

�6ROXWLRQV

8QLW��3URFHVVLQJ�&KDQJHV�ZLWK�:RUNIORZ7RSLF��6HW�XS�DQG�DSSOLFDWLRQ�RI�WKH�6$3�VWDQGDUGZRUNIORZ

1-1 Use the SAP menu and choose7RROV�→�$FFHOHUDWHG�6$3�→�&XVWRPL]LQJ�→�(GLW�SURMHFWCopy transaction 6352 to your favorites (right mouse button)

Go to 6$3�5HIHUHQFH�,0*��RU�)���Choose

/RJLVWLFV��*HQHUDO�→�(QJLQ��FKDQJH�PJPW�→�&KDQJH�W\SH�→'HILQH�FKDQJH�W\SHV�IRU�FKDQJH�PDVWHU�UHFRUGV�H[HFXWH�Õ Workflow template: WS 20000067

1-2 Between 51 and 70.(Group number + 50)

1-3 … → 'HILQH�FKDQJH�W\SHV�IRU�REMHFWVÕ Status profile: PP000005

1-4 Between 51 and 70

1-5 Go back to the SAP basic menu and choose7RROV�→�%XVLQHVV�:RUNIORZ�→�'HYHORSPHQW�→�'HILQLWLRQ�WRROV�→2UJDQL]DWLRQDO�PDQDJHPHQW�→�2UJDQL]DWLRQDO�SODQ�→�&UHDWHto go to the organizational management.Copy this transaction �5HO����F��332&:��5HO����E��332&� to your favorites list(right mouse button).

Do not change the dialog box relating to the effectivity period.(Valid from: TodayValid-to: 31.12.9999)

Overwrite bottom right:New Org. unit with: &HQWUDO�����New organizational unit with: &HQWUDO�JURXS���Goto the top right, to the first button on the left ("Goto") and choose �6WDIIDVVLJQPHQWV��OLVW��.

Page 150: LO 980 engineering change mgmt

© SAP AG LO980 6-25

Goto the top right, to the second button on the left �³&UHDWH�SRVLWLRQ´�.

Call up the detail screen for the entry of a new position by double-clicking top righton the table entry�1HZ�SRVLWLRQ�.In the detail screen (bottom right) enter:Position: &HQWUDO��Description &HQWUDO�JURXS���(described) job: 3URGXFWLRQ (via F4 help with

search term: Production)

Now you have to occupy this job with your user.Goto the top left, to find by the line User.Enter 3'0 as a search string.�,Q�5HOHDVH����&� Move your user 3'0��� using Drag & Drop from bottom left,to top right into the first line of the table in the column "Employee of …"��LQ�5HO�����E� Drag your user 3'0��� using Drag & Drop from bottom left fromsearch results to the list holder bottom right�Save.

Now the corresponding change type is assigned to your organizational unit.

Go back to the SAP basic menu and choose7RROV�→�%XVLQHVV�:RUNIORZ�→�'HYHORSPHQW�→�'HILQLWLRQ�WRROV�→2UJDQL]DWLRQDO�PDQDJHPHQW→�6$3�2UJ��2EMHFWV�→�&UHDWH�$VVLJQPHQWVto go to the corresponding transaction.Copy transaction 3)20 to your favorites (right mouse button).

Look for your organizational unit using the F4 help with the search string FHQWUDO Leave the radio button on 2UJDQL]DWLRQDO�REMHFW�W\SH and enter 7&&��.

Click �FKDQJH�.Place the cursor on the organizational unit (blue entry) and then click �&UHDWH� )���Enter your FKDQJH�W\SH here.( Group number + 50)

�RSWLRQDO�SRLQW�IRU�5HO�����F�Change types for master records: For menu path, see 1-1 or transaction OS56. Herechange the workflow task (…754) and save.Change types for object management record: For menu path, see 1-3 or transactionOS58. Here change the workflow task (…748) and save.

Page 151: LO 980 engineering change mgmt

© SAP AG LO980 6-26

1-6 Repeat the steps 1-5 with the data from the tasks.

Org.unit: Local-##Description: Engineering/design department group ##

Position: Local##Description: Engineering/design department group ##Job: Production

Holder: PDM-##

Org.object type: TCC13Change type: As according to exercise 1-4

(Group number + 50)

1-7 (Compare to creating the ECR point 1-1, the solution of the exercise for the unitECR/ECO)

In the user menu, goto(QJLQ��FKDQJH�PJPW�→�&KDQJH�1XPEHU�→�&UHDWH

In the initial screen enter:

Change no.: &����Type: (&5Change type: �����*URXS�QXPEHU (see exercise 1-2)

Rest unchanged

The change header appears. Enter text and status 01 here. The rest remainsunchanged.

After a data release, or by clicking on ‘2EMHFW�W\SHV’ the object types overviewappears. Keep the suggested selections in the line document, and delete theindicator in the other lines.

By clicking on �2EMHFWV� �)���the object overview appears.

Here enter the given document on the tabpage 'RFXPHQW�2YHUYLHZ.

7�)����'5:�������

Go to the Detail screen (= Jigsaw button) and set your change type.'R�QRW�VHW�DQ\�VWDWXVHV��After saving the ECR, go back to the SAP menu.

2IILFH�→�:RUN�SODFH,QER[�→ :RUNIORZYou should find you ECR again here.

Execute the task(Double-click in the field in the 1. column "Ex… ").Set the status “ Check request” and save.

%XWWRQ��8SGDWH

Page 152: LO 980 engineering change mgmt

© SAP AG LO980 6-27

Execute the task ‘Distribute object entry...’(Double-click in the field in the 1. column "Ex… "). Click “ Continue checking the request” .

Carry out the task "ECR C##-6 Object … " and in the ECR in the objectmanagement record, set the system status “&KHFN�SRVVLEOH” , then save.

%XWWRQ��8SGDWHCarry out the task ‘ECR: C##-6 can be checked” .Next confirm the status report.Set the statuses ‘5HTXHVW�FKHFNHG’, ‘$SSURYH�UHTXHVW’ ‘&RQYHUW�UHTXHVW’. Go backto the object management record. Enter a date (today + 3 months) and save.

%XWWRQ��8SGDWHCarry out the task ‘ECR C##-6: Object...’.From the object management record, call up the document info record using thecorresponding button.Set the status from CH (checked) to RL (released). Confirm the log field window.As a result of the system setting, a revision level is assigned and the status“&RPSOHWH�FKDQJH” is set automatically in the object management record.Go back (F3) and set the status “5HOHDVH�FKDQJH” in the object management record,continue and save.

%XWWRQ��8SGDWHCarry out the task ‘ECO: C##-6 can be completed” . Set the statuses “ CompleteECO” “ Release ECO” and save the ECO.

%XWWRQ��8SGDWHConsequently, your ECR/ECO is processed and has disappeared from your inbox.

&RQJUDWXODWLRQV��

Page 153: LO 980 engineering change mgmt

© SAP AG LO980 6-28

6ROXWLRQV8QLW��3URFHVVLQJ�&KDQJHV�ZLWK�:RUNIORZ7RSLF��$SSOLFDWLRQ�RI�WKH�:RUNIORZ�7HPSODWH

(2-1) The trainer is working – please be patient.

2-2 Goto the SAP menu and choose:

2IILFH�→�:RUN�SODFH,QER[�→ :RUNIORZ

In your integrated inbox, you find the task of checking your document object DRWT-F4## … (the feasibility of the changes):

Execute the task(Double-click in the field in the 1. column "Ex… ")

If necessary, confirm in the corresponding Work item that you want to proceed withchecking the ECR.

The corresponding object management record appears. Select ‘Display Document', in order to check

document T-F4## DRW 000 00.

Go back to the detail screen and set the system status µ&KDQJH�SRVVLEOH¶, byclicking µ6HW�VWDWXV¶ and clicking on the corresponding button in the dialog box.

Save the ECR.

(2-3) The trainer is working – please be patient.

Page 154: LO 980 engineering change mgmt

© SAP AG LO980 6-29

2-4 After the trainer has done this you find, in your inbox,�after an XSGDWH� the task ofclosing the change to your document T-F4##.

Execute the task(Double-click in the field in the 1. column "Ex… ").

The corresponding object management record appears. There, select &KDQJHGRFXPHQW, in order to change the statusin document T-F4## DRW 000 00.Copy the reserved change number and save.

The UHYLVLRQ�OHYHO�01 is assigned.

Go back to the detail screen of the object management record and make sure thatthe status &RPSOHWH�FKDQJH has been set there (Button 6HW�VWDWXV ). Release yourobject management record.

Save the ECR.

The task is now finished for you.

(2.5) The trainer completes the ECO and releases it.

Page 155: LO 980 engineering change mgmt

© SAP AG LO980 7-1

SAP AG 1999

l &KDQJH�+LHUDUFK\l 5HOHDVH�NH\l 3DUDPHWHU�HIIHFWLYLWLHV��HIIHFWLYLW\�SDUDPHWHU��HIIHFWLYLW\

W\SHVl 8VDJH�DQG�UHODWLRQVKLS�ZLWK�QHZ�IXQFWLRQDOLWLHV

&RQWHQWV�

&KDQJH�+LHUDUFK\��5HOHDVH�.H\��3DUDPHWHU(IIHFWLYLW\

Page 156: LO 980 engineering change mgmt

© SAP AG LO980 7-2

SAP AG 1999

l 6HW�XS�FKDQJH�KLHUDUFKLHVl 8VH�WKH�UHOHDVH�NH\l &RQWURO�WKH�UHOHDVH�RI�FKDQJH�KLHUDUFKLHVl 8VH�HIIHFWLYLW\�W\SHV�ZLWK�QHZ�HIIHFWLYLW\

SDUDPHWHUV�IRU�WKH�OLQNHG�REMHFWV�LQ�FKDQJHQXPEHUV

l 0DNH�WKH�QHFHVVDU\�VHWWLQJV�LQ�&XVWRPL]LQJ�WR�EHDEOH�WR�XVH�WKLV�IXQFWLRQDOLW\

$W�WKH�FRQFOXVLRQ�RI�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�

&KDQJH�+LHUDUFK\��5HOHDVH�.H\��������7RSLF2EMHFWLYHV

Page 157: LO 980 engineering change mgmt

© SAP AG LO980 7-3

SAP AG 1999

&RXUVH�2YHUYLHZ�'LDJUDP

2EMHFW�&KDQJHV2EMHFW�&KDQJHV ��

5HSRUWLQJ5HSRUWLQJ ��

�� ��&KDQJH�0DVWHU�5HFRUG&KDQJH�0DVWHU�5HFRUG

3URFHVVLQJ�&KDQJHV�3URFHVVLQJ�&KDQJHV�ZLWK�:RUNIORZZLWK�:RUNIORZ ��&RXUVH�2YHUYLHZ&RXUVH�2YHUYLHZ ��

(&5���(&2(&5���(&2 ��

6XPPDU\6XPPDU\ ��

2UGHU�&KDQJH2UGHU�&KDQJH0DQDJHPHQW��2&0�0DQDJHPHQW��2&0� ��

&KDQJH�+LHUDUFK\��&KDQJH�+LHUDUFK\��5HOHDVH�3DUDPHWHU��5HOHDVH�3DUDPHWHU��3DUDPHWHU�(IIHFWLYLW\�3DUDPHWHU�(IIHFWLYLW\�

Page 158: LO 980 engineering change mgmt

© SAP AG LO980 7-4

SAP AG 1999

l 7KH�FHQWUDO�(&0�ZDQWV�WR�XVH�DGGLWLRQDOIXQFWLRQDOLW\�LQ�WKH�FKDQJH�SURFHVVHV�� 7KHUHIRUH�VHYHUDO�FKDQJHV�VKRXOG�EH�FXPXODWHG

VWUXFWXUDOO\�� 7KH�LQFOXVLRQ�RI�VFKHGXOHG�FKDQJHV�LQWR�WKH

ORJLVWLFV�SURFHVV��VKRXOG�EH�FRQWUROOHG�DQGJUDGXDO�

� 7KH�LQFOXVLRQ�RI�FKDQJHV�VKRXOG�QRW�MXVW�EHFRQWUROOHG�E\�WKH�HIIHFWLYLW\�GDWH��$GGLWLRQDOSDUDPHWHUV�VKRXOG�UHIOHFW�WKHVH�GHSHQGHQFLHV�

&KDQJH�+LHUDUFK\��5HOHDVH�.H\��������%XVLQHVV6FHQDULR

n A change hierarchy consists of a leading change master record (change leader), change packages,and the assigned objects.

Page 159: LO 980 engineering change mgmt

© SAP AG LO980 7-5

SAP AG 1999

&KDQJH�OHDGHU

&KDQJH�SDFNDJHV

2EMHFW�OHYHOV

&KDQJH�+LHUDUFK\���6WUXFWXUH

l 7KH�FKDQJH�QXPEHU�KLHUDUFK\

n As of Release 4.0 you have the option to structure complex product changes transparently and in aneasily understandable way, from different views (such as organizational and functional) with thehierarchy of the change master records.

n A hierarchy is made up from change master records with the functions Change leader and Changepackage.

n The &KDQJH�OHDGHU is the superior change master record in a hierarchy, which cumulates severalsubordinate change packages. Important control functions that are valid for all assigned changepackages, are maintained in a change leader.

n The &KDQJH�SDFNDJH is the subordinate change master record or ECR/ECO in a hierarchy. Theprocessing of the objects (such as BOMs) is done with reference to change packages.

n For this, the objects to be processed are assigned to individual change packages. At the same time, afunctional outline is useful.

Page 160: LO 980 engineering change mgmt

© SAP AG LO980 7-6

SAP AG 1999

&KDQJH�+LHUDUFK\���)XQFWLRQDOLW\

� Workflow� System status� User status� Technical release� Object mgmt records� Deletion flag (local)

3DFNDJHV�FRQWUROOHG�XVLQJ�� Effectivity types� Release indicator� Deletion flag (global)&KDQJH�SDFNDJH�$&KDQJH�SDFNDJH�$&KDQJH�SDFNDJH�$

&KDQJH�OHDGHU&KDQJH�OHDGHU&KDQJH�OHDGHU

&KDQJH�SDFNDJH�%&KDQJH�SDFNDJH�%&KDQJH�SDFNDJH�%

&KDQJH�SDFNDJH�&&KDQJH�SDFNDJH�&&KDQJH�SDFNDJH�&

l )XQFWLRQ�RI�WKH�KLHUDUFK\�OHYHOV

n On the one hand, complex product changes can be clearly structured and controlled with a changemaster record hierarchy and on the other hand, can be copied as a logical unit into an operative area.

n An important attribute of the change hierarchy is the option to define different, organization-specificchange processes on the change package level, using status management and the integratedWorkflow. Some control elements of the change leader are maintained centrally for the entirehierarchy.

Page 161: LO 980 engineering change mgmt

© SAP AG LO980 7-7

SAP AG 1999

5HOHDVH�.H\��2YHUYLHZ

:RUNLQJ�ZLWKRXW�WKH�UHOHDVH�NH\�&KDQJHV�WKDW�DUH�PDLQWDLQHG�ZLWK�FKDQJH�QXPEHUV�ZLWKRXW�WKH�UHOHDVH�NH\�DUH�HIIHFWLYH�LPPHGLDWHO\�SURYLGHG�WKH�HIIHFWLYLW\�FRQGLWLRQVDUH�PHW��

:RUNLQJ�ZLWKRXW�WKH�UHOHDVH�NH\�&KDQJHV�WKDW�DUH�PDLQWDLQHG�ZLWK�FKDQJH�QXPEHUV�ZLWKRXW�WKH�UHOHDVH�NH\�DUH�HIIHFWLYH�LPPHGLDWHO\�SURYLGHG�WKH�HIIHFWLYLW\�FRQGLWLRQVDUH�PHW��

:RUNLQJ�ZLWK�WKH�UHOHDVH�NH\�$ORQJVLGH�WKH�HIIHFWLYLW\�FRQGLWLRQV�TXHU\��PDLQWDLQHG�FKDQJHV�LQ�WKH�XVHG�GDWD�DUH�RQO\�LQFOXGHG�ZLWK�FKDQJH�QXPEHUV�LQ�WKH�ORJLVWLFV�FKDLQ�SURFHVVHV�LI�WKHVH�FKDQJHV�DUH�DOUHDG\�UHOHDVHG�IRU�WKLV�SURFHVV�

:RUNLQJ�ZLWK�WKH�UHOHDVH�NH\�LV�RSWLRQDO��H[FHSW�LQ�FKDQJH�KLHUDUFKLHV�

:RUNLQJ�ZLWK�WKH�UHOHDVH�NH\�$ORQJVLGH�WKH�HIIHFWLYLW\�FRQGLWLRQV�TXHU\��PDLQWDLQHG�FKDQJHV�LQ�WKH�XVHG�GDWD�DUH�RQO\�LQFOXGHG�ZLWK�FKDQJH�QXPEHUV�LQ�WKH�ORJLVWLFV�FKDLQ�SURFHVVHV�LI�WKHVH�FKDQJHV�DUH�DOUHDG\�UHOHDVHG�IRU�WKLV�SURFHVV�

:RUNLQJ�ZLWK�WKH�UHOHDVH�NH\�LV�RSWLRQDO��H[FHSW�LQ�FKDQJH�KLHUDUFKLHV�

,Q�WKH�FKDQJH�PDVWHU�UHFRUG�WKH�UHOHDVH�NH\�FRQWUROV�WKH�UHOHDVHRI�REMHFW�FKDQJHV�IRU�YDULRXV�DUHDV�LQ�WKH�FRPSDQ\�$W�D�VSHFLILF�WLPH��\RX�FDQ�HLWKHU�UHOHDVH�FKDQJHV�JOREDOO\�RUIRU�LQGLYLGXDO�DUHDV�RI�WKH�FRPSDQ\��VXFK�DV�FRVWLQJ��SODQQLQJ�RUSURGXFWLRQ��

,Q�WKH�FKDQJH�PDVWHU�UHFRUG�WKH�UHOHDVH�NH\�FRQWUROV�WKH�UHOHDVHRI�REMHFW�FKDQJHV�IRU�YDULRXV�DUHDV�LQ�WKH�FRPSDQ\�$W�D�VSHFLILF�WLPH��\RX�FDQ�HLWKHU�UHOHDVH�FKDQJHV�JOREDOO\�RUIRU�LQGLYLGXDO�DUHDV�RI�WKH�FRPSDQ\��VXFK�DV�FRVWLQJ��SODQQLQJ�RUSURGXFWLRQ��

n The release key controls the release procedure for successive work areas (for example, production).The function of the release key has been available since Release 4.0. However, in Release 4.0 onlyglobal release was possible.

n Changes with a release key do not take effect until the effectivity conditions are met and the releasekey is set.

Page 162: LO 980 engineering change mgmt

© SAP AG LO980 7-8

SAP AG 1999

���

%20

5RXWLQJ

&KDUDF�&ODVVLILFDWLRQ

&KDQJH

l )RU�DOO�DUHDV�RI�WKH�FRPSDQ\l )RU�LQGLYLGXDO�DUHDV�RI�WKH�FRPSDQ\

5HOHDVH�.H\���3URFHVV�6SHFLILF�5HOHDVH

2SHUDWLYH�DUHDV�l 6DOHV�DQG�0DUNHWLQJ

�VDOHV�RUGHU��SODQQHGLQGHSHQGHQWUHTXLUHPHQW�

l 3URGXFWLRQ�SODQQLQJ�053�UXQ��SODQQHGRUGHUV�

l 3URGXFWLRQ�FRQWURO�SURGXFWLRQ�RUGHU�

l &RVWLQJ��SURGXFWFRVWLQJ�

n Release for company area:

You can define a release key that enables a special release for the following areas:

• Costing

• Planning

• Production

• Simulation for production

With this indicator you can control that changes are also taken into consideration in the simulationfor the production. This simulation enables you to check new developments or changes in simulationorders for the production. For example, you have early control over whether all changed data (suchas BOM, task list, ...) goes together.

Simulative production orders are also used in OCM.

n Processing a change master record after release:

In Customizing, using the control data, you can determine whether change numbers that are alreadyreleased for one or more areas, should be locked. Then after the lock, you can process the releasekey and the deletion flag.

Page 163: LO 980 engineering change mgmt

© SAP AG LO980 7-9

SAP AG 1999

'HILQLWLRQ�RI�WKH�5HOHDVH�.H\

5HO'DWH5HO2&05HO*ORE5HO3URG5HO3ODQ5HO&RVW5HO6LP5HO.H\

,Q�WKH�FRQWURO�GDWD���6HW�WKH�XVDJH�RI�WKH�UHOHDVH�NH\�WR�DFWLYH��/RFN�WKH�FKDQJH�QXPEHU�IRU�WKH�LPSOHPHQWDWLRQ�RI�DGGLWLRQDO�FKDQJHV���LI�DOUHDG\�UHOHDVHG�IRU

��&RVWLQJ��3ODQQLQJ��3URGXFWLRQ��*OREDO�

n 5HO6LP� Indicator that controls that changes are also taken into consideration in the simulation forthe production. This simulation enables you to check new developments or changes in the simulationorders for production to see whether all changed data (such as BOM, task list or document) gotogether.

n 5HO&RVW� Indicator that controls that the changes in costing are taken into consideration.

n 5HO3ODQ� Indicator that controls that the changes in planning are taken into consideration.

n 5HO3URG� Indicator that controls that the changes in production are taken into consideration. Changescan only be taken into consideration in production if the changes in the planning are taken intoconsideration at the same time. Therefore, also set the release indicator for planning. For a releasekey that releases the changes for the production, you also have to set the indicator release forsimulation.

n 5HO*ORE� Indicator that controls that change master records for all areas of the company are released.If you set this indicator, then the changes for all areas are released automatically. Therefore do notenter any more indicators.

n 5HO2&0� Indicator that controls that for basic data changes with this release key, a change flag isautomatically created for the order change process. The change flag triggers the change process andmanages the change activities.

n 5HO'DWH� Indicator that controls that during date shifting, a change flag is automatically created forthe order change process.

Page 164: LO 980 engineering change mgmt

© SAP AG LO980 7-10

SAP AG 1999

5HOHDVH�.H\�LQ�+LHUDUFKLHV

&KDQJH�OHDGHU

&KDQJH�SDFNDJHV

2EMHFW�OHYHOV

2QO\�ZKHQ�DOO�FKDQJHSDFNDJHV�DUH��WHFKQLFDOO\��UHOHDVHG��FDQ�WKH�FKDQJH�OHDGHU�EH�UHOHDVHG�IRU�SURGXFWLRQ�RU�JOREDOO\

([FHSWLRQ��³/DWH�SDFNDJHV�DOORZHG³

n If you want to release a change leader, then all subordinated change packages have to be technicallyreleased. This dependency, however, only applies for global release and release for the production.

n If this indicator is set, it cannot be revoked.

n You can only process an object with reference to a package that is not technically released.

n Release of the change leader without released packages:

In the standard system, you cannot add additional packages after the release of change leader for theproduction. However, you can add late packages or use packages that are not technically released, ifthe ’ODWH�SDFNDJHV�indicator is set in the ’&RQWURO�GDWD�ZRUN�VWHS.

n You can always define the changes to a hierarchy whose change leader defines the effectivity usingthe 9DOLG�IURP date, as a valid basis change. All changes to this change hierarchy are always viewedas valid, irrespective of the 9DOLG�IURP date. However, for this leader no additional late packages arepossible.

n If an ECR is included in the hierarchy, then the technical release is carried out automatically by thesystem provided the system status has been set to ’5HOHDVH�RUGHU’.

Page 165: LO 980 engineering change mgmt

© SAP AG LO980 7-11

SAP AG 1999

���

����� �� �� ��� ����� ��� � � ����� ��� ��� ��� ��������� ���� ����� � ���� � �! � ������� � �

" ��� ��# ���$� � �%� � � & � ��� � ��'" �������� ()���*�� ���*+����$�" ����������(,���� -�-�-

7UDQVIHU�WR�2SHUDWLYH�$UHDV

(&5 2&0

n The best change process, whether flexible using the Workflow, or direct using the approvalprocesses given, is useless, if you do not convert the planned changes. For example, this can be thecase if sales orders or projects that are affected by changes are already planned in the production andare converted in production orders. The R/3 System 2rder &hange 0anagement (OCM) tool cansort this out. It enables product structures to be converted into production structures and processes atthe earliest time necessary using MRP and also for them to be changed at the last possible moment. Itis also possible to adapt processed production orders to the changed product structure. The changescan either be initiated by a changed customer requirement or by a design change using an ECR.

Page 166: LO 980 engineering change mgmt

© SAP AG LO980 7-12

SAP AG 1999

l (IIHFWLYLW\�SDUDPHWHUl (IIHFWLYLW\�W\SHVl /LQNHG�REMHFWVl $SSOLFDWLRQ�DUHDVl ,QWHUUHODWLRQ�RI�YDULRXV�FKDQJH�QXPEHUV�

5HOHDVH�NH\3ULRULWLHV5DQN&UHDWLRQ�GDWH

2YHUYLHZ��(IIHFWLYLW\�3DUDPHWHUV

Page 167: LO 980 engineering change mgmt

© SAP AG LO980 7-13

SAP AG 1999

2YHUYLHZ�RI�1HZ�(IIHFWLYLW\�3DUDPHWHUV

> � @# 4711 # 4712 # 4713

. /*0 1�2

/ +

� � ��

:KLFK�HIIHFWLYLW\�SDUDPHWHUV�DUH�DYDLODEOH�"3 DATE �VWDQGDUG��DV�D�VLQJOH�YDOXH�RU�DV�DQ�LQWHUYDO�

4 RSHQ�RU4 FRPSOHWHG

3 SERIAL NUMBER �VWDQGDUG��DV�D�VLQJOH�YDOXH�RU�DV�DQ�LQWHUYDO�4 RSHQ�RU4 FRPSOHWHG

3 MATERIAL NUMBER �VWDQGDUG��DV�D�VLQJOH�YDOXH

3 company-specific defined effectivity parameters �IUHHO\�GHILQDEOH�VXFK�DV�

4 &86720(54 6(48(1&(��OLQH�RI�SURGXFWV�4 02'(/4 9(56,21�������

n In the standard, the effectivity of changes maintained with change numbers is determined by the’YDOLG�IURP�GDWH.

n In the R/3 System, you have the option to fix the effectivity of change numbers to other effectivityparameters.

These effectivity parameters can therefore be valuated not only by maintaining change numbers butalso by the use of objects that are processed with such numbers

n In the R/3 System the effectivity parameters 7LPH�LQWHUYDO��'$7(�� 6HULDO�QXPEHU�LQWHUYDO��6(5�12�DQG�0DWHULDO�QXPEHU��0$715� are defined as standard. In addition, other company-specificeffectivity types can be defined.

n The following information has to be defined for each effectivity parameter in Customizing::

é Name of the effectivity parameter

é Data element: contains data type (such as character format CHAR), number of characters, outputlength

(such as always 18)

é Parameter type: S = Individual valueI = closed interval or individual valueO = open interval or individual value

é Description, check tables, sorting in the value assignment screen,

Page 168: LO 980 engineering change mgmt

© SAP AG LO980 7-14

SAP AG 1999

2YHUYLHZ�RI�1HZ�(IIHFWLYLW\�7\SHV(IIHFWLYLW\�W\SHV�3 DATE

defined byparameter:

DATE3 SERIAL NUMBER

defined byparameter:

SERIAL NUMBER,MATERIAL NUMBER

3 company-specificdefinedeffectivity types

(IIHFWLYLW\�W\SHV�DUH�GHILQHG�XVLQJ�WKH�SUHYLRXVO\�GHILQHG�HIIHFWLYLW\SDUDPHWHUV�)RU�WKH�HIIHFWLYLW\�W\SHV��WKH�

'HVFULSWLRQV�DQG�WKH�3ULRULW\�DUH�GHILQHG�

(IIHFWLYLW\�SDUDPHWHU�3 DATE3 SERIAL NUMBER3 MATERIAL NUMBER3 company-specific

defined effectivity parameter

n In the R/3 System the effectivity types 7LPH�LQWHUYDO��'$7(�� and 6HULDO�QXPEHU�LQWHUYDO��6(5�12�are defined as standard. In addition, other company-specific effectivity types can be defined.

n With the effectivity type 7LPH�LQWHUYDO��'$7(� you can control object changes, which, for example,due to the season are only valid for a certain period of time.

n With the effectivity type 6HULDO�QXPEHU�LQWHUYDO��6(5�12� you can control object change statusesindependently of the serial number of a product.The effectivity type 6HULDO�QXPEHU�LQWHUYDO uses the parameter combination 0DWHULDO (individualvalue) and 6HULDO�QXPEHU (open interval).

n Since it is practically impossible to establish all imaginable variants of effectivity types in respect tostandard software, the option exists in Customizing Engineering Change Management to determineother effectivity types with freely definable parameters.

Page 169: LO 980 engineering change mgmt

© SAP AG LO980 7-15

SAP AG 1999

2EMHFWLYH2EMHFWLYH

%LOO�RI�PDWHULDO5RXWLQJ

&KDUDFWHULVWLFV�RI�FODVV&ODVVLILFDWLRQ

���

������

,QWHJUDWLRQ�RI�DOO�WKH�REMHFWV�OLQNHG�WROLQNHG�2EMHFWV,QWHJUDWLRQ�RI�DOO�WKH�REMHFWV�OLQNHG�WROLQNHG�2EMHFWV

(IIHFWLYLW\�3DUDPHWHUV�/LQNHG�2EMHFWV

5HIHUHQFH�RSHUDWLRQ�VHW&KDUDFWHULVWLF

������RQO\�ZLWK�(:%������RQO\�ZLWK�(:%���

l )RU�ZKLFK�REMHFWV�LV�D�FKDQJH�RU�QHZ�HIIHFWLYLW\�W\SH�SRVVLEOH�"

n As of Release 4.0 BOMs in all forms can be processed.

n As of Release 4.5 both the change objects and the application areas have been enhanced in that neweffectivity parameters can be used.

Page 170: LO 980 engineering change mgmt

© SAP AG LO980 7-16

SAP AG 1999

2EMHFWLYH2EMHFWLYH

(QJLQHHULQJ�GHVLJQ3ODQQLQJ3URGXFWLRQ6LPXODWLRQ�IRU�SURGXFWLRQ��������������������������������������������������

���

&RVWLQJ��������������������������������������������������������������

���������

���

&RPSOHWH�LQWHJUDWLRQ�LQWR�DOO�SURFHVVHVRI�WKH�ORJLVWLFV�FKDLQ&RPSOHWH�LQWHJUDWLRQ�LQWR�DOO�SURFHVVHVRI�WKH�ORJLVWLFV�FKDLQ

(IIHFWLYLW\�3DUDPHWHUV���/LQNHG�3URFHVVHV

l ,Q�ZKLFK�DSSOLFDWLRQV�DUH�FKDQJHV�WR�QHZ�HIIHFWLYLW\�W\SHVWDNHQ�LQWR�FRQVLGHUDWLRQ"

Page 171: LO 980 engineering change mgmt

© SAP AG LO980 7-17

SAP AG 1999

3URGXFW�&KDQJHV�ZLWK�3DUDPHWHU�(IIHFWLYLW\

3XPS

��0DWHULDO�PDVWHU�UHFRUG�����HYDOXDWH�HIIHFWLYLW\

&KDQJHVWR

%205RXWLQJ

&ODVVLILFDWLRQ�V\VWHP

&KDQJHQXPEHU1��

&KDQJHQXPEHU1��

'$7('$7(

6HULDO�QXPEHU6HULDO�QXPEHU

n If you want to use parameter effectivity for changes to these products, specify this in the materialmaster in the basic data.

n Note the following when maintaining BOMs, routings and the objects in the classification system:

é Routings can only be processed with parameter effectivity in the Engineering Workbench. Historyrequirements exist here.

é For the objects in the classification system, it is necessary to enter the maintenance value in thedefinition of the change number. This then precisely defines for which development status thechanges with parameter effectivity are set.

é For maintaining the class characteristics and classification the ECM with parameter effectivity isactivated as class type-specific in Customizing.For class types that have not been newly created the report RCLAUSPT must first run.

Page 172: LO 980 engineering change mgmt

© SAP AG LO980 7-18

SAP AG 1999

3DUDPHWHU�(IIHFWLYLW\�LQ�WKH�/RJLVWLFV�&KDLQ576 8:9 ; 8�<�=>=�?%?%=A@�<CB 6DB <FEHGA87I%8�JK=�<%=LI

'DWH0DWHULDO6HULDO�QXPEHU

6WDQGDUG�YDOXDWLRQ

5HOHDVH�IRU�SURGXFWLRQ����������������������&RVWLQJ��������������������������������������������������������������

������3ODQQLQJ������6LPXODWLRQ(QJLQHHULQJ�GHVLJQ

�0DVWHU�GDWD�PDLQWHQDQFH�UHSRUWLQJ�

6DOHV�VDOHV�RUGHU� 3ODQQLQJ

�053��3ODQQHG�RUGHU�

3URGXFWLRQ�SURGXFWLRQ�RUGHU�

n For the explosion of master data, information is required that determines which changes to parameterdependencies should be included here. In general this takes place using the value assignment of theeffectivity parameter. However, you also have the option to overwrite these entries directly using thechange numbers.

Page 173: LO 980 engineering change mgmt

© SAP AG LO980 7-19

SAP AG 1999

:KLFK�&KDQJHV�+DYH�7R�%H�0DGH�"

3XPS

&KDQJHPDVWHU�UHFRUG1��

M N OHPQ=L9 =�8�RA=KS =�ETRA=�<:N7U V�<7RA=�<DW

&KDQJHPDVWHU�UHFRUG1��

&KDQJHPDVWHU�UHFRUG1��

&KDQJHPDVWHU�UHFRUG1��

&KDQJHPDVWHU�UHFRUG1��

6HULDO�QXPEHU�6HULDO�QXPEHU�

6HULDO�QXPEHU�6HULDO�

QXPEHU�

""

&KDQJHPDVWHU�UHFRUG1��

&KDQJHPDVWHU�UHFRUG1��

'$7('$7(

'$7('$7(

n Various change numbers can refer to the same object. For the new ECM control elements (releasekey, parameter effectivity), new tools for the correct explosion of the relevant objects also have toexist

Page 174: LO 980 engineering change mgmt

© SAP AG LO980 7-20

SAP AG 1999

���(YDOXDWLRQ�RI�WKH�5HOHDVH�.H\

3XPS

&KDQJHPDVWHU�UHFRUG1��

&KDQJHPDVWHU�UHFRUG1��

&KDQJHPDVWHU�UHFRUG1��

&KDQJHPDVWHU�UHFRUG1��

6HULDO�QXPEHU�6HULDO�

QXPEHU�

""

n If you work without a release key, then all changes become active immediately after maintenance.This means that all the changes flow into the object immediately.

n If you work with the release key, then the changes only become active for the desired applicationwhen you specifically release them for the relevant application using the release key. Theconsideration of the effectivities is carried out analogous to the above.

n You can see which changes have ultimately been included when we look at the next slides.

Page 175: LO 980 engineering change mgmt

© SAP AG LO980 7-21

SAP AG 1999

l $IWHU�WKH�DFWLYH�FKDQJHV�KDYH�EHHQ�ILOWHUHG�RXW�DFFRUGLQJWR�WKH�UHOHDVH�NH\��WKHQ�WKH�SULRULW\�RI�FKDQJHV�ZLWKGLIIHUHQW�HIIHFWLYLW\�W\SHV�LV�HYDOXDWHG�

���3ULRULW\�RI�WKH�(IIHFWLYLW\�7\SHV

&KDQJH�PDVWHU�UHFRUG1��

&KDQJH�PDVWHU�UHFRUG1��

6HULDO�QXPEHU�6HULDO�

QXPEHU�

&KDQJH�PDVWHU�UHFRUG1��

'$7('$7(&KDQJH�PDVWHU�UHFRUG1��

������

(II��W\SH 3ULRULW\

'$7( ��

6(5�12� ��

« ��

�ROG�YDOLG�IURPKDV�ORZHVW�SULR��

(II��W\SH 3ULRULW\

'$7( ��

6(5�12� ��

« ��

�ROG�YDOLG�IURPKDV�ORZHVW�SULR��

n After the active changes have been filtered out for the relevant object, then we have to ask ourselveswhich change number we have to take into consideration.

n The release key GLIIHUHQW�FKDQJH�W\SH�decides the SULRULW\�of the change type for active changenumbers. The priority is a required entry for the definition of the change type in Customizing.

Page 176: LO 980 engineering change mgmt

© SAP AG LO980 7-22

SAP AG 1999

l 2QFH�WKH�FKDQJH�QXPEHUV�KDYH�EHHQ�ILOWHUHG�DFFRUGLQJ�WRWKH�UHOHDVH�NH\�DQG�WKH�HIIHFWLYLW\�W\SH��\RX�KDYH�WRHYDOXDWH�WKH�UDQN�RI�WKH�FKDQJH�QXPEHU�

���5DQN�RI�WKH�&KDQJH�1XPEHUV

&KDQJH�PDVWHU�UHFRUG1��

&KDQJH�PDVWHU�UHFRUG1��

&KDQJH�PDVWHU�UHFRUG1��

&KDQJH�PDVWHU�UHFRUG1��

5DQN��� 5DQN���

(IIHFWLYLW\�

����������5DQN�DFWLYH

(IIHFWLYLW\�

����������5DQN�DFWLYH

5DQN���

5DQN���

n For active changes with WKH�VDPH�HIIHFWLYLW\�W\SH�the ranks of the individual change numbers areevaluated.

n If you do not work with ranks or if you use one rank often, then proceed to the next slide.

Page 177: LO 980 engineering change mgmt

© SAP AG LO980 7-23

SAP AG 1999

2QFH�WKH�FKDQJH�QXPEHUV�KDYH�EHHQ�HYDOXDWHG�DFFRUGLQJ�WRUHOHDVH�NH\��SULRULW\�DQG�UDQN��WKHQ�\RX�KDYH�WR�HYDOXDWH�WKHFKDQJH�IRU�VLPLODU�RU�PLVVLQJ�UDQNV�

���6HTXHQFH�IRU�&UHDWLQJ�&KDQJHV

&KDQJHPDVWHU�UHFRUG1��

&KDQJHPDVWHU�UHFRUG1��

&KDQJHPDVWHU�UHFRUG1��

&KDQJHPDVWHU�UHFRUG1��

W � W � W � W �

���6HTXHQFH�IRU�&UHDWLQJ�&KDQJHV

n If you work without rank or with change numbers with similar ranks, then the change with the mostcurrent change creation date is derived from the changes to the similar object.

n Summary of the last slides:

é Depending on the parameters you set, the system assigns an appropriate effectivity type. If thereare different change statuses with different effectivity types, the system chooses the one with thehighest priority and a release key that is set. If there are several effectivity types that are the same,the system chooses according to rank.

é This process first takes place for the BOM of the header material. This is repeated for eachexplosion level.

é If, for example, you work with changes relating to the effectivity type serial number, then youmaintain all changes to the complete structure with reference to the serial number of the finishedproduct. The later explosion of the structure follows likewise.

Page 178: LO 980 engineering change mgmt

© SAP AG LO980 7-24

SAP AG 1999

l :KHUH�LQ�WKH�V\VWHP�LV�WKH�QHZ�HIIHFWLYLW\�FRQWUROOHG�"

XQIYB VZICB <FE[V�?:<]\ =[5:?%?%=A@�<^B 67B <FE`_�EDGA=�R5:?a?b= @�<]B 6DB <aE[GA87I�8 JK=�<�=7I5:?a?b= @�<]B 6DB <aEc<aEZGA=�R5:?a?b= @�<]B 6DB <aEc<aEZGA=cV�?D8T@L\A8LU d:=KU:;�JfeA=LIPg=79 =�8�RA=hS =�EPg87U:SiV�?D8>@L\ 8LU dL=KU:;�JjeA=LI

1HZ�HIIHFWLYLW\k ;�R�<�V7JfB l BmU dk ;�R�<�V7JfB l BmU dk ;�R�<�V7JfB l BmU d

k \A87U dL=`9 =A8AnL=:ILNLJ[8�R�<b=LIQI�= @AVZIonk \A87U dL=`9 =A8AnL=:ILNLJ[8�R�<b=LIQI�= @AVZIonk \A87U dL=`9 =A8AnL=:ILNLJ[8�R�<b=LIQI�= @AVZIon

0DLQWHQDQFH

&RQWUROOLQJ�3DUDPHWHU�(IIHFWLYLW\

Page 179: LO 980 engineering change mgmt

© SAP AG LO980 7-25

SAP AG 1999

ZLWK'HVFULSWLRQ����ZLWK'HVFULSWLRQ����

9DOLGFURVV�FOLHQW

PDWHULDO�VSHFLILF9DOLG

FURVV�FOLHQWPDWHULDO�VSHFLILF

(IIHFWLYLW\�SURILOH

5HOHDVH�NH\

3DUDPHWHU�HIIHFWLYLW\5DQN�DFWLYH5HOHDVH�DFWLYH����/RFN�/DWH�SDFNDJHV

3DUDPHWHU�HIIHFWLYLW\5DQN�DFWLYH5HOHDVH�DFWLYH����/RFN�/DWH�SDFNDJHV

6HW�FRQWURO�GDWD

ZLWK'HVFULSWLRQ����ZLWK'HVFULSWLRQ����

(IIHFWLYLW\�SDUDPHWHU

(IIHFWLYLW\�W\SHV������&RPELQDWLRQ�RI�HIIHFWLYLW\�SDUDPHWHUV������'HVFULSWLRQ�RI�WKH�W\SH

�������������DQG�WKH�SDUDPHWHU�UHODWLQJ�WR�W\SH������3ULRULW\

p

ppp

&XVWRPL]LQJ��&KDQJH�+LHUDUFK\��5HOHDVH�.H\�����

Page 180: LO 980 engineering change mgmt

© SAP AG LO980 7-26

SAP AG 1999

Additional Control Options

&XVWRP�&XVWRP�

l $FWLYDWH���GHDFWLYDWH�WKH�UHOHDVH�NH\��SDUDPHWHUHIIHFWLYLW\��UDQN��FKDQJH�KLHUDUFK\

l &URVV�FOLHQW�RUPDWHULDO�VSHFLILF�HIIHFWLYLW\�SURILOH

l 6WDQGDUG�YDOXDWLRQVl 2YHUULGH�FKDQJH�QXPEHUV

�SUHUHTXLVLWH��������HIIHFWLYLW\�DFWLYH�LQ�WKH�PDWHULDO�PDVWHU�LQ�WKH�UHSRUWLQJ�GLDORJ�ER[

&XVWRP�&&��

q � �,r � ���F��(s� t�� ���q � �u�����vA��� � ������a� ���rw��� � ��� " ��(x� (,��� �

$GGLWLRQDO�&RQWURO�2SWLRQV

&&��

&&��

Page 181: LO 980 engineering change mgmt

© SAP AG LO980 7-27

SAP AG 1999

<RX�DUH�QRZ�DEOH�WR�

&KDQJH�+LHUDUFK\��5HOHDVH�.H\��������8QLW�6XPPDU\

l 6HW�XS�FKDQJH�KLHUDUFKLHVl 8VH�WKH�UHOHDVH�NH\l &RQWURO�WKH�UHOHDVH�RI�FKDQJH�KLHUDUFKLHVl 8VH�HIIHFWLYLW\�W\SHV�ZLWK�QHZ�HIIHFWLYLW\

SDUDPHWHUV�IRU�WKH�OLQNHG�REMHFWV�LQ�FKDQJHQXPEHUV

l 0DNH�WKH�QHFHVVDU\�VHWWLQJV�LQ�&XVWRPL]LQJ�WR�EHDEOH�WR�XVH�WKLV�IXQFWLRQDOLW\

n The change hierarchy consists of a leading change master record (change leader) and changepackages.

n The release key controls the release of object changes for successive work areas or application areasin the logistics chain.

n There are different effectivity types (date interval, serial number, additional freely definable). Thesedifferent types can also be combined.

n The BOM explosions with these effectivity types take place according to priority, rank and creationdate.

Page 182: LO 980 engineering change mgmt

© SAP AG LO980 7-28

([HUFLVHV

8QLW��&KDQJH�+y LHUDUFK\��5HOHDVH�.H\�(IIHFWLYLW\�3DUDPHWHUV

7RSLF�� 3DUDPHWHU�HIIHFWLYLW\�DQG�5HOHDVH�NH\At the conclusion of this exercise, you will be able to:

• Create change numbers with effectivity types with parametereffectivity and make changes to objects with reference to thischange number.

• Test the release of the changes for certain processes in thelogistics chain using the release key.

For the scheduling of detailed changes you want to use theparameter effectivity options.

The release of this change should also be controllable.

1-1 In the material master records 7�)��� and 7�%��� set the indicator �$VVLJQHIIHFW��YDOXHV�� (basic data screen)

Create a change master &�����with�UHOHDVH�NH\ and effectivity type ³6(515´(serial number).For this, use the profile 35(&0��.

As a description, maintain "Change to SERNR. 100 - 200", rank 10, reason forchange "Exercise example", as effectivity 7�)��� in the closed interval of ����to���.Control the entries relating to status and object types.(Material BOM changes with automatic generation of object management recordsmust be possible.)Save.

1-2 In a second session, change your BOM 7�)��� with the change master recordabove.

Start from the development status of the BOM that is effective today. (Filter inBOM maintenance or maintenance value in the change number)

Change the TXDQWLW\ of the item for the hexagonal head screw to �.Save.

Page 183: LO 980 engineering change mgmt

© SAP AG LO980 7-29

1-3 In the second session, change your BOM 7�%��� with the change master recordabove.

Start from the development status of the BOM that is effective today. (Filter inBOM maintenance or maintenance value in the change number)

Change the TXDQWLW\ of the item for the seals to ��and for the hexagonal head screwto �.Save.

Explode your BOM T-F1## level-by-level.

For this, use the BOM application 33��, explode a required quantity of �� fortoday’s date:

Start the explosion.In the value assignment screen of the parameter effectivity, enter your SXPS and����DV�WKH�VHULDO�QXPEHU.1. Process: Do not change the default values concerning the

Release key. What is the result of this?

2. Process: Delete all indicators concerning the UHOHDVH�NH\except free production. What is the result of this?

3. Process: Delete all indicators concerning the UHOHDVH�NH\�What is the result of this?

1-4 In your change master, set a release key� that enables the release for productionorders. The release for other areas should kept as low as possible.

Test the result again in the BOM explosion for 7�)���� Repeat the second processfrom point 1-4 above.

1-5 Test the result by creating a production order for your VKDIW�7�%����Production plant is 1000.Order type is PP01Ignore the query for account assignment and cancel.

Order quantity to 10.Finish date should be today + 1 month.

In the value assignment screen of the parameter effectivity, enter your SXPS and����DV�WKH�VHULDO�QXPEHU.Display the component overview. Have your changes to the BOM been taken intoconsideration?

Page 184: LO 980 engineering change mgmt

© SAP AG LO980 7-30

([HUFLVH8QLW��&KDQJH�+y LHUDUFK\��5HOHDVH�.H\�

(IIHFWLYLW\�3DUDPHWHUV7RSLF��&KDQJH�+y LHUDUFK\�DQG�5HOHDVH�.H\• Create leading change masters and packages and carry this out

with the help of these changes

• With this exercise, you prepare the data for unit ��µOrderChange Management (OCM)’.

For carrying out changes with respect to Engineering ChangeManagement of master data (ECM), you should use the tool forthe change hierarchies.

You want to apply this as a structuring tool in your workmethods.

2-1 Call up the Engineering Workbench and select the working area ‘3B$/ z / z (6‘.

1RWH�WKDW�WKH�WDVN�OLVW�KHDGHU�WDE�SDJH�LV�DFWLYDWHG��

2-1-1 By copying, create a new routing for your pump7�)���.First select the available task list with the following data:Material 7�)���Plant ����&RS\ the task list with the group counter � (lot size 80to 140) KLHUDUFKLFDOO\ to the next free group counter and set up the ORW�VL]HDUHD from ��WR����and the�WDVN�OLVW�VWDWXV�µJHQHUDO�UHOHDVH¶� ��.

Make a note of the task list group and the group counter:

3DWK� 0HQX�SDWK��6$3�0HQX�→�/RJLVWLFV�→�3URGXFWLRQ�→�0DVWHU�GDWD→�(QJLQHHULQJ�:RUNEHQFK� �&(:%RU8VHU�PHQX�→�(QJLQHHULQJ�:RUNEHQFK� �&(:%�5HO�����%�� �&:%33�

Page 185: LO 980 engineering change mgmt

© SAP AG LO980 7-31

2-1-2 Change the BOM of the material 7�)��� in plant ����without using a change number.Add the components 7�%�����7�%���and 7�%��� each with � piece and item category / z as stock item to theBOM.

3DWK� 8VLQJ�WKH�PHQX��JRWR�WKH�LWHP�RYHUYLHZ�RI�WKH� %20�IRU�PDWHULDO�7�)���

� →�%LOOV�RI�0DWHULDO�→�,WHPV

2-2 Create a leading change master 7�&+ { �� (function leading change master)with the following data

Description 8QLW�JURXS���Valid-from 7RGD\�����PRQWKVReason for change ([HUFLVH�H[DPSOHRelease key ZLWKRXW�YDOXH��HPSW\�Status �

2-3 Create a change package 7�&3��� (function change master + change package)with the profile 33������ and the following data

Description 3DFNDJH���JURXS���Leading change master 7�&+ { ��Valid-from &RSLHG�IURP�WKH�OHDGHU.Reason for change ([HUFLVH�H[DPSOHStatus �With this package, at least one BOM should be changeable.

2-4 Create a change SDFNDJH 7�&3��� (function ECR + change package)with change type ���� profile 33������ and the following data

Description 3DFNDJH���JURXS���Leading change master T-CH##Valid from &RSLHG�IURP�WKH�OHDGHUReason for change ([HUFLVH�H[DPSOHStatus �With this package, at least one routing should be changeable.

2-5 Assign an object management record to the change package 7�&3���for the routing you created in �����.Set the system status so that changes to this routing are possible with this changenumber and can be processed.

Page 186: LO 980 engineering change mgmt

© SAP AG LO980 7-32

2-6 In the Engineering Workbench, make the following changes to your BOM 7�)��� withthe change package 7�&3���:

Items� 7�%��� DeleteItem 7�%��� Increase the quantity from � to �Item ������� Add from � pieces as stock item

2-7 In the Engineering Workbench, make the following changes to your newly createdrouting for the material 7�)��� with the change package 7�&3���:

Operations ���� DeleteOperation ���� Delete the PRT 33�)+ { 06Operation ���� Add operation with the data

Work center 7�0��Description / z RQJ�WHUP�WHVWLabor time ���PLQV per pieceMachine time ���PLQV per piece

Page 187: LO 980 engineering change mgmt

© SAP AG LO980 7-33

6ROXWLRQV

8QLW��&KDQJH�+y LHUDUFK\��5HOHDVH�.H\(IIHFWLYLW\�3DUDPHWHUV

7RSLF�� 3DUDPHWHU�HIIHFWLYLW\�DQG�5HOHDVH�NH\

1-1 Start from the user menu and click0DWHULDO�→�&KDQJH�→�,PPHGLDWHO\Access your change master 7�)����View: %DVLF�'DWD��above in the block �*HQHUDO�GDWD�Indicator �9DOXDWH�WKH�HIIHFWLYLW\�Carry out this step analogously for material 7�%���.

Start from the user menu again and click(QJLQ��FKDQJH�PJPW�→�&KDQJH�QXPEHU�→�&UHDWHin the initial screen, enter:Change no.: C##-7Type: &KDQJH�PDVWHU�UHFRUGFunction: :LWK�UHOHDVH�NH\Effectivity type: 6(515Profile: 35(&0��The change header appears. Here you maintain theDescription,Rank,Effectivity (using the corresponding buttons)

The list of the object types is filled out as requested according to the profile.The entries for the material master, are missing from the profile. At the moment, thematerial master can not be changed with parameter effectivities.

Save the data.

Page 188: LO 980 engineering change mgmt

© SAP AG LO980 7-34

1-2 Start from the user menu and click%LOO�RI�PDWHULDO�→�0DWHULDO�%20�→�&KDQJHin the initial screen of the BOM change, enter:

Material: 7�)���Plant: 1000Usage: �Change number: &����Valid-from: (ignore)

The item overview appears.

Click ³(IIHFWLYLW\� �6KLIW���)�� and the desired selection screen appears. Onlyselect the 'DWH.Enter WRGD\ as the XSSHU�DQG�ORZHU�GDWH�OLPLW�(in the effectivity parameters).

In item ���� of the hexagonal head screw overwrite the quantity from 8 to �.

Save the data

1-3 Start from the user menu and click%LOO�RI�PDWHULDO�→�0DWHULDO�%20�→�&KDQJHin the initial screen of the BOM change, enter:

Material: 7�%���Plant: 1000Usage: �Change number: &����Valid-from: (ignore)

The item overview appears.

Click ³(IIHFWLYLW\� �6KLIW���)�� and the desired selection screen appears. Onlyselect the 'DWH.Enter WRGD\ as the XSSHU�DQG�ORZHU�GDWH�OLPLW�(in the effectivity parameters).

In item ���� material T-T2## overwrite the quantity from 1 to ��In item ���� material T-T3## overwrite the quantity from 8 to �Save the data

Page 189: LO 980 engineering change mgmt

© SAP AG LO980 7-35

1-4 Start from your user menu and select�5HO�����%�%LOO�RI�0DWHULDO�→�5HSRUWLQJ�→�([SORGH�PDWHULDO�%20 →�%20�OHYHOE\�OHYHO�5HO�����F�%LOO�RI�0DWHULDO�→�5HSRUWLQJ�→�%20�H[SORVLRQ�→ 0DWHULDO�%20�→%20�OHYHO�E\�OHYHOIn the initial screen enter:Material: 7�)���Plant: ����Alternative BOM: �Alternative: 33��Valid from: 7RGD\¶V�GDWHChange number: -Revision level: -Required quantity: ��

Execute = F8

The $VVLJQ�YDOXHV�WR�HIIHFWLYLW\�SDUDPHWHUV�screen appears. Here, you valuate the:Material: 7�)���Serial number: ���and in the 1. run: all indicators relating to release key

remain unchanged

As a result, you see that the above changes have not been taken into consideration.

Reexecute the BOM explosion with the same settings as above, except:in the 2. run: all indicators relating to release key

deleted except production

As a result, you see that the above changes have not been taken into consideration.

Reexecute the BOM explosion with the same settings as above, except:in the 3. run: all indicators relating to release key

deleted

As a result, you see that the changes made to T-F1## and to T-B1## have beentaken into consideration.

1-5 Start from the user menu again and goto(QJLQ��FKDQJH�PJPW�→�&KDQJH�1XPEHU�→�'LVSOD\Change no.: &����Use the F4 help in the header to set the corresponding release key.

(The release key has to have been created in the demonstration. There is not arelease key that only releases the changes for production.)

Page 190: LO 980 engineering change mgmt

© SAP AG LO980 7-36

1-6 Start from the user menu and click%LOO�RI�PDWHULDO�→�5HSRUWLQJ�→�([SORGH�PDWHULDO�%20�→�%20�OHYHO�E\�OHYHOin the initial screen of the BOM change, enter:Material: 7�)���Plant: ����Alternative BOM: �Alternative: 33��Valid from: 7RGD\¶V�GDWHChange number: -Revision level: -Required quantity: ��

Execute = F8

The $VVLJQ�YDOXHV�WR�HIIHFWLYLW\�SDUDPHWHUV�screen appears. Here, you valuate the:Material: 7�)���Serial number: ���and in the 1. run: all indicators relating to release key

remain unchanged

As a result, you see that the above changes have not been taken into consideration.

Reexecute the BOM explosion with the same settings as above, except:in the 2. run: all indicators relating to release key

deleted except production

As a result, you see that the changes made to T-F1## and to T-B1## have beentaken into consideration.

Page 191: LO 980 engineering change mgmt

© SAP AG LO980 7-37

1-7 Start from the SAP menu and choose/RJLVWLFV�→�3URGXFWLRQ→�3URGXFWLRQ�FRQWURO�→�2UGHU�→�&UHDWH�→�:LWK�PDWHULDOAdd this transaction CO01 to the favorites (place the cursor over the entry and clickthe right mouse button)

In the initial screen, enter:Material: 7�%���Production plant: ����Planning plant: -Order type: 33��Order: -

(continue)

In the DFFRXQW�DVVLJQPHQW window, click FDQFHO.Confirm the warning message that materials with parameter effectivity should beupdated as individual customer stock.

In the header screen of the production order, enter:Total quantity: ��Basic finish date: 7RGD\�����PRQWK

(continue)

In the value assignment screen of the parameter effectivity, enter:Material: 7�)�����������:DUQLQJ���Serial number: ���

(continue)Click on the corresponding button to goto the &RPSRQHQW�RYHUYLHZ� �)�The changes have been taken into account.

Page 192: LO 980 engineering change mgmt

© SAP AG LO980 7-38

6ROXWLRQV8QLW��&KDQJH�+y LHUDUFK\��5HOHDVH�.H\

(IIHFWLYLW\�3DUDPHWHUV7RSLF��&KDQJH�+y LHUDUFK\�DQG�5HOHDVH�.H\

2-1 Start from the user menu in the Engineering Workbench.

Select the working area ‘3B$/ z / z (6’.

In the selection criteria, enter 7�)��� as material and 1000 as plant. Execute theselection (Button or F8)

The overview of the task list header appears. Select the task list with the groupcounter � (Lot size 80 to 140) and copy it hierarchically. Confirm the first windowwithout changing anything. In the second window (copy target data) choose (Rel.4.6b) Options or (Rel. 4.6c) Copy range = Shift + F11.Here enter at least material-routing assignment, task list header, sequence, operationand PRT as the copy range. Select ‘Multi-level copy’ and execute.Change the lot size range in ��WR���. Make a note of the task list group and thegroup counter:________________________________________________________

Choose %LOOV�RI�PDWHULDO�→�,WHPV in the item overview. Add the components 7�%�����7�%���and 7�%��� each with � piece as stock item (item category / z )�to the BOM. Save.Close the work in the Engineering Workbench by clicking on the correspondingbutton.

2-2 Start from the user menu again and click(QJLQ��FKDQJH�PJPW�→�&KDQJH�QXPEHU�→�&UHDWHin the initial screen, enter:Change no.: 7�&+ { ��Type: &KDQJH�PDVWHU�UHFRUGFunction: / z HDGLQJ�FKDQJH�PDVWHUThe change header appears. Here, you maintain theDescription,Valid-from,Reason for changeStatus

Save the leading change master.

Page 193: LO 980 engineering change mgmt

© SAP AG LO980 7-39

2-3 Start from the user menu again and click(QJLQ��FKDQJH�PJPW�→�&KDQJH�QXPEHU�→�&UHDWHin the initial screen, enter:Change no.: 7�&3���Type: &KDQJH�PDVWHU�UHFRUGFunction: &KDQJH�SDFNDJHProfile: 33������The change header appears. Here, you maintain theDescriptionLeading change masterStatus

The list of the object types is filled out as requested according to the profile.

Save your change package.

2-4Start from the user menu again and click(QJLQ��FKDQJH�PJPW�→�&KDQJH�QXPEHU�→�&UHDWHin the initial screen, enter:Change no.: 7�&3���Type: (&5Function: &KDQJH�SDFNDJHChange type: ���Profile: 33������The change header appears. Here maintain theDescription,Leading change masterStatus

(Rel. 4.6b: You can enhance the object types using both flags in the routing lines.(Release 4.6C: The list of the object types is filled out as requested according to theprofile.

2-5 Then go to the list of the objects. Enter the task list you noted above with the tasklist type N. (poss. F4-Help, task list search with material number T-F2##)

In the header, change the system status to ‘Check request’ .In the object management record, change the system status to ‘Change possible’ .In the task list header, change the system statuses and possibly the user statuses oneafter the other until ‘request converted’ .

Save your change package.

Page 194: LO 980 engineering change mgmt

© SAP AG LO980 7-40

2-6 Start from the user menu in the Engineering Workbench.

Select the working area ‘3B$/ z / z (6’ .

In the selection criteria, enter 7�)��� as material and 1000 as plant. Execute theselection (Button or F8)

The overview of the task list header appears. Choose %LOOV�RI�PDWHULDO�→�,WHPV togo to the item overview (since only one BOM exists for your material, a previousselection is not necessary.)

Select the items with materials T-B4## and T-B2## and lock these using the changebutton or F6. In the window that appears, enter the change number T-CP1##.– Delete item T-B4##.– Increase the quantity of T-B2## to 2.– Add a stock item of 8 piece hexagonal head screws 100-300 (item 50).

Save.Do not exist the transaction (Engineering Workbench)

2-7You are in the item overview in the Engineering Workbench.

Choose 7DVN�OLVWV�→�7DVN�OLVW�KHDGHUV and go to the task list header overview.Select the task list that you created above and choose 7DVN�OLVWV�→�2SHUDWLRQV togoto the operation overview.

Select the operations 40 and 50 and lock these using the change button or F6.Change the change number to T-CP2##. (Button next to the change number)– Delete operation 40.– In operation 50 delete the PRT PP-FHMS, by selecting the operation, via 7DVN�OLVWV�→�357�in the corresponding overview.– Add an operation 70 with the work center T-M##, the description ‘Long-term test’ , the labor and machine times of 10 mins each as processingtimes (corresponding tab page).

Save and exit the transaction.

Page 195: LO 980 engineering change mgmt

© SAP AG LO980 8-1

SAP AG 1999

2UGHU�&KDQJH�0DQDJHPHQW��2&0���&RQWHQWV

l $LP�RI�2UGHU�&KDQJH�0DQDJHPHQWl $SSOLFDWLRQ�DUHDl 3UHUHTXLVLWHV�IRU�WKH�DSSOLFDWLRQl 0DVWHU�GDWD�FKDQJH�SURFHVVl &KDQJH�REMHFWVl 6DOHV�RUGHU�FKDQJH�SURFHVVl &KDQJH�SURFHVV�LQ�DVVHPEO\�RUGHUVl 0DQDJHPHQW�RI�PDVV�FKDQJHV

Page 196: LO 980 engineering change mgmt

© SAP AG LO980 8-2

SAP AG 1999

$W�WKH�FRQFOXVLRQ�RI�WKLV�XQLW��\RX�ZLOO�NQRZ�

2UGHU�&KDQJH�0DQDJHPHQW��2&0���&RXUVH2EMHFWLYHV

l 7KH�DLPV�RI�2UGHU�&KDQJH�0DQDJHPHQW��2&0�l :KLFK�DSSOLFDWLRQ�DUHD�DQG�SUHUHTXLVLWHV�WKLVDSSOLFDWLRQ�FRYHUVl +RZ�WKH�PDVWHU�GDWD�FKDQJH�SURFHVV�UXQV�DQGZKLFK�FKDQJH�REMHFWV�LW�WDNHV�LQWR�FRQVLGHUDWLRQl +RZ�WKH�VDOHV�RUGHU�FKDQJH�SURFHVV�UXQVl +RZ�WKH�FKDQJH�SURFHVV�UXQV�LQ�DVVHPEO\�RUGHUVl +RZ�PDVV�FKDQJHV�DUH�PDQDJHG

Page 197: LO 980 engineering change mgmt

© SAP AG LO980 8-3

SAP AG 1999

l $V�D�UXOH��DXWRPDWLF�FKDQJHV�DUH�QRW�SRVVLEOH�IRUSURGXFWLRQ�RUGHUV�DOUHDG\�LQ�SURGXFWLRQ���VXFK�DVXSGDWHG�RU�SDUWLDOO\�FRQILUPHG�PDWHULDOFRQVXPSWLRQ�«���

l 7KURXJK�2UGHU�&KDQJH�0DQDJHPHQW��2&0��WKH�5��6\VWHP�RIIHUV�WKH�IXQFWLRQV�IRU�FRQWUROOHG�FKDQJHV�

l 2&0�FRQFHQWUDWHV�RQ�WKH�H[HFXWLRQ�RI�FKDQJHV�WRWKH�SURGXFWLRQ�RUGHUV�DOUHDG\�LQ�SURGXFWLRQ�

l 7KH�EDVLV�IRU�2&0�FKDQJHV�DUH�FKDQJHV�WR�SURGXFWPDVWHU�GDWD��(&0��RU�VSHFLILF�FKDQJHV�IURP�VDOHVRUGHUV��6'��

2UGHU�&KDQJH�0DQDJHPHQW��%XVLQHVV�6FHQDULR

Page 198: LO 980 engineering change mgmt

© SAP AG LO980 8-4

SAP AG 1999

&RXUVH�2YHUYLHZ�'LDJUDP

2EMHFW�&KDQJHV2EMHFW�&KDQJHV ��5HSRUWLQJ5HSRUWLQJ ��

�� &KDQJH�+LHUDUFK\��&KDQJH�+LHUDUFK\��5HOHDVH�.H\�5HOHDVH�.H\�«« ��&KDQJH�0DVWHU�5HFRUG&KDQJH�0DVWHU�5HFRUG

3URFHVVLQJ�&KDQJHV�3URFHVVLQJ�&KDQJHV�ZLWK�:RUNIORZZLWK�:RUNIORZ ��&RXUVH�2YHUYLHZ&RXUVH�2YHUYLHZ ��

(&5���(&2(&5���(&2 ��

6XPPDU\6XPPDU\ ��

��2UGHU�&KDQJH�2UGHU�&KDQJH�0DQDJHPHQW��2&0�0DQDJHPHQW��2&0�

Page 199: LO 980 engineering change mgmt

© SAP AG LO980 8-5

SAP AG 1999

�����&KDQJH�PDVWHU�UHFRUG��(&5���(&2�ZLWK�REMHFW�PDQDJHPHQW�

UHFRUGV&KDQJHV�WR�REMHFWV��PDWHULDO�PDVWHUV��%20V��URXWLQJV��

GRFXPHQWV�DQG�VR�RQ�5HSRUWLQJ&KDQJH�SURFHVVLQJ�ZLWK�:RUNIORZ

&KDQJH�IODJV�IRU�FKDQJH�PDVWHU�UHFRUGV�(from ECM)&KDQJH�IODJV�IRU�FKDQJH�REMHFWV�(from ECM)&KDQJH�IODJV�IRU�VDOHV�RUGHUV&KDQJH�SURFHVV�ZLWK�WKH�VWHSV������������� ����������������� ��������������� � "! #�! $%#�&�' (

������������� �����������*)�+,�-��. +,��/0��������)���+1���2�� ��34)���+5�������6���78������+9�6��:���;��� 3��/0.���������<=� +,<-��+>3=��&? �@ ACB2&�' DE$F@ GHDI&?'>J�GH'D1(K ���:��+1/;��L�4����<;�����M��N����-�����O�%3P-Q ����.-�:�R�"�������S�%3T�U V�$E �WMG�#�V�G�$%XF# !�YZGL[�'\&"J�]�XF# !�&% �&�'\J"G^':D_(

2UGHU�&KDQJH�0DQDJHPHQW��2&0�

(QJLQHHULQJ�&KDQJH�0DQDJHPHQW��(&0�

(QJLQHHULQJ�&KDQJH�0DQDJHPHQW��2YHUYLHZ�

n Engineering Change Management offers the user the possibility to make changes to individual orseveral objects (product master data and documents for current business processes).

n The R/3 System is divided into:� (&0� �(QJLQHHULQJ�Change Management2&0 = 2UGHU� Change Management

n (&0 concentrates on the preparation and execution of changes to product master data

n 2&0 concentrates on the execution of changes to the production orders DOUHDG\�LQ�SURGXFWLRQ (andon looking for planned orders and purchase orders affected by changes).

n The basis for OCM changes are changes to product master data (ECM) or specific changes fromsales orders (SD).

n Since no automatic and unchecked changes are possible for running production orders (such asupdated or partially confirmed material consumption …), the R/3 System offers the functions forcontrolled changes to orders.

n These functions essentially go beyond the previous possibilities of the function³5HDGLQJ�PDVWHUGDWD´.

Page 200: LO 980 engineering change mgmt

© SAP AG LO980 8-6

SAP AG 1999

`_ab

cd11 1

7 58 4

210

2UGHU�&KDQJH�0DQDJHPHQW��2&0�

l :KHQ�DUH�WKH�2&0�WRROV�QHHGHG"e 3URGXFWLRQ�RUGHUV�DUH�LQ�SURGXFWLRQ�DQG�SURFHVVHG�e &XVWRPHUV�FKDQJH�WKHLU�RUGHUVe 'HVLJQ�RU�WHFKQRORJLFDO�FKDQJHV�DUH�UHTXLUHGe 0DVV�RUGHUV�DUH�DIIHFWHG�E\�FKDQJHV��VXFK�DV�FROOHFWLYH�RUGHUV�

l :KR�QHHGV�WKH�2&0�WRROV"e 6DOHV�RUGHU�VSHFLILF�SURGXFWLRQ��PDNH�WR�RUGHU

SURGXFWLRQe 3URGXFWV�ZLWK�ORQJ�OHDG�WLPHV

l $LP�RI�2UGHU�&KDQJH�0DQDJHPHQWe 3UHSDUDWLRQ�RI�D�V\VWHP�VXSSRUWHG�WRRO�IRU�FRQWUROOLQJ�DXWRPDWHG

FKDQJHV�WR�SURGXFWLRQ�RUGHUV�DOUHDG\�LQ�SURGXFWLRQ�e 7KH�DIIHFWHG�FKDQJHV�FDQ�EH�WULJJHUHG

E\�VDOHV�RUGHUV�DQG���RU�PDVWHU�GDWD�FKDQJHV

Page 201: LO 980 engineering change mgmt

© SAP AG LO980 8-7

SAP AG 1999

$SSOLFDWLRQ�5HFRPPHQGDWLRQV�IRU�2&0

l 0DQXDO�FKDQJHV�WR�SURGXFWLRQ�RUGHUVe OK for VPDOO production orders

(as a rule for ’flat’ product structures and simple routings)

l )XQFWLRQ��5HDGLQJ�33�PDVWHU�GDWDn < 4.0A : Only with the status: opened

n >= 4.0A : Also with the status: releasede Changes only so long as the production process has

not yet started

l $VVHPEO\�SURFHVV��ZLWK�FROOHFWLYH�RUGHUV�e Automatic changes only so long as the production process has

not yet started

n Alongside the application of OCM, you should DOVR�FKHFN whether the VLPSOH�VROXWLRQV namedabove are also successful.

n Only if changes also have to be made in the FXUUHQW�SURGXFWLRQ, or to mass orders does(QJLQHHULQJ�&KDQJH�0DQDJHPHQW have a KLJK�XVH.

n 7KH�IROORZLQJ�IXQFWLRQDOLWLHV are currently taken into consideration in OCM�• Multi-level make-to-order production ZLWKRXW�collective orders

• Changes to operation sequence, PRT, trigger point, Batch split, co-products, discontinued parts,alternative items.

Page 202: LO 980 engineering change mgmt

© SAP AG LO980 8-8

SAP AG 1999

6DOHV�RUGHU

&KDQJHV�WRVDOHV�RUGHU

Production order (Copy of the basic data at the time the order was created) Production order (Copy of the basic data at the time the order was created)

�,WHPV

Material

Date / quantity

Values (characteristics)

&KDQJHV�WRSURGXFWV�RU�WRWHFKQRORJ\

�5RXWLQJ�%LOO�RI�PDWHULDO

%DVLF�GDWD

&KDQJHPDVWHU�UHFRUG

old

NEW(released)

NEW

&KDQJH�3URFHVV�RI�WKH�2&0�7RRO

n Changes can come from PP master data and / or sales orders.

n Order Change Management takes into consideration WZR�GLIIHUHQW�FKDQJH�SURFHVVHV�&KDQJH�SURFHVV�IRU�PDVWHU�GDWD�FKDQJHV&KDQJH�SURFHVV�IRU�VDOHV�RUGHU�FKDQJHV

n $W�DQ\�RQH�WLPH, a PO can RQO\ run through RQH of these two SURFHVVHV.

Page 203: LO 980 engineering change mgmt

© SAP AG LO980 8-9

SAP AG 1999

MaterialA

&KDQJHPDVWHU�UHFRUG

2&0��3UHUHTXLVLWHV�IRU�&KDQJH�3URFHVVHV

l &XVWRPL]LQJ 6HWWLQJV�IRU�DQ�RYHUDOO�FKDQJH�SURILOHl 0DWHULDO�PDVWHU $VVLJQPHQW�RI�DQ�RYHUDOO�FKDQJH�SURILOH

�:RUN�VFKHGXOLQJ�VFUHHQ�l &KDQJH�SURFHVV�IRU�EDVLF�GDWD

&KDQJH�PDVWHU�ZLWK�UHOHDVH�NH\�5HO2&0�VZLWFK�DFWLYDWHG�

(IIHFWLYLWLHV��GDWH��FXVWRPHU��VHULDO�QXPEHU������

l &KDQJH�SURFHVV�IRU�VDOHV�RUGHU�FKDQJHV5HTXLUHPHQWV�FODVV��&KJ��3URG��2UGHU�VZLWFK��DFWLYDWHG

n To apply Engineering Change Management effectively, you have to meet the SUHUHTXLVLWHVPHQWLRQHG�DERYH.

n The feasibility of the changes is controlled in detail using the RYHUDOO�FKDQJH�SURILOH.n The overall change profile is made up of WKUHH�VXESURILOHV for controlling the changes to PP master

data, sales orders and assembly processing.

n These profiles are maintained in Customizing (-> Production orders -> Operations -> EngineeringChange Management).

n You assign the overall change profile to the material master record.

n If you make a change to an OCM sales order item, the UHTXLUHPHQWV�FODVV (Customizing SD) of therequirements type has to be prepared accordingly.

Page 204: LO 980 engineering change mgmt

© SAP AG LO980 8-10

SAP AG 1999

2&0��0DVWHU�'DWD�&KDQJH�3URFHVV

6HOHFWLRQ�RI�WKH�SURFXUHPHQW�HOHPHQWV�DIIHFWHG�E\�FKDQJHV

&UHDWH�FKDQJH�PDVWHU

5HOHDVH�RI�FKDQJHV

'HWHUPLQH�WKH�FKDQJHV

&KHFN�IHDVLELOLW\�RI�FKDQJHV

&DUU\�RXW�FKDQJHV�WR�WKH�32

&KDQJHPDVWHU�UHFRUG

&KDQJHIODJPDVWHU�UHFRUG

(automatically for release date,can also be created manually)

&KDQJHREMHFWV

�$FWLYH�32

� �"

&KDQJHV

&KDQJHIODJVIRU�32

n The master data change process RQO\�FRYHUV�FKDQJHV�WR: BOMs (material BOMs, sales order BOMs and WBS BOMs) and routings

n With the UHOHDVH�of a leading change master (master data) the system�DXWRPDWLFDOO\ generates aFKDQJH�IODJ�IRU�WKH�FKDQJH�PDVWHU�UHFRUG�

n On the basis of the change flags for change master records, the production orders affected bychanges are determined using an interim step and the change flags for the ECRs found generated.

n The QHFHVVDU\�FKDQJHV (change instructions) are determined by a multi-level process in the form ofFKDQJH�REMHFWV�(see the slide ’change objects’).

n When you�VWDUW�GHWHUPLQLQJ changes, the DFWLYH�32�LV�ORFNHG�WR�SUHYHQW�FKDQJHV�n The IHDVLELOLW\�RI�FKDQJHV is checked using FKDQJH�SURILOHV in the material master. This controls the

generation of info, warning and error messages.

n When you�VWDUW�FKHFNLQJ changes, the DFWLYH�32�LV�ORFNHG�WR�SUHYHQW�WKH�FUHDWLRQ�RI�DFWXDO�GDWD�n The change process presented on the slide is completed by the functions Confirm changes

(optional) and deletion of the temporarily generated data objects (such as change flags, determinedchanges,......).

n BOM changes can be made dependent of SDUDPHWHU�HIIHFWLYLWLHV.

Page 205: LO 980 engineering change mgmt

© SAP AG LO980 8-11

SAP AG 1999

2&0�2EMHFWV

&KDQJH�9LHZ��2EMHFW�W\SH�SURILOH��GHWDLO���2YHUYLHZf%gihjg,kml n�o g1p

q?o rms tZu�vFl�n�w9x_l2w,n�gy�z rmkmu^g-{�r_p1l�gmnFn g9x1tZn |�}^n t^~�o� �i� g1xil^l �m}mg-}^n tZ~ o s g�� t9�mgmn �^o g�6�>� g1x_l,l �,}9g-}Zn tZ~ o s g�� |^g_l r

���i� g1xil^l �m}mg-}^n tF�� �mg,n�n�w^s g1r � s g

���i� � �^}�q?g_p9xmn�o }9l�o tFk ��xil2� ���\� g1x1l���u^l �?g1x���gmk^� kmg>h���gmk^q�o rms��mt^x,�� r_l g,n2o r,s1� � �"pq?t^x,w^{�g,k9l^p1l�n�w9x_l2w,n gvEr,s g1p6tZn�|^gmnE� � ��?tHw9l2o k1u�?g_~ gmn gmk^x1g�tH}mgmn r1l�o tZk-p9gilq?t^x,w^{�g,k9l� r_l g,n2o r,sy�z r,n r1x_l�gmn�o p_l2o xy s r_p_p^o ~2o x9r_l o tFk���i� g1x_l^|Zg,}9gmkm|^gmk,xmo g_py tHk9~2o u^wHn ril2o tZkL},n�tm~2o s g�?r,n�o r,kml,l r � s g

n The 2&0�FKDQJHV can only be determined for the IODJJHG�REMHFWV.

Page 206: LO 980 engineering change mgmt

© SAP AG LO980 8-12

SAP AG 1999

7ULJJHU�E\�&KDQJH�1XPEHU

&KDQJHKLHUDUFK\

&KDQJH�SDFNDJH

l 5HOHDVH�ZLWK�WKH�UHOHDVH�NH\

l /DWH�SDFNDJH�IRU�OHDGLQJ�FKDQJH�PDVWHU

l 'DWH�VKLIW

n &KDQJH�IODJV for the master data - change process are generated at the WLPHV given in the slide.

Page 207: LO 980 engineering change mgmt

© SAP AG LO980 8-13

SAP AG 1999

5HOHDVH�.H\

&KDQJH�OHDGHU

&KDQJH�SDFNDJH�$

&KDQJH�SDFNDJH�%

&KDQJH�SDFNDJH�&

���%�?�Z�H�����F�2�F�\�H� &KDQJH�OHDGHU

&KDQJH�SDFNDJH�$

&KDQJH�SDFNDJH�%

&KDQJH�SDFNDJH�&

���%�?�^�F���5�Z���F�\�H�

� ��� �F�F�E�C�Z�,� � ��� �Z�E�E�C�^�Z�

RelOCM

DateOCM

n The release key controls the XVDELOLW\�RI�WKH�OHDGLQJ�FKDQJH�PDVWHU�for Order Change Management(OCM).

n You cannot set the release key for a change leader until all its change packages have the systemstatus "Released".

n &KDQJHV with a release key GR�QRW�WDNH�HIIHFW until the HIIHFWLYLW\�FRQGLWLRQV (see XQLW�) are metDQG�the release key is set.

n 7ZR�VZLWFKHV�in the release key are of SDUWLFXODU�LPSRUWDQFH�IRU�2&0�• 5(/2&0 By releasing the master record, a change flag is written

• '$7(2&0 During a date shift, a change flag is written

Page 208: LO 980 engineering change mgmt

© SAP AG LO980 8-14

SAP AG 1999

Change flag for initiator

Change flag for procurement operation

&KDQJHIODJ�IRU�FKDQJHPDVWHU�RUVDOHV�RUGHU

&KDQJHIODJ�IRUSURGXFWLRQ�RUGHU

&KDQJH�)ODJV

l )XQFWLRQV  &RQWURO�REMHFW�IRU�SURJUHVV�RI�WKH�FKDQJH�SURFHVV�IRU�HDFK�SURGXFWLRQ�RUGHU

l 'HWDLOHG�LQIRUPDWLRQ  2UGHU�QXPEHU��XVHU��GDWH��WLPH  ,QGLFDWRU�IRU�WKH�QHFHVVLW\�RI�WKH�FKDQJH�WR�D�SURGXFWLRQ�RUGHU

l )XQFWLRQV  %DVLV�IRU�WKH�VHOHFWLRQ�RI�WKH�SURGXFWLRQ�RUGHUV�WR�EH�FKDQJHG

E\�WKH�LQLWLDWRUl 'HWDLOHG�LQIRUPDWLRQ

  :KR�WKH�LQLWLDWRU�LV��VDOHV�RUGHU�RU�FKDQJH�PDVWHU�UHFRUG  $FWLRQ�FDXVHG�E\�LQLWLDWRU

� Engineering Change Management allows�WZR�W\SHV�RI�FKDQJH�IODJV�• Flags for the�LQLWLDWRU of a change (sales order, change master record)

• Flags for�SURFXUHPHQW�RSHUDWLRQV�DIIHFWHG by changes (production orders)

� These change flags are managed by separate transactions.

Page 209: LO 980 engineering change mgmt

© SAP AG LO980 8-15

SAP AG 1999

'HWHUPLQLQJ�&KDQJHV

l 3UHSDUHG�ZRUN�e /RFN�WKH�DFWLYH�SURGXFWLRQ�RUGHU�WR�SUHYHQW�PDQXDO�FKDQJHVe 6WDWXV12&+ �FKDQJHV�QRW�DOORZHG�e 2QO\�FRQILUPDWLRQV�DQG�JRRGV�PRYHPHQWV�DUH�DOORZHG

l /RJLFe 6WUXFWXUH�FRPSDULVRQ�RI�WKH�VLPXODWLRQ�RUGHU�ZLWK�WKH�DFWLYHSURGXFWLRQ�RUGHU

e *HQHUDWLQJ�FKDQJH�LQVWUXFWLRQV�DQG�VDYLQJ�WKHP�LQ�WKH�GDWDEDVHe 'LVSOD\�RSWLRQV�IRU�FKDQJH�LQVWUXFWLRQV

l &RPSOHWHG�ZRUNe 'HOHWLRQ�RI�WKH�FKDQJH�IODJ�IRU�WKH�SURFXUHPHQW�W\SHDIWHU�H[HFXWLQJ�DQG�FRQILUPLQJ�FKDQJHV��RSWLRQDO�

n %HIRUH�DFWLYH�FKDQJHV to an operative production order can be made, the system has to determinethe necessary changes in the IRUP�RI�FKDQJH�LQVWUXFWLRQV�

n The determination of necessary changes is GLIIHUHQW�IRU�HDFK�FKDQJH�SURFHVV.n For PDVWHU�GDWD���FKDQJH�SURFHVV the change instruction takes place in a WZR�OHYHO�SURFHVV from the

known change objects of the (&0�UDZ�FKDQJHV (see the next slide).

n A comparison of the operative PO with a simulated PO is carried out by a sales order - changeprocess (see the slide on Sales order - change process).The result is concrete change instructions.

n By�GHOHWLQJ�WKH�FKDQJH�IODJV�for a procurement element, all the existing FKDQJH�REMHFWV�DQGFKDQJH�LQVWUXFWLRQV�DUH�DXWRPDWLFDOO\�GHOHWHG.

Page 210: LO 980 engineering change mgmt

© SAP AG LO980 8-16

SAP AG 1999

l :KDW�DUH�&KDQJH�2EMHFWV"e 2QO\�SURGXFWLRQ�RUGHU�REMHFWV�WKDW�KDYH�WR�EH�FKDQJHG�RUDGGHG��VXFK�DV�WKH�GDWD�VWUXFWXUH�RI�D�SVHXGR�RUGHU�

e 7KRVH�GHULYHG�IURP�FKDQJHV�WR�FKDQJH�PDVWHU�UHFRUGVDQG�RSHUDWLYH�SURGXFWLRQ�RUGHUV�WR�EH�FKDQJHG

e 6XETXDQWLW\�RI�SRVVLEOH�VLPXODWHG�RUGHU�REMHFWV

l :K\�DUH�FKDQJH�REMHFWV�XVHG"e 2SHQLQJ�RI�VLPXODWHG�RUGHUV�LV�RPLWWHGe 6WUXFWXUDO�FRPSDULVRQ�RI�RUGHUV�LV�RPLWWHGe %HWWHU�SHUIRUPDQFH�VLQFH�RQO\�D�VXETXDQWLW\�RI�REMHFWVDQG�QRW�WKH�HQWLUH�RUGHU�VWUXFWXUH�KDV�WR�EH�SURFHVVHG

e 7\SH�RI�FKDQJH�LQVWUXFWLRQ�LV�NQRZQ�E\�WKH�FKDQJH�PDVWHUUHFRUG

&KDQJH�2EMHFWV

n The master data change process does not need simulated orders to determine the change instructionsbecause these are already known from changes to BOMs and routings with reference to a changemaster record.

n The FKDQJH�REMHFWV�are created in a PXOWL�OHYHO�SURFHVV (see next slide).

n They are not to be confused with the term change master record change objects.

Page 211: LO 980 engineering change mgmt

© SAP AG LO980 8-17

SAP AG 1999

&RPSDULVRQ�RI&KDQJH�GRFXPHQWV

�2OG�URXWLQJ�1HZ�URXWLQJ

�1HZ�%20 �2OG�%20

5DZ�FKDQJHV

�������&KDQJH�REMHFWVJHQHUDWH

&KDQJHPDVWHU�UHFRUG

&KDQJH�REMHFWV Record structuring of the PO

*HQHUDWLQJ�&KDQJH�2EMHFWV

Page 212: LO 980 engineering change mgmt

© SAP AG LO980 8-18

SAP AG 1999

� $FWLYH�32

Mat. no.�����Order quantity

Comp no. requirements quantity

Oper. no. Work center -No. Operation quantityItem 1 | 10 Pc

Item 2 | 20 Pc

Item 3 | 30 Pc

PRT1 | 10 Pc

Op.1 | Apl1 | 10Pc

Item 4 | 10 Pc

PRT2 | 2 Pc

Op. 2 | Apl2 | 10Pc

Item 1 | 12 Pc

Item 3 | 30 Pc

Item 5 | 10 Pc

PRT1 | 10 Pc

Op. 1 | Apl2 | 10Pc

Item 4 | 10 Pc

PRT3 | 2 Pc

Op. 2 | Apl3 | 10Pc

�6LPXO��32

Order no | Mat1 | 10 Pc Order no | Mat1 | 10 Pc

PRT no. ����requirements quantity

([DPSOH�RI�D�&RPSDULVRQ

2EMHFW�W\SH���&RPSDULVRQ�DWWULEXWH�������3ULPDU\�����6HFRQGDU\

n Instead of simulated orders, the previously determined change objects appear during the master datachange process

Page 213: LO 980 engineering change mgmt

© SAP AG LO980 8-19

SAP AG 1999

352'8&7,21�5(6285&(6�722/6PRT ID Rqmts quantity Rqmts date

,7(0Mat. no. quantity

6(48(1&(Sequence no. Branch op. Return op.

25'(5�+($'(5Order no. Mat. no. Total quantity

23(5$7,21Op.no. Work center Operation quantity Date

Mat.no. BOM ID Quantity Rqmts date&20321(17

7\SHV�RI�&KDQJH�,QVWUXFWLRQV

n $GG�REMHFW�WR�WKHSODQQHG�SRVLWLRQ�LI�QRW�DYDLODEOH�

n 'HOHWH�REMHFW�LI�QR�ORQJHU�XVHG�

n &KDQJH�REMHFWn 6KLIW�REMHFW

�RQO\�IRU�PDWHULDO�FRPSRQHQWV�

n &KDQJH�LQVWUXFWLRQV�are generated directly from the change objects and by comparing the activeproduction orders to the related simulated orders.

n You can choose from IRXU�GLIIHUHQW�W\SHV of change instruction (see above).

n A SDLU�IRUPDWLRQ runs internally IRU�DOO�REMHFW�of these ECRs.

n This pair formation is made up of DWWULEXWHV.é 3ULPDU\ attributes serve the pair formation of objects.

é 6HFRQGDU\ attributes serve the more detailed check for identity per pair (same or not).

n 2EMHFWV�ZLWKRXW�D�FRXQWHU�SDUW are either QHZ�RU�GHOHWHG.

n A User-Exit &22&0��� can be used for the definition of additional specific attributes.

Page 214: LO 980 engineering change mgmt

© SAP AG LO980 8-20

SAP AG 1999

'HWHUPLQLQJ�&RQIOLFWV��&KHFN�&KDQJHV�

l 3UHSDUDWLRQn /RFN�WKH�SURGXFWLRQ�RUGHUV�WR�SUHYHQW�FRQILUPDWLRQVDQG�JRRGV�PRYHPHQWV

n 6WDWXV�&*(% (Confirmations and goods movement notallowed)

n &KHFN�HDFK�FKDQJH�LQVWUXFWLRQ�IRU�FRQIOLFWn 'HILQH�FKDQJH�SURILOH�FRQIOLFW�VLWXDWLRQVn 'HILQH�FKDQJH�SURILOH�VHULRXVQHVV�RI�WKH�FRQIOLFW

(information, warning, error)

l 'LVSOD\�WKH�FRQIOLFWVn ,Q�WKH�OLVW�RI�FKDQJH�LQVWUXFWLRQV

Page 215: LO 980 engineering change mgmt

© SAP AG LO980 8-21

SAP AG 1999

'HOHWH 2SHUDWLRQ�LV�SDUW�RI�ILQDOO\�FRQILUPHG'HOHWH &RPSRQHQW�KDV�DOUHDG\�EHHQ�ZLWKGUDZQ'HOHWH &RPSRQHQW�LV�DOUHDG\�EHLQJ�XVHG

,QVHUW 6XEVHTXHQW�RSHUDWLRQ�LV�FRQILUPHG,QVHUW 2SHUDWLRQ�WKDW�VKRXOG�EH�DVVLJQHG�WR�WKH

FRPSRQHQWV�LV�ILQDOO\�FRQILUPHG&KDQJH &RPSRQHQW�KDV�DOUHDG\�EHHQ�FRQILUPHG

DQG�VKRXOG�EH�FKDQJHG

([DPSOHV�IRU�&RQIOLFW

,QVWUXFWLRQ�W\SH������2EMHFW�W\SH�������6WDWXV�RI�WKH�SURGXFWLRQ�RUGHU�REMHFW

n For special checks for the individual change instructions, the user has a

User-Exit��(;,7B6$3/&22&0%B���� (See Customizing production orders ’SystemAdjustments’)

Page 216: LO 980 engineering change mgmt

© SAP AG LO980 8-22

SAP AG 1999

0DQXDO�GHFLVLRQ UHTXLUHG���

Type of Conflict Change profile type

Change (Check result) Selected execution Non selected execution.

All types None Normal Normal

Error No update of the PO No update of the PO

Change Warning Automat. change and No automatic Warning symbol Execution

Insert Warning Automat. insert and No automatic Warning symbol Execution

Information Normal Normal

Delete Warning Deletion flag No automatic with symbol Execution

&KDQJHV�WR�$FWLYH�3URGXFWLRQ�2UGHUV

l &RQWUROOHG�H[HFXWLRQ�RI�WKH�FKDQJH�LQVWUXFWLRQV

n $OO�determined changes are carried out LQ�RQH�JR (in one process) for the operative production order.

Therefore, the�QRWLILFDWLRQ�FDWHJRU\�GHWHUPLQHG during the check of the change plays�DQLPSRUWDQW�UROH.

n The W\SH�RI�JHQHUDWHG�QRWLILFDWLRQ�W\SH is determined from the settings for the 2&0�RYHUDOOSURILOH in &XVWRPL]LQJ�2UGHU�&KDQJH�0DQDJHPHQW�

n The�FRQIOLFW (see above) covers the QRWLILFDWLRQ�W\SH that the FKHFN�RI�WKH�FKDQJHV generated.For the conflict types :DUQLQJ or (UURU a GHFLVLRQ�has to be made in thH�GLDORJ�ER[.

n The 2&0�SURFHVV can be carried out VHOHFWHG or QRQ�VHOHFWHG.

The 2&0�RYHUDOO�SURILOH in the material master contains the relevant VZLWFK for this.

n The VHOHFWHG�H[HFXWLRQ�enables the automatic execution of changes (particularly for warnings) butwith information from a warning symbol.

n $IWHU�VXFFHVVIXOO\�SURFHVVLQJ all change instructions of a change flag,the RSHUDWLYH�(&5�can be changed�DJDLQ,

updated and transferred to an additional change process.

The change flag is completed.

n In the production order (header data) you can see a KLVWRU\�RI�WKH�FKDQJH�SURFHVV.

Page 217: LO 980 engineering change mgmt

© SAP AG LO980 8-23

SAP AG 1999

(IIHFWLYLW\��9DOLG�)URP�'DWH

&KDQJH�RQ�FDVLQJ

&KDQJH�QXPEHU�1��

t1Time

Reason for change:

Change date:

&XUUHQW�VWDWXV

t1

n %HIRUH Release 4.5 the GDWH could only be used as an LQGLYLGXDO�HIIHFWLYLW\�SDUDPHWHU.

Page 218: LO 980 engineering change mgmt

© SAP AG LO980 8-24

SAP AG 1999

3DUDPHWHU���(IIHFWLYLWLHV

,Q�WKH�FDVH�RI�GLIIHUHQW�HIIHFWLYLWLHV�IRU�REMHFWV�:KLFK�VWUXFWXUH�LV�YDOLG�"+RZ�LV�WKH�%20�H[SORVLRQ�FDUULHG�RXW�LQ�WKH�V\VWHP"+RZ�DUH�FRQIOLFWV�EHWZHHQ�FRQIOLFWLQJ�FKDQJHV)RU�GLIIHUHQW�HIIHFWLYLWLHV�VROYHG�"

&XVWRPHU�QXPEHU

6HULDO�QXPEHU

n )URP Release 4.5 DGGLWLRQDO�HIIHFWLYLW\�SDUDPHWHUV (see XQLW��) can be used.

n These effectivites are prepared in Customizing.

n A FKDQJH�LV�RQO\�UHOHYDQW for a production order�LI�DOO�SDUDPHWHU�YDOXHV�PHHW�DW�WKH�VDPH�WLPH(such as customer, material, serial number, date,....).

Page 219: LO 980 engineering change mgmt

© SAP AG LO980 8-25

SAP AG 1999

2&0��6DOHV�2UGHU�&KDQJH�3URFHVV

6HOHFWLRQ�RI�WKH�SURFXUHPHQW�HOHPHQWV�DIIHFWHG�E\�FKDQJHV

(QWHU�FKDQJH�WRVDOHV�RUGHU

*HQHUDWH�D�VLPXODWHG�32

'HWHUPLQH�WKH�FKDQJHV

&KHFN�IHDVLELOLW\�RI�FKDQJHV

&DUU\�RXW�FKDQJHV�WR�WKH�32

�$FWLYH�32

� �"

&KDQJHIODJVIRU�32

(+ Purchaseorder, plannedorder)

&KDQJHV

�6LPXODWHG�32

&KDQJHIODJ6DOHV�RUGHU

(automatic for the release date, can also be created manually)

n Necessary�FKDQJHV�WR�D�VDOHV�RUGHU lead�DXWRPDWLFDOO\�to a�FKDQJH�IODJ�n 5HOHYDQW�FKDQJHV for this process could be:

• Changes to characteristic values (variant configuration)

• Changes to the serial number

• Change master records, WKDW D� are assigned to the sales order (direct assignment)

E� are valid for this sales order (parameter effectivity)

n The QHFHVVDU\�FKDQJHV are determined for this process by a FRPSDULVRQ�RI�WKH�REMHFWV of the DFWLYHPO and of a VLPXODWHG PO.

n A VLPXODWHG�SURGXFWLRQ�RUGHU is always necessary. This is RSHUDWLYHO\�QRW�HIIHFWLYH.n When you�VWDUW�GHWHUPLQLQJ changes, the DFWLYH�32�LV�ORFNHG�WR�SUHYHQW�FKDQJHV�n The IHDVLELOLW\�RI�FKDQJHV is checked using FKDQJH�SURILOHV in the material master. This controls the

generation of info, warning and error messages.

n When you�VWDUW�FKHFNLQJ changes, the DFWLYH�32�LV�ORFNHG�WR�SUHYHQW�WKH�FUHDWLRQ�RI�DFWXDO�GDWD�n The change process presented on the slide is completed by the functions

Confirm changes (optional) and deletion of the temporarily generated data objects (such as changeflags, determined changes,......).

n For planned orders and purchase orders QR changes are generated.

Page 220: LO 980 engineering change mgmt

© SAP AG LO980 8-26

SAP AG 1999

2&0�5HOHYDQW�&KDQJHV�WR�6DOHV�2UGHUV

l &KDQJHV�WR�FRQILJXUDWLRQ��YDOXHV�l &KDQJHV�WR�WKH�HIIHFWLYLW\�SDUDPHWHUl &KDQJHV�WR�WKH�VHULDO�QXPEHUl 'LUHFW�DVVLJQPHQW�RI�FKDQJH�PDVWHU�UHFRUGV�WR

VDOHV�RUGHUV

l 1RW��4XDQWLW\�DQG�UHTXLUHPHQWV�GDWH

Page 221: LO 980 engineering change mgmt

© SAP AG LO980 8-27

SAP AG 1999

2SHQLQJ�D�6LPXODWHG�2UGHU

l 3XUSRVH�RI�VLPXODWHG�RUGHUV¡ 0HDQV�RI�FRPSDULVRQ for determining change instructions

l 2SHQLQJ�ORJLF¡ Based on the changed parameters of the sales order:

Valuation (configuration), effectivity, serial number¡ Based on the FKDQJHG master data

l 3URFHGXUH¡ Selection of the production orders affected by changes¡ Opening a simulated order for each affected production order in the list

of change flags¡ Flag ‘Simulated order‘ exists in the change flag for the procurement

element (that means per PO)¡ Navigation options to display the simulated order

n As preparation for determining the detailed change instructions, a VLPXODWHG�RUGHU is opened foreach operative production order to be changed.

n The simulated order is FUHDWHG�ZLWK�• The same order type

• The changed sales order standard values

• The master data for these standard values

• Without individual lead-time scheduling

Page 222: LO 980 engineering change mgmt

© SAP AG LO980 8-28

SAP AG 1999

2&0��(QJLQHHULQJ�&KDQJH�0DQDJHPHQW�LQ$VVHPEO\�2UGHUV

(QWHU�FKDQJH�WRVDOHV�RUGHU

*HQHUDWH�D�VLPXODWHG�32

'HWHUPLQH�WKH�FKDQJHV

&DUU\�RXW�FKDQJHV�WR�WKH�32

�$VVHPEO\�32

� �"

&KDQJH�IODJ�IRUDVVHPEO\�RUGHU

&KDQJHV

�6LPXODWHG�32

&KDQJHIODJ6DOHV�RUGHU �

&KHFN�IHDVLELOLW\�RI�FKDQJHV

$XWRPDWLF�EDFNJURXQG�

n Necessary�FKDQJHV�WR�D�VDOHV�RUGHU are carried out�DXWRPDWLFDOO\�by�FKDQJHV�WR�WKH�DVVHPEO\RUGHU�

Page 223: LO 980 engineering change mgmt

© SAP AG LO980 8-29

SAP AG 1999

2&0���0DVV�3URFHVVLQJ

* ¢�£�¤�¥�¦"¤�§>¦6¨ ¦�©MªM¦M«T¬>£�§�­Mª ¦¯®

l 5HSRUW��&2B2&0B25'(5B/,67+¡ /RRNV�IRU�WKH�LQLWLDWRU�RI�WKH�FKDQJHV¡ /RRNV�IRU�WKH�SURFXUHPHQW�HOHPHQWV�DIIHFWHG�E\�FKDQJHV¡ 0DQDJHPHQW�RI�WKH�FKDQJH�IODJ�LQLWLDWRU�DQG�SURFXUHPHQW�HOHPHQW�

l 5HSRUW��&2B2&0B2%-(&7B/,67¡ ([HFXWLRQ�RI�WKH�FKDQJH�SURFHVV�IRU�WKH�RSHUDWLYH�RUGHUV¡ 3URFHVVLQJ�RI�WKH�WDEOH�)812&0

l 5HSRUW��&22&03,&.� ¡ ([HFXWLRQ�RI�JRRGV�PRYHPHQWV�WKDW�UHVXOW�IURP�FKDQJHV

n Order Change Management can also carry out EDFNJURXQG�SURFHVVLQJ.

Page 224: LO 980 engineering change mgmt

© SAP AG LO980 8-30

SAP AG 1999

2&0���:DVWH�3URGXFWV

l 6LPXODWHG�SURGXFWLRQ�RUGHUV��7$�&2��6�° &UHDWH�WR�WHVW��VLPXODWH�DQG�SOD\° &UHDWH�ZLWKRXW�VDOHV�RUGHU�RU�SURMHFW° $OVR�FUHDWH�ZLWK�YDULDQW�FRQILJXUDWLRQ�DQG�RU�SDUDPHWHU�HIIHFWLYLW\° 1R�DXWKRUL]DWLRQ�FKHFN�ZLWK�REMHFWV�IURP�WKH�RSHUDWLYH�RUGHU° 6FKHGXOH��SULQW�LQGHSHQGHQW�RI�VWDWXV

7KH�IROORZLQJ�FDQ�QRW�EH�FDUULHG�RXW�° 5HOHDVH��FRQILUPDWLRQ��FRVWLQJ�����

l &RPSDULVRQ�WUDQVDFWLRQ��7$�&2���° &RPSDUHV�WHPSRUDULO\�JHQHUDWHG�DQG�H[LVWLQJ�RUGHUV

Page 225: LO 980 engineering change mgmt

© SAP AG LO980 8-31

SAP AG 1999

2&0���1HJDWLYH�/LVW

l *HQHUDO° &KDQJHV�WR�EDWFKHV° &R�SURGXFWV° 3URGXFWLRQ�UHVRXUFHV�WRROV

l 0DVWHU�GDWD° 'LVFRQWLQXHG�LWHPV° $OWHUQDWLYH�LWHPV° 3URGXFWLRQ�UHVRXUFHV�WRROV° 3KDQWRP�KHDGHU�LWHPV° 6WUXFWXUH�RI�FROOHFWLYH�RUGHUV

l 6DOHV�RUGHU° 0XOWL�OHYHO�SURGXFWLRQ�ZLWKRXW�GLUHFW�SURGXFWLRQ��UHTXLUHPHQWV�W\SH�.(�

Page 226: LO 980 engineering change mgmt

© SAP AG LO980 8-32

SAP AG 1999

2&0���6SHFLDO�3UREOHPV

l &RQIOLFWLQJ�DFFHVV�RI�VHYHUDO�FKDQJH�SURFHVVWR�WKH�VDPH�RUGHU¡ 0DVWHU�GDWD���!�6DOHV�RUGHU¡ 6HYHUDO�VXSSOHPHQWV�RI�FKDQJH�QXPEHUV

l 3UREOHP�FDVHV���0RQLWRU�IXQFWLRQ¡ VXFK�DV�VWDUWHG�VDOHV�RUGHU�SURFHVV�ORFNV�PDVWHU�GDWD�SURFHVV¡ 6HOHFWLRQ�RI�325'�WKDW�KDV�QRW�EHHQ�DEOH�WR�EH�SURFHVVHG�IRU�D�VSHFLILF�SHULRG

Page 227: LO 980 engineering change mgmt

© SAP AG LO980 8-33

SAP AG 1999

2&0���8VHU�([LWV

l (;,7B6$3/&22&0%B������8VHU�VSHFLILF�FKHFNV¡ $IWHU�WKH�6$3�WHVW��D�VHOI�GHILQHG�FKHFN�FDQ�EH�PDGH�LQ�WKH�8VHU�([LW�¡ 0HVVDJHV�VHQW�ZLWK�0(66$*(B6725(�DUHVDYHG�DQG�GLVSOD\HG�ZLWK�6$3�0HVVDJHV�

l (;,7B6$3/&22&0B������'HILQLWLRQ�RI�FRPSDULVRQ�ILHOGV

Page 228: LO 980 engineering change mgmt

© SAP AG LO980 8-34

SAP AG 1999

2&0���2XWORRN��)XWXUH�'HYHORSPHQWV�

l ��8SGDWLQJ�WKH�,QWHUIDFH���8VLQJ�$%$3�/LVW�9LHZHU�$/9

l ,QWURGXFWLRQ�RI�DGGLWLRQDO�WULJJHUV�IRU�WKH�FKDQJH�SURFHVV° 2UGHU�%20�FKDQJHV° &KDQJHV�WR�JOREDO�REMHFW�GHSHQGHQFLHV��+3"�° ���

l 1HFHVVDU\�HQKDQFHPHQWV�WR�LQWHJUDWLRQ° ,QFOXVLRQ�LQ�&RQILJXUDWLRQ�0DQDJHPHQW��$V�EXLOW�° VXFK�DV�H[WHUQDO�SURFXUHPHQW

l 3RVW�SURFHVVLQJ�RI�VHOHFWHG�FKDQJHG�FRPSRQHQWV��&2&0��l 3ULQWLQJ�RI�UHVWUXFWXUH�SDSHUVl $FWLYH�SURSRVDOV�IRU�WKH�UHXVDELOLW\�RI�DVVHPEOLHVl ���

���&

���&

Page 229: LO 980 engineering change mgmt

© SAP AG LO980 8-35

SAP AG 1999

2UGHU�&KDQJH�0DQDJHPHQW��2&0���6XPPDU\

l $V�RI�5HOHDVH�����\RX�FDQ�XVH�2UGHU�&KDQJH0DQDJHPHQW��2&0��

l $�SUHUHTXLVLWH�IRU�WKLV�LV�WKH�PDVWHU�GDWD��(QJLQHHULQJ�&KDQJH�0DQDJHPHQW��(&0��� ��

l 2&0�UHFRJQL]HV�WZR�FKDQJH�SURFHVVHV��WKH�PDVWHUGDWD�DQG�WKH�VDOHV�RUGHU�FKDQJH�SURFHVVHV�

l 7KLV�FRXUVH�SURYLGHV�\RX�ZLWK�DQ�RYHUYLHZ�RI�WKHDSSOLFDWLRQ�RSWLRQV��SUHUHTXLVLWHV�DQG�FKDQJHSURFHGXUHV�

Page 230: LO 980 engineering change mgmt

© SAP AG LO980 8-36

([HUFLVHV

8QLW��2UGHU�&KDQJH�0DQDJHPHQW��2&0�7RSLF��)RXQGDWLRQ�RI�(QJLQHHULQJ�&KDQJH0DQDJHPHQW• Create complete change profiles for OCM

• Get to know the necessary decisions

• Enhance the material master records for OCM

• Preparation of production orders

As a production manager, production scheduler or foreman, youare responsible for the timely and proper implementation ofproduction orders.In your company, Engineering Change Management is to be usedfor both the maintenance of master data and in existingproduction processes.For this, you have to satisfy additional prerequisites forEngineering Change Management in production.This exercise will teach you the necessary settings and data.In particular, you have to prepare the change profiles for theOCM process and use these to make decisions about theeligibility of changes in production.

1-1 First determine in Customizing, which subprofiles are contained in the entire changeprofile 33���� for Order Change Management (OCM)?

Change profile for master data changes 33����Change profile for sales order changes 33����Change profile for assembly order changes 33����

3DWK� &XVWRPL]LQJ��6352��→�)��→ 3URGXFWLRQ�→�3URGXFWLRQ�FRQWURO→ 2SHUDWLRQV�→�2UGHU�&KDQJH�0DQDJHPHQW��2&0��→ 'HILQH�FRPSOHWHFKDQJH�SURILOH� �23/�

Page 231: LO 980 engineering change mgmt

© SAP AG LO980 8-37

1-2 Look at the settings of the individual subprofiles and answerthe following questions:

3DWK� &XVWRPL]LQJ��6352��→�)��→ 3URGXFWLRQ�→�3URGXFWLRQ�FRQWURO→ 2SHUDWLRQV�→�2UGHU�&KDQJH�0DQDJHPHQW��2&0��→ 'HILQH�FKDQJHSURILOH� �23/�

1-2-1 Is the line ‘When warning appears, execute and mark changes’ IODJJHG whenPDVWHU�GDWD changes are made ?

$QVZHU� BBBBBBBBBB

1-2-2 You have DGGHG an RSHUDWLRQ to a URXWLQJ�and this change shouldshould lead to the change in an already ILQDOO\�FRQILUPHG production order.As a result of the profile setting, which message type is the change process(OCM) likely to generate?

$QVZHU� BBBBBBBBBB

1-2-3 As a result of the change to a VDOHV�RUGHU� a material component to an alreadySDUWLDOO\�FRQILUPHG�RSHUDWLRQ should no longer be required (omitted).As a result of the profile setting, which message type is the change process(OCM) likely to generate?

$QVZHU� BBBBBBBBBB

1-3 Ensure that the following PDWHULDO�PDVWHU�UHFRUGV (work scheduling screen) contain acomplete change profile 33����.

7�)�����7�%�����7�%�����7�%����DQG�7�%���

Page 232: LO 980 engineering change mgmt

© SAP AG LO980 8-38

1-4 Open several (about five, using the template of the first one created) production orderswith the following entries

Material 7�)���Production plant ����Order type 33��Total quantity ���SLHFHBasic start date &XUUHQW�GDWH���PRUH�WKDQ���PRQWKVScheduling type )RUZDUGV

3DWK� 6$3�0HQX�→�/RJLVWLFV�→�3URGXFWLRQ�→�3URGXFWLRQ�&RQWURO→ 2UGHU�→�&UHDWH�→�:LWK�PDWHULDO� �&2��

3DWK� →�2UGHU�→�6DYH

Order no. BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB__________________

1-5 With the following steps, carry out a FROOHFWLYH�UHOHDVH for DOO orders for yourSURGXFWLRQ�VFKHGXOHU�±�QXPEHU.

1RWH�WKH�UHFRPPHQGHG�UHOHDVH�SHULRG

3DWK� 6$3�0HQX�→�/RJLVWLFV�→�3URGXFWLRQ�→�3URGXFWLRQ�&RQWURO→ &RQWURO�→�&ROOHFWLYH�UHOHDVH� �&2��1

1-5-1 Choose the WDE�6(/(&7,21 and select with the following parameters:

Material 7�)���Prod. plant ����Order type 33��Production scheduler ���

Page 233: LO 980 engineering change mgmt

© SAP AG LO980 8-39

1-5-2 Choose the WDE�0$66�352&(66,1*��5(/($6(and make the following settings here:

Function 5HOHDVH&DUU\�RXW�IXQFWLRQ�LPPHGLDWHO\

Function parameter 2UGHU�UHOHDVH3DWK� 3URJUDP�→�([HFXWH

6HOHFW�DOO�WKH�RUGHUV�UHFRPPHQGHG�E\�WKH�V\VWHP����4.6b:

1-5-3 Carry out the mass processing

3DWK�� 0DVV�SURFHVVLQJ�→�([HFXWH����� 4.6b:

4.6c:

After each situation, it is possible that the system will reporta lack of material, capacity or PRT availability. Release theorders anyway.

1-5-4 Check the release log for possible errors

3DWK� →�0DVV�SURFHVVLQJ�→�/RJ�ODVW�PDVV�SURFHVVLQJRU

→�%XWWRQ��2UGHU

1-5-5 Refresh the list and control the generated system status ofthe orders

3DWK� →�/LVW�→�5HIUHVK�→ )XOO

Page 234: LO 980 engineering change mgmt

© SAP AG LO980 8-40

1-6 For at least one order, carry out a SDUWLDO�FRQILUPDWLRQ (quantity = ��SLHFHV and DQ\activity) for operation ���� of the order.For this, use the RSHUDWLRQ�UHODWHG confirmation µWLPH�WLFNHW¶

('2�127 confirm the entire order !!)

3DWK� 6$3�0HQX�→�/RJLVWLFV�→�3URGXFWLRQ�→�3URGXFWLRQ�&RQWURO→ &RQILUPDWLRQ�→�(QWHU�→�)RU�RSHUDWLRQ�→�7LPH�WLFNHW� �&2��1

With this exercise, you have generated production orders thatcan be found in the production. :LWKRXW�2&0� you canonly�PDQXDOO\ change these orders!

Optionally you can test these in the change mode forproduction orders.

Page 235: LO 980 engineering change mgmt

© SAP AG LO980 8-41

([HUFLVHV8QLW��2UGHU�&KDQJH�0DQDJHPHQW��2&0�7RSLF��0DVWHU�'DWD�±�&KDQJH�3URFHVVHV

• Release of changes (see 2nd exercise for unit 7)

• Selecting the change initiator (change master record)

• Selecting the procurement elements (production orders)

• Carrying out the master data change processes

In the course of time, changes to design and productionscheduling in the Engineering Change Management of masterdata (ECM) arise.As a production scheduler, it is your SHUPDQHQW�MRE,to evaluate these changes with the help of the OCM – tools and toexecute or reject changes in production.

1-1 Technically release the change package (master record) 7�&3���.

3DWK� 6$3�0HQX�→�/RJLVWLFV�→�3URGXFWLRQ�→�0DVWHU�GDWD�→ (QJLQHHULQJ&KDQJH�0DQDJHPHQW�→�&KDQJH�QXPEHU��→�&KDQJH� �&&��RU8VHU�PHQX�→�(QJLQHHULQJ�&KDQJH�0DQDJHPHQW�→ &KDQJH�QXPEHU��→&KDQJH

(GLW�→�7HFKQLFDOO\�UHOHDVH

1-2 Complete the routing changes (change object !) to material 7�)��� in the changepackage 7�&3��� and release the changes.

For this, you have to go into the object management recordsof the ECO and process the status management there step bystep.

1-3 Now totally complete the change package 7�&3��� using the status management in theheader screen of the change master record and release this change master record.As a result of this release, the indicator µ7HFKQLFDOO\�UHOHDVHG¶ also has to be set.

Page 236: LO 980 engineering change mgmt

© SAP AG LO980 8-42

1-4 Now control the entire leading change master 7�&+���All change packages for this leader have to be released.You will see this from the JUHHQ�VSRW in the change package line.

3DWK� 6$3�0HQX�→�/RJLVWLFV�→�3URGXFWLRQ�→�0DVWHU�GDWD→ (QJLQHHULQJ�&KDQJH�0DQDJHPHQW�→�5HSRUWLQJ�→�&KDQJH�KLHUDUFK\ �&&��RU8VHU�PHQX�→�(QJLQHHULQJ�&KDQJH�0DQDJHPHQW�→�5HSRUWLQJ�→�&KDQJHKLHUDUFK\

1-5 Technically release the leading change master (master record) 7�&+�� andset the UHOHDVH�NH\ with ��.

2 With the following steps, carry out the master data – change processfor production orders.

2-1 Determine whether change flags exist for your leading change master?

Choose with the following settings

Ind.: Select change numbers

Change number 7�&+��Prod. plant ����Processing status 8QSURFHVVHGProcurement element to look for Production orders

3DWK� 6$3�0HQX�→�/RJLVWLFV�→�3URGXFWLRQ�→�3URGXFWLRQ�FRQWURO→ &RQWURO�→�2UGHU�FKDQJH�PDQDJHPHQW�→�&KDQJH�SURFHVV�→�,QLWLDWLQJREMHFW� �&2&0

The system has to find your leading change master as a resultof these steps. If this is not the case, then you have made amistake in the previous exercises.If necessary, ask the trainer for assistance with this exercise.

2-2 Determine the production orders affected by changes to the leading change master andsave the result.

3DWK��� �����→�(',7�→ 6($5&+�)25�352&85(0(17�(/(0(17

Page 237: LO 980 engineering change mgmt

© SAP AG LO980 8-43

2-3 Now process the flags for the procurement elements (production orders) determined inthe previous step, in order to be able to carry out the actual change process.

Choose with the following settings

Procurement element 3URGXFWLRQ�RUGHUVProd. plant ����Production scheduler ���Reason for change DOOStatus change process 1R�UHVWULFWLRQV

3DWK� 6$3�0HQX�→�/RJLVWLFV�→�3URGXFWLRQ�→�3URGXFWLRQ�FRQWURO→ &RQWURO�→�2UGHU�FKDQJH�PDQDJHPHQW�→�&KDQJH�SURFHVV�→3URFXUHPHQW�HOHPHQW�IODJ� �&2&0�

2-4 Carry out the change process step by step for the first flagged production order.

2-4-1 Select the order and start with determining the necessary changes

3DWK� (',7�→ (;(&87(�352&(66�67(3

Select the step 'HWHUPLQH�FKDQJHV

2-4-2 From the process processing, control the changes determined and checktheir accuracy

3DWK� *272�→ &+$1*(6

2-4-3 What is the new status of the production order to be changed ?

$QVZHU� BBBBBBBBBB

3DWK��� �'RXEOH�FOLFN�RQ�WKH�RUGHU�QXPEHU

2-4-4 Carry out the process step for checking the changes.

3DWK� (',7�→ (;(&87(�352&(66�67(3

Select the step &KHFN�FKDQJHV

Page 238: LO 980 engineering change mgmt

© SAP AG LO980 8-44

2-4-5 What is the new status of the production order to be changed ?

$QVZHU� BBBBBBBBBB

2-4-6 Control the determined changes again and read the information provided by thesystem (warnings and errors).

Should the system display DQ�HUURU��UHG�OLJKW� then youhave to set this change action to µGR�QRW�FDUU\�RXW¶.Otherwise, you can QRW carry out the entire change processand finally, you can QRW complete the change.

In this case, proceed as follows:

Select the individual change information (line with the red light)

→(GLW�→ 6WDWXV�→ 6HW�µ'R�QRW�H[HFXWH¶

6DYH�WKLV�SURFHVVLQJ�DQG�RQO\�FRQWLQXH�ZKHQ�WKH�UHG�OLJKWKDV�JRQH�

2-4-7 Carry out the process step &KDQJH�RULJLQDO�RUGHU.

3DWK �(',7�→ (;(&87(�352&(66�67(3

Select the step &KDQJH�RULJLQDO�RUGHU

Page 239: LO 980 engineering change mgmt

© SAP AG LO980 8-45

3 In the original order, check the following information

3-1 Are both change process statuses (NOCH, CGFB) deleted ?

$QVZHU� BBBBBBBBBB

3-2 Have the changes been made ?

3-3 The history of the change process

3DWK� → *272�→ �&+$1*(�0$1$*(0(17

4 Carry out the change process for another flagged production order in one step.

Select the order and start with the change process.

3DWK� (',7�→ (;(&87(�352&(66�67(3

Select DOO�VWHSV of the change process.

Control the result of the change process.

Page 240: LO 980 engineering change mgmt

© SAP AG LO980 8-46

([HUFLVHV8QLW��2UGHU�&KDQJH�0DQDJHPHQW��2&0�7RSLF��6DOHV�2UGHU�±�&KDQJH�3URFHVVHV

• Create and change a sales order

• Selecting the change initiator (sales orders)

• Selecting the procurement elements (production orders)

• Carrying out the sales order change processes

In the course of time, changes in sales orders arise that affect theproduction orders.As a production scheduler, it is your SHUPDQHQW�MRE,to evaluate these changes with the help of the OCM – tools and toexecute or reject changes in production.

1-1 For the product 3���� enter a VDOHV�RUGHU with the following data:

3DWK� 6$3�0HQX�→�/RJLVWLFV�→�6DOHV��'LVWULEXWLRQ�→�6DOHV� → 2UGHU�→�&UHDWH� �9$��

Order type 7$ (Standard order)Sales organization ����Distribution channel �� (consumer sales)Division �� (cross division)Sales office ���� (Frankfurt)

Sold-to party ���� (Becker Ltd. Berlin)Goods recipient 1��� (Becker Ltd. Berlin)Purchase order number *5��B���Requested delivery date &XUUHQW�GDWH�����PRQWK

Material:�3����� Order quantity ��SLHFHCharacteristic value Pump medium ���Oil

Drive ���manualPump type ���Reciprocating pumpMax. pump height �� mPump capacity ���� L/hDirection of rotation ���rightPump execution ���constantSupport <HVDrawing <HVProtection against dry running 7

Page 241: LO 980 engineering change mgmt

© SAP AG LO980 8-47

Suction height ��Activity input ����

6DYH�WKH�VDOHV�RUGHU�DQG�QRWH�WKH�RUGHU�DQG�LWHP�QXPEHUV

Should the system recommend DQRWKHU�GHOLYHU\�GDWHconfirm it by clicking on the symbol

Order no. BBBBBBBBBBBBBBBBBBBBBBB� BBBBBBBB

1-2 Execute a PXOWL�OHYHO�053 (single-item planning)for a sales order.

Use the following inputs:

Create purchase requisition � (only planned orders)Planning mode � (Normal mode)Schedule lines � (No) Scheduling � (Lead time scheduling) 'R�QRW�DFWLYDWH�DQ\�RWKHU�VZLWFKHV��

3DWK� 6$3�0HQX�→�/RJLVWLFV�→�3URGXFWLRQ�→�5HTXLUHPHQWV�SODQQLQJ→ 3ODQQLQJ�→�6LQJOH�LWHP�VDOHV�RUGHU� �0'��

1-3 Control the VWRFN���UHTXLUHPHQWV�VLWXDWLRQ for the material 3����

3DWK� 6$3�0HQX�→�/RJLVWLFV�→�3URGXFWLRQ�→�5HTXLUHPHQWV�SODQQLQJ→ 5HSRUWLQJ�→�6WRFN�5HTXLUHPHQWV�/LVW�

� ����0'��

1-4 In the VWRFN���UHTXLUHPHQWV�OLVW convert the planned order that has been generated foryour sales order, into a production order release it and save.

.

Order no. _______________

3DWK� 6HOHFW�WKH�SODQQHG�RUGHU�E\�GRXEOH�FOLFNLQJ�RQ�LW�→&OLFN�WKH�EXWWRQ� �!�352'��25'(5

Page 242: LO 980 engineering change mgmt

© SAP AG LO980 8-48

1-5 For the production orders generated in ��� carry out a SDUWLDO�confirmation to operation���� with any actual date.

3DWK� 6$3�0HQX�→�/RJLVWLFV�→�3URGXFWLRQ�→�3URGXFWLRQ�&RQWURO→ &RQILUPDWLRQ�→�(QWHU�→�)RU�RSHUDWLRQ�→�7LPH�WLFNHW� �&2��1

2 With the following steps, carry out the VDOHV�RUGHU�±�FKDQJH�SURFHVV (OCM)for production orders.

2-1 The customer rings his sales office and wants the following changes to be madeto the sales order created in ���.Therefore, make the following characteristic value changes to the sales order:

3DWK� 6$3�0HQX�→�/RJLVWLFV�→�6DOHV��'LVWULEXWLRQ�→�6DOHV→ 2UGHU�→�&KDQJH� �9$��

→ %XWWRQ� ,WHP�GHWDLO�FRQILJXUDWLRQ

Characteristic value QHZ

Pump medium ���Waste waterPump type ���Vane cell pump

The system warns the sales person and reports the productionorders already in production.,JQRUH�WKH�ZDUQLQJ

6DYH�WKH�VDOHV�RUGHU�

2-2 Determine whether change flags (OCM) exist for your sales order?

Choose with the following settings

Sales order BBBBBBBBBBBBBBBBProcessing status 8QSURFHVVHGProcurement element to look for Production orders

3DWK� 6$3�0HQX�→�/RJLVWLFV�→�3URGXFWLRQ�→�3URGXFWLRQ�FRQWURO→ &RQWURO�→�2UGHU�FKDQJH�PDQDJHPHQW�→�&KDQJH�SURFHVV�→�,QLWLDWLQJREMHFW� �&2&0

Page 243: LO 980 engineering change mgmt

© SAP AG LO980 8-49

The system has to find your sales order change as a result ofthese steps. If this is not the case, then you have made amistake in the previous steps.If necessary, ask the trainer for assistance with this exercise.

2-3 Determine the production orders affected by changes to the sales order and save theresult.

3DWK��� �����→�(',7�→ 6($5&+�)25�352&85(0(17�(/(0(17

2-4 Now process the flags for the procurement elements (production orders) determined inthe previous step, in order to be able to carry out the actual change process.

Choose with the following settings

Procurement element 3URGXFWLRQ�RUGHUVReason for change DOOStatus change process 1R�UHVWULFWLRQV

3DWK� 6$3�0HQX�→�/RJLVWLFV�→�3URGXFWLRQ�→�3URGXFWLRQ�FRQWURO→ &RQWURO�→�2UGHU�FKDQJH�PDQDJHPHQW�→�&KDQJH�SURFHVV�→3URFXUHPHQW�HOHPHQW�IODJ� �&2&0�

2-5 Carry out the individual steps of the actual change process for the flagged production order.

2-5-1 Select the order and start with opening a simulation order

3DWK (',7�→ (;(&87(�352&(66�67(3

Select the step 2SHQ�VLPXODWLRQ�RUGHU

2-5-2 Control the structure and content of the simulation order

3DWK��� *RWR�→ 6LPXODWLRQ�RUGHU

2-5-3 Carry out the process step for determining and checking the changes.

3DWK�� (',7�→ (;(&87(�352&(66�67(3

Select the step 'HWHUPLQH�DQG�FKHFN�FKDQJHV

Page 244: LO 980 engineering change mgmt

© SAP AG LO980 8-50

2-5-4 Control the determined changes and read the information provided by thesystem (warnings and errors).

Should the system display DQ�HUURU��UHG�OLJKW� then youhave to set this change action to µGR�QRW�FDUU\�RXW¶.Otherwise, you can QRW carry out the entire change processand finally, you can QRW complete the change.

In this case, proceed as follows:

Select the individual change information (line with the red light)

→(GLW�→ 6WDWXV�→ 6HW�µ'R�QRW�H[HFXWH¶

6DYH�WKLV�SURFHVVLQJ�DQG�RQO\�FRQWLQXH�ZKHQ�WKH�UHG�OLJKWKDV�JRQH�

2-5-5 Carry out the process step &KDQJH�RULJLQDO�RUGHU.3DWK��� (',7�→ (;(&87(�352&(66�67(3Select the step &KDQJH�RULJLQDO�RUGHU

3 In the original order, check the following information

3-1 Are both change process statuses (NOCH, CGFB) deleted ?

$QVZHU� BBBBBBBBBB

3-2 Have the changes been made ?

3-3 The history of the change process

3DWK� → *272�→ �&+$1*(�0$1$*(0(17

Page 245: LO 980 engineering change mgmt

© SAP AG LO980 8-51

�6ROXWLRQV

8QLW��2UGHU�&KDQJH�0DQDJHPHQW��2&0�7RSLF��)RXQGDWLRQ�RI�(QJLQHHULQJ�&KDQJH0DQDJHPHQW

1-2-1 Answer: Yes (Sub profile PP0001 – General tab page 1.Flag)

1-2-2 Answer: Error (Sub profile PP0001 – Operation tab page 4.Flagfrom the bottom)

1-2-3 Answer: Warning (Sub profile PP0002 – Component tab page 2.Flag)

1-3 Results variant with mass changes

� 8VHU�PHQX�0DWHULDO��!�2WKHU��!�0DVV�PDLQWHQDQFH�«� �00��

Tables tab page: Select the lines 0$5&Fields tab page Find and select the line 0$5&�2&03)Execute

=> "Records to be changed"Material: all 5 material numbers using multiple selectionPlant: 1000Execute

=> "Plant data for material"New values: PP0001

EnterChange fields = Shift + F8Save

(Display possible messages)

Page 246: LO 980 engineering change mgmt

© SAP AG LO980 8-52

6ROXWLRQV8QLW��2UGHU�&KDQJH�0DQDJHPHQW��2&0�7RSLF��0DVWHU�'DWD�±�&KDQJH�3URFHVVHV

2-4-3 Answer: NOCH��&KDQJHV�QRW�DOORZHG�

2-4-5 Answer: CGFB��&RQILUPDWLRQV�DQG�JRRGV�PRYHPHQW�QRW�DOORZHG�

Page 247: LO 980 engineering change mgmt

© SAP AG LO980 8-53

6ROXWLRQV8QLW��2UGHU�&KDQJH�0DQDJHPHQW��2&0�7RSLF���6DOHV�2UGHU�±�&KDQJH�3URFHVVHV

3-1 Answer: Yes ��2UGHU�LV�IUHH�IRU�WKH�QH[W�FKDQJH�SURFHVV�

Page 248: LO 980 engineering change mgmt

© SAP AG LO980 9-1

SAP AG 1999

6XPPDU\

2EMHFW�&KDQJHV2EMHFW�&KDQJHV ��5HSRUWLQJ5HSRUWLQJ ��

�� &KDQJH�+LHUDUFK\��&KDQJH�+LHUDUFK\��5HOHDVH�.H\�5HOHDVH�.H\�«« ��&KDQJH�0DVWHU�5HFRUG&KDQJH�0DVWHU�5HFRUG

3URFHVVLQJ�&KDQJHV�3URFHVVLQJ�&KDQJHV�ZLWK�:RUNIORZZLWK�:RUNIORZ ��&RXUVH�2YHUYLHZ&RXUVH�2YHUYLHZ ��

(&5���(&2(&5���(&2 ��

6XPPDU\6XPPDU\ ��

2UGHU�&KDQJH�2UGHU�&KDQJH�0DQDJHPHQW��2&0�0DQDJHPHQW��2&0� ��

Page 249: LO 980 engineering change mgmt

© SAP AG LO980 9-2

SAP AG 1999

&RXUVH�2EMHFWLYHV

<RX�DUH�QRZ�DEOH�WR�

l You can recognize the interaction of changes on documents, material masters, BOMs, and routings.

l Support the change process using the standard workflow for Engineering Change Management

l Change production orders in a controlled manner with the help of Engineering Change Management and Order Change Management.

Page 250: LO 980 engineering change mgmt

© SAP AG LO980 9-3

SAP AG 1999

5HFRPPHQGHG�)ROORZ�XS�,QIRUPDWLRQ

l 6$3�/LEUDU\�/RJLVWLFV��/2�/RJLVWLFV���JHQHUDO�

l ������KWWS���ZZZ�VDS�FRP�SOP

l �3'0�3URGXFW�0DQDJHPHQW

/2���&KDQJH�0DQDJHPHQW

Page 251: LO 980 engineering change mgmt

© SAP AG LO980 9-4

SAP AG 1999

5HFRPPHQGHG�)ROORZ�XS�$FWLYLWLHV

l *R�WKURXJK�WKH�H[HUFLVHV�XVLQJ�,'(6�GDWD�RU�\RXU�RZQ�GDWDl 5HDG�RQ�OLQH�GRFXPHQWDWLRQl 5HDG�,0*�GRFXPHQWDWLRQl 5HDG�UHOHDVH�QRWHV

Page 252: LO 980 engineering change mgmt

© SAP AG LO980 10-1

SAP AG 1999

l 0HQX�SDWKVl $GGLWLRQDO�VOLGHV

&RQWHQWV�

$SSHQGL[

Page 253: LO 980 engineering change mgmt

© SAP AG LO980 10-2

)UHTXHQWO\�8VHG�0HQX�3DWKV$FWLYLWLHV 0HQX�SDWK(QJLQHHULQJ�&KDQJH�0DQDJHPHQW�Create change number CC01 ���6$3�0HQX�→����/RJLVWLFV�→����&HQWUDO�)XQFWLRQV�→

���(QJLQHHULQJ�&KDQJH�0DQDJHPHQW�→���&KDQJH�1XPEHU�→����&UHDWH

… change CC02 «→����&KDQJH… display CC03 «→����'LVSOD\Display material BOMchange documents

VHH�%LOO�RI�0DWHULDO��%20�

Change Overview CC05 ���5HSRUWLQJ�→����&KDQJH�2YHUYLHZ

Customizing: Change typesECR OS56

���6$3�0HQX�→����7RROV→����$FFHOHUDWHG6$3�→���&XVWRPL]LQJ�→����(GLW�SURMHFW�→����6$3�5HIHUHQFH,0*→����/RJLVWLFV���*HQHUDO�→����(QJLQHHULQJ�&KDQJH0DQDJHPHQW�→����&KDQJH�7\SH→�����'HILQH�&KDQJH�7\SHV�IRU�&KDQJH�0DVWHU5HFRUGV

Customizing: Change typesobject management recordOS58

«�→�����'HILQH�&KDQJH�7\SHV�IRU�2EMHFWV

CustomizingComplete change profileOPL9

���6$3�0HQX�→����3URGXFWLRQ�→����3URGXFWLRQ�&RQWURO→����2SHUDWLRQV�→����&KDQJH�PDQDJHPHQW�IRUSURGXFWLRQ�RUGHUV��2&0��→����&RPSOHWH�FKDQJHSURILOH

CustomizingPartial change profile OPL7

«�→����'HILQH�FKDQJH�SURILOH

Page 254: LO 980 engineering change mgmt

© SAP AG LO980 10-3

$FWLYLWLHV 0HQX�SDWK0DVWHU�GDWD�PDLQWHQDQFH�(QJLQHHULQJ�:RUNEHQFKEngineering Workbench CWBPPCEWB

���6$3�0HQX�→����/RJLVWLFV�→����3URGXFWLRQ�→���0DVWHU�'DWD�→���(QJLQHHULQJ�:RUNEHQFK

%20�Create material BOM CS01 ���6$3�0HQX�→����/RJLVWLFV�→����3URGXFWLRQ�→���

0DVWHU�'DWD�→���%LOOV�RI�0DWHULDO�→���%LOO�RI�0DWHULDO�→����0DWHULDO%20�→����&UHDWH

… change CS02 «→����&KDQJH… display CS03 «→����'LVSOD\Display material BOMchange documents CS80

«→����%LOOV�RI�0DWHULDO�→����(YDOXDWLRQV�→����&KDQJH'RFXPHQWV�→����0DWHULDO�%20

Material BOM explosionlevel by level CS11

«→����%LOOV�RI�0DWHULDO�→����(YDOXDWLRQV�→����%20([SORVLRQ�→����0DWHULDO�%20→����%20��0XOWL�/HYHO�

0DWHULDO�PDVWHU�UHFRUG�Schedule material mastercreation MM11

���6$3�0HQX�→����/RJLVWLFV�→����3URGXFWLRQ�→���0DVWHU�'DWD�→���0DWHULDO�0DVWHU�→���0DWHULDO�→����&UHDWH��*HQHUDO�→����6FKHGXOH

Schedule change MM12 ���&KDQJH�→����6FKHGXOHChange immediately MM02 ���&KDQJH�→����,PPHGLDWHO\Schedule display MM19 ���'LVSOD\�→����'LVSOD\�DW�.H\�'DWH

$FWLYLWLHV 0HQX�SDWK5RXWLQJCreate routing CA01 «�→����5RXWLQJV�→����5RXWLQJV�→����6WDQGDUG

5RXWLQJV�→����&UHDWH… change CA02 «→����&KDQJH… display CA03 «�→����'LVSOD\Task List Changes ���5HSRUWLQJ�→����7DVN�/LVW�&KDQJHV

Page 255: LO 980 engineering change mgmt

© SAP AG LO980 10-4

$FWLYLWLHV 0HQX�SDWKRouting change documentsCA61

���5HSRUWLQJ�→����&KDQJH�'RFXPHQWV�→����5RXWLQJ

2EMHFWV�LQ�WKH�&ODVVLILFDWLRQ�6\VWHP�Characteristics maintenance ���6$3�0HQX�→����/RJLVWLFV�→����&HQWUDO�)XQFWLRQV�→

���&ODVVLILFDWLRQ�→���0DVWHU�'DWD�→����&KDUDFWHULVWLFV

Class maintenance «→����&ODVVHVClassification:n objects to a class CL24N

���$VVLJQPHQW�→����$VVLJQ�2EMHFWV�&ODVVHV�WR�&ODVV

2EMHFWV�LQ�WKH�9DULDQW�0HQX�Display simple dependency ���6$3�0HQX�→����/RJLVWLFV�→����&HQWUDO�)XQFWLRQV�→

���9DULDQW�&RQILJXUDWLRQ�→���'HSHQGHQF\�→����6LQJOH�'HSHQGHQF\�→����'LVSOD\

… change «→����&KDQJH… create «�→����&UHDWHDisplay constraints &networks

���6$3�0HQX�→����/RJLVWLFV�→����&HQWUDO�)XQFWLRQV�→���9DULDQW�&RQILJXUDWLRQ�→���'HSHQGHQF\�→����'HSHQGHQF\�QHW�→����'LVSOD\

… change «→����&KDQJH… create «�→����&UHDWHDisplay configuration profile ���6$3�0HQX�→����/RJLVWLFV�→����&HQWUDO�)XQFWLRQV�→

���9DULDQW�&RQILJXUDWLRQ→���&RQILJXUDWLRQ�3URILOH�→����'LVSOD\

… change «→����&KDQJH… create «�→����&UHDWH

$FWLYLWLHV 0HQX�SDWK:RUNIORZWorkflow inbox for the workcenter SBWP

���6$3�0HQX�→����2IILFH�→����:RUNSODFH→����,QER[�→����:RUNIORZ

Create organizationalstructure PPOC

��� 6$3�0HQX�→����7RROV→����%XVLQHVV�:RUNIORZ�→����'HYHORSPHQW→����'HILQLWLRQ�7RROV→����2UJDQL]DWLRQDO�0DQDJHPHQW→����2UJDQL]DWLRQDO�3ODQ�→����&UHDWH

Assign SAP OrganizationalObject PFOM

«→����6$3�2UJ2EMHFWV�→����&UHDWH�$VVLJQPHQWV

6DOHV�3ODQQLQJ�3URGXFWLRQ

Page 256: LO 980 engineering change mgmt

© SAP AG LO980 10-5

$FWLYLWLHV 0HQX�SDWKCreate sales orderVA01

���6$3�0HQX�→����/RJLVWLFV�→����6DOHV�DQG'LVWULEXWLRQ�→����6DOHV�→���2UGHU�→����&UHDWH

Create planned independentrequirements (0'��):

«�→����3URGXFWLRQ�→����3URGXFWLRQ�3ODQQLQJ→����'HPDQG�0DQDJHPHQW�→����3ODQQHG�,QGHSHQGHQW5HTXLUHPHQWV→����&UHDWH

Create planned independentrequirements (0'��):

«�→����053�→����3ODQQLQJ�→����6LQJOH�,WHP��6DOHV2UGHU

Create production order CO01 «�→����3URGXFWLRQ�→����3URGXFWLRQ�&RQWURO→����2UGHU�→����&UHDWH�→����:LWK�0DWHULDO

Production order collectiverelease CO05N

«�→����&RQWURO�→�����&ROOHFWLYH�UHOHDVH

Confirmation (Time ticket)CO11N

«�→����&RQILUPDWLRQ�→����(QWHU�→����)RU�2SHUDWLRQ�→���7LPH�7LFNHW

2&0Initiating object COCM ���6$3�0HQX�→����/RJLVWLFV�→����3URGXFWLRQ�→���

3URGXFWLRQ�&RQWURO�→����&RQWURO�→����2UGHU�&KDQJH0DQDJHPHQW�→����&KDQJH�3URFHVV�→����,QLWLDWLQJ2EMHFWV

Procurement elementsCOCM1

→����3URFXUHPHQW�HOHPHQW�FKDQJH�UHFRUGV

Page 257: LO 980 engineering change mgmt

© SAP AG LO980 10-6

SAP AG 1999

6WDWXV�PDQDJHPHQW

6WDWXV�SURILOHV

(&0�JHQHUDO������ ����&RQWURO�GDWD��SDUW���

(&5V���2EMHFWV�

'HILQH�FKDQJH�W\SHV

&RQWURO�GDWD��SDUW���5HYLVLRQ�OHYHO�PDQDJHPHQW�

(IIHFWLYLW\�W\SHV

5HOHDVH�NH\

'HILQH�UHYLVLRQ�OHYHOV

&RQILJXUDWLRQ�6HTXHQFH�IRU�(&0

n First you make general settings for (QJLQHHULQJ�&KDQJH�0DQDJHPHQW: effectivity, date shift, numberranges, object maintenance, revision levels, statuses

n New effectivity types and release keys

n Then you make settings for the ECR/ECO and the object management record (if necessary): statusprofiles (user status), change types.

n Finally you make settings for status management (if necessary): activating revision levelmanagement, defining the sequence of revision levels.

n Please note that you can make further settings that affect (QJLQHHULQJ�&KDQJH�0DQDJHPHQW inCustomizing for each individual object (for example, BOM).

Page 258: LO 980 engineering change mgmt

© SAP AG LO980 10-7

SAP AG 1999

+LVWRU\�UHTXLUHPHQW�IRU�%20V

'HILQH�GRFXPHQW�VWDWXV

%20�PDQDJHPHQW� ����0RGLILFDWLRQ�SDUDPHWHUV

'RFXPHQW�PDQDJHPHQW�

5HYLVLRQ�OHYHO�DVVLJQPHQW�IRU�GRF��W\SH

'HILQH�ILHOG�VHOHFWLRQ5RXWLQJ�

2WKHU�6HWWLQJV�IRU�(QJLQHHULQJ�&KDQJH�0JPW

n BOM: modification parameters (activating engineering change management especially for BOMs),history requirement (dependently of BOM usage and status).

n Document: document status (setting to determine whether you can regard a specific status ascomplete in terms of engineering change management). Document type (whether revision levelassignment is allowed).

n Routing: Field selection (when you make settings on the selection screen for PP routings, you candetermine whether the entry for the change number is required or optional).

Page 259: LO 980 engineering change mgmt

© SAP AG LO980 10-8

SAP AG 1999

1��,WHP������FUHDWHG

1��$,WHP������GHOHWHG

&KDQJH�PDVWHU�UHFRUG����

&KDQJH�QXPEHU�1��,WHP�������1(:

����EHIRUH�GHOHWLRQ

&KDQJH�QXPEHU�1��,WHP�������,QQ

,WHP�������,QG

����DIWHU�GHOHWLRQ

&KDQJH�QXPEHU�1��$

([DPSOHV�IRU�3URFHVVLQJ�,QGLFDWRUV

n Item 0010 is created with reference to the change number N-1.

n Then it is deleted with reference to the change number N-1A. Change numbers N-1 and N-1A havethe same YDOLG�IURP date.

n &KDQJH�PDVWHU�UHFRUG�1��Before deletion, item 0010 is identified by the processing indicator 1(: in this change masterrecord. After deletion, the item record is identified as being inactive (invalid) with the processingindicator ,QQ (the item starts with the change number N-1).

n &KDQJH�PDVWHU�UHFRUG�1��$In this change master record the item 0010 is also identified as being inactive after deletion, this timewith processing indicator ,QG (the item ends with the change number N-1A).

Page 260: LO 980 engineering change mgmt

© SAP AG LO980 10-9

SAP AG 1999

������� ��

��� ������������� ����������

��� ������������� ����������

���������� �! "��

#��%$���& �� ��

' ��(*)���+� ,! ��&- !.& �

$UFKLYLQJ

n Archiving of change numbers takes place for the change numbers and not for the changesthemselves.

n Archiving takes place after a flexible selection of the change numbers

é It can also take place irrespective of the deletion flag that is set for a change number.

n Archiving can be controlled to take place at a certain time on a certain date and it is alwaysdocumented in a log.

Page 261: LO 980 engineering change mgmt

© SAP AG LO980 10-10

SAP AG 1999

'HYHORSPHQW�FODVV�HV�)XQFWLRQ�JURXS�V�0RGXOH�SRRO/RJLFDO�GDWDEDVH�V�

&&&&����6$30&��&/2B&+$1*(B0107

1XPEHU�UDQJH�REMHFW�V�15�HOHPHQW

15�JURXS�WDEOH15�JURXS�V�15�WUDQVDFWLRQ$XWKRUL]DWLRQ�FODVV$XWKRUL]DWLRQ�REMHFW�V�

$(115([WHUQDO�QR��DVVJW�IURP�DQ\�QR��UDQJH���UHVHUYHG�IRU�LQWHUQDO�QR��DVVJW1RQH1RQH&&��3URGXFWLRQ�SODQQLQJ&B$(15B%*5�&B$(15B59���&B$(15B59�

/RFN�REMHFW�V�&KDQJH�GRFXPHQW�REMHFW

(&$(15(��(&$(156$(115

0DWFKFRGH�REMHFW�V�0HVVDJH�FODVV�HV�$UFKLYLQJ�FODVV$UFKLYLQJ�REMHFW

$(1�&&�/2B&+$1*(0

7HFKQLFDO�'HWDLOV�IRU�(&0

n You can use an authorization object (belonging to a certain authorization group) to control who canprocess specific change master records or ECRs/ECOs.

n Please note that there are also authorization objects for the object changes. These authorizationobjects are object type specific.

Page 262: LO 980 engineering change mgmt

© SAP AG LO980 10-11

SAP AG 1999

$(15

$(2,

$('7$(19$(()

$(+,

7DEOH�6WUXFWXUH�IRU�(&0

n Each table contains the following data:

é AENR General data for the change master record

é AEEF Effectivity data

é AENV Object types with a specific change number

é AEOI Object management record

é AEDT Alternative date

é AEHI Change hierarchy