《SAP标准培训教材bc040PRINT2》由会员分享，可在线阅读，更多相关《SAP标准培训教材bc040PRINT2（111页珍藏版）》请在金锄头文库上搜索。
1、SAP AG Technical Core CompetenceTable of Contentso Implementation of SAP must first begin by defining the R/3 Systems and clients needed to bring a customer to a productive state. The systems themselves form what is called the system landscape. Clients are then distributed in this landscape. Once th
2、e system landscape has been defined, an implementation strategy is needed for both the setup and maintenance of the systems and clients within this landscape.o SAP recommends that a customer implement its software using a three-system landscape, dedicating one system to development activities, anoth
3、er for quality assurance testing, and one for the actual production environment. Some customers may find that more systems are necessary (for example, a large, multinational implementation). Others may have constraints that require implementation using only a one- or two-system landscape.o The setup
4、 of a system landscape requires a well defined strategy. When establishing a planned approached for building up a landscape, the distribution of the system objects (such as client-independent and client-dependent Customizing settings, Repository objects, and application data) need to be considered.
5、These settings and objects are managed and distributed differently using the available R/3 tools (such as client copy, change request management, client transport, and database copy).o Once a system landscape has been established and clients exist, all changes need to be distributed in the form of c
6、hange requests. Change request management is the only recommended procedure for maintaining a system landscape.o When establishing an system landscape, issues to consider include: data security of production data acceptable levels of quality assurance and testing management of all customer developme
7、nt and customizing settings resource availability and associated administrative overhead system performance quantity of proposed customer developmentso Customizing is the standard procedure used to adapt the functionality of the delivered SAP components to the requirements of a company. Document and
8、 monitoring of each phase of the R/3 implementation and customizing is possible using easy-to-handle project control tools. For project planning, SAP provides the Procedure Model; the Implementation Guide (IMG) is used for planning individual steps.o Customizing is required for all implementations o
9、f SAP R/3. Customizing is a highly integrated process, both between functional modules and within the modules themselves. Because of this intense integration, all customizing efforts must be performed and managed from within a single client, usually known as the development client. In this client it
10、 is also recommended that development tasks be performed. This provides a single environment for all implementation efforts.o Project Management is supported by both the Customizing Organizer and Workbench Organizer functionality and the use of appropriate user authorizations. At the start of either
11、 a development or customizing project, the project leader is responsible for creating change requests for all team members. o As project team members complete their project efforts, they release their changes saved in tasks. This requires that each member document the changes contained in the task.
12、When all project team members have released their tasks, the project leader releases the change request for transport to other systems within the system landscape.o The transport of changes can technically be defined by the following procedures. Note that no step is automatic, requiring not only a r
13、esponsible persons but also sufficient quality assurance verification. The first step in the transport process is to release all the SAP objects to be transported from the database of the source system. This requires that a project leader release the change requests. Log files are generated stating
14、the success of the export. The changes themselves will then reside at the operating system level. The second step is to import the SAP objects into the database of the target system. There is no procedure that automatically imports a change request immediately after its export. This require manual i
15、ntervention and the use of the operating system transport command tp. After the import into the target system, extensive testing needs to be carried out. All errors should be be corrected in the source system and again released and imported into the target system. If additional systems exist in the
16、system landscape, the change requests must be imported into those systems as well. Again, this is not an automatic process and requires use of the operating system transport command. If additional clients exist and these clients need to receive the changes, it is possible to copy the change request to these clients. Additional systems and clients should on
