Scribd
Upload
16 views14 pages

Client Copy Procedure

Uploaded by

Ahmed Ali Syed Brilliant
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
16 views14 pages

Client Copy Procedure

Uploaded by

Ahmed Ali Syed Brilliant
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 14

AWSM ERP Project

Client Copy Procedure

Title: Client Copy Procedure

Purpose:
This document describes the procedure for creating new clients and performing client copies to new and
existing clients.
Adding New Client:
1. Verify how new client is to be used and in which system to create the client.

2. Add entry in client table for new client using transaction “SCC4”

3. Verify source client(s) from person requesting new client and what data must be copied into the
new client (i.e. configuration, master and transactional data, user master data, etc.).

4. Verify there is adequate space available in database to perform a client copy to the new client.

a. Database space requirements are determined by the amount of data in the source client
and the client copy profile to be used. The space requirements can vary anywhere from
1 GB up to 5 GB
.
b. If necessary, add space to data files.

5. Logon to new client as user SAP* and schedule the client copy as a background job.

6. Create logical system for the new client.

7. If new client is not in development system (ECL), transport the logical system to the system
where new client resides.

8. Assign the logical system to the new client.

9. Determine if new client will be added to CUA. If it will be added to CUA:

a. Create CUA RFC


b. Notify Security Team that new client must be added to CUA

10. Determine if new client must be in the transport path. If client must be in transport path, update
the appropriate target group.

11. Verify client copy completed successfully.

12. Create RFC for new client to allow Derivation transports. The RFC must adhere to the following
naming standard:
FINBTR@<SID>CLNT<Client Number> (i.e. FINBTR@QASCLNT810)

13. Transport Derivation change request (ECLK901858) to new client.

14. Reset Number Range Buffer with transaction “SM56”.

15. Execute the following reports in transaction “SE38”

AWSM ERP Project Page 1 of 14


AWSM ERP Project
Client Copy Procedure

a. RGUGGLT0:

Select “execute” icon

AWSM ERP Project Page 2 of 14


AWSM ERP Project
Client Copy Procedure

AWSM ERP Project Page 3 of 14


AWSM ERP Project
Client Copy Procedure

b. RGZZGLUX:

Select “execute” icon

AWSM ERP Project Page 4 of 14


AWSM ERP Project
Client Copy Procedure

AWSM ERP Project Page 5 of 14


AWSM ERP Project
Client Copy Procedure

c. RGIMOVV0

Select “execute” icon

AWSM ERP Project Page 6 of 14


AWSM ERP Project
Client Copy Procedure

AWSM ERP Project Page 7 of 14


AWSM ERP Project
Client Copy Procedure

d. RGUGBR00

Select “execute” icon

AWSM ERP Project Page 8 of 14


AWSM ERP Project
Client Copy Procedure

Select all options and select execute

AWSM ERP Project Page 9 of 14


AWSM ERP Project
Client Copy Procedure

AWSM ERP Project Page 10 of 14


AWSM ERP Project
Client Copy Procedure

AWSM ERP Project Page 11 of 14


AWSM ERP Project
Client Copy Procedure

e. FMGL_CHANGE_APPL_IN_LEDGER

Select “execute” icon

AWSM ERP Project Page 12 of 14


AWSM ERP Project
Client Copy Procedure

16. Notify person requesting new client that client is ready for use.

AWSM ERP Project Page 13 of 14


AWSM ERP Project
Client Copy Procedure

Client Copy/Refresh of an Existing Client:


1. Verify source client from person(s) requesting client refresh and what data must be copied
into the new client (i.e. configuration, master and transactional data, user master data, etc.).

2. Verify timing for scheduling client refresh

3. Verify there is adequate space in database to perform the client copy. (check server disk
space & DB02)

4. Logon to client that is to be refreshed as yourself (or you can use DDIC or SAP*) and
schedule client copy as background job. (SCCL)

5. Verify client copy completed successfully. (SM37, SM50)

6. Transport Derivation change request (ECLK901858) to new client. (STMS)

7. Reset Number Range Buffer with transaction. (SM56)

8. Notify person requesting client refresh that client is ready for use.

AWSM ERP Project Page 14 of 14

You might also like