SAP标准培训教材bc040 PRINT2.doc

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 the 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, another 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 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. 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 change 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 development 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 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 of 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 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 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. 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 responsible 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 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 intervention 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 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 only receive complete imports after extensive testing. The original change requests and any requests containing corrections are imported in their sequential order. This ensures proper delivery of all changes to the entire system landscape.o Plan the upgrade to ensure fast and unproblematic import of the new version. Apart from preparing the hardware and software, it is particularly important to decide on an appropriate strategy. The strategy you choose determines the optimal schedule for the upgrade.o Ideally, the systems in your landscape should be upgraded in the sequence defined by the transport path. If you have modified SAP objects and wish to retain the changes, you must adhere to your transport route. A complete record of the changes is only kept by the Version Management of the system in which the changes were made (typically the development system). Only this system can provide optimal support for adjusting modifications.o During an upgrade, all SAP objects modified by customers must be reviewed. To adjust the Dictionary, use transaction SPDD. Transaction SPAU is used to merge all other repository objects. This merging process is not automatic. Customers must decide which development efforts and modifications they wish to keep, taking into account the new SAP functionality. Having complete documentation for each modified object prior the start of the upgrade is recommended. This will greatly assist in the process of merging new SAP standards with customer changes.n To achieve a high availability system, plan your hardware requirements with an SAP hardware partner and SAP Competence Center.n R/3 offers two categories of services for high availability :(1) the services, which can be kept redundant (Dialog, Background, Update, Spool), and (2) the services with the Message Server and the Enqueue Server, which can only be run individually.n In a high availability system, restart and recovery procedures and decision paths are also described for each critical background job.n R/3 provides standard interface programs in most business functionalities for data transfer into R/3. For detailed information, see the documentation for each specific application.n When you define an R/3 interface, consider the following : What data volume will be transferred through the interface? Will the data transfer from the source into the target system be synchronous or asynchronous? Which restart process should be used? How and by whom? Will the interface be used regularly (for example, a steady flow of document transfers in financial accounting ) or for ad hoc applications during a transaction?o Once you have completed all of the functional testing of the load programs, perform a test in order to determine: disk requirements time requirements dependencies between data load programso It is important to note that data integrity with respect to your customizing is only guaranteed if you use SAP's standard functionality for loading data. The data must always be loaded by simulating on-line data entry transactions. By doing so, you ensure that the data is validated properly.o Test your data load with a small amount of data. (For example, test your data load with approximately 10% of the total.)o SAP's standard interface for data load "batch input" provides a lot of functionality with respect to recovery, restart and on-line correction.The price for such comforts includes the cost for additional resources and the constraints for managing Batch-Input Queues.o SAP also provides low level interfaces for data loads. These interfaces require more expertise and care in order to manage restarts and recovery.o Parallel the data load by utilizing a number of SAP application servers.o Typically, the complete data load has to run and be completed within a given weekend.o Each load step should be checked and tested carefully. You should make sure that you cross-check the loaded data against your former legacy systems. For example, verify samples of the loaded master records with your consultants and your functional departments.o Recovery and restart options must be defined and documented.o It is vital to add performance checks to your quality assurance policies. Depending on your development efforts and customization of the SAP R/3 System to your business requirements, there may be performance issues and constraints within the database.o Even if you try to keep developments and modifications at a minimum, the adjustment of standard print programs, like delivery notes and invoices, can have severe impacts on overall performance.o You will not be able to carefully check all functions of the R/3 System with respect to performance.o Therefore, a list of your vital data entry transactions and important queries must be created.o For these transactions and queries, a performance check should be done using the SAP provided CCMS utilities.o Even after completing performance checks for all core transactions and important queries, you are still unable to ensure reasonable service level in the production environment.o Constraints in the different system components from SAP-Enqueue to database resources can greatly decrease performance in a multi-user environment.o An ideal stress test would be as follows: All employees come in on a Saturday. All transactions performed the previous day are repeated in the R/3 System.o Knowing that this ideal test cannot be organized and reproduced, a simulate "ideal stress test" can be devised using a representative number of users or scripts and simulation software.o Note that a stress test is only valid if the performance quality checks were completed successfully.o The first step of a stress test is to identify the critical transactions and queries. They are usually quite easy to determine by having each each functional departments list their critical tasks. For example, Sales and Distribution comprises of the following critical tasks: creation of a sales order creation of a delivery note creation of a pick list creation of a goods issue creation of an invoice.o The second step is to define the right mix of critical transactions. Obviously, the simplest way to accomplish this to run the stress test with a representative number of users from each functional department.o Be prepared to run the stress test several times. Each run should take about one hour. For each subsequent run you should gradually increase the number of users.o Critical issues pertaining to initial sizing estimates: Sizing is typically done at a point in time when the decision to implement SAP R/3 occurred. It is therefore based on the transaction volumes and data volumes from a companys legacy systems. Sizing input related to - integration options you have chosen to utilize (or not to utilize)- the amount and accuracy of availability checking for sales articles - the complexity of your pricing schemes were not taken into account.o The innovation cycles of hardware and new software technologies are now less than one year. o SAP, for example, is shipping major software releases on a yearly basis.o The requirements and expectations of your functional departments will need to follow these cycles. Summary of Technical Implementation PlanningTo prepare for the technical kick-off meeting, the following procedure is recommended:1.For each topic, work through the material !2.Work through the questionnaire. Add your comments and suggestions.3.Proceed as for "SAP Input for IT Operation" Customer Survey"Implementation of SAP System Management"BC040Technical Core CompetenceTable of ContentsGeneral InformationDatabase AdministrationBackup StrategyDatabase MaintenanceRecovery ProcedureDatabase MonitoringSupport and AdministrationSoftware LogisticsR/3 System LandscapeCorrections, Modifications and Add-onsQuality AssuranceUpgrading SAP Software ReleasesSystem AdministrationUser AdministrationSystem SecurityPrintingBackground ProcessingLoad DistributionSystem ConfigurationSystem MonitoringDaily Administrative TasksSupport and AdministrationDocumentation of ProceduresStart PhaseData TransferStress TestSAP ServicesSupport and AdministrationWork Center Administration and NetworksWork Center EquipmentInstallation StrategyCentral Information ServicesLocal Print InfrastructureLocal Network InfrastructureNetwork Connections between R/3 ServersNetwork Connection to Remote SystemsNetwork Connection for Mobile Work CentersOperationHigh AvailabilityMonitoring InterfacesStrategies for High AvailabilityProcedure for Monitoring Interfaces2023/3/127General InformationGeneral InformationCompany portrait1. What branch of industry does the company belong to?2. How many employees work for your company?(Headquarters, Subsidiaries, Foreign offices)3.How high is your turnover?4. How many offices does your company have?5. How many foreign offices do you have?IT Infrastructure before implementation of R/36. Which software applications did your company work with before the implementation of R/3?7. What hardware and what operating system were being used before the implementation of R/3 ?8.What data storage system or database system was being used in your company ?IT Infrastructure with R/39. Which R/3 modules (SD, MM, PP, FI, .) do you use, and in what chronological order were they introduced or used productively ? 10. How long did the introductory phase for R/3 last ?11.