来源:互联网 发布:linux for windows10 编辑:IT博客网 时间:2020/02/25 13:12

SAP R/3 Instances and Clients

SAP R/3 实例与实集


An SAP R/3 implementation is usually performed with more thanone R/3 “system.” As with any software and database, theenvironments where configuration is performed and where newprograms are written and tested should not be the same environmentwhere the system is used on a day-to-day basis. SAP accommodatesthe need for these separate environments with instances andclients.



An instance is typically named for the type of environment itsupports, it often has a three-character name, and its data iscontained in a separate database from other instances. An instancenamed DEV, for example, would indicate that development work wouldbe performed on this instance. An instance named PRD, for anotherexample, would indicate that this instance is used for“production,” or day-to-day use, and programming, configuration,and testing should not be performed in this instance. Onceconfiguration settings are satisfactory in a particular instance,they will be transported to another instance. Transporting will bediscussed later. There are typically three or more instancesdefined. The purposes of each instance include (but are certainlynot limited to) development & testing, qualityassurance, and production.



A client, in SAP terms, indicates a “subsystem” within aninstance, and is indicated by a number, usually three digits. A PRD(productive) instance will likely have only one client (that isusable). That instance and client combination may be referred to asPRD100, for example. Other instances may contain a number ofclients, particularly if some development, configuration, programdevelopment, testing, or training must be done without affecting orbeing affected by other work currently being performed.



It is common to see a DEV instance with clients such as 100,200, 300, and so on defined. In such a case, DEV100 may be theinstance/client that is considered the “clean” source for theconfiguration that will be used in the production instance& client, perhaps PRD100. DEV200 might be used forconfiguration testing. While much configuration is client-specific(if it is configured in DEV200, for example, it only affectsDEV200), some configuration is cross-client or not client specific(if it is configured in DEV200, it affects every client in the DEVinstance—100, 200, 300, and so on). Usually, the system willprovide a warning that a configuration step is cross-client.

一个DEV实例有几个实集是很常见的,比如象100、200、300等等这样定义的实集。在这种情形下,DEV100可以作为是“清洁”配置源的实例/实集,它的配置将被用于正式生产性的实例/实集中,可能称为PRD100。DEV200可以用于测试配置结果。虽然许多配置是针对具体实集的(例如,如果配置是在DEV200完成的,它只会影响DEV200),有些配置是跨实集的,即不是针对具体实集的(如果配置是在DEV200中完成的,它将影响DEV实例中的所有实集– 100、200、300等等)。通常系统会警告说某个配置步骤是跨实集的。


Programming (ABAP programming and so on) is usuallycross-client. If a programmer activates a program in DEV300, forexample, it will affect DEV100, DEV200, DEV300, and so on. It isfor this reason, in part, that during some SAP R/3 implementations,a separate instance may be reserved for program testing.

编程(ABAP编程等)通常是跨实集的。例如,如果一个程序员在DEV300中激活一个程序,它将影响DEV100、DEV200、DEV300等实集。正是部分地因为这个原因,在SAP R/3实施期间,会给程序测试预留一个单独的实例。


As discussed earlier, SAP “systems” are organized into“instances, ” each of which contains one or more “clients.”Examples of instances are DEV (for development and configuration),QAS (for quality assurance) and PRD (for the productive system).There may be more instances, but rarely less.



Each instance (DEV, QAS, PRD, etc.) may consist of more than oneclient.

The clients are typically identified by a three-digit number,such as 100, 110, 120, 200, etc. Each client within an instance canshare SAP R/3 programs, but will have its own transactional data.Some configuration will affect all of the clients in an instance,but some configuration will only affect the client in which it hasbeen performed. Each unique combination of instance and client isidentified as “DEV100, ”“DEV 120” and “QAS100, ” for example. Sincethe productive/production instance normally contains only one(accessible) client, it is often referred to simply as “PRD.”Instances and clients will be discussed again later.

每个实例(DEV, QAS,PRD等)可以由不止一个实集(Client)组成。这些实集通常是用三位数的数字来识别身份,例如100, 110, 120,200等。一个实例中的每个实集可以共享SAPR/3程序,但是将拥有自己的事务数据。某些配置将影响一个实例中的所有实集,但是有些配置只会影响设置这个配置的那个实集。每个唯一的实例实集组合是以诸如“DEV100”、“DEV 120” 和“QAS100”等来识别身份的。由于生产(性)实例通常只包含一个(可使用的)实集,它通常简单地称为“PRD”就足够了。(本书)将在以后对实例和实集做进一步讨论。