Local Client Copy - SCCL

Step by Step Procedure to create a copy of a client locally in the same SAP server.

1. Logon to SAP server

2. Use Transaction Code SCC4

3. Go to change mode

4. Create a new client, assign client number & description as per request

5. Logoff from current client.

6. Login to newly created client using the following credentials :

i. Client Number : Newly created one

ii. User Id : SAP*

iii. Password : PASS

7. Use Transaction Code SCCL for local client copy

8. Give reference client for copy and profile as per the request

9. Use SCC3 Transaction code to monitor progress of Client Copy.

Golden rules for CLIENT Copies

1. Master data can not be copied without copying transactional data and transactional data can not be copied without copying master data.

2. Application data (transactional and master) should not be copied without copying configuration data.

3. Client copy requires a valid client as the destination client. Make sure that the client exists in T000 table and you can logon to that client.

4. The transport system and the transport management system of 4.0 are the only proper tool to be use to keep multiple systems in sync by transporting development and customizing changes to another instance.

5. When you copy a client from one system to another, client-independent tables should only be copied if they are not yet modified in the target system.

6. We recommend the users to read all the OSS notes regarding client copy that applies to their SAP release. It is always better to schedule the client copy job in the background for the night run when normal work is not taking place.

7. Always check the database space before performing a client copy.

8. To avoid data inconsistencies all the users working in the source and target clients should logoff from the system.

9. RSCLICHK program should be run in the target system remotely before doing a client export. This program will give information about the missing definitions from the data dictionary in the target. After executing this program and getting successful results you can ensure that the client copy will have no problems. In case some tables are different; you can use SE11 to compare and adjust the table structure in both the system before the client copy. A remote test client copy also can be executed to know the differences between source client and target client.

10. If you are not in release 2.2 then do not use R3trans to copy a client.

Change default SAP Logo on front screen..

Replace SAP Splash Logo : Change default SAP Logo on front screen..

1. Identify a picture to replace the existing SAP logo. This picture can be in any valid picture format - gif, bmp, jpg. But convert it to jpg since that is the smallest available picture type. Store the picture somewhere on your workstation.

2. Go to transaction SMW0.

3. On the SAP Web Repository: Initial Screen, click “on” the radio button for Binary data for WebRFC applications, and click the Find icon or press F8. On the SAP Web Repository: Objection selection screen, click the Execute icon or press F8.

4. On the SAP Web Repository: Object display screen, first make sure that the mime extension exists for your picture type. Click Settings -> Maintain MIME types. Look to the far right of the Data Browser: Table MIMETYPES Select Entries screen, and if you don’t see your file type - gif, jpg, bmp - then you need to add it. Once you at done, back out to SAP Web Repository: Object display screen.

5. Now you can upload your picture. Click the Create icon or press F5. Fill in the name of your picture and a brief description and click the Import icon. Then provide the location of your picture and load it in.

6. Go to transaction SM30. Fill in the table name SSM_CUST and click Maintain.

7. On the Change View “Set Values for the Session Manager / Profile Generator” screen, click New Entries and add an entry called START_IMAGE and set the value to the name of your picture created in step #5. Then press the Save icon.

You have replaced the SAP splash screen picture. Log off and back on to view your work!

SAP R/3 dispatcher and work processes

Types of work processes:

• Message : Coordinates the communication between different instances of a single SAP R/3 system. Used for Logon purpose and load balancing.

• Dispatcher : Redirect the request from GUI client to free process.

• Dialog : Interpreting the ABAP code and execute the business logic. Used for interactive online processing.

• Batch : For Background jobs.

• Enqueue : Single “Central Lock Management Service” that controls the locking mechanism between the different application servers and the database.

• Update : Responsible for consistency in asynchronous data changes.

• Gateway : Used for transport of bigger amount of data between application servers as well as external (non SAP) systems that communicate with SAP.

Profile Parameters for Client Login and password security (RZ10, RZ11)

login/accept_sso2_ticket

login/certificate_request_ca_url

login/certificate_request_subject

login/create_sso2_ticket

login/disable_cpic

login/disable_multi_gui_login

login/disable_multi_rfc_login

login/disable_password_logon

login/failed_user_auto_unlock

login/fails_to_session_end

login/fails_to_user_lock
login/min_password_diff

login/min_password_digits

login/min_password_letters

login/min_password_lng

login/min_password_specials

login/no_automatic_user_sapstar

login/password_change_for_SSO

login/password_expiration_time

login/password_logon_usergroup

login/password_max_new_valid

login/password_max_reset_valid

login/system_client

login/ticket_expiration_time

login/ticket_only_by_https

login/ticket_only_to_host

login/ticketcache_entries_max

login/ticketcache_off

login/update_logon_timestamp

Increasing or Decreasing the Number of Work Processes

1. Log on to any client in the appropriate SAP system.

2. Go to transaction RZ10.

3. On the Save profile popup, click the No button.

4. On the Edit Profiles screen, select the _DVEBMGS00_SAP Profile from the dropdown, or whatever instance profile you need to change. In the Edit profile section, click the radio button to the left of Extended maintenance. Click the Change button.

5. On the Maintain R/3 Profile screen, locate the dialog processes rdisp/wp_no_dialine in the Parameter name column. Change the matching value under Parameter value to the new value. Click the Copy button. Do the same for the batch processes, rdisp/wp_no_btc, and the update processes, rdisp/wp_no_vb. Be sure to click the Copy button after each change. When all the changes have been made, click the white arrow on green picture-icon.

6. On the Edit Profiles screen, click the Save picture-icon.

7. On the Save profile popup, click the No button.

8. On the Activate profile popup, click the Yes button.

9. On the Edit Profiles popup, click the green √ button.

10. On the Caution! Caution! Caution! popup, click the green √ button.

11. If you receive a Possible Inconsistencies in OP Modes screen, double click over the unless you are unsure of why this message has been displayed.

12. You will not get a confirmation message. You may now leave the RZ10 transaction.

What Needs to Be Backed Up?

The PRD Instance

Daily backup should be made for these SAP specific directories:

/usr/sap/

/sapmnt/

/usr/sap/trans on the TMS Domain Controller Server

Any directories containing flat files that are used by the SAP instance

Daily backups should be made for these Oracle specific directories:

/oracle

Directory holding redo logs if not in the /oracle structure

Weekly backup should be made for these OS specific directories:

Root

/etc

/dev

For Oracle, the entire /oracle directory should be backed up daily if there is only one Oracle Instance on the server, and each separate /oracle/ directory if there is more than one instance on the server.

It is also recommended that a full offline image of the entire server be made before the monthly closing cycle.

The DEV and QAS Instances

Weekly backup should be made for these SAP specific directories:

/usr/sap/

/sapmnt/

Any directories containing flat files that are used by the SAP instance

Weekly backups should be made for these Oracle specific directories:

/oracle

Directory holding redo logs if not in the /oracle structure

Monthly backup should be made for these OS specific directories:

Root

/etc

/dev

For Oracle, the entire /oracle directory should be backed up daily if there is only one Oracle Instance on the server, and each separate /oracle/ directory if there is more than one instance on the server.

It is also recommended that a full offline image of the entire server be made at the same time every month.

Creating a User Audit Profile

Creating a User Audit Profile

1. Log on to any client in the appropriate SAP system.

2. Go to transaction SM19.

3. From the top-most menu bar on the Security Audit: Administer Audit
Profile screen, click Profile -> Create.

4. On the Create new profile popup, type in a new Profile name and click
the green √ picture-icon.

5. On the Filter 1 tab of the Security Audit: Administer Audit Profile
screen, click the □ to the left of Filter active to place a √ in the box.
In the Selection criteria section, select the Clients and User names to
be traced. In the Audit classes section, click “on” all the auditing
functions you need for this profile. In the Events section, click the
radio button to the left of the level of auditing you need. Once you
have entered all your trace information, click the Save picture-icon.
You will receive an Audit profile saved in the status bar at the bottom
of the screen.

6. Please note that while the user trace profile has been saved, it is not
yet active. To activate the user trace, see the next section Activating
a User Audit Profile.

7. You may now leave the SM19 transaction.

Activating a User Audit Profile

1. Log on to any client in the appropriate SAP system.

2. Go to transaction SM19.

3. On the Security Audit: Administer Audit Profile screen, select the audit
profile to be activated from the Profile dropdown. Click the lit match
picture-icon to activate it. You will receive an Audit profile activated
for next system start in the status bar at the bottom of the screen.
The audit will not begin until after the SAP instance has been recycled.

4. You may now leave the SM19 transaction.

Viewing the Audit Analysis Report

1. Log on to any client in the appropriate SAP system.

2. Go to transaction SM20.

3. In the Selection, Audit classes, and Events to select sections of the
Security Audit Log: Local Analysis screen, provide your information to
filter the audit information. If you need to trace the activities of a
specific user, be sure to include that user’s ID. Click the Re-read
audit log button.

4. The resulting list is displayed. This list can be printed using the usual
methods.

5. You may now leave the SM20 transaction.

UNIX Kernel Patch: UNIX Kernel Replacement

1. Download the two necessary archives - SAPEXE.SAR and SAPEXEDB.SAR - from SAP MarketPlace. There files can be found at http://service.sap.com/patches. Be careful that your Basis level is high enough to use the patch level of the files you download. For example, if your SAP instance is on Basis level 39 and the description of one of the SAPEXE.SAR files is Stack 42, you need to download a SAPEXE.SAR of a lower level.

2. Once both files have been downloaded, log on to the UNIX server as adm and copy them up to a directory on the UNIX server - I use one called /usr/sap/trans/NewKernel. unCAR the files with SAPCAR command “sapcar -xvf “SAPEXE*.SAR”.

3. As adm, stop the SAP instance. Log on as ora and stop the TNS listener, and log on as root and stop saposcol.

4. Make a backup of your run directory before patching. I usually create a /usr/sap//SYS/exe/backup_run and copy all the files in /usr/sap//SYS/exe/run to it.

5. Copy all the files unCARed in step 2 to /usr/sap//SYS/exe/run. If prompted, overwrite all.

6. Change the owner of saposcol to root, sapdba & all br* files to ora, and all the rest to adm.

7. Start saposcol, the TNS listeners, and the SAP instance.

8. You have patched your UNIX SAP kernel. If you run into any problems starting your SAP instances, stop everything, rename the directories /usr/sap//SYS/exe/run to /usr/sap//SYS/exe/bad_run and /usr/sap//SYS/exe/backup_run to /usr/sap//SYS/exe/run to restore your old kernel.

UNIX commands used for SAP administration

1. stopsap/startsap for stopping/starting SAP+ DB, stopsap r3/startsap r3 for stopping/starting R3

2. Cdpro for checking the profiles path SAPMNT//profile

3. Cdexe for checking the kernel folder

4. find . -name filename -print for checking the file in the present directory

5. dpmon pf= , jcmon pf=

6. df -k, bdf for checking all file system usages; df -k ., bdf. for individual file usages

7. ls -lrt for listing of files according to the date modified

8. du -a | sort -k 1n,1 for sorting the files in a recursive manner.

9. h for listing previous used commands.

10. rm <> for removing file, gzip for zipping the file.

11. Ps -ef is to check the how many running process and Kill any running process

12. gunzip to unzip file

13. tar -xvzf file name to run the zip folder of file content

14. mv mo from one path to another

15. Rf remove forcifully any file

16. Make command to effect any coading content

17. make clean to clean the effect of make command

18. cp coppy from one location to another

19. pwd check the current directory