System Architecture Set
An R / 3 corresponds to each of a complete, independent R / 3 installation. The initial installation requires only a few hours or days. Then the real work begins the basic group (System S Administrator), with the technical assistance of the computer system a significant contribution makes for a successful R / 3 implementation.
The aim of the system architecture is the definition of the nature, scope and role the following systems:
• Development Systems
• Test systems
• Training Systems
• Collection systems
• Basic Systems
• Productive
Depending on the size and scope of the project can also some systems are combined into an R / 3. It is typical here, for example, the summary of test and training systems, or development and test systems.
A stable system with a good runtime behavior (short response times) is the basis for effective project work. Systemic work such as backups, the basic group agrees with the project team off.
• The SAP delivers a client with the marking "000". He is as "costumer reference" with numerous settings against changes locked.
• For Customizing is normally used by the client "001" the client a copy of "000" corresponds.
• The one or more production systems will need to receive attention to the following criteria is designed:
• Use load (user / transaction loads Batch Load)
• Volume of data (documents / information / statistics)
• Definition of which business sectors on a hardware cluster cooperate
• Networks, databases
Risk analysis
At this place an external review of potential risks which may implementation of the proposed transaction with respect to the application and the technical and operational framework made will. This service is used by SAP under the term "feasibility Check 'available. Details can be found in the aforementioned Website of the SAP Services Solutions Map.
Role and authorization concept define
At this point, is once again the necessity for the project team during the introductory phase and those for the users in the later to distinguish productive phase. With regard to the project team are relatively far-reaching privileges necessary to the activities during to ensure the customizing and testing work.
Since the eve of Production operations mostly just test data are used, are Privacy issues are not the prime considerations. Regarding the users is in productive use within the design phase to define the different roles. Under a role the totality of all operational functions needed by a user understood.
This set of functions is summarized in a role that assigned to the relevant user ID is. In this way, to ensure that the user in its initial screen after login the SAP system, only the actually needed for its area of responsibility Functionality is offered. Thus a possible abuse prevented, while the menu tree for function selection clearly hold. With the roles of the authorization profiles are connected, in which the permissions summarized the use of the individual transactions.
In addition to the restriction on certain transactions and programs the parameters for its execution determined. For example, can within the financial authorization for execution issued by property accounts bookings building on certain company codes be limited. In the interplay of roles and permissions, a principle is followed, which can be simplified this way: The user sees what he can and may do what he sees. SAP provides with a variety of standard pre-defined roles and authorization profiles from which are used by the project team and varies can.
During the design phase of the required roles and Profiles identified and documented, which then as a blueprint for the implementation phase serves. At the same time, the personal responsibility of the user administration is and the procedure for the award during operation defined. |
