6\VWHP $GPLQLVWUDWLRQ 0DGH (DV\

Chapter 1: R/3 System Administration BasicsR/3 System GuidelinesDocumentation must be changed when: Documented items change.Inaccurate documentation could be dangerous because it describes a process that shouldnot be followed. Changes are made to the system. Problems, such as hardware failures, error log entries, and security violations, occur.“Hot” projects or emergencies tend to take precedence over writing documentation. Donot postpone writing documentation, or the task may never get done. Record everythingthat is done to the system—as it is being done. Record everything done to the system, as it is being done, so details are not forgotten. Document items clearly and sufficiently so that, without assistance, a qualified personcan read what you have written and perform the task. Re-read older documentation to see where improvements can be made. Obvious itemsget “fuzzy” over time and are no longer obvious. Use graphics, flowcharts, and screenshots to clarify documentation. Keep a log (notebook) on each server and record everything that you do on the servers. Keep a log for everything done remotely to any of the servers. Keep a log for other related items.A checklist lists the steps required to complete a task. Each step requires anacknowledgement of completion (a check) or an entry (date, time, size, etc.). Checklists enforce a standardized process and reduce the chance that you will overlookcritical steps.For example, if you were to use a checklist every time you drive a car, then you wouldremember to turn off your headlights when you park your car, or you would not driveoff with your parking brake still set. Checklists force you to document events, such as run times, which may later becomeimportant.1–8Release 4.6A/B