SAP R/3 Environment
SAP implementations often require a new technical environment. It basicly means operation system, data base and network protocol. In order to make the project available the whole environment has to be carefully planned in advance.
The site might be overestimated taking into account possible capacity planning mistakes. Even if you intend to upgrade the system in the near future. Two independent systems - development and production - is the minimum configuration recommended. Make an effort for having exactly the same people when installing both systems. It avoids some possible differences and keep both of them at the same pattern. Sharing the SAP's box with non-R/3 applications should be avoided.
When new modules go live it is not rare an upgrade. A simple rule say users' workload goes according to their respective modules. See the standard reference below:
- one standard FI user values 1.0 (reference value)
- one standard CO user values 1.0 FI user
- one standard MM user values 3.0 FI user
- one standard SD user values 5.0 FI user
- one standard PP user values 5.0 FI user
It means a box may support 100 FI users or 20 SD users. Nevertheless if the system is highly customized the proportion shall be increased. See the new example:
- one standard FI user values 1.0 (reference value)
- one customized FI user values 1.5 FI user
- one customized CO user values 1.5 FI user
- one customized MM user values 3.5 FI user
- one customized SD user values 7.0 FI user
- one customized PP user values 6.0 FI user
Some functionalities cause also a considerable CPU load. On-line pricing, on-line availability check, capacity requirements planning, and material requirements planning can be mentioned for instance.
Note: Research based on version 3.0f under Unix, Oracle data base and Windows.
Copyright © 1997-2001 by Ricardo F Miranda
Last modified in November 17, 1998.