13.07.2015 Views

6\VWHP $GPLQLVWUDWLRQ 0DGH (DV\

6\VWHP $GPLQLVWUDWLRQ 0DGH (DV\

6\VWHP $GPLQLVWUDWLRQ 0DGH (DV\

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 17: Change ManagementChange ControlChange control is the managing of the changes, modifications and customizing made toyour system. This control allows you to be aware of and control what changes are made.These change must be made in a controlled manner, because uncontrolled changes are arecipe for disaster.The process is: Managing the changes: SAP notes that are applied to the system. Authorization process for moving the changes from one system to another. Making the changes to the R/3 System. Moving the changes from one system to another.The SAP training class BC325 (Software Logistics) covers change management andtransports. Also see Software Logistics by Sue McFarland.SAP notes were formerly known as OSS notes.Managing SAP notes means tracking the notes that you have reviewed and applied. Thesenotes are release and configuration specific and may (or may not) relate to your system’sconfiguration. Some of these notes may actually be specific to individual systems in yourenvironment.There are several reasons to track SAP notes that are applied to your system: If a problem arises, SAP may ask if a specific note has been applied.If you do not have a record of what notes you have applied, then you must manuallyinvestigate your system. This process can be difficult and time consuming. When the system is upgraded, for conflict resolution, you need to know what notes havebeen applied.You must know what notes: Are included in the upgrade, so you can go back to SAP standard code May need reapplying because they are not included in the upgradeSystem Administration Made Easy17–9

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!