Monday, November 21, 2011

How to transport a client

Procedure: To transport clients from one system to another, go to System Administration then choose Tools -> Administration -> Client admin->Client transport -> Client export or transaction SCC8. In the client transport screen you can select a copy profile that matches your requirements and the target system in your CTS pipeline. Then you can execute the client export in the background or online. Before the client export starts, a popup screen shows all the information about the command files that will be created after the client export is done. After the process starts. You can watch the export process in client copy log using transaction SCC3.
After the client export procedure is completed, if you chose the client independent data then three transports are created in /usr/sap/trans/cofiles or there will be two transports:
KO for the client-independent data ( if selected). For example if the client export is done from development client 100 then the file will look like DEVKO0001.
KT for the client-specific data. For example DEVKT0001
KX for the SAPscript objects as Texts and forms. For example DEVKX0001
The data export is performed automatically. The output of the export includes the name of the COMMFILE that has to be imported. The following data files will be created in/usr/sap/trans/data directory using the same example given above:
For client dependent data: /usr/sap/trans/data/RT00001.DEV
For client independent customizing data: /usr/sap/trans/data/RO00001.DEV
For SAPscript data of a client: /usr/sap/trans/data/SX00011.DEV
Tips: Make sure that all the cofiles and the datafiles exist in the data and cofile directories before starting the import phase.
Then add all the command files to the buffer by using the TP command in /usr/sap/trans/bin directory as following:
tp addtobuffer 
Using the above example cofile: tp addtobuffer devkt00001 qas (if qas is our target system)
tp addtobuffer devko00001 qas
tp addtobuffer devkx00001 qas
Then logon as adm to the target system and then use then import the transports as following:
tp import devkt00001 qas client100 u148 – For the client dependent data
tp import devko00001 qas client100 u148 – For client independent data
(In the above example QAS is the target system and 100 is the target client)
After you import a client from another system, you must perform post-processing, activities in order to adapt the runtime environment to the current state of the data. To execute post-processing, choose Tools -> Administration- >Client admin ->Client transport->client import or transaction SCC7. Transaction SCC7 will take you to the client import post-processing screen . In that screen the transport from the last tp import is proposed. Please check the transport number and if every thing is according to the order then press enter and that will take care of the post processing activities. You can also use SCC2 to execute the same process as in transaction SCC7. During this process, the SAPscript texts are imported and application reports are generated. If there are inconsistencies, you need to repeat the import after checking the log.
If you get any problem importing the SAPscript objects then use the RSTXR3TR program in the target client to import those. In this screen you can enter the transport request for the SAPscript object. According to the above example devkx00001. In the second line you need to enter the path for the SAPscript data file as following:
/usr/sap/trans/SX00001.DEV (using the above example)
You can choose the import option from the “mode” option. Then you can continue to execute the program and it will successfully complete the import of SAPscript objects to the target client.
Up to release 3.0, RSCLIEXP program can be used to create the command files. The tp command is used to do the import as we have seen before and the RSCLIIMP program is executed for the post-processing activities and the consistency of data.
Using the transport procedure in 4.0
In 4.0 after the client is exported from the source system using transaction SCC8 as we have seen in the client export section, the following transport files are created.
KO: For the client-independent data (if the copy profile selected includes client independent data:
KR: For the client-specific data.
KX: For the Texts and forms.
When all the above transports get released from the source system, the data is exported to the data files of /usr/sap/trans/data directory automatically. The cofiles are also created in the /usr/sap/trans/cofiles directory.
Then the command files need to be added to the buffer for the import using the format from the cofiles as following:
Logon to the target system as adm
cd /usr/sap/trans/bin – Change to the transport directory
tp addtobuffer – Adds to the buffer
If you are transporting to a new client then the new client should be created in the target system. Then you can start the import into the target system as shown in the following UNIX example:
tp import client from /usr/sap/trans/bin directory
After the “tp import” process completes successfully, start transaction SCC2 and then execute the import into the target client. This process imports all the SAPscript objects and generates all the programs. After the client is imported successfully, you should perform the post-processing activities by using the following path:
Tools ->Administration->Client admin->Client transport->Post-process import.
After the post processing is done, we recommend doing table compare between the source client and the target client to check all the client dependent and independent tables for consistency.

Saturday, November 19, 2011

Some simple UNIX commands used for SAP administration

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 < file> 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

Friday, November 18, 2011

How to do a Remote Client Copy

Step by Step Procedure to copy a Client to the Remote SAP Server.
Logon to destination SAP server
Use Transaction Code SCC4
Go to change mode
Create a new client, assign client number & description as per request
Logoff from current client.
Login to newly created client in destination SAP server using the following credentials :
i. Client Number : Newly created one
ii User Id : SAP*
iii Password : PASS
Use Transaction Code SM59 to create a RFC Connection for client copy if does not exist already.
RFC Connection should have Target Server as Destination and the test results should say “Connection test OK”
Use SCC9 Transaction code to go to client copy screen.
Give profile as per the request.
Select RFC destination created for the purpose for the source client to client copy
Use Transaction code SCC3 for monitoring the 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.

Thursday, November 17, 2011

Change Data In Table Without Authorization Using Transaction se16

There is a way to change entries of a table with SE16 even if you don’t have the authorization:
Go in SE16, enter your table Name (ex: USR02). Display the entry (or entries) you want to modify.
When you have your entry, write ‘/h’ to go in debug mode. Cross the line you want to modify and press F7 (display function). Here, you are in the code… Press F7 again to skip some code…
Now you should see the code:
Refresh Exclude_Tab.
If Code = ‘SHOW’.
Set Titlebar ‘TAB’ With Name ‘anzeigen’(100).
Elseif Code = ‘EDIT’.
Change the value from SHOW to EDIT, click Change FLD Contents, and press F8…
or to delete an entry
Change the value from SHOW to DELE, click Change FLD Contents, and press F8…
Here we are… You can change the value to what you want, and don’t forget to save!

Wednesday, November 16, 2011

How to modify SAP System Parameter

1. Log on to any client in the appropriate SAP system.
2. Go to transaction RZ10.
3. On the Edit Profiles screen, select the _DVEBMGS00_SAP Profilefrom the dropdown, or whatever instance profile you need to change. In theEdit profile section, click the radio button to the left of Extended maintenance. Click the Change button.
4. On the Maintain R/3 Profile screen, locate the parameter that needs to be changed in the Parameter name column. Change the matching value underParameter value to the new value. Click the Copy button. Click the white arrow on green picture-icon.
5. On the Edit Profiles screen, click the Save picture-icon.
6. On the Save profile popup, click the No button.
7. On the Activate profile popup, click the Yes button.
8. On the Edit Profiles popup, click the green √ button.
9. On the Caution! Caution! Caution! popup, click the green √ button.
10. 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.
11. You will not get a confirmation message. You may now leave the RZ10transaction.