6\VWHP $GPLQLVWUDWLRQ 0DGH (DV\

Chapter 1: R/3 System Administration BasicsR/3 System GuidelinesDirect database access means allowing a user to run a query or update directly to thedatabase without going through R/3. By not going through R/3, there is the risk of corrupting the database. Directly updating the database could put the database out of sync with the R/3 buffers. When R/3 writes to the database, it could be writing to many different tables.If a user writes directly to the tables, missing a single table may corrupt the database byputting the tables out of sync with each other. With direct database access, a user could accidentally execute an update or delete, ratherthan a read. Do not allow users to directly access (telnet, remote access, etc.) the R/3 server(s). Do not use the R/3 server as a general file server. Do not run programs that are not directly related to R/3 on an R/3 server. SecurityNot allowing users to have access to the R/3 server reduces the chance of files frombeing accidentally deleted or changed.No access also means that user cannot look at confidential or sensitive information. PerformanceUsing the production R/3 sever as a file server creates resource contention, whereperformance is a primary concern. Programs running on the R/3 servers will contendfor the same resources that R/3 is using, which affects the performance of R/3.Use other servers to perform functions unrelated to R/3.1–12Release 4.6A/B