SAP BASIS: Client Administration and Local Client Copy in SAP

 SAP BASIS: Client Administration


Client copy is used to create new clients for training, test and production environments. The new clients are created using 000 client as reference. Administrator can choose what content to copy while doing client copy. For example if SAP_USER profile is selected, it copies all the user master data.

The new client is created using SCC4 transaction code. For the newly created client, SAP* and password "PASS" is used to login and perform client copy.

There are three types of client copies.

1. Local Client copy: It is the process of copying clients within the system.

2. Remote Client copy: In this process, clients are copied from another system.

3. Client Transport: It is the process of copying clients from another system. The difference between remote copy and client transport is, in client transport, transport tools are used to perform the copy.


Client copy process copies the three components like user master data, customizing data and cross-client customizing data from source client to target client. SAP_USER profile contains the user master data and except this profile all other is customizing data.

Below are some profiles available to select while performing the client copy.

a. SAP_USER -  It copies all the users, roles and authorizations

b. SAP_PROF - It copies only authorization profiles

c. SAP_CUST - It copies customizing data including authorization profiles

d. SAP_ALL - It copies all client data except change documents

e. SAP_APPL - It copies all the data same as SAP_ALL except user master data.


How to perform Local Client Copy:

Before executing client copy, new client is to be created in SCC4 transaction code. Watch the step by step video on how to create a new client.





Once the new client is created, login to the new client with user id and password as sap* and "pass" and execute SCCL transaction code or follow the below menu path.


1. Go to --> SAP Menu --> Tools --> Administration --> Client Admin --> Client Copy --> Local Copy

or Execute Transaction code SCCL.


2. Select a copy profile, Source Client and Schedule as Background Job.




3. Verify all the selected parameters and click on continue to execute local copy.

4. Execute SM37 to monitor the Background Job.

5. Execute Transaction code SCC3 to see the Client copy logs.















Location: Chicago, IL, USA

Comments

Post a Comment

Popular posts from this blog

SAP Security: Critical Authorization Objects

SAP Security: Critical Authorization Objects 1. S_TABU_DIS: This authorization object enables authorization check for displaying or modifying the table content. For accessing the table data, users use SE16, SM30 or SM31 transaction codes. This object contains two fields, DICBERCLS (authorization group) and ACTCT. 2. S_RFC: This authorization object enables authorization check for remote function call to access program modules (function modules). This authorization object contains three fields, RFC_TYPE, RFC_NAME and ACTCT. 3. S_DATASET: This authorization object enable file access at operating system level. This gives permission to access files from ABAP programs. This object contains three fields, File name, Program and Activity. 4. S_ADMI_FCD: This authorization objects enable access to various administrator activities like system monitoring, spool administration, client creations, update administration etc. This object contains one field, system administration functions. 5. S_DE
Read more

SAP Security: How to set auto Logoff for Inactive users in SAP

Image
How to set auto Logoff for Inactive users in SAP SAP provides an options for logging of inactive users in SAP automatically. Inactive means if there is no activity for a specific period of time. By setting the auto logoff improves the security in the SAP system. The auto logoff options is not active in the system by default. This needs to be activated using the profile parameter called rdisp/gui_auto_logout. The value for this parameter should be set in the form of seconds. The inactive users are logout of the system after the specific time period that is set in the parameter. The SAP system doesn't save the data before auto logoff and it does not popup any prompt before auto logoff. Procedure to set the value in the Profile parameter: Execute transaction code RZ10 Select the DEFAULT profile from the selection menu. Select the Extended maintenance and click on change icon. Click on the create parameter icon as shown below. Enter the new parameter name as rdisp/gui_auto_logout and c
Read more

SAP GRC Security Consultant Roles and Responsibilities

SAP GRC Security Consultant Roles and Responsibilities 1. SAP GRC Consultant should have a knowledge on Governance, Risk and Compliance products. 2. Should have a thorough knowledge as well as experience in relation between ERP and GRC systems. 3. Should have an experience in configuring and supporting of GRC components like ARA, ARM, BRM and EAM. 4. GRC consultant should be having good understanding of GRC architecture. 5. Should be having hands on experience in user provisioning, role management, risk analysis, emergency access management and monitoring. 6. Should have experience in pre installation, post installation, connector settings, rule building and MSMP workflows and BRF+ in the ARM and BRM components. 7. Should have experience in end to end implementation of GRC Access Controls. 8. Should have experience in designing and developing the SAP business process. 9. Should be able to gather business requirements and implement the same in the GRC AC modules like ARA, ARM, BRM and E
Read more