Knowledge Base > Automation Engine and Target Systems > SAP > SAP R/3 Client Copies

SAP R/3 Client Copies

Like the Automation EngineThis component drives an Automation Engine system and consists of different types of server processes., SAP R/3 is a clientA closed environment within an Automation Engine system where you can create and run objects. A client name consists of a 4-digit number that must be indicated when a user logs on to the Automation Engine system. Users and their rights are also defined in clients. A particular Automation Engine object type.-capable applicationAn application is a software which helps a user to fulfill specific tasks. In the context of ARA see also: Application entity.. The individual clients are completely separate units. In some cases, periodical data exchange between clients is necessary. AE can be used to automate these processes.

The "client" is the top-level hierarchy in R/3 applications. Settings on client level apply to all structures in the R/3 enterprise organization. The client is a self-contained unit in technical, economical and organizational terms.

This client concept can be used for:

In such an environmentAn Environment consists of Deployment Targets which represent your endpoints. Different environments are used for different phases in the software delivery cycle, for example Development, QA, Staging, Production. An environment is typically set up once and used by several applications. it is often required to supply a QA or test client with consistent data. The most suitable way to obtain this data is copying the production client. Regularly copy this client in order to establish a realistic test environment.

Client Copies in SAP R/3

Copying clients in SAP R/3 involves some effort, especially the creation of periodical copies for supplying test systems with current data.

SAP R/3 supports the online copying and transportation of clients. These transactions are not suitable for periodical execution (SAP Release 4.0 to 4.6D).

The R/3 background jobAn Automation Engine object type for a process that runs on a target system. control cannot perform such periodical transactions because dynamic variants are used.

Problem Definition

Huge amounts of data are transferred when a client is copied. A client without application data allocates about 500 MB databaseA database is an organized collection of data including relevant data structures. memory. The copying process can therefore take several hours with one or more dialog processes being busy during this process.

Users should not use the source and target client during the copying process. Active users in other clients consume additional resources and extend the time required for copying.

A test run should be performed before starting the copying process. In doing so, you can determine which tables need to be modified and the available database memory is also checked.

The target client is often deleted before a client is copied, thus deleting all master userIn the Automation Engine, a user is an instance of a User object, and generally the user is a specific person who works with Automic products. The User object is assigned a user ID and then a set of access rights to various parts of the Automation Engine system and product suite. These access rights come in the form of Automation Engine authorizations and privileges, Decision user roles and EventBase rights and ARA web application object rights. You can manage all these centrally in the ECC user management functions. See also, Unified user management. data. Therefore, only the user SAP* can log on to the target client.

R/3 Client Copies with AE

Using AE for the periodical creation of client copies makes this process easier and more secure. Test run and copying process can be automated and the normal operation is not interrupted.

The copying process starts depending on test results and resource availability. AE informs the operator immediately if an error occurs.

The SAP system must meet the following requirements before AE can create client copies:

If all the above requirements are met, you can create an AE job for copying clients. Dependencies can be represented within a workflowAn object of the Automation Engine that can include several executable objects and which runs them in a specified order. [Formerly called "ProcessFlow" and "JobPlan."]. Test run and the actual copy process can run in automated form. AE ensures sufficient system resources. Periodical client copies can so be created in an easy and secure way.

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH