SAP 4.6 LO980 engineering change mgmt

50 %
50 %
Information about SAP 4.6 LO980 engineering change mgmt
Software

Published on October 7, 2014

Author: edfgaviria

Source: slideshare.net

Description

SAP 4.6 LO980 engineering change mgmt

1. © SAP AG 1999 LO980 Engineering Change Management /2/2 (QJLQHHULQJ &KDQJH 0DQDJHPHQW (QJLQHHULQJ &KDQJH 0DQDJHPHQW n R/3 System n Release 4.6C n November 2000 n Material Number 5004 1897

2. © SAP AG 1999 &RSULJKW  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 SULRU FRQVHQW RI 6$3 $* 7KH LQIRUPDWLRQ FRQWDLQHG LQ WKLV GRFXPHQW LV VXEMHFW WR FKDQJH DQG VXSSOHPHQW ZLWKRXW SULRU QRWLFH $OO ULJKWV UHVHUYHG &RSULJKW 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 of Technology, 545 Technology Square, Cambridge, MA 02139. n JAVA® is a registered trademark of Sun Microsystems, Inc. , 901 San Antonio Road, Palo Alto, CA 94303 USA. n JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. n SAP, SAP Logo, mySAP.com, mySAP.com Marketplace, mySAP.com Workplace, mySAP.com Business Scenarios, mySAP.com Application Hosting, WebFlow, R/2, R/3, RIVA, ABAP™, SAP Business Workflow, SAP EarlyWatch, SAP ArchiveLink, BAPI, SAPPHIRE, Management Cockpit, SEM, are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies. n Design: SAP Communications Media

3. © SAP AG 1999 3URGXFW /LIHFFOH 0DQDJHPHQW 3/0

4. Product Lifecycle Management  ¢¡¤£¦¥§£ 3 days /HYHO  /HYHO  Basic Data for Discrete Manufacturing  ¦¡©¨¢£§ 3 days Document Management System  ¦¡©¥¢§ 3 days Engineering Change Management  ¦¡¤¥¦§£ 3 days Variant Configuration Part 1  ¦¡©¥¢¥§£ 5 days Classification  ¦¡¤¥¦§ 3 days Variant Configuration Part 2  ¢¡¤¥¦¥ 3 days

5. © SAP AG 1999 3URGXFWLRQ 3ODQQLQJ /HYHO  /HYHO  Manufacturing Planning & Execution for Discrete & Repetitive  ¦¡£§§£ 5 days Engineering Change Management  ¦¡¥§¢£ 3 days Batch Management  ¦¡©¥¢§ 3 days KANBAN  ¦¡¨§§ 2 days Classification  ¦¡¥§¢ 3 days Special Features of LIS in Production  ¦¡¤¨¦§ 2 days Logistics Info Planning  ¦¡¤¥¦§ 2 days CAP Calculation of Standard Values  ¦¡¤¦¨§£ 2 days Repetitive Manufacturing  ¦¡¨§¨¦ 3 days Capacity Planning  ¦¡¤¨¦§£ 5 days Logistics Information System (LIS) Reporting  ¦¡¥§¦£ 2 days Basic Data Part 2  ¦¡¨§£¦ 3 days Basic Data for Discrete Manufacturing  ¦¡¨§£§ 3 days Production Orders  ¦¡¨ 5 days Production Planning  ¦¡¨£ 5 days Variant Configuration Part 1  ¦¡¤¥¦¥§£ 5 days Variant Configuration Part 2  ¦¡¥§¥ 3 days

6. © 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 and control, as well as ECM within a company l $OVR UHFRPPHQGHG l /2 - Production Orders

7. © SAP AG 1999 l 3DUWLFLSDQWV  3URMHFW WHDP PHPEHUV &RQVXOWDQWV 2UJDQL]HUV

8.  ZKR DUH UHVSRQVLEOH IRU WKH LPSOHPHQWDWLRQ RI 5 6VWHP VROXWLRQV IRU WKH (&0 RI PDVWHU GDWD DQG SURGXFWLRQ RUGHUV 3URGXFWLRQ

9.   7HDP OHDGHUV DQG HPSORHHV WKDW KDYH WR ZRUN ZLWK (QJLQHHULQJ &KDQJH 0DQDJHPHQW GHVLJQ HQJLQHHUV SURGXFWLRQ VFKHGXOHUV DQG VR RQ

10.  7DUJHW *URXS l 'XUDWLRQ  GDV 1RWHV WR WKH XVHU n 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.

11. © SAP AG LO980 1-1 © SAP AG 1999 l &RXUVH *RDOV l &RXUVH 2EMHFWLYHV l &RXUVH &RQWHQW l &RXUVH 2YHUYLHZ 'LDJUDP l 0DLQ %XVLQHVV 6FHQDULR &RQWHQWV &RXUVH 2YHUYLHZ

12. © 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 change management for basic data and production orders.

13. © 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 Management l Change production orders in a controlled manner with the help of Engineering Change Management and Order Change Management

14. © 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

15. © SAP AG LO980 1-5 © SAP AG 1999 Unit 1 &RXUVH 2YHUYLHZ Unit 2 &KDQJH 0DVWHU 5HFRUGV Unit 3 2EMHFW &KDQJHV Unit 4 5HSRUWLQJ Unit 5 (&5(&2 Unit 6 3URFHVVLQJ &KDQJHV ZLWK :RUNIORZ 3UHIDFH $SSHQGL[ &RXUVH &RQWHQW Unit 7 &KDQJH +LHUDUFKLHV 5HOHDVH .H 3DUDPHWHU (IIHFWLYLW Unit 8 2UGHU &KDQJH 0DQDJHPHQW 2&0

16. Unit 9 &RQFOXVLRQ

17. © SAP AG LO980 1-6 © SAP AG 1999 &RXUVH 2YHUYLHZ 'LDJUDP 2EMHFW &KDQJHV2EMHFW &KDQJHV  5HSRUWLQJ5HSRUWLQJ  6XPPDU6XPPDU  2UGHU &KDQJH2UGHU &KDQJH 0DQDJHPHQW 2&0

18. 0DQDJHPHQW 2&0

19.   &KDQJH +LHUDUFK&KDQJH +LHUDUFK 5HOHDVH .H5HOHDVH .H«« &KDQJH 0DVWHU 5HFRUG&KDQJH 0DVWHU 5HFRUG 3URFHVVLQJ &KDQJHV3URFHVVLQJ &KDQJHV ZLWK :RUNIORZZLWK :RUNIORZ &RXUVH 2YHUYLHZ&RXUVH 2YHUYLHZ  (&5  (&2(&5  (&2 

20. © SAP AG LO980 1-7 © SAP AG 1999 1HZ GHYHORSPHQW DQG FKDQJHV WR UHOHYDQW SURGXFWV DUH WKH GDLO WDVNV RI D FRPSDQ 7KH SRVH DW OHDVW RQH 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 DOZDV EH FRQWUROOHG DV FKDQJHDEOH 0DLQ %XVLQHVV 6FHQDULR

21. © SAP AG LO980 2-1 © SAP AG 1999 &RQWHQWV l ,QWHJUDWLRQ LQ WKH 5 6VWHP l &KDQJHV ZLWK +LVWRU l /LQNHG 2EMHFWV l 6WUXFWXUH DQG )XQFWLRQV RI WKH &KDQJH 0DVWHU 5HFRUG l 2EMHFW PDQDJHPHQW UHFRUGV l $OWHUQDWLYH GDWHV l 3URGXFW 6WUXFWXUH &KDQJH 0DVWHU 5HFRUG

22. © 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 &KDQJH 0DQDJHPHQW ZLWK WKH KHOS RI WKH SURGXFW VWUXFWXUH &KDQJH 0DVWHU 5HFRUG 7RSLF 2EMHFWLYHV

23. © SAP AG LO980 2-3 © SAP AG 1999 &RXUVH 2YHUYLHZ 'LDJUDP 2EMHFW &KDQJHV2EMHFW &KDQJHV  5HSRUWLQJ5HSRUWLQJ   &KDQJH +LHUDUFK&KDQJH +LHUDUFK 5HOHDVH .H5HOHDVH .H««  3URFHVVLQJ &KDQJHV3URFHVVLQJ &KDQJHV ZLWK :RUNIORZZLWK :RUNIORZ &RXUVH 2YHUYLHZ&RXUVH 2YHUYLHZ  (&5  (&2(&5  (&2  &KDQJH 0DVWHU 5HFRUG&KDQJH 0DVWHU 5HFRUG 6XPPDU6XPPDU  2UGHU &KDQJH2UGHU &KDQJH 0DQDJHPHQW 2&0

24. 0DQDJHPHQW 2&0

25. 

26. © SAP AG LO980 2-4 © SAP AG 1999 &KDQJH 0DVWHU 5HFRUG %XVLQHVV 6HQDULR l 7KH FHQWUDO (QJLQHHULQJ &KDQJH 0DQDJHPHQW OHDUQV WKH IXQFWLRQV DQG WKH VWUXFWXUH RI WKH FKDQJH PDVWHUV l )RU H[DPSOH D %20 LV FKDQJHG ZLWK WKH KHOS RI WKH SURGXFW VWUXFWXUH DQG WKH HIIHFWV GLVSODHG

27. © SAP AG LO980 2-5 © SAP AG 1999 (QJLQHHULQJ &KDQJH 0DQDJHPHQW 3DUW RI 3'0 &ODVVLILFDWLRQ&ODVVLILFDWLRQ 3URMHFW3URMHFW 6VWHP6VWHP 'RFXPHQW'RFXPHQW PDQDJHPHQWPDQDJHPHQW 9DULDQW9DULDQW FRQILJXUDWLRQFRQILJXUDWLRQ 0DVWHU GDWD0DVWHU GDWD ¡£¢¥¤§¦©¨¢  "!$#%"&'"!$#%( &$' LQWHUIDFH&$' LQWHUIDFH (QJLQHHULQJ &KDQJH 0DQDJHPHQW é Engineering Change Management is a central, integral part of Product Data Management (PDM) in the 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

28. © SAP AG LO980 2-6 © SAP AG 1999 IRU GLIIHUHQW REMHFWVIRU GLIIHUHQW REMHFWV IRU WKH VDPH RU GLIIHUHQWIRU WKH VDPH RU GLIIHUHQW SRLQWV LQ WLPHSRLQWV LQ WLPH ZLWK VSHFLDO FRPSUHKHQVLYHZLWK VSHFLDO FRPSUHKHQVLYH GRFXPHQWDWLRQGRFXPHQWDWLRQ :K 0DNH &KDQJHV ZLWK (QJLQHHULQJ &KDQJH 0DQDJHPHQW" 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

29. © SAP AG LO980 2-7 © SAP AG 1999 )1032465 798A@¥B 8C4D4FEGB 8A@ )143E H¥BIC4 P1Q ERI3SC0D5AB 8D@P EUT3V Q I6WXBT18 Y 203838`B8A@ P EUT3V Q I6WXBT18 a Q 032 BWcb d 0`8C0A@e4Afg438CW P EUTihU4DI6W d 038D0e@e4Ffp438CW 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 the production and converted in the production orders, have to be changed. For this, you use the R/3 System 2UGHU &KDQJH 0DQDJHPHQW (OCM). It enables product structures to be converted into production structures and processes at the earliest time necessary using MRP and also for them to be changed at the last possible moment. It is also possible to adapt processed production orders to the changed product structure. The changes can either be initiated by a changed customer requirement or by a design change using a change master record.

30. © SAP AG LO980 2-8 © SAP AG 1999 :LWK KLVWRU:LWK KLVWRU q :LWKRXW KLVWRU:LWKRXW KLVWRU r s t ¦3u r vs t ¦¥u r s t ¦3u wyx ¢ t1€ ¦ s r©©‚9ƒ ¦ t ¤G„ q wyx ¢ t€ ¦ s r©‚9ƒ ¦ t ¤G„ &KDQJH 'RFXPHQWV DQG +LVWRU :LWKRXW KLVWRU:LWKRXW KLVWRU EXWEXW ZLWKZLWK FKDQJH GRFXPHQWVFKDQJH GRFXPHQWV n You can perform object changes (for example, BOM and routing changes) in the SAP R/3 System either ZLWK or ZLWKRXW KLVWRU. However, you should be aware that WKH VVWHP JHQHUDWHV FKDQJH GRFXPHQWV 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 the development 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 the object 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. These change 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 changes completely. Some of these changes may be needed for product liability purposes, for example.

31. © 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" " …¥…†…¥…†……¥…†…¥…†……¥…†…¥…†…

32. © SAP AG LO980 2-10 © SAP AG 1999 &KDQJLQJ D %20 8VLQJ D &KDQJH 0DVWHU 5HFRUG ‡ˆSC0F8e@34 f‰0i5DWc4FE9Ec4DIDT`EUV ’‘ v¨“¢  ¢†„© t9€’‘ v¨X¢  ¢`„© t1€ ’x ¢`”§¤gx ¢`”§¤ • ‚9ƒ ‘• ‚9ƒ ‘ !©–—u x ¦¥¦!–˜u x ¦†¦© ’‘ v¨X¢  ¢¥„© t1€p‘ v¨X¢©  ¢`„™ t1€ px ¢¥”d¤’x ¢¥”§¤ • ‚9ƒ ‘fe• ‚9ƒ ‘fe !–—u x ¦¥¦ e!©–—u x ¦¥¦™ e n If you change a BOM using the change master record, the system saves both the status before and after the change.

33. © SAP AG LO980 2-11 © SAP AG 1999 7DVN OLVWV g  rh‚ ¤i t1€ g j¦`”G¦¨“¦ t1 ¦ r ‘ ¦¨X¢¥¤i rht „1¦¥¤ g j¦`”G¦¨“¦ t1 ¦k¨X¢†¤§¦l¨ rh‚ ¤m t9€ gon t „ ‘ ¦  ¤m rpt ‘ ¢ t ghqhr ‚ ‘ ƒ ¦ t ¤©¤X¢†„©s—R„1¤ g ¡t¢`„†¤§¦©¨ˆ¨“¦  ‘ ¦ gu ¦ t ¦©¨G¢© ƒ ¢ t ¤X¦ t ¢ t1 ¦ %20V g ¡v¢¥¤X¦¨¢†wxt¡v„ gpy r©9‚9ƒ ¦ t ¤™„¥¤z¨ ‚1 ¤ ‚ ¨“¦ gpqor ‚ ‘ ƒ ¦ t ¤ˆwˆ—¡ g ! ‚©t1 ¤zrht ¢©¥ r™ ¢¥¤i r{t wjt¡ g  ¢©¦¥„ r ¨“s¦¨jwj£¡ 0DVWHU PDVWHUV &KDUDFWHULVWLFV &KDUDFWHULVWLFV RI FODVV &ODVVLILFDWLRQ 'RFXPHQWV &RQILJXUDWLRQ SURILOH 2EMHFW GHSHQGHQFLHV 9DULDQW WDEOH |~}iU€‚Gƒ|z}mU€‚§ƒ „c…c†R‡‰ˆŠ†v‹§ŒdŽGc‘D’ “” •§–—˜ “™v“” š” ™” 6XEVWDQFH 3KUDVH 'DQJHURXV JRRGV /LQNHG 2EMHFW 7SHV &KDQJH PDVWHU UHFRUG

34. © SAP AG LO980 2-12 © SAP AG 1999 5HDVRQ IRU FKDQJH 9DOLG IURP 6WDWXV &KDQJH KHDGHU&KDQJH KHDGHU 0DWHULDO PDVWHU UHFRUG %20V 5RXWLQJV  2EMHFW PJPW UHFRUGV2EMHFW PJPW UHFRUGV $OWHUQDWLYH GDWHV$OWHUQDWLYH GDWHV $FFRPSDQLQJ GRFXPHQWV$FFRPSDQLQJ GRFXPHQWV 2EMHFW WSHV2EMHFW WSHV &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 change status. n You determine which objects can be changed with the change master record by selecting the object types. n One of the functions of the object management record is to enable you to document changes to a specific 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.

35. © SAP AG LO980 2-13 © SAP AG 1999 'HVFULSWLRQ &KDQJH QXPEHU  ORQJ WH[W 9DOLGIURP GDWH  HIIHFWLYLW &KDQJH QXPEHU VWDWXV  UHOHDVH NH $XWKRUL]DWLRQ JURXS 5HDVRQ IRU FKDQJH  DFFRPSDQLQJ GRFXPHQWV › œ§œ§œ§œdœœ§œ§œ§œdœœ§œ§œ§œdœ $GPLQLVWUDWLYH GDWD &KDQJH KHDGHU&KDQJH KHDGHU &KDQJH +HDGHU 'DWD

36. © SAP AG LO980 2-14 © SAP AG 1999 2EMHFW 7SH ,QGLFDWRUV $FWLYH2EMHFW WSH ;%LOO RI PDWHULDO ;7DVN OLVW ;'RFXPHQW ;0DWHULDO &KDUDFWHULVWLF  &ODVV ; 2EMHFW ; ;

37. /RFN ; *HQGLDO*HQQHZ0JW5HF ;; ; ; The following indicators control processing with the change number for the individual object types: n $FWLYH REMHFW WSH IRU WKH FKDQJH QXPEHU LV DFWLYH You must set this indicator if you want to process 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, then you can only make a change to an object of the object type concerned if you create an object management record for the object first. n 0JW5HF REMHFW PDQDJHPHQW UHFRUG LV JHQHUDWHG If you set this indicator, the system generates an object management record automatically when you process (create or change) an object of the object type concerned with the change number. If you set this indicator, you can make changes to all objects of the object type with the change number. n *HQ QHZ REMHFW PDQDJHPHQW UHFRUG LV RQO JHQHUDWHG DXWRPDWLFDOO ZKHQ RX FUHDWH DQ REMHFW IRU WKH ILUVW WLPH If you set this indicator, an object management record is only created automatically when you create an object of the object type concerned. If you want to process an existing 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 DQ REMHFW PDQDJHPHQW UHFRUG LQ GLDORJ When the object management record is generated automatically, the system branches to a dialog screen where you can enter object-specific documentation (exception: (Exception: Sales order BOM) n /RFN REMHFW WSH ORFNHG IRU FKDQJHV You can lock and unlock the object type as required.

38. © SAP AG LO980 2-15 © SAP AG 1999 &KDQJH PDVWHU UHFRUG 2EMHFW WSH2EMHFW WSH  2EMHFW d 0CWc4FEGB032 P¥RžCŸA  2EMHFW ¡9¢ d£P¥d ‰ŸDŸC¤A iŸCŸDŸC¤3  2EMHFW PJPW UHFRUG 2EMHFW 0DWHULDO 3 2EMHFW d 0CWU4AEGB032 P3G ¥ŸDŸ 2EMHFW PJPW UHFRUG 2EMHFW 0DWHULDO 3 2EMHFW PDQDJHPHQW UHFRUG 2EMHFW   +HDGHU+HDGHU 2EMHFW WSH2EMHFW WSH 0DWHULDO0DWHULDO 2EMHFW WSH2EMHFW WSH %20%20 $VVLJQPHQW DQG 'DWD IRU WKH 2EMHFW 0JPW 5HFRUGV ¦ 465eIAEGB Y WGBT18¨§¥©AT`8A@ªWU4‰«eW ¬ 032 BV v­ EUT`f®V306Wc4¯§ ° 2WU4FE§8e06WGBHe4pV30‰Wd4 ©AT3IF± ° V¥fvB 8FB5CWGEc06WGBHD4gV30‰WU0 F­ T¥E`T1²h§4DI6W`f‰@`fpW9Ec4DIDT¥EdV F­ T¥E`T1²h§4DI6W3I3SC0`8C@34 ° 5D53B@¥8e4DVyT1²zh§4DI6W 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 therefore change number-specific. n When you enter objects in the object overview of the change master record, an object management record is created in the background. You can create any number of object management records for a change 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 (for example, material number). n 2EMHFW PDQDJHPHQW UHFRUG GHVFULSWLRQ You describe the change or reason for the change. You can also enter a long text. n 9DOLGIURP GDWH  DVVLJQPHQW RI DOWHUQDWLYH GDWHV The change made to the assigned object with reference to the change number becomes effective from this date. This date comes from the change header or from the assignment of the alternative date. n /RFN If you set this indicator, you can temporarily lock the assigned object against eventual changes with reference to a change number. n $GPLQLVWUDWLYH GDWD IRU REMHFW PDQDJHPHQW UHFRUG DQG IRU FKDQJHV WR DVVLJQHG REMHFWV Change date, last person to make the change...

39. © SAP AG LO980 2-16 © SAP AG 1999 W $ +HDGHU % &KDQJH PDVWHU UHFRUG 0DWHULDO 3 %20 3   0DWHULDO 3 %20 3   2EMHFW WSH2EMHFW WSH 0DWHULDO0DWHULDO 2EMHFW WSH2EMHFW WSH %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 the change number become effective. If you want to override this for an object, then you must create alternative dates. The alternative date only exists within the change master record. You then assign these 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 sets the object assignments indicator for this alternative date.

40. © SAP AG LO980 2-17 © SAP AG 1999 6HOHFWLQJ 2EMHFWV IURP WKH 3URGXFW 6WUXFWXUH YLD *RWR 2EMHFW VHOHFWLRQ &WUO  )

41. RX JRWR ³~´ µz¶~·i¸G¹~ºG¹ ´· m¸G¹ ·z´ » ¼‰½zµ´¹m¹ »§¾“¹³~·z¿9À ÁgÂ¥ÃDĥťÆÇxÄ3ÈUĆťÆUÉUÊ9ËhÌ1ÍxÎ~Ê©Ï©ÐoÅ¥Æ9ÇxÆUΥЩņƧÐ1봀 ¼‰»“Ñ»“¸G¹ ÒFÓiÔmӓÕz» ¼¥Ó§Öz» × ½zӓÔmÕ»¥Ôz·m¿9Øm»i´ Ùi»“º“¸i´ ÚÀX¹ Úµ~Ô ÒFÓG¹»i´ ÚӓÑiÛiÜ3ÒAº Ý~Þ·mÚÀ¿¥»mԓ¹iÛ¥Ü3ÒAº ىµ¸“·z¿1»iԓ¹ºX¹ ´· m¸§¹ ·´»Xº ßm·zÔz¸§¹ Úµ~ÔmÓiÑXѵz¸XÓX¹ Úµ~Ô9ÛiÜFÒAº ىµ¸“·z¿1»iԓ¹º ÒFÓG¹»i´ ÚӓѺ ài»GÖzÚºmÚµzÔ9Ñ»GÖm»iѺ Ùiµz¸m·m¿†»iԓ¹º Ý~Þ·ÚÀz¿1»“Ôi¹ × ½mÓmÔiÕz»¥Ôz·¿†Øz»i´º × ÑÓXº“ºmÚá Ú¸iÓG¹ ÚµÔ ÛiÜ3ÒAº â{½m»i´»“ã·iºi»“¶9Ñ ÚºG¹ ¼~¹ÓiÔm¶zÓi´ ¶9À·m¿1Àmº ¼~¹ÓiÔm¶zÓi´ ¶9À·m¿1Àmº ¼~¹ÓiÔm¶zÓi´ ¶9À·m¿1Àmº ¼~¹ÓiÔm¶zÓi´ ¶9À·m¿1Àmº ¼~¹ÓiÔm¶zÓi´ ¶9À·m¿1Àmº n One of the functions of a change master record is to group together changes to related objects. To select these objects quickly and easily, you can create object management records from the product structure 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 can navigate through the BOMs on several different levels. n You can only select an object if the change master record contains the appropriate indicators for the corresponding product structure browser. n Furthermore, the product structure browser enables you to display and change all relevant objects both in the selection and by directly calling up (transaction CC04).

42. © SAP AG LO980 2-18 © SAP AG 1999 l 1HZ LQLWLDO REMHFW &RQILJXUDWLRQ 0DQDJHPHQW l 1HZ VHOHFWDEOH REMHFWV 5RXWLQJV l 5HODWLRQVKLSV IRU URXWLQJV 6HTXHQFH 0DWHULDOV &ODVVLILFDWLRQ l 2WKHU REMHFWV 5HIHUHQFH RSHUDWLRQ VHW ,QVSHFWLRQ SODQ 0DWHULDO VSHFLILFDWLRQ 40

43. &KHFN DQG PDVWHU FKHFN FKDUDFWHULVWLFV 40

44. l (QKDQFHG ILOWHU VHWWLQJV 1HZ IRU 6HOHFWLRQ IURP WKH 3URGXFW 6WUXFWXUH &

45. © 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 WKH FRPSDQ l &UHDWH DQG XVH WKH FKDQJH PDVWHU UHFRUG ZLWK LWV VWUXFWXUH DQG LWV IXQFWLRQDOLW u &KDQJH KHDGHU u 2EMHFW PDQDJHPHQW UHFRUG u $OWHUQDWLYH GDWHV l 6HOHFW DQG FRS REMHFWV IRU (QJLQHHULQJ &KDQJH 0DQDJHPHQW ZLWK WKH KHOS RI WKH SURGXFW VWUXFWXUH &KDQJH 0DVWHU 5HFRUG 8QLW 6XPPDU n You can use Engineering Change Management to control and document changes made with history in the system. n Changes with history become effective on a key date. The object status both before and after the change 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 enables you 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 object management records. n You can select objects that you want to change by using the product structure.

46. © SAP AG LO980 2-20 ([HUFLVH ([SODQDWLRQ RI WKH 6PEROV 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 6VWHP Material 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

47. © 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 ,'(6 6VWHP 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

48. © SAP AG LO980 2-22 ([HUFLVHV 8QLW &KDQJH 0DVWHU 5HFRUG 7RSLF 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 change BOMs and material master records • Assign the meaning of the object management records As a result of technical problems, pump T-F1## has to be changed. Therefore, change the BOM with and without history. The following abbreviations and conditions apply for DOO exercises *URXS QXPEHU such 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.

49. © 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 following data: – Change no.: &  Text: 7HFKQ XSGDWLQJ SDUW  Valid-from: 7RGD¶V GDWH   PRQWK Status: $FWLYH – Object types: BOMs and such that the object management records have to be maintained manually. Materials and such that the object management records are 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) with the 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 the change master record & . Give a reason for the system message. _____________________________________________________ _____________________________________________________ _____________________________________________________ _____________________________________________________

50. © SAP AG LO980 2-24 ([HUFLVHV 8QLW &KDQJH 0DVWHU 5HFRUG 7RSLF 6HOHFWLQJ 2EMHFWV IURP WKH 3URGXFW 6WUXFWXUH At the conclusion of this exercise, you will be able to: • Select objects for Engineering Change Management with the help of the product structure • Use alternative dates. As a result of technical problems, pump T-F1## has to be changed again. Therefore, change BOMs for your BOM structure with history. 2-1 In a second session create another change master record for that with the following data: Change no.: &  Text: 7HFKQ XSGDWLQJ SDUW  Valid-from: 7RGD¶V GDWH   PRQWKV Status: Insufficient consistency Status: DFWLYH Long text: Techn. updating part 2, Problems after 1000 operating hours: Oil leak from the casing. Object types: BOMs and such that the object management records have to be maintained manually. Materials and such that the object management records is generated automatically. Task lists and such that the object management records is generated automatically and a dialog box appears giving a reason for the change. 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.

51. © SAP AG LO980 2-25 Generate object management records for the BOMs T-F1## 1000 1 and T-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 with the valid-from date 7RGD¶V GDWH   PRQWKV. Select the alternative date and assign is to the object management record of the BOM 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. Optional In the BOM for the spiral casing 7% replace the seals 77 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 data for the component)? Why ? In six weeks In three months Entire lifetime Branch 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?

52. © SAP AG LO980 2-26 6ROXWLRQV 8QLW &KDQJH 0DVWHU 5HFRUG 7RSLF 6WUXFWXUH RI WKH &KDQJH 0DVWHU 5HFRUG In this course, the activity 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 relate to your user menu. You can find the menu paths relating to the SAP menu, in the appendix. 1 Choose %LOO RI PDWHULDO → 0DWHULDO %20 → &KDQJH 1-1 In the initial screen enter: Material: T-F1## Plant: 1000 Usage: 1 Valid 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 this change. 1-2 Open a second session by clicking µ&UHDWH D QHZ VHVVLRQ¶ or 6VWHP → &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 record Function: Without release key The rest remain blank The change header appears. Here, enter: Text, Valid-from date and Status. The date release in the object types overview appears. Select: in the line %LOO RI PDWHULDO the fields $FWLYH and 2EMHFW and in the line 0DWHULDO the fields $FWLYH  and 0JW5HF.

53. © SAP AG LO980 2-27 For material masters, the field “ Object” is automatically set when you set “ Active”. By clicking on 2EMHFWV ) the object overview appears. Select the tab page “ Mater. BOM” and enter your BOM here: Material: 7) Plant: 1000 Usage: 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: 1000 Usage:  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 with material T-B1##: The change master is only planned for changes to the BOM T-F1##. For changes to other BOMs, the corresponding object management records have to be created in the change master C##-1.

54. © SAP AG LO980 2-28 6ROXWLRQV 8QLW &KDQJH 0DVWHU 5HFRUG 7RSLF 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 record Function: Without release key The rest remain blank The change header appears. Enter here Text, Long text (Click ³&KDQJH KHDGHU ORQJ WH[W´ 6KLIW  )) Save long text! and go back enter valid-from date and status. By clicking on 2EMHFW WSHV 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 and in 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.

55. © SAP AG LO980 2-29 Generate object management records for the BOMs T-F1## 1000 1 and T-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 management record 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: 1000 Usage:  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 the alternative text. Save the changes.

56. © SAP AG LO980 2-30 2-3 Choose 0DWHULDO %20 → 'LVSOD. In the initial screen enter: Material: 7) Plant: 1000 Usage: 1 Valid from: Yesterday Valid-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 select 5HO & %LOO RI 0DWHULDO → 5HSRUWLQJ → &KDQJH 'RFXPHQW → 0DWHULDO %20 5HO % (QJLQHHULQJ &KDQJH 0DQDJHPHQW → 5HSRUWLQJ → &KDQJH 'RFXPHQW → 0DWHULDO %20. or from any BOM transaction (QYLURQPHQW → &KDQJH 'RFXPHQW In the initial screen enter: Material: 7) Plant: 1000 Usage: 1 Selection 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 component scrap). In the second document, you find 3 entries created. A new item was created and for 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 changed historically. In Rel. 4.6C the last change number was also changed to C##-1.

57. © 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 fourth entry provides information about the BOM header. Only in Rel. 4.6C do you find in the fifth document that the change number has been changed to C##-2.

58. © SAP AG LO980 3-1 © SAP AG 1999 2EMHFW &KDQJHV l &KDQJHV WR PDWHULDO PDVWHU UHFRUGV l &KDQJHV WR GRFXPHQWV l &KDQJHV WR %20V l &KDQJHV WR URXWLQJV l &KDQJHV WR FODVVHV FKDUDFWHULVWLF DVVLJQPHQWV WR FODVVHV DQG FODVVLILFDWLRQ l &KDQJHV WR REMHFW GHSHQGHQFLHV FRQILJXUDWLRQ SURILOHV DQG YDULDQW WDEOHV &RQWHQWV

59. © 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 VWDWXVHV l 3URFHVV WKH YDULRXV REMHFWV ZLWK UHIHUHQFH WR D FKDQJH QXPEHU l 1DPH WKH GLIIHUHQFHV DQG WKH VSHFLDO IHDWXUHV RI PDLQWDLQLQJ REMHFW WSHV ZLWK D FKDQJH PDVWHU UHFRUG l :RUN ZLWK DOWHUQDWLYH GDWHV DQG GDWH VKLIWV

60. © SAP AG LO980 3-3 © SAP AG 1999  5HSRUWLQJ5HSRUWLQJ   &KDQJH +LHUDUFK&KDQJH +LHUDUFK 5HOHDVH .H5HOHDVH .H«« &KDQJH 0DVWHU 5HFRUG&KDQJH 0DVWHU 5HFRUG 3URFHVVLQJ &KDQJHV3URFHVVLQJ &KDQJHV ZLWK :RUNIORZZLWK :RUNIORZ &RXUVH 2YHUYLHZ&RXUVH 2YHUYLHZ  (&5  (&2(&5  (&2  2EMHFW &KDQJHV2EMHFW &KDQJHV 6XPPDU6XPPDU  2UGHU &KDQJH2UGHU &KDQJH 0DQDJHPHQW 2&0

61. 0DQDJHPHQW 2&0

62.  &RXUVH 2YHUYLHZ 'LDJUDP

63. © SAP AG LO980 3-4 © SAP AG 1999 l 6DOHV ZRXOG OLNH WR VHOO D QHZ SXPS WSH 7KH FHQWUDO FKDQJH GHSDUWPHQW LV DVNHG WR DUUDQJH DQG H[HFXWH WKH QHFHVVDU FKDQJHV l $OO UHODWHG REMHFWV DUH FKDQJHG 2EMHFW &KDQJHV %XVLQHVV 6FHQDULR

64. © 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&KDQJH WKH GRFXPHQWWKH GRFXPHQW  &KDQJH PDVWHU UHFRUG 1 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.

65. © SAP AG LO980 3-6 © SAP AG 1999 0DWHULDO 0DVWHU 5HFRUG  &KDQJH ,PPHGLDWHO W  ¢¡¤£¥£§¦©¨©¦ ©  "!$#%£'&"()¤§¦01¨2%34¦654789&£A@B¡¤£%£C¦©¨©D¦ 0DWHULDO PDVWHU UHFRUG 053 FRQWUROOHU   E£C¦¦4F&¨9G H©IP H©IP QH8HH &KDQJH GRFXPHQW 053 FRQWUROOHU  ,PPHG &KDQJH  &KDQJH GRFXPHQW 053 FRQWUROOHU  ,PPHG &KDQJH  $ 1 RTS%URTS%UVWR%R¥R % 1 RXSWURWYTUV%R¥R%R  n If you want to change materials with the function &KDQJH -> ,PPHGLDWHO, you can only change them with reference to a change number if the YDOLGIURP 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 system saves 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, the data 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 date without reference to a change number even if you have previously processed them with reference to a change number. You would still have complete documentation because change documents are saved for all material changes - regardless of whether you made the changes with or without a change number. n 2EMHFW PDQDJHPHQW UHFRUGV are required by material master records for changes with change numbers. The relevant indicator in the object type overview is set automatically. However, you have to ensure that a relevant object management record exists or is automatically created.

66. © SAP AG LO980 3-7 © SAP AG 1999 0DWHULDO 0DVWHU 5HFRUG  6FKHGXOHG &KDQJH 0DWHULDO PDVWHU UHFRUG `badc @4&¨¥£C& ¦ "£¥G IeH¤I  E£C¦¦Bf&¨G H©IP Hhg¤P Q8HHH 6FKHGXOH &KDQJH  $FWLYDWLRQ H¤IP H¤IP H©I iqpsrtsuhv wxhye€‚ vet„ƒ …‡†9ˆ y‚x t„ƒ§‰ x8 v‚‰'‘ ’„’s“ 'RF WCreated on 9DOLGIURP GDWH LQ WKH IXWXUH 'RF 6FKHGXOH &KDQJH  $FWLYDWLRQ H”BP H©IP HQ iqp„ret‚uhv wx•yh€‚ vet„ƒ …–†"ˆ ysx t„ƒ‰ x8 ve‰§‘ ’„’—“ 1 R¥S%URXS¥UV¥R%R¥S 1 RTS%URTS%UV%RWR¥V n If you want to change materials with the function &KDQJH -> 6FKHGXOH, you can only change them with 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 be activated on a specific date if they are to become effective. When you activate the changes, the system 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 change numbers. The relevant indicator in the object type overview is set automatically. However, you have to ensure that a relevant object management record exists or is automatically created.

67. © SAP AG LO980 3-8 © SAP AG 1999 &UHDWH ZLWK FKDQJH PDVWHU 3XPS3XPS 6KDIW6KDIW&DVLQJ&DVLQJ ([DPSOH  &KDQJH ZLWK FKDQJH PDVWHU 3XPS3XPS  &KDQJH ZLWK FKDQJH PDVWHU 3XPS3XPS  &KDQJH ZLWK FKDQJH PDVWHU 3XPS3XPS &KDQJH QR   ‡&"(˜58&¨4¦¤¨ 7B@©£§©5G I•H4™ &KDQJH QR  5HYLVLRQ OHYHO  &KDQJH QR  5HYLVLRQ OHYHO  &KDQJH QR  5HYLVLRQ OHYHO  6KDIW6KDIW&DVLQJ&DVLQJ &DVLQJ&DVLQJ 6KDIW6KDIW &DVLQJ&DVLQJ 6KDIW6KDIW 7KH 5HYLVLRQ /HYHO  2YHUYLHZ n If you make changes to material masters or documents with reference to a change number, you can assign a revision level to a specific change status. You can either assign a new revision level to every change with reference to a change number, or you can use revision levels for particular changes (for example, for larger, more important changes). n This means that you can process the objects concerned at a later date either with reference to a change number or with reference to the revision level. n You can only assign one revision level per change number. An object management record must exist before 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 of the UHYLVLRQ OHYHO QXPEHUV in Customizing.

68. © SAP AG LO980 3-9 © SAP AG 1999 5HYLVLRQ 6WDWXV $VVLJQPHQW IRU 0DWHULDO 0DVWHU 5HFRUGV … rsƒ$ve‰dr — rse—ƒ1v‰… rsƒ$ve‰dr — r„esƒ$vh‰ PDLQWHQDQFHPDLQWHQDQFH fBgh…f©gi… PDLQWHQDQFHPDLQWHQDQFH 7UDQVDFWLRQ7UDQVDFWLRQ 5HYLVLRQ OHYHO5HYLVLRQ OHYHO 'LVSODHG LQ'LVSODHG 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 RI8VDEOH 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 revision level. This revision level is assigned to the header material of the changed BOM. You can also refer to the revision level when you process routings for the material. n Revision levels require object management records for the material master records.

69. © SAP AG LO980 3-10 © SAP AG 1999 &KDQJLQJ 'RFXPHQWV ZLWK (&0 UHVHUYHGUHVHUYHG UHVHUYHGUHVHUYHG DVVLJQHG UHVHUYHGUHVHUYHG 'RFXPHQW YHUVLRQ  &KDQJH QR 1 &KDQJH PDVWHU UHFRUG 1 &KDQJH PDVWHU UHFRUG 1 &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 a certain 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 that starts on the YDOLGIURP date. n You can UHVHUYH a document for more than one change number. To do this, you create an object management record for the document in each of the change master records. If you change the document, 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 a change number from the reservation list in the document, you can no longer change the change number. This also applies if you enter a change number directly in a document that is not reserved for a change number. n If you want to create a reference to another change number, create a new version.

70. © SAP AG LO980 3-11 © SAP AG 1999 5HYLVLRQ /HYHO $VVLJQPHQW IRU 'RFXPHQWV :LWKRXW UHIHUHQFH WR D FKDQJH QXPEHU releasedreleased &KDQJH PDVWHU UHFRUG 1 &KDQJH PDVWHU UHFRUG 1 'RFXPHQW YHUVLRQ  &KDQJH QR 1 'RFXPHQW YHUVLRQ  'RFXPHQW YHUVLRQ  &KDQJH QR 1 '' 5HYLVLRQ OHYHO n The revision level serves as an identification number for an important document version. You can only 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 the first 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 a revision level. n You make settings for revision levels for documents in Customizing for 'RFXPHQW 0DQDJHPHQW. n Under 'HILQH GRFXPHQW WSHV 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 &KDQJH 0DQDJHPHQW menu.

71. © SAP AG LO980 3-12 © SAP AG 1999 %20  +HDGHU 'DWD 6WDWXV QHZ YDOXH      D E &KDQJH QXPEHU 1 0DWHULDO 3 W &UHDWH %DVH TXDQWLW QHZ YDOXH  F &KDQJH QXPEHU 1 0DWHULDO 3 %20%20 +HDGHU RYHUYLHZ %20 KHDGHUV 9DOLGIURP 9DOLGWR &KJ QU   1   1   n When you change header data with reference to a change number, the system saves both the old and the 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 YDOLGIURP and the YDOLGWR dates. The system determines the YDOLGIURP date from the change master record. n The validity periods end with the YDOLGWR date. This date is automatically determined by the system. 31.12.9999 is the maximum 9DOLGWR date. The 9DOLGWR date is not explicitly saved with this. If you process the BOM header more than once with reference to different change numbers, then the YDOLGIURP date of the following change number is the YDOLGWR date of the previous data record. n Some header data is QRW stored with history. The old values are overwritten by the new values when you 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

72. © SAP AG LO980 3-13 © SAP AG 1999 %20  ,WHP 'DWD F 2SHUDWLRQ VFUDS QHZ YDOXH  D E ,WHP TXDQWLW QHZ YDOXH  &KDQJH QXPEHU 1 &RPSRQHQW  &KDQJH QXPEHU 1 &RPSRQHQW  QjBPkIIP HH IeQBP$IhQBP HH Q©IP H”BP H¤I l©IP1I•QBP m4m4mm W &UHDWH %20%20 n When you change item data with reference to a change number, the system saves both the old and the 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. For technical reasons, the system creates a new item record for the following item data, even if you cancel 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 YDOLGIURP and the YDOLGWR dates. The system determines the YDOLGIURP date from the change master record. n The effectivity period ends with the 9DOLGWR date that the system determines dynamically. The 9DOLGWR date is not explicitly saved with this.. The last possible YDOLGWR 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 YDOLGWR date of the previous item record.

73. © SAP AG LO980 3-14 © SAP AG 1999 %20  (IIHFWLYLW 3HULRG l©IPkI•QBP mm8mm 9DOLG9DOLG IURPIURP &KDQJH QXPEHU 1 H©IP H"IP H¤IP HQ©P H©IP H4lBP H©IP Hg¤P $ $ $ 1 1 1 $ ,WHP %,WHP % ,WHP $,WHP $ ,WHP &,WHP & %20%20 9DOLG9DOLG IURPIURP &KDQJH QXPEHU 1 9DOLG9DOLG IURPIURP &KDQJH&KDQJH QXPEHUQXPEHU 11 1 1 %20 KHDGHU%20 KHDGHU " n If you process the BOM with reference to a change number, the system determines the valid header record and also the valid item records for the YDOLGIURP date. In this example, there are two valid items for the YDOLGIURP 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 you configure your BOM management system (in Customizing). Under 'HILQH PRGLILFDWLRQ SDUDPHWHUV you can make basic settings. For example, you can activate Engineering Change Management for BOM processing. If you do this, then there is a history requirement for BOMs. You can also specify whether you must enter a change number when you create a BOM. In Customizing (Set history requirement) you can define for a BOM usage (for example, production) that you must use a change number to change a BOM that has a certain status - even if you have not worked with a change number until then. n In exceptional cases, you can allow a BOM change without a change number for BOMs with history requirement by using authorization object C_STUE_NOH. Please note that, in this case, the changes are not documented completely.

74. © SAP AG LO980 3-15 © SAP AG 1999 5RXWLQJV l"IP$IeQ©P mmm4m .H GDWH.H GDWH 7DVN OLVW7DVN OLVW KHDGHUKHDGHU 6HTXHQFH6HTXHQFH 2SHUDWLRQ 2SHUDWLRQ  2SHUDWLRQ 2SHUDWLRQ   E38¤¨8n¤¦pob¥38&¡ @©34¤¨8n©¦F¨¤¡B(rq4¦©£ n When you process the following WDVN OLVW REMHFWV with reference to a change number, the system saves 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 the YDOLGIURP date from the change master record. n The validity periods end with the YDOLGWR date. This date is automatically determined by the system. The last possible YDOLGWR date is 12/31/9999. If you process the task list object more than once with reference to different change numbers, then the YDOLGIURP date of the following change number is the YDOLGWR date of the previous data record. If you process the task list on a specific date, the system determines all task list objects that are valid on that date. n Task list objects can be processed without reference to a change number, even if you have previously processed them with reference to a change number. In this case, however, you will be left with an incomplete history. In the above example, operation 2 was created with reference to a change number and then changed without a change number. No new validity period exists. The new value (for example, base quantity) is valid from the YDOLGIURP date of the change number.

75. © SAP AG LO980 3-16 © SAP AG 1999 l¤IP$IeQ©P mmm4m9DOLG 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 £§¦4 q¤s¡B¦ n£§¦4¦¤¨ ob3"§¦ 2EMHFWV LQ WKH &ODVVLILFDWLRQ 6VWHP n There is a KLVWRU UHTXLUHPHQW for all objects in the classification system that you have processed with reference to a change number. n The system saves both the old and the new status of the objects in the classification system that you change with reference to a change number. n 2EMHFW PDQDJHPHQW UHFRUGV are QRW supported for objects in the classification system. This means that you cannot, for example, select an alternative YDOLGIURP date for a classification system object. n The validity periods of an object are determined by the YDOLGIURP and YDOLGWR dates. There are no limitations for the YDOLGIURP date. If you process an object with reference to a change number, the system determines the YDOLGIURP date from the change master record. n The validity period ends with the YDOLGWR date. This date is automatically determined by the system. The last possible YDOLGWR 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 YDOLGWR date of the previous data record. n In Customizing for &ODVVHV you can define for each class type whether (QJLQHHULQJ &KDQJH 0DQDJHPHQW can be used for changing classification system objects.

76. © SAP AG LO980 3-17 © SAP AG 1999 2EMHFW2EMHFW GHSHQGHQFLHVGHSHQGHQFLHV &RQILJXUDWLRQ SURILOH IRU FRQILJXUDEOH REMHFWV %DVLF GDWD%DVLF GDWD 6RXUFH FRGH6RXUFH FRGH Material master record Std network PM ECR Model specs !8tp5¤5" @ ' &¨vu ¦ho¢7 !©wqX¡7 !8t‡779 n¨B(6¦©¨ s¨4D¦¤£#§8@¦x©¦7¤ n¨ !©wi¦kX ¨8nB7 !8t‡779 n¨B(6¦©¨A@B 787 &q‚yC¦4@©¦©54¦¤¨8©¦¤¨B@B¦7 !©¤¨8f© e&BX34¦©£ 54©£C8(f¦§¦©£§7 !4tv5¤5" @ ' &¨vu" ¦o¢7 !Bwi¥¡7 !4t–77" n¨B(f¦©¨  ¨§¦"£#D8@¦b©¦47¤ n¨ !Bwh¦D¥ ¨8nB7 !4t–77" n¨B(f¦©¨9@© 747 &q‚y¦B@h9©¦¤54¦¤¨8¤¦©¨8@© ¦7 9DULDQW &RQILJXUDWLRQ 2EMHFWV RQO  YLHZ VHYHUDO YLHZV 9DULDQW WDEOHV9DULDQW WDEOHV 7DEOH7DEOH FRQWHQWVFRQWHQWV n You can maintain both a VLQJOH GHSHQGHQF and a GHSHQGHQF QHWZRUN with reference to a change number. When you change the basic data or the source code with reference to a change number, the system 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, is processed in Customizing for 9DULDQW &RQILJXUDWLRQ. Under 0DLQWDLQ VWDWXV you determine for each configurable object whether changes to configuration profiles with a certain status (for example, UHOHDVHG) are stored with history. Several views exist for the configuration object 0DWHULDO. For the other configuration objects only one view exists. n The table contents of a variant table can also be changed historically, however, the table structure can not. n There is a KLVWRU UHTXLUHPHQW for all variant configuration objects that you have processed with reference to a change number.

77. © SAP AG LO980 3-18 © SAP AG 1999 X 2EMHFW 1HZ GDWD UHFRUGV +LVWRU UHTPW 2EMHFW PJPW UHFRUG $FWLYLWLHV LQ &XVWRPL]LQJ %LOO RI PDWHULDO 7DVN OLVW 'RFXPHQW 0DWHULDO 2EMHFWV IURP FODVVLILFDWLRQ 2EMHFW IRU YDULDQW FRQILJXUDWLRQ ; ; ; ; ; ;

78. EWB ;    ; ; Status   ;  ;  for class type ; ;  Status for configurable objects 2YHUYLHZ RI &KDQJH 2EMHFWV ; Mod.parameter Status n As a rule, both the old and the new status are saved in different data records when you make a change 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 a validity period from the change number. n There is a history requirement for BOMs, documents, objects in the classification system, variant configuration objects, and partly for routings (EWB). As soon as you have released a document version with reference to a change number, following versions can also only be released with reference to a change number. You can, however, process the object 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 change number, 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, task lists, documents, and materials. n You must make settings in Customizing for BOMs, documents, and class types. For BOMs and configuration profiles you can define status-dependent history requirements.

79. © SAP AG LO980 3-19 © SAP AG 1999 'DWH 6KLIW :LWKRXW &KDQJLQJ WKH (IIHFWLYLW 3HULRG 0DWHULDO0DWHULDO %20%20 5RXWLQJ5RXWLQJ 'RFXPHQW'RFXPHQW  W 1 1 1 1 &KDQJH PDVWHU UHFRUG  ¤  "!$#%£'&"()¤§¦9G 1 n As long as there are no changes to objects, you can enter a new valid-from date. However, the status of the change master record must allow you to change the date. As soon as there is at least one object change, you must perform a date shift. n When you try to perform a date shift, the system checks the settings in Customizing. If the date check is activated, then you can only perform a date shift to a date outside the "protected time period". n As long as the date shift does not lead to inconsistencies in any of the objects that have already been changed with the change number (for example, two changes to a BOM header on the same date) and it does not lead to a change in the sequence of the validity period, then you can perform this date shift for any object type.

80. © SAP AG LO980 3-20 © SAP AG 1999 'DWH 6KLIW &KDQJLQJ WKH (IIHFWLYLW 3HULRG 0DWHULDO0DWHULDO %20%20 5RXWLQJ5RXWLQJ 'RFXPHQW'RFXPHQW  W 1R 1R 1R 1R1R &KDQJH PDVWHU UHFRUG ©  9!$#%£C&"(z©'¦"G1

81. © 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 VWDWXVHV l 3URFHVV WKH YDULRXV REMHFWV ZLWK UHIHUHQFH WR D FKDQJH QXPEHU l 1DPH WKH GLIIHUHQFHV DQG WKH VSHFLDO IHDWXUHV RI PDLQWDLQLQJ REMHFW WSHV ZLWK D FKDQJH PDVWHU 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.

82. © SAP AG LO980 3-22 ([HUFLVHV 8QLW 2EMHFW &KDQJHV 7RSLF %DVLF GDWD REMHFW FKDQJHV At the conclusion of this exercise, you will be able to: • Change the various objects with Engineering Change Management. • 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 to drawings, BOMs, routings, material masters and objects in the classification 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  PRQWKV Status: Active Reason for change: Further complications Long text: Techn. updating part 3 Problems after 1000 operating hours: Break of hexagonal head screws. View: Object types: BOM: active; object management records (manual)

83. © 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 active Characteristics of the class: active Classification: Active Object dependencies: active Configuration profile: active Variant table: Active View: Object: Switch to the product structure (= Select object = Ctrl. + F6) and enter with the DOCUMENT: Document: 7) Document type: DRW Document part: 000 Document 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 the material master. Open the material T-F1##, from there, open the BOM folder and copy the BOM to 7) . 2QO LQ 5HOHDVH & Open the routing folder and copy the first routing: 1 «  

84. Click &RS REMHFWV Save your change master record.

85. © S

Add a comment

Related presentations

Speaker: Matt Stine Developing for the Cloud Track Marc Andressen has famou...

This presentation explains how to develop a Web API in Java using (JAX-RS or Restl...

1 App,

1 App,

November 10, 2014

How to bring innovation to your organization by streamlining the deployment proces...

Cisco Call-control solutions can handle voice, video and data

Nathan Sharp of Siemens Energy recently spoke at the SAP Project Management in Atl...

Related pages

Engineering Change Management in Document Management ...

Engineering Change Management in Document ... engineering change management to perform the following functions: To link documents to other SAP ...
Read more

It Change Mgmt | LinkedIn

Lead IT Change Mgmt Analyst at DST Systems. Kansas City, Missouri Area. Financial Services. See more. Current ... Civil Engineering. See more. Past ...
Read more

LO980 Engineering change Management03

A workflow management system coordinates the flow of all types of information by different activities. Workflow ensures that the correct task is given to ...
Read more

Complete for Engineering Change Management - Document ...

Complete for Engineering Change ... More portals for customers and partners SAP Community Network SAP Support Portal SAP Ariba ... Product Lifecycle Mgmt;
Read more

The new ASAP Methodology - SAP Community Network

SAP Field Services The new ASAP Methodology ... The New ASAP Methodology supporting multiple ... & Change Mgmt Solution
Read more

Change Mgmt. | LinkedIn

View 5526 Change Mgmt. posts, presentations, experts, and more. Get the professional knowledge you need on LinkedIn.
Read more