What is SAP ? 1. what is SAP (System, Application and Products)? SAP is an ERP(Enterprise Resource Planner).

. SAP is a software for Big Enterprises as well as for Small and Medium EnterPrises. SAP contains all functional modules like MM, PP, HR, FI CO SD SAP is Hardware, Database and OS independent. It can be installed on any hardware and it can work with different databases like Orale, MS SQL, DB2.SAP also provides Industry specific software like Banking, Aviation, Oil industry, Defense etc. Supporting modules for reporting and for presentation are also available from SAP. Like SAP BW/BI - SAP Business Intelligence For Dynamic Reports SAP EP - Enterprise Portal For Company portal to display company news and give Single Sign on for every user. SAP XI - eXchange Infrastructure To merge Companys old legacy Software with SAP ERP SAP Tips & Tricks Logging on without being authorized Client 066 usually exists in a SAP system because of EarlyWatch services. Often this client does not have master users. If it is true, anyone can log into the system using the client 066, user SAP*, and password PASS. Enjoy yourself. Locking the whole system Using the command tp locksys SysID only the user SAP* will be allowed to login. The commandtp unlocksys SysID cancels the lock. Connection between SAP R/3 and operating system : Release SAP Job from OS The command sapevt can be used to trigger an event from the operation system. Thus, a job previously defined within R/3 will be released. SQL code help Run the command oerr ora error number under user oraSysID. Direct input logs The transaction BMV0 (direct input logs) shows all direct input logs. Oracle import and export explanations Run the command imp help=yes under user oraSysID. This format can also be used with exp,impst, and expst. Table analyses between two systems The contents of a table between two systems can be checked through the transaction OY19. Setting up module FI/CO without using IMG Almost all parameters can be set using the transactions ORFA (Asset Accounting), ORFB (Financial Accounting), and ORKS (Cost Center Accounting). Long messages on footer Click on the message and hold the mouse button. After moving the mouse to the left side. Graphics on SAPscript The program RSTXLDMC can be used to upload graphics (file extension .tif on PC files) into individual standard text. Deleting cost elements and cost centers Since they have no postings you can use the transaction KA04 for deleting cost elements and KS04 for deleting cost centers. Filling up an empty date field quickly Strike the key F4 (or click on matchcode symbol) and press ESCAPE. The current date is automaticly set. Displaying check object when not authorized Soon after the lock try to access the transaction SU53. It reports the last objects verified and also the respective values.

Correction and transport system The transaction SE10 provides the easiest way to manage any request/transport and corrections. Helpful reports RSCLTCOP Copy tables across clients RSAVGL00 Table adjustment across clients RSINCL00 Extended program list RSBDCSUB Release batch-input sessions automaticly RSTXSCRP Transport SAPscript files across systems RSORAREL Get the Oracle Release RGUGBR00 Substitution/Validation utility RSPARAM Display all instance parameters RSUSR003 Check the passwords of users SAP* and DDIC in all clients RSUSR006 List users last login Reapplying hot packages If you accidently applied hot packages out of sequence for instance. Use the transaction SM31 to modify table PAT03. You have to choose the desired patch and click on delete entry. Scheduling of system maintenance jobs RSBTCDEL Clean the old background job records RSDBCREO Clean batch input session log RSPO0041 Removing old spooling objects RSSNAPDL Clean the old ABAP error dumps List of most used SAP extensions and their components CUST1 MENUS000+C01 Customer option in the Office menu CUST2 MENUS000+C02 Customer option in the Logistics menu CUST3 MENUS000+C03 Customer option in the Accounting menu CUST4 MENUS000+C04 Customer option in the Human Resources menu CUST5 MENUS000+C05 Customer option in the Information Systems menu CUST6 MENUS000+C06 Customer option in the Tools menu CUST7 MENUS000+C07 Customer option in the System menu ZXUSRU01 Exit_saplsusf_001 At login time SAPMF02D Exit_sapmf02d_001 When saving customer master data SAPMF02K Exit_sapmf02k_001 When saving vendor master data M61X0001 Exit_saplm61c_001 When processing MRP planning M61X0001 Exit_sapmm61x_001 When processing MRP planning FYTX0001 Exit_saplv61a_001 Modifications in pricing procedures MBCF0002 Exit_sapmm07m_001 Checks for materials documents SDVFX002 Exit_saplv60b_002 Link between SD and FI documents M06B0003 Exit_sapmm06b_001 When saving MM documents Before going live It is highly advisable to increase the next extends size of some tables and their indexes even before initial loadings Reset SAINT queue / reset SPAM queue / reset OCS queue Find below steps to Reset the OCS queue while applying add on / support packs. While applying add on or support packs, if process hang up in IMPORT_PROPER phase of DDIC activation phase etc and if you are not able to re import or reset the queue, please follow below procedure. At command line on <sidadm> prompt Run below command tp r3i all <SID> pf=/usr/sap/trans/bin/TP_DOMAIN_<SID>.PFL tag=spam -Dclientcascade=yes -Drepeatonerror=8 After this it will again come on your <sidadm> prompt. Then go in se37 run below program ocs_reset_queue Hit F8

Give following parameter IV_TOOL = SPAM / SAINT IV_FORCE = X Hit execute. Now run SPAM or SAINT and redefine your queue.

Steps to install extra languages in to a SAP system.

1. Download Language DVD from SAP Service Market Place suitable to your SAP ECC version(e.g SAP 4.7, ECC 6.0 etc) 2. Place .PAT files to EPS/in folder. 3. Login to SAP in client 000 with Admin user. 4. Execute SE38 5. Execute program RSCPINST 6. Add an entry for the language you are willing to install. 7. Execute transaction SMLT 8. Create a new entry in SMLT for the required language. Give Supplementation language as English. 9. Click on the Import Language/Package symbol next to newly created entry for your language. 10. Default path is set to EPS/in folder, where it will search for the .PAT file required. 11. Found language should show either Green or Yellow button. If it is showing Red button it means you have downloaded the wrong source. Double check on SAP Service Market Place and download the right source files. 12. Press Execute to install the selected Language. 13. Monitor the import process in SM37 and Import transport logs. 14. Once installation get finished go to SE38, execute RSCPINST. 15. Click on Simulate button and copy new value for parameter zcsa/installed_languages. 16. Go back and activate the settings. 17. Go to RZ10 and change instance profile.Add new parameter zcsa/installed_languages and set its value as suggested in point 15 above. 18. Restart the SAP instance and try login with new Language. 19. Go to SE38 Execute RSTLAN_IMPORT_OCS Select the newly installed language and press OK It will show you the support packages whose language parts you want to import. 20. GO to Next screen. Copy the PAR or CAR files to EPS/in folder for all support packages showing in RED. This will import the language specific parts of those support packages. Press Import Language Data and Overwrite. It will show you the message The Support Package language Data was imported correctly. All system languages are up to date. 21. Next step is to copy the client specific data to required client. Login to yr non default client or product client. Go to SE38 and execute RSREFILL. 22. Reference Language EN Language to be updated Newly installed one Update Mode I Log Directory \sapmnt\trans\*.snd 23. Go to SE38 Execute RSTLAN_SUPPLEMENT_UNI. Select your language from drop down Press Client Maintenance with Customizing Translations what is SAP Note Notes are released by SAP to correct errors or to provide some missing functionality. They also serve as a knowledge bank of procedure for some activities in the SAP system that is not available with the documentation. These Notes may require the end-users to make some corrections to the source code. The Note would also mention at what support package level the error is corrected in. Sometimes it is not possible to apply all the support packages. Then the corrections have to be performed manually. It is a good idea to document and make the corrections in an orderly fashion. This will be of help at a later point of time during an upgrade or when further support packages are being applied, which may affect the same programs.

Whenever a line is being inserted or deleted, SAP recommends that the note number (that suggested the change) be typed on the same line. This will be very helpful later during the application of further corrections. It is also recommended that the ABAP modification assistant is activated to be able to track changes. Download SAP Note SAP Notes can be download from SAP Service Market Place SMP (OSS Online SAP Support) from below sap notes link : Download SAP Note Link : service.sap.com/notes How to apply SAP Note Types of SAP Note : Implementable : One can download Implementable SAP Note and apply in the system from SNOTE Transaction. Which will make the changes in SAP notes to the SAP system automatically. When you will download from SAP Notes browser it will show in In processing status and once implemented it will show Successfully Implemented. Can not be implement : This type of sap note may contain either manual changes which will be carried out by SAP consultants or contains only knowledge bank of procedures for some activities. One can download this type of note to SAP system but will not be able to implement. Keywords: support packages in sap, support pack upgrade sap, support packs in sap What is Support Packs in SAP: SAP releases Support packs, which are a collection of advanced corrections. Types of Support Packages are listed below: HR Support Package, ABAP Support Package, APPL Support Package, Basis Support Package Add-on Support Packages These are available for download directly from the SAP Service marketplace at below link SPAM package download: service.sap.com/patches On demand the Support packs available are sent in form of CDs to SAPs customers. The system should be update by the designated personnel as early as possible. The support packages have certain dependencies and the same is to be checked on. Basis and ABAP support packages can be loaded independently whereas special care is to be taken while loading application support packages to include the CRTs of addon packages otherwise some conflict can arise and system can go to an unstable state. How to apply Support Packs (SPAM package) to SAP : After collecting the required information on CRTs and the like, the Support packs can either be downloaded from the SAPNET or uploaded from (Support packages) CD into the usr/sap/trans/EPS/in directory. The CAR files will also have to be extracted to the same directory. Login to the system on client 000 - With any user-id other than SAP* or DDIC. The login-id should have SAP-ALL and SAP-NEW authorizations. Run transaction code SPAM to invoke the SAP Patch manager. You can choose the upload button to upload data directly from /usr/sap/trans/EPS/in directory on the server or from a path on your local Front end. Execute the SPAM transaction again. You will now be able to see the support packs window. Use the drop down box menu to verify the queue. The support packs will be in the queue followed by their corresponding CRTs for the different add-on. Press the consistency check button to verify the queue is okay. Go to the Menu Option settings on the SPAM screen and change the settings from S to T (Standard to Test mode) The queue may be applied in test mode to check if it has conflict with any object that is already modified in the system. If there are any modifications to the program that the hot pack is also affecting, then the hot pack will create versions for the same. It will make the program delivered by it to be the current request the active version. Transaction SPAU (SAP Adjustments) will need to be run to make the required adjustments. If CIN programs are also affected, please check with SAP India. Please Note: Make sure that you have applied the latest SPAM update before you apply any other patches. Always apply patches to your test system before you start to apply them to your production system!

Only the system administrator should be able to download, apply, confirm, or reset the status of patches. To use all the SPAM functions, you require the authorizations.S_CTS_TR_ALL and S_CTS_ADMIN. You can find both of them in the authorization profile S_A.SYSTEM Ensure that you are logged into client 000 with the proper authorizations. If you log into another client, or do not have the correct authorizations, you can only use the display functions. Make all the users log off before you apply patches in scenario S. During the patch application steps, the R/3 system must not be in use, i.e. only the system administrator is allowed to be logged on. Otherwise you risk program terminations. Shut down all application servers except the central one for the duration of the import. Otherwise, buffer synchronization problems with program terminations, and possibly data inconsistency, may result. You cannot have any incompletely applied patches in your system. To check this, under Directory choose Aborted patches and then choose Display. No patches should be displayed. Under the section Patch, the status should display a green traffic light. Check the logs before confirming the patch application. Never apply patches directly with tp. You will lose all of your modifications and overwrite your Add-On, if you have installed one. If you have made a modification adjustment for the Patch Queue in your test system, ensure that you do not import the resulting modification adjustment transport into further systems until you have applied the same patches to these systems. While a patch is being applied the session is blocked. Open a second session before you apply the patch to avoid logging on again. What is sap kernel R/3 consists of 2 parts, the database and the kernel. The Kernel consists of the executable programs that reside under the path /sapmnt/<SID>/exe. These files are responsible to startup the R/3 system, initialize the memory, create buffers and start managing the requests from users and effectively utilizing the hardware resources to do so. The kernel is also responsible for starting and stopping all the application services like dispatcher, message server, collector etc. The kernel provides latest upgrade to driver files used for printing etc.,hence need to be upgraded constantly to better utilize the hardware resources and new functionality released by SAP. What is sap kernel upgrade The Database part consists of the ABAP Repository which consists of programs, tables, structures, domains, data elements etc., they reside inside the database software under the instance name <SID>. They may also be accessed partly through standard database tools. However, it is not recommended to make any modifications to the database directly because, direct modifications to database are not reflected in the ABAP data dictionary. The Database Release and the R/3 kernel release may differ. Always the kernel release should be equal to or greater than the database release. SAP releases the various kernel and their downward compatibility in R/3 notes. These notes are frequently updated and hence it is required that though you might have obtained a hard copy long time back, it is still mandatory for you to access the same note again to understand if there are any changes. The downward compatibility matrix shows what is the lowest release of R/3 database that the kernel can work with. Before you can upgrade to a higher kernel version, it must be checked whether your existing Operating System release and Database release are compatible. Otherwise, you will definitely need to upgrade them before upgrading the kernel. How to upgrade the kernel is also available as a note on the R/3 Online Support System. However, before upgrade of the kernel, the old kernel should be backup so that it can be used to revert back to old status in case of any problem. How To Find Out Current Kernel Version Sap 1. Start transaction SM51. Position the cursor on the server from which you want the current kernel version and patch level, then choose function Release notes. You will get a list containing information about the current R/3 kernel as well as the supported environment and a listing of all the patch texts with their corresponding note numbers. 2. From the operating system level - change to the directory that contains the SAP executables, i.e., /sapmnt/<SAPSID>/exe, and execute disp+work V This procedure should allow the Basis team to Stop or Start SAP Service on a Windows server.

1. Logon to Server using <SID>ADM id 2. Double click on MMC Icon for SAP on Desktop of SAP Admin 3. Select Instance to Stop / Start 4. Right Click Instance/Use the buttons given on MMC tool bar. 5. Click Start/Stop and wait for couple of minutes for status change of the Instance. 6. For starting the sequence of Instances color visual display would be Gray -> Yellow -> Green 7. For stop the sequence of Instances color visual display would be Green -> Yellow ->Gray This procedure should allow the Basis team to Stop or Start SAP Service on a Unix/Linux server. 1. Logon to server using telnet with any id. 2. login to user <SIDADM> using command su - <sid>adm 3. To start SAP Services use command startsap a 4. To stop SAP Services use command stopsap 5. To log off from server use command exit 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. Modifying System Parameters

1. Log on to any client in the appropriate SAP system. 2. Go to transaction RZ10. 3. On the Edit Profiles screen, select the <SID>_DVEBMGS00_SAP<SID> 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 <No> 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. Stopping Run-Away or Bad Work Processes 1. Log on to any client in the appropriate SAP system. 2. Go to transaction SM50. 3. On the Process Overview screen, find the process which must be stopped. Place a in the to the left of the process number to be stopped by pressing Space. On the top-most menu bar, click the Process Cancel without core. 4. Click the blue arrow circle picture-icon to refresh the Process Overview screen until the stopped process has cleared from the display. 5. You may now leave the SM50 transaction. If this does not kill the process, you can go to transaction SM04 and kill the users session. If this does not kill the process, you can log on to the server, open a Task Manager session, and End the Process. If this does not kill the session, there is an executable in the RUN directory on the server called sapntkill.exe. Run it providing the process ID number. If none of the above work, you have no choice but to bounce the SAP instance and/or possibly the serve. This procedure should allow the Basis team to create a RFC connection in any SAP server. 1. Logon to SAP server 2. Use Transaction Code SM59 3. On SM59 screen click on Create button 4. On the new screen, give RFC destination name Name by which the connection would be identified 5. Give Connection Type ( 3 for any SAP to SAP communication ) F4 Help will list down all possible types of connections 6. Give Description for the RFC Connection Generally the purpose of the connection is mentioned here 7. Click SAVE 8. Give IP address/Host name and system number for destination server inTechnical Settings tab 9. Click SAVE 10. Use Test Connection to check RFC. 11. If Trusted RFC connection is required, give user credentials in Logon/Security tab Transporting 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: <sid>KO<no> 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. <sid>KT<no> for the client-specific data. For example DEVKT0001 <sid>KX<no> 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 /usr/sap/trans/data/DX00001.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 <cofile name> <target sid name> 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 <sid>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/data/<data file for the SAPscript objects> /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 postprocessing 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. <sid>KO<no>: For the client-independent data (if the copy profile selected includes client independent data: <sid>KR<no>: For the client-specific data. <sid>KX<no>: 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 <sid>adm cd /usr/sap/trans/bin - Change to the transport directory tp addtobuffer <command file-name> <target-sys-id> - 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 <target-sys-id> client<target-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. 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. SAP BASIS Interview Questions: Q. What is difference between Application Server & central instance? Ans.- Central instance have message server and dialog, update, spool, enque, gateway, background work processes. Application server has only Dialog, update, spool, gateway and Background work process. Note: SAP server has only one message server and Enqueue server. Q. What is difference between consolidated & delivery routs. Ans. - In a 3 system landscape, transports from development and quality is called Consolidation Route (this can have target groups & CTC). Transports route from Quality to production is called delivery route. Q. What are the prerequisites for applying a support pack? What is the Procedure for applying support packs? Download the Support Patches from market place. Login through 000 client with user DDIC. Go to Transaction SAPM. From the menu support packages - > load package -> from Front End.. Then Select display button in the screen and select the patch and gives import. Import the Package queue. Take care that no users are in online while u upload the support packages. Q. Auto Start SAP on Windows Instance Use transaction RZ10 to edit your startup profile. Add the following entry: Autostart = 1 Then save the profile. Next time your server reboots, your SAP instance will come up automatically! Q. What is the procedure for applying sap notes to sap system? Goto Tcode SNOTE. GOTO Menu -> Download SAPNote. Give the Note No. After downloading check the status. If it shows that it can be implemented. Then Select that Note goto Menu SAPNote -> implement Note. Q. How to lock SAP Client? Is there any Tcode to lock the particular Client? Execute Transaction code SE37. Enter the Functional Module SCCR_LOCK_CLIENT. Execute this and enter the client u need to lock. Q. Change the default Support Pack Path It is because the path is defined in the parameter DIR_EPS_ROOT. Q. SAP ECC6.0 Installation Steps 1. Once the Linux OS is over u configure the network card and change the Host name . 2. Install JDK and saplocales. 3. Then add the java home in profile file. 4. Modify the parameters in sysctl.conf. 5. Before install oracle u have to change the parameters in limits.conf. (Installation guide for oracle in linux is available from oracle site) 6. Install SAP by executing sapinst. 7. In the 3rd phase it will ask u to create user for oracle (user should be ora<ianstancename>). Suppose if u r going to install oracle in middle of sapinstallation only. Rest SAP will handle own its own. Q. STAT, STAD and ST03N tcode is showing error RFC error, No performance data collected. Start SAP standard job SAP_COLLECTOR_FOR_PERFMONITOR(program RSCOLL00).

Q. What is the difference between client 000 & 001? Why we use client 000 for client copy, why dont 001? 000 client is standard client and contain client independent setting. 000 client contain simple organizational structure of test company and include all parameter for application, standard setting 001 client is copy of 000 client. It is reserve for the activity for preparing the system for production system. Q. Which are the default SAP background jobs run for Basis data? SAP_REORG_JOBS SAP_REORG_SPOOL SAP_REORG_BATCHINPUT SAP_REORG_ABAPDUMPS SAP_COLLECTOR_FOR_JOBSTATISTIC SAP_COLLECTOR_FOR_PERFMONITOR RSPO1043 Q. What are Homogenous system copy and Heterogeneous system copy and how you will do that? Homogenous- Same OS +Same DB Heterogeneous- Different OS+ Different DB or Same DB. Q. What is SAPS? The SAP Application Performance Standard (SAPS) is a hardware-independent unit that describes the performance of a system configuration in the SAP environment. Q. Which table space, gets filled frequently and we add datafile to that? PSAPBTABD/I, PSAPSTABD/I, PSCAPLUCD etc. Q. What is SAP NETWEAVER, SAP XI, SAP BIW, SAP WAS and SAP BI. What is difference between these? 1. SAPNW - Netweaver is a web based technology includes java, based on your installation choices during software installation. It includes BI/XI/EP and different level of its configuration. 2. BI: It is an OLAP (on line analytical processing), which provides a plate form to collect the data and user extract the data from BI or BW (older version) to analyze it 3. EP: Enterprise portal provides web based secure access to all the application, services and information. you can log in to EP using host name:port#/ <service name> and user name and password 4. SAP -XI: Exchange Infrastructure is used to establish a cross system connections between system by different vendors and versions 5. Web AS: Web Application Server is the platform for ABAP and J2EE stacks in Netweaver. 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/<SID>/profile 3. Cdexe for checking the kernel folder 4. find . -name filename -print for checking the file in the present directory 5. dpmon pf= <Instance profile path>, jcmon pf=<instance profile path> 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 <file> 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 Steps For SAP System Copy. 1. Take offline backup of both the server (source and target servers) 2. Verify the backup is successfully done. 3. Run the following command on source system. a. Login as adm b. svrmgrl c. connect internal d. alter database backup controlfile to trace; e. exit; f. Above command will generate a .trc file in /oracle/P01/saptrance/usertrace directory. g. Copy the text from CREATE CONTROLFILE until the (;) and paste it in to any new .sql or controlfile.sql file. h. Copy the controlfile.sql to target system.. i. Edit the file and replace the entire source SID to target SID. j.. Edit the reuse database command with the set database command 4. Copy the generated during the backup file from the source system to target system. (/oracle//sapbackup) a. Change all the source to target . b. Only dont change the backup volume name it must be target system . c. Copy the above aft file name line from the source back.log to target.log file. 5. Shutdown the target server instance. 6. From this onwards all the command on the target system only. a. Login as Orasid b. run the brtools c. select Restore/Recovery d. select Full restore and recovery e. select Select backup type f. Select the offline backup which you want to restore. g. It will take some time to restore. h. Once the database is restored login as orasid and run the i. svrmgrl j. connect internal; k. startup nomount (if the database is already mounted shutdown it using the shutdown command) l. run the following command m. @controlfile.sql (file name of the control file contains the CREATE CONTROLFILE statement) n. After the run the above command it should give the Statement Processed) o. alter database open resetlogs p. shutdown q. Start the database and SAP services using startup. 7. After this you have to reconfigure the STMS. 8. All the jobs also you have to reconfigure and reschedule. 9. Reconfigure all the printers. 10. If you want to change the Client number then use the local copy tool and remove the original client after successful import to new client. 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 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 dont 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! 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 <sid>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 <sid>adm, stop the SAP instance. Log on as ora<sid> 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/<SID>/SYS/exe/backup_run and copy all the files in /usr/sap/<SID>/SYS/exe/run to it. 5. Copy all the files unCARed in step 2 to /usr/sap/<SID>/SYS/exe/run. If prompted, overwrite all. 6. Change the owner of saposcol to root, sapdba & all br* files to ora<sid>, and all the rest to <sid>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/<SID>/SYS/exe/run to /usr/sap/<SID>/SYS/exe/bad_run and /usr/sap/<SID>/SYS/exe/backup_run to /usr/sap/<SID>/SYS/exe/run to restore your old kernel. Add an Object to a Transport To add an object to a existing unreleased transport, you must do the following: 1. Log on to the client in which the main transport was created. 2. Go to transaction se10 and pull up a list containing the main transport. 3. High-light the main transport in the list - not the subtasks contained in the list - and click Ctrl+F11. 4. Turn on the radio button Freely selected objects that appears in the popup and press Enter or click the Copy button. 5. In the Include objects in request screen, turn on the Selected Objects in the Selection by type and name section. 6. Check on the check box on the appropriate line, and enter the name of the object to be added to the transport - ZPROGRAM in our case. Click the Execute button or press F8. 7. On the Include objects in request screen, click the Include Request button or press F9. You will see a confirmation message in the status bar at the bottom of the screen. How to set-up and open a REMOTE SERVICE CONNECTION WITH SAP 1. Set-up a remote network connection to SAP. 2. Install SAP router on a Windows machine. 3. Install SAPCRYPTOLIB on the same machine. 4. Check the saprouttab file : a) you should have only one in your system and b) it should look like this: P 10.1.1.* 194.117.106.129 * P 10.1.1.* 194.117.106.130 * P 194.117.106.129 10.1.1.61 3200 5. Test you connection to SAP by DOS cd: ping sapserv1. 6. Go to http://service.sap.com/system-data. 7. Go to the Problem Solving tab. 8. Go to the Connecting to SAP tab. 9. Click on Maintain Connections 10. Click on Display all systems 11. Double click on your system ID 12. The Service Connection-System ID page opens. 13. Click on Systemdata next to Logbook 14. Under System tab, scroll down to SAP-router, and look for an edit icon to the right. Click on the edit icon, and enter the saprouters NETBIOS name, and under Service-port enter 3299. 15. Under DB server tab click on the change icon and enter the NETBIOS name of the server, along with the local IP address. Unless you have two saprouters, do not enter anything under Additional SAP-Router field.

16. Under Appl.Server tab do the same thing. If you have a system that has the db server and the application server running on it, then the IP address will be the same. 17. On a workstation (Windows XP) that has the SAP GUI, install Service Connector from SAPs site. 18. Install on the same machine LOP (Line Opener program). 19. To set-up the maximum time for SAP connection, click on Semi-Automatic Opening and enter the number of days for connecting to SAP. When you are done installing then, run first SAPServiceConnector, and the LOP.After less than a minute, you can check on the SAP website if the connection is open. SAPConnect SMTP Setup: Sending email out of SAP using SMTP 1. First, make sure your SAP Server has the SMTP service installed and that the service is active. 2. Activate the SMTP service using SICF. 3. Using the SCOT transaction, click View -> System Status. 1. Click Settings -> Default Domain. Enter your email domain WITHOUT the @ sign. For example. The domain for SAP Super Users would be sapsuperusers.com. Save the information and go back to the main SCOT page. 2. Double-click on the SMTP node under INT. Change the Mail Host and Mail Port information, and turn Node in Use on. Click the Set button beside Internet in the Support address types section. Put an * in the firstline of Address area. Confirm your way back to the main screen. 3. Back on the main SCOT screen, click View -> Jobs. Click the create button and fill in a name for the email send job then click on the green check mark. Highlight the variant you want to use I use SAP&CONNECTALL then click the Schedule button. Fill in the start date and time, and then click Schedule periodically. Fill in the correct periodic information and click Create. Your job has been added. 4. Receiving email into SAP using SMTP 1. Complete the tasks in Sending email out of SAP using SMTP. 2. Using transaction RZ10, add these parameters to your instance profile: icm/server_port_<*> = PROT=SMTP,PORT=<port> is/SMTP/virt_host_<*> = <host>:<port>,<port>,; The second parameter is only necessary if you are going to have multiple clients in the same SAP system receiving email. Here is an example of how these parameters can be configured: rdisp/start_icman = true icm/server_port_2 = PROT=SMTP,PORT=25000,TIMEOUT=180 icm/server_port_3 = PROT=SMTP,PORT=25001,TIMEOUT=180 is/SMTP/virt_host_0 = *:25000; is/SMTP/virt_host_1 = *:25001; If multiple clients in your SAP system need to receive External email, your must create a unique is/SMTP/virt_host_<*> parameter for each client. 3. Using transaction SU01, create a SAPEmail system user with the S_A.SCON profile. And make sure all the users who will be receiving email have a valid email address in their SU01 profile. 4. Using transaction SICF, each client to receive email must be assigned an SMTP server. There is one already provided as a template. If only one client will be receiving email you only need to use the template. Make these changes: a.Change the Host Data to contain the proper Profile Parameter Number. See step 2. b.Change the Logon Data to contain the information about the user created in step 3. c.Change the Handler List to SMTP_EXT_SAPCONNECT on line 1. 5. Save your changes, deactivate the SAPconnect service andthen re-activate it. Technical Table Characteristics Data class

The data class defines the physical area of the database (for ORACLE the TABLESPACE) in which your table is logically stored. If you choose a data class correctly, your table will automatically be assigned to the correct area when it is created on the database. The most important data classes are (other than the system data): APPL0 Master data APPL1 Transaction data APPL2 Organisational and customizing data Master data is data which is frequently read, but rarely updated. Transaction data is data which is frequently updated. Organizational and customizing data is data which is defined when the system is initialized and then rarely changed. There are two more data classes available, USR and USR1. These are reserved for user developments. The tables assigned to these data classes are stored in a tablespace for user developments. Note:The data class only has an effect on table storage for the database systems ORACLE and INFORMIX. Size category The size category determines the probable space requirement for a table in the database. You can select the categories 0 to 4 for your table. Each category is assigned a specific fixed storage area value in the database. When you create a table, initial space is saved for it in the database. If more space is required later as a result of data that has been entered, the storage space is increased in accordance with the category selected. Press F4 on the field Size category to see the number of data records that can be maintained for the individual categories of your table without complications ensuing. These complications could be for example a reorganization becoming necessary because the maximum space to be reserved for the table was exceeded due to the maintained size category. Buffering status The buffering status specifies whether or not a table may be buffered. This depends on how the table is used, for example on the expected volume of data in the table or on the type of access to a table. (mainly read or mainly write access to the table. In the latter case, for example, one would not select buffering). You should therefore select: - Buffering not allowed if a table may not be buffered. - Buffering allowed but not activated if buffering is principally allowed for a table, but at the moment no buffering should be active. The buffering type specified in this case is only a suggestion. - Buffering allowed if the table should be buffered. In this case a buffering type must be specified. Buffering type The buffering type defines whether and how the table should be buffered. There are the following types of buffering: single-record buffering generic area buffering full buffering In generic area buffering, a number of key fields between 1 and no. of key fields-1 must be specified. Log data changes The logging flag defines whether changes to the data records of a table should be logged. If logging is activated, every change (with UPDATE, DELETE) to an existing data record by a user or an application program is recorded in a log table in the database. Note: Activating logging slows down accesses that change the table. First of all, a record must be written in the log table for each change. Secondly, many users access this log table in parallel. This could cause lock situations even though the users are working with different application tables. Logging Dependencies Logging only takes place if parameter rec/client in the system profile is set correctly. Setting the flag on its own does not cause the table changes to be logged. The existing logs can be displayed with Transaction Table history (SCU3).

Convert to transparent table or maintain transparency This flag shows that a table should be transparent and that this attribute should be kept even after a change of release or an upgrade. Transparent Table Use You can convert pooled tables into transparent tables in a simple manner using the transparent flag. The pooled table must have active status. Activate the technical settings after setting the flag. You can now decide whether the table should be converted to a transparent table in the background or interactively for a pooled table. If you want to change the type of a table whose transparent flag has been set, you must first reset the flag and activate the technical settings. The table type must then be changed explicitly and the table must be converted using the database utility. Note: Only use the transparent flag if the table type is to change from pooled to transparent. You should never use the flag for other table conversions. Resolve problems with SAPGUI history SAPGUI has a handy feature that remembers fields contents, This is pretty useful especially when loging into SAP. I simply type the first letter of my UserID, press the Arrow-Down key and finally press ENTER. There ya go, my whole userID is typed for me. Unfortunately, sometimes SAP stops showing old entries. Heres how to troubleshoot this: Basic steps: - Press ALT-F12 (or click the color-monitor icon) - Choose OPTIONS - Click on the LOCAL DATA tab. - Make sure that History is set to ON - Make sure that Directory for Local Data really exists. if unsure, change that to C:\ - If anything was changed, click on OK, stop your all SAPGUI sessions and do not forget to shutdown SAPLOGON (or SAPLOGON PAD) - restart SAPGUI/SAPLOGON and check if all works Low-Speed - in SAPLOGON, click once on the entry you wish to connect - Click on CHANGE ITEM - Click on ADVANCED - Make sure that LOW-SPEED CONNECTION is not checked. Corrupted MDB - in the directory Directory for Local data found in Alt-F12, You should find a SAPhistory*.MDB and SAPhistory*.LDB files, these may be corrupted. Close down SAPGUI and SAPLOGON - Delete all these files - Note that all history will be lost but it may re-enable the functionnality Corrupted DAO files - SAPGUI uses the MsJet Access database engine to store history. These files may get ruined by another application. - possible solution is to re-install SAPGUI from scratch - other possibility is to re-install DAO. These files are available in the DAO35 or DAO36 folder of the SAPGUI installation CD. You can also get it Here Additional steps - Make sure that SAPGUI is fully patched - read OSS Note 199527. - try rebooting your PC! Troubleshooting SAP Startup Problems in Windows Theres probably nothing worse than not being able to start your SAP system Especially the production system! Aside from the operating system and the database server you must pay close attention to certain places in SAP to find out what caused the problem and how to solve it. Here are

the two places you will definitely need to check: EventViewer (Application and System logs) and the SAP Management Console (MMC). EventViewer can provide useful information and it may help you pinpoint where the problem resides. The SAP MMC gives you the ability to visually see the system status (green, yellow or red lights), view the work processes status and view the developer traces, which are stored in the work directory. Example: \usr\sap\TST\DVEBMGS00\work. For a central SAP instance to start successfully, both the message server and the dispatcher need to start. If one of them or both fail to start, users cannot log in to the system. The following scenarios will illustrate possible causes of why an SAP instance might not start and the reason of the message: *** DISPATCHER EMERGENCY SHUTDOWN ***. Things you need to get familiar with: Developer Traces: dev_disp Dispatcher developer trace dev_ms Message Server developer trace dev_wp0 Work process 0 developer trace The services file, which contains TCP and UDP services and their respective port numbers. This plain-text configuration file is located under %winnt%/system32/drivers/etc. Windows Task Manager (TASKMGR.exe). Dispatcher Monitor (DPMON.exe), which is located under \usr\sap\<SID>\sys\exe\run. Database logs. EventViewer (EVENTVWR.exe). TROUBLESHOOTING SAP STARTUP PROBLEMS Scenario 1: Dispatcher does not start due to a port conflict Symptoms No work processes (disp+work.exe) exist in Task Manager. Dispatcher shows status stopped in the SAP MMC. Errors found in dev_disp: ***LOG Q0I=> NiPBind: bind (10048: WSAEADDRINUSE: Address already in use) [ninti.c 1488] *** ERROR => NiIBind: service sapdp00 in use [nixxi.c 3936] *** ERROR => NiIDgBind: NiBind (rc=-4) [nixxi.c 3505] *** ERROR => DpCommInit: NiDgBind [dpxxdisp.c 7326] *** DP_FATAL_ERROR => DpSapEnvInit: DpCommInit *** DISPATCHER EMERGENCY SHUTDOWN *** Problem Analysis Possible causes for error messages above: Address already in use Service sapdp00 in use The TCP port number assigned in the services file is being occupied by another application. Due to the conflict, the dispatcher shuts down. Solution If your server has a firewall client, disable it and attempt to start the SAP instance again. If the instance starts successfully you can enable the client firewall back again. If there is no firewall client at all, or if disabling it did not resolve the problem, edit the services file and check what port the appropriate sapdp is using. If the instance number is 00, look for sapdp00. If the instance number is 01 look for sapdp01 and so on. You can use the following OS command to help you resolve port conflicts: netstat -p TCP There are also utilities on the Internet that can help you list all the TCP and UDP ports a system is using. Scenario 2: Dispatcher dies due to a database connection problem Symptoms No database connections. No work processes.

SAP MMC -> WP Table shows all processes as ended. Errors found in dev_disp: C setuser tst failed connect terminated C failed to establish conn. 0 M ***LOG R19=> tskh_init, db_connect (DB-Connect 000256) [thxxhead.c 1102] M in_ThErrHandle: 1 M *** ERROR => tskh_init: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c 8437] *** ERROR => W0 (pid 2460) died [dpxxdisp.c 11651] *** ERROR => W1 (pid 2468) died [dpxxdisp.c 11651] *** ERROR => W2 (pid 2476) died [dpxxdisp.c 11651] *** ERROR => W11 (pid 2552) died [dpxxdisp.c 11651] *** ERROR => W12 (pid 2592) died [dpxxdisp.c 11651] my types changed after wp death/restart 0xbf > 080 *** DP_FATAL_ERROR => DpEnvCheck: no more work processes *** DISPATCHER EMERGENCY SHUTDOWN *** DpModState: change server state from STARTING to SHUTDOWN Problem Analysis A connection to the database could not be established because either the SQL login specified in parameter dbs/mss/schema is set incorrectly or the SQL login was deleted from the database server. This parameter needs to be set in the DEFAULT.pfl system profile (under \usr\sap\<SID>\sys\profile). In the messages above, we see that the SQL login tst is expected but it does not exist at the database level. Solution Set the entry to the appropriate database owner. If the system is based on Basis <= 4.6 or if the system was upgraded from 4.x to 4.7 the database owner should be dbo. But, if the system was installed from scratch and its based on the Web AS 6.x the database owner should match the SID name in lower case. Example: if the SID is TST then the database owner should be tst. If the parameter is set correctly in the DEFAULT.pfl profile check at the database level if the SQL login exists. If it doesnt, create it and give it database ownership to the <SID>. Scenario 3: SAP does not start at all: no message server and no dispatcher Symptoms The message server and the dispatcher do not start at all in the SAP MMC. The following error when trying to view the developer traces within the SAP MMC: The network path was not found. No new developer traces written to disk (under the work directory.) Problem Analysis The network shares saploc and sapmnt do not exist. That explains the network path not found message when attempting to view the developer traces within the SAP MMC. Solution Re-create the saploc and sapmnt network shares. Both need to be created on the \usr\sap directory. Scenario 4: Users get No logon possible messages when they attempt to log in Symptoms Work processes start but no logins are possible. Users get the login screen but the system does not log them in. Instead, they get this error: No logon possible (no hw ID received by mssg server). In the SAP MMC, the message server (msg_server.exe) shows status stopped. The dev_ms file reports these errors: [Thr 2548] *** ERROR => MsCommInit: NiBufListen(sapmsTST) (rc=NIESERV_UNKNOWN) [msxxserv.c 8163] [Thr 2548] *** ERROR => MsSInit: MsSCommInit [msxxserv.c 1561] [Thr 2548] *** ERROR => main: MsSInit [msxxserv.c 5023] [Thr 2548] ***LOG Q02=> MsSHalt, MSStop (Msg Server 2900) [msxxserv.c 5078] Problem Analysis

Work processes were able to start but the message server was not. The reason is because the services file is missing the SAP System Message Port entry. Example: SAPmsTST 3600/tcp Solution Edit the services file and add the entry. Then, re-start the instance. Make sure you specify the appropriate TCP port (e.g. 3600) for the message server. Scenario 5: The message server starts but the dispatcher doesnt Symptoms The dispatcher shows status stopped in the SAP MMC. The dev_disp file shows these errors: ***LOG Q0A=> NiIServToNo, service_unknown (sapdp00) [nixxi.c 2580] *** ERROR => DpCommInit: NiDgBind [dpxxdisp.c 7326] *** DP_FATAL_ERROR => DpSapEnvInit: DpCommInit *** DISPATCHER EMERGENCY SHUTDOWN *** Problem Analysis The keyword in the messages above is service unknown followed by the entry name sapdp00. The dispatcher entry sapdp00 is missing in the services file. Example: sapdp00 3200/tcp Solution Add the necessary entry in the services file. Example: sapdp00 3200/tcp Then, re-start the instance. Scenario 6: Work processes die soon after they start Symptoms All work processes die right after the instance is started. The SAP MMC shows work processes with status ended. Only one work process shows status wait. An ABAP dump saying PXA_NO_SHARED_MEMORY is generated as soon as a user logs in. The SAP MMC Syslog shows the following error multiple times: SAP-Basis System: Shared Memory for PXA buffer not available. Problem Analysis The instance profile contains misconfigured memory-related parameters. Most likely the abap/buffersize instance profile parameter is set to high. Solution Edit the instance system profile at the OS level under \usr\sap\<SID>\sys\profile and lower the value assigned to abap/buffersize. Then, restart the instance. Also, its important to find out if any other memory parameter were changed. If not, the system should start once the adequate memory allocation has been set to the the abap/buffersize parameter. Understanding the Two Internet OSS Links Explain the two most common OSS link options offered by SAP. I believe that the frame relay is still offered but it is way expensive so we are going to concentrate on the two internet options: VPN and SNC. If VPN is your choice for connection to SAP, you will need the help of your IT staff to make the adjustments to the companys current VPN mapping. You provide an IP address for your VPN and your saprouter server IP address to SAP, and they FAX you back an information sheet with data similiar to this: Once the proper configuration of the VPN has been done, you just install the saprouter software - I usually install it on the DEV server - test it out, and you are done. The second alternative is SNC over the internet. In this case, you need a server with a public IP address placed in your DMZ - a real DMZ which means that the server is not behind a firewall. SAP will be looking for a connection from the public IP address and no other IP address in your network. Once the server is in the DMZ and ready to go, you send your information to SAP - the server public IP address and the server name - and SAP will send you information regarding how to install and configure the saprouter software, SAP cryptograhic software, and SNC. The instructions are pretty easy to follow so you should be ready to test before you know it. I generally use a very open saprouttab for testing, and tighten it later. So you can test with: PHP Code:

P * * * KT p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE 194.39.131.34 * This saprouttab opens permission for all servers to go out to sapserv2. So, that is really all there is to it. Hopefully, you can explain this procedure with better understanding to your current and future employers/clients. Send an Instant Message in R/3 Ever wanted to send a message to a single logged on user but dont know their email address or phone number? Run function TH_POPUP from SE37 and enter the client, message (128 chars max) and username. The message immediately appears on that users screen. Change Data In Table Without Authorization Using Transaction SE16 There is a way to change entries of a table with SE16 even if you dont 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 dont forget to save! Trace a Users Activity 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 users 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 What Needs to Be Backed Up? The PRD Instance Daily backup should be made for these SAP specific directories: /usr/sap/<SID> /sapmnt/<SID> /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/<SID> 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/<SID> /sapmnt/<SID> 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/<SID> 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 Working with saprouter Starting saprouter (OSS Link)

1. Log on to the appropriate server as <sid>adm. 2. Click Start Administrative Tools Services to open a Services window. 3. Right-click on the SAPROUTER service and click Start. 4. You may now log off the server. Verifying the Status of saprouter If you have previously successfully established SAPNet (OSS) communications with SAP via saprouter in the past, there can only be three reasons for a broken SAPNet connection to SAP: the SAP VPN is down (which rarely happens); your saprouter configuration has been incorrectly changed (also very rare); or your saprouter is not running (happens all the time). 1. Log on to the appropriate server as <sid>adm. 2. Click Start Administrative Tools Services to open a Services window. 3. Look at the SAPROUTER service. If is not started, right-click to start the service. If it is started, right-click & Stop the service and then right-click & Start the service. This should bounce your saprouter instance. 4. You may now log off the server. 1. Log on to the appropriate server as <sid>adm. 2. Click Start Administrative Tools Services to open a Services window. 3. Right-click on the SAPROUTER service and click Stop. 4. You may now log off the server. What is SAP Client? A client is organizational and legal entity in the SAP system. All the business management data is protected here because other clients can not access them. The main objective of the client is to keep the data isolated. The data in a client can be only visible within that client; it can not be displayed or changed from another client. In a physical SAP system there can be multiple clients. Each of these clients can have different objective or each client represents a unique work environment. In a development environment one client can be used as sandbox client (developers learn how to configuration using SAP environment), one can be used as prototype client (users do the customizing according to the companys requirements and testing) and another one can be used as the master development and configuration client (where the final configuration is done). A client has its own set of tables and user data. To know whether a table is client dependant or independent you can search for a field MANDT. The client dependant tables always include the client field MANDT as a part of the primary key. There can be multiple clients in each of the system of SAP system landscape as we have already seen in chapter 5. It is better to understand the customizing process in the CTS pipeline before designing a good client strategy for the SAP systems. Customizing is a method in the SAP R/3 system that helps the user to configure the functionality from SAP, according to the customer requirements. When the SAP objects are just used by only one client, we define them as client dependant data. There are some objects as ABAP/4 programs, which are used by all the clients in a SAP system. Those objects are called client independent data. The functional changes resulting from customizing can be client specific (client dependant) or general (client independent). You must know the fact that client independent customizing can create problems if the authorizations and the client strategy are not defined properly. For example if you have three clients in a development environment then the role of each client should be defined properly. One of these three clients should be used for client independent customizing and in other clients, users will not have the authority to do any client independent configuration. About SAP Clients With a standard installation, SAP delivers 000, 001 and 066 clients. Client 000 is considered to be a SAP reference client and it should not be changed or deleted at anytime from the system. After a SAP system is installed, you can create other clients from 000 by using the client copy procedure. For some important configuration you have to logon to client 000. For example, if you want to configure your CTS system then this client must be used. Client 000 also plays a very important role in upgrade process. Every time you do upgrade client dependant changes will be automatically upgraded in this client and later on the changes can be copied to other clients. The customer uses client 001 as a SAP sample client. After a new installation both 000 and 001

clients are identical, but after an upgrade 000 will have additional customizing data. Lot of customer sites does not use 001 client at all. Client 066 is there for SAP Early Watch service. This client enables SAP to remotely access the customer system. SAP provides this service to the customer to improve the system performance. After Early Watch group goes through the checking methodology, a system performance summery and recommendations to improve performance report are provided to the customer. SAP recommends to go for an Early Watch session before your project goes live and another one sometime after the go live date. Client 066 should not be changed or deleted from the system. In case this client was deleted from the system, then you have to follow the instructions in OSS note 7312 to download the client data from sapserv3 and import this data to create 066 client. Creating a client and setting up the client attributes To create a client you have to maintain T000 table. From 3.0 onward, transaction SCC4can be used to maintain T000 table. Also you can chose Administration-> Client admin -> Client Maintenance from the initial screen to do the same. In client table T000, SAP system displays all the clients available, their names, currency used and when the client was changed last as shown in Figure 9.1. If the system is in display mode then you must change it to the change mode by selecting the display/change icon to create a new client. When you click display/change button, a warning is displayed as Warning: the table is client-independent. The New entries icon should be clicked to create a new client as shown in Figure 9.2. Figure 9.1 shows Client overview in SCC4 transaction In the new client creation screen to define a new client you must fill all the required entries. The client number and the name are entered first. Then in the second line the location of the SAP system is defined. Logical system is defined next. SAP uses logical system concept in ALE (Application Link Enabling), workflow and EDI areas. The logical system must be unique through out the company and any other ALE system group can not use it. You must be careful changing the logical system entry. SAP treats a logical system as a client. You can use transaction BD54 to create a logical system and then enter that entry in the logical system box while creating a client. Next entry standard currency can be defined according to the country. For example USD can be used as a standard currency for USA. To enter a category of a client you must know the objective of that client beforehand. For example if this client will be used as a customizing client then customizing entry should be used from the options. In the next category Changes and transports for client-dependent objects, there are four options. If you want to use this client as a sandbox client; and you do not want to record or create a change request every time a change happens to the client then Changes W/O automatic recording is the right option. If all the changes to the client should be recorded in a change request then Automatic recording of changes is the right option. You must choose this option for your master configuration client. If No changes allowed is chosen, then no changes will be allowed to this client. You must chose his option for clients in the production environment to protect your system. No transport option is used when you do not want any user to create a transport from this client. Figure 9.2 shows the client create screen The Client-independent object changes category determines if the client independent data maintenance is allowed in this new client. You get following four options in this category: Changes to Repository and client-ind. customizing allowed No changes to client-independent customizing objects No changes to Repository objects No changes to Repository and client-independent custom. obj. To choose the right option from Client-independent object changes category, you must know the definition of Clint independent customizing objects and repository objects. The examples of SAP repository objects are data dictionary objects, module pools and screens. Client independent objects apply to all the clients. The factory calendar is an example of client independent object of customizing. For sandbox client, where user learns how to do the customizing, you must not allow the client independent customizing. Changes to Repository and client-ind. customizing allowed: Both client independent customizing objects and SAP repository objects can be maintained. Usually this option is selected in a mastercustomizing client.

No changes to client-independent customizing objects: No change is allowed for client independent customizing objects but changes to repository objects are allowed. This option can be used for a sand box client. No changes to Repository objects: If you select this option, then no changes are allowed to the Repository objects but the client independent customizing is allowed. When you want to protect the repository objects in a client, this is the right option to use. No changes to Repository and client-independent custom. Obj: This option does not allow any changes to client independent customizing objects and repository objects. You should use this option for a consolidation and production client where the security of client independent objects and repository objects are necessary. In the restriction category of the Change View Clients: Details screen, there are four options. You are allowed to maintain only the following three options as shown in Figure 9.2: Protection against overwrite by copying: If you chose this option, a client copy can not overwrite the new client. You should chose this option for a master-customizing client or for an important client as production. Start of CATT processes allowed: This option determines whether you want to allow the CATT (Computer Aided Test Tool) process in the client or not. Computer Aided Test Tool (CATT) is tool provided by SAP to test different functionality of the SAP system. To run the CATT tool you can execute transaction SCAT. CATT process changes the database extensively and requires lot of system resources. So we recommend not to chose this option if you are in the production environment. Protection against SAP upgrade: If you chose this option, then this client will be not updated in time of upgrade. You should use this option for a client that is used for backup purposes or client 066 (Early Watch client) that is used by SAP for customers SAP system performance. If you chose this option for any client, the upgrade will not provide any data to this client and it can not be used as a regular customizing client. You need S_CTS_ALL authorization to maintain this option. System-level control in transaction SE06 You can use the system change option to control the system level access to different types of users in a SAP project. To use system change option screen you can chose SE06 and then system change option or use SE03 and then go to for setting the system category and chose set system change options. The option you chose here directly affects ABAP/4 workbench, Workbench Organizer and the transport system. You need all access to Workbench Organizer to change the system change options as shown in Figure 9.3. There are some TP commands that can be used to control the system level access. System change option in se06 figure9.3 The following are the four system change options: Objects cannot be changed: If you select this option then no changes of any kind are allowed for any objects in the SAP system. The SAP customers use this option in the consolidation and production environment. Using this option you can control the developers and the customizing people directly changing any development objects and customizing objects in the consolidation and production environment. So the users use the transport method to move the objects from development system to other systems instead of directly creating or maintaining them in the target systems. The tp command tp lock_eu <sapsid> can be used in the operating system level to set the system to cannot be changed and the command tp unlock_eu<sapsid> puts the system back to where it was when the lock command was executed. Only original objects (w. Workbench Organizer): If you go for this option then only original objects those are created in this system can be changed. If the original object exists in some other system and you have a copy of that object in this system then you can not change that object. In special cases you can use this option for the QA or test system. All the changes are recorded in Workbench Organizer. All customer objects (w. Workbench Organizer): This option allows you to edit or repair an object though it is not the original object of the current system. Any changes to customer

objects are allowed. The changes are controlled and recorded by the Workbench Organizer. This option does not allow changing the objects came from SAP originally. You can use this option in a training system. All objects (w. Workbench Organizer): With this option you can change or repair any objects in the system. Now the system is totally open for any changes to all the objects. With this option also every change is recorded and controlled by the Workbench Organizer. This option is generally selected in a development or sandbox environment. From 4.0 version the se06 change option looks as following: Pre-Configured Client from SAP The pre-configured client from SAP has pre-configured customizing objects for a simple organizational structure. The pre-configured settings of the client help a customer to configure a system quickly. SAP recommends the customers to install the pre-configured client in their system if they want to go for a rapid implementation using ASAP (Accelerated SAP) methodology. In the ASAP chapter we are going to give you an extensive definition about this methodology. Now instead of starting from client 001 copy, you can start from a pre-configured client that will provide more configured features. SAP provides the transports and help documentation to create a pre-configured client. The preconfigured client for FI/CO, SD, AM, MM, HR and PP modules is already available from SAP. According to SAP, customers that have used the pre-configured client saved 4 to 6 weeks of project implementation time. The way pre-configured client is designed; some of the small companies can run the pre-configured client for production after the out of the box installation. Following procedure is used to create a pre-configured client: A client is created in T000 table Copying client 000 to the new client Copying the data files and cofiles from SAP to your system Adding those change requests to the buffer and then importing them to the target client We recommend to check your number ranges after the import Creating a user and assigning SAP_ALL and SAP_NEW profiles Run the SCAT transaction for CATT tool to test the pre-configured client. This tool is a great tool for those users, who want to learn about SAP functionality and, what a pre-configured client can do for them? The pre-configured client comes with non-matric units of mass, area, length and volume and a sample factory calendar is pre-configured with the ten US government holidays. Client COPY Procedures After the SAP system is installed, the client copy is a common thing to do for creating new clients. A client copy can be done from one system to another or within one system. A client copy can affect the database and current users in the system; so you need to be aware of the following important information before scheduling a client copy. For the stability of the system, always schedule the client copy in the nighttime when the users are not working in the system. To avoid data inconsistency you should not keep on working in the source or target clients when the client copy is going on. For the best performance, always schedule the client copy in the background. Try to examine the maximum online runtime parameter max_wp_run_time in the instance profile. You might need to increase this for a large table copy. You should have proper authorizations to run the client copy. As a basis system administrator you should have SAP_ALL profile to complete a client copy successfully. If you do not want a generic id to run the client copy; we recommend using SAP*. The internal user SAP* has all the authorizations needed by the client copy. Always check the database resources before executing a client copy. You can do that by running a test run client copy. The test run will provide all the information about the necessary database table spaces that you need in the target client. The main memory plays a significant role in the client copy. Make sure that you have enough memory to finish the client copy without any problem. When you are planning the hardware

requirement for the SAP installation, it is always better to install memory recommended by SAP. Version 3.X and 4.X require more memory for memory management and client copy. When you trying to copy a large productive client, it better to copy the cluster tables first. You should look for all the OSS notes that apply to the client copy in a particular version of SAP. For example according to OSS note number 34547, SAP_USR client copy parameter that suppose to copy only user data in the background also copies customizing data in the background for release 3.0B. If the client copy is locked by another client copy run, then check the log before deleting the lock entry in SM12 to remove the lock. In 2.2 release of SAP R3trans is used for client copy, client export and client import. You should not do the same in 3.0 or 4.0 release of SAP. You can use R3trans to remove a client in 3.0 and 4.0 also and we will see the procedure in the deleting a client part of this chapter. R3trans can be used also for some other important jobs as described in chapter 10. It is very important to know that the number ranges have to be reset in the target client if you are just copying the customizing data. Though the client copy utility has been improved a lot still we get problems with number ranges. We recommend checking the OSS notes about number ranges before dealing with them. When you perform a client copy, it is very important to know the three levels of data in SAP system and how they affect the client copy. The client dependent application data is created from the master and transaction data of the system during the application system operation. The client dependant customizing data is created during the development process of a SAP project and this data depend upon the client dependent application data. The client independent customizing data applies to the entire client. The client copy procedure copies the client dependent application data and client dependent customizing data unless you specify to copy the client independent customizing. To maintain the consistency you should follow some SAP rules. When you are copying the customizing data, you should copy the application data (master and transaction data). If you just want to copy the customizing data then remember that all the application tables are reset in the process and this reset process can guarantee the consistency of the client Creating custom PROFILES to copy Clients Client copy profiles are used to copy specific data from one client to another. SAP provides some custom profiles to perform a client copy. The following are the example of profiles provided by SAP. SAP_ALL: All data of a client SAP_APPL: Customizing, master and transaction data SAP_CUST: Customizing data SAP_UAPP: Customizing, master&transact.data, user masters SAP_UCUS: Customizing data, user masters SAP_USR: Authorizations and user masters The objective of above client copy profiles is defined clearly. What profile you are going to use; depends on what you want to copy from one client to another. For example you want to copy the entire data of a client then you want to choose SAP_ALL as your copy profile. you can select a profile name from the profile input field possible entries and then chose Profile -> Display profile from the menu. You can create a custom profile according to your requirement. To create a custom profile you need to chose the path Profile-> Create profile from client copy or client export screen. Profile: Here you define the profile name. The name should be according to the SAP standard; so it should start with either Z or Y. Last changed by and last changed on: These fields show the information about the person who last changed the profile and the time it was changed. In the data selection category we have the following three selections: User masters: If you chose this option then the user master records will be copied from the source client to the target client. Customizing data: If you want to copy all customizing data then chose this option. Appl. Data. Initialization. Cust. Data: This option copies master, transaction and customizing data from the source client to the target client. Important tips: It is very important for you to understand the data selection procedure before the client copy. In SAP environment it is not possible to copy selected parts of the application and

customizing alone. If you want to copy application data, we recommend doing it in batch input. With batch input consistency is ensured. In the copy mode category the following options are displayed: Initialize Recreate: This option is grayed out and already selected. This option allows the system to delete all the tables (not selected in the client copy process) in the target client and initialize them. You can use the path Extras -> No initialization to have an option for not choosing this option. We recommend not doing that; it might create instability in the target client. Copy variants: If you want to include variants in the client copy then chose this option. In transport between 2 systems category there is one option: Client Independent data: If you chose this option then the client independent data will be copied from one client to another. We recommend executing the client copy remote compare program RSCLICMP, before choosing this option to do a client copy. This program provides all the information regarding the differences between the source and target systems client independent tables. The other options are: Default source client: You define the default source client for the client copy in the profile. You can change the client after choosing this profile before starting the client copy. Default source client user master record: You can enter the client number from where the user master records will be copied to the target client. You can also change this like default source client. Comment: You should provide a meaningful description for the profile here. Client COPY within a system SCC0 or RSCLICOP (SCCL as of 3.1 release) In 3.0 SAP uses RSCLICOP program in transaction SCC0 to copy the customizing environment from one client to another. This will copy clientdependent tables, match codes, number ranges and resolve the logical dependencies between tables and programs. RSCLIC01 or RSCLIC02 were used to copy clients in 2.0 release. These programs use to create command files and the basis administrator was running R3trans utility to transport the data files. Those programs are not supported in 3.0 anymore. For the mass data transfer and large number of table copy, we recommend you to run the RSCLICOP program in the background. Tips: Trace information about each client copy run is stored in table CCCFLOW. Use program RSCCPROT to display information about the client copy. You can run RDDANATB program in the background to get the information about the size of all the tables in all the clients. If you start the RSCLICOP in restart mode then try to check the checkentries in table CCCFLOW. The copy procedure using SCCL If you are planning to copy the source client to a new client then you must create a new client in SCC4 or table T000 before starting the client copy. Logon to the target client and chose transaction SCCL or use the path Tools ->Administration>Choose Administration ->Client admin->Client copy ->Local copy and you will see a initial client copy screen as shown in Figure 9.6. The current client is your target client so it is already selected for you in the first line. In the second line select the appropriate profile you want to use for the client copy. You choose the source client in the third line. In fourth line you can define the client from which you want to copy the user master records. The Source Client User Master does not have to be same as source client. Then if you want to run the local client copy to get the information about the storage requirements or a complete table statistics then select the test run flag. We recommend you to run the client copy using the test run mode first. In test run phase, database updates are not performed. You should schedule the client copy in the background after all the parameters are selected as shown in figure Figure 9.6. You can run a client copy online if you are just copying the user master records; because when you copy only user master records very limited data is copied form a client and it does not take that long to copy those data. Figure 9.6 local copy transaction sccl If the client copy fails for some reason then you can restart the client copy in the restart mode after the fixing the problems. In this case the client copy will start exactly from the same point where it

failed. A pre-analysis phase requires sometime determining the restart point. SAP recommends to set the restart flag in the Execute in background screen when you plan to copy a large client. Tips: We recommend to reset the buffers by entering /SYNC in the OK code on all the application servers after executing the RSCLACOP or SCC0 for the client copy. RSCLICOP compares the contents of each table in the source client with that in the target client. Client COPY from one system to another Client copy from one system to another: SCC1, SCC2, SCC7, SCC8, RSCLIEXP, RSCLIIMP The client export/import and remote client copy procedures are commonly used to copy a client from one system to another. The client can be exported from the system using transaction SCC8 and then importing the client using SCC7 or using the transaction SCC2 for both export and import process, the second procedure is to do a remote client copy from one system to another. If you are copying a production size client we recommend performing the client copy using the first procedure. The following are the steps in the whole procedure: First the data from the client in the source system is exported from the database to a transport file on hard disk. Before you transport a client from the source client database, you need to know exactly what you want to transport and you use SAP delivered profiles accordingly. Then the SAP delivered TP command is used for the import to the target system client database. The post processing procedure is run in the target client to successfully complete the client import. You have to be very careful when copying the client independent data, because client-dependent customizing objects are dependent on entries in client-independent tables. SAP recommends that you should not copy the client independent tables if they are not yet modified in the target system. If the customizing is being done in a system regularly then you have to be very careful taking the client independent customizing to that system; otherwise you might overwrite the whole client independent customizing settings and the system will become inconsistent. We recommend to consult the customizing team of a project before copying the client independent customizing tables. Transporting 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 as shown in figure 9.7. 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. Figure 9.7 showing transaction SCC8 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: <sid>KO<no> 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. <sid>KT<no> for the client-specific data. For example DEVKT0001 <sid>KX<no> 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 /usr/sap/trans/data/DX00001.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 <cofile name> <target sid name> 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 <sid>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/data/<data file for the SAPscript objects> /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 postprocessing 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. <sid>KO<no>: For the client-independent data (if the copy profile selected includes client independent data: <sid>KR<no>: For the client-specific data. <sid>KX<no>: 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 <sid>adm cd /usr/sap/trans/bin - Change to the transport directory tp addtobuffer <command file-name> <target-sys-id> - 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 <target-sys-id> client<target-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.

Remote CLIENT Copy SCC9 transaction Overview of a remote client copy: Remote client copy is done using the RFC connection between two systems. You might get errors if you do not have all the proper authorization you need including user administration authorization. Tips: A remote copy requires as much memory as needed by the largest table in the system. Upto 4.0, remote copy can not handle large volume of data. Remote client copy reads the entire table from the source system and then copies that to the target system using RFC connection. For big tables as BSEG, it takes more time then the RFC wait time; so it might not copy the big table at all. For the same RFC wait time constraint, large quantity of texts can not be copied and remote client copy might terminate without any error. You are not going to see this problem in 4.0 release, because the tables are copied in blocks by RFC. You should check the memory parameters for memory and MAX_wprun_time for run time before starting the remote client copy. Try to add the big tables to the exception list by executing RSCCEXPT report. In 4.0 an inconsistency check is performed automatically during the remote client copy; if any inconsistency is there then the system returns an error. We recommend avoiding big client copies using remote client copy procedure until release 4.0. In the beginning of a development project upto 3.1I release you can use remote client copy for the smaller clients; when the client gets real big it is better to run client export/ import procedure instead. Remote client copy procedure: Before you perform a client copy, the RFC destination for the source system needs to be defined using transaction SM59. In transaction SM59 screen chose R/3 connections under RFC destinations. Now you click on the create button to create a RFC connection as shown in Figure 9.9. Figure 9.9 picture of creating a RFC destination After the RFC connection for the source system is created, you are ready to perform a remote client copy. You can chose SCC9 or the menu path Tools ->Administration->Client admin->Client copy ->Remote copy. First line shows the target client, which is the current client as shown in Figure 9.10. Now you select a copy profile according your requirements. We have already seen how to create a profile and what is their objective. In the fourth line enter the source client (from where you are copying). If click the enter button the fifth line Source Client User Master will be filled with the same number as source client. You can change it if you want to. Enter the source system name or RFC destination name that you created in SM59. You can execute the remote client copy in the test mode by selecting the test run flag. After you are done with all the selection you can click on the Execute in backgrd. button to start the remote client copy procedure as a background job. Figure 9.10 to show the remote client copy screen Deleting a CLIENT You need to perform two steps to delete a client. First you need to delete the complete client from database and then delete it from client maintenance table T000. To delete a client from a SAP system: First log on to the client to be deleted with the proper authorization to delete a client. Then choose path Tools ->Administration->Client admin->Special functions->Delete client or transaction SCC5 and you are going to see a delete client screen as shown in figure 9.11. In this screen you are going to find two entries; test run and also delete from T000. If you want to run a client delete process to find out information about all the tables that will be deleted then test run is the right option to use. If you do not want to copy another client to this client and get rid of this client forever then delete from T000 is the right option to use. You can delete the client in SCC5 by executing it online or in the background. You can choose either one of these options and in the verification popup screen you can check all the parameters for client deletion. After the client deletion process starts you can use SCC3 log entries to check the client deletion process. Figure 9.11 to show the client delete screen of SCC5 In all the SAP releases so far you can use R3trans to delete a client. We have seen significant timesaving in this way of deleting a client. If you use the R3trans command in the operating system

level to delete a client then the first step is to create the command file in /usr/sap/trans/bin (it does not have to be /use/sap/trans/bin as long as you provide the right path in the OS level) with the following contents: Clientremove Client = 100 Select * For the above example the command file name = del100 and the client we want to delete = 100 are used Then in /usr/sap/trans/bin directory run the following command to delete the client: R3trans w <log file for the deletion> -u 1 <path name and the command file> For our example here you run: R3trans -w del100.log u 1 del100 You can VI to the del100.log to anytime to the progress in the deletion process. Tips: For the database performance, we recommend to do database reorganization after you delete a production size client from the system. To check the contents of the log: Choose Tools ->Administration ->Choose Administration ->Client admin->Copy logs then Select a client by double clicking on it and select a copy process by double-clicking on it. The transaction for the log selection is SCC3 transaction. You also can run the program RSCCPROT to get the same result. You can select one of the client copy entry from Client copy log analysis second screen, following three buttons are provided as shown in figure 9.13. Log Monitor Refresh System log Resource Analysis Figure 9.13 for the client copy log screen If you select a Log button from the Client copy log analysis third screen, then not only you get the general information about the client copy but also the following information for each of the table copied in the process. Table name Delivery class Development class Number of entries in the source client Number of inserts necessary in the current client Number of updates Number of deletes Additional space required by the copied table in bytes The following is an example of what you will see in a log display screen. Table Dev.cl Class nbr-all -ins -upd -del bytes sec ANKA ANKP ANKT ANKV T009Y T082A T082H AA AA AA AA AA AA AA C C C C C C C 35 0 43 0 2 16 27 0 0 0 0 0 0 0 35 0 43 0 2 16 27 COPY COPY COPY COPY COPY COPY COPY 13 0 8 0 0 0 1 1 0 1 0 0 0 0

The above example shows the class C. The class represents the delivery class. Through the delivery class you can know the kind of data the table has or what environment the table belongs to. For example, all the tables shown in the above display belongs to the customizing environment or

they have customizing data. The following are the examples of the delivery classes and their definitions. Delivery Class Description A Application table includes the master and transaction data C Customizing table L Table for storing temporary data G Customizing table. It is protected against SAP Update E Control table S System table. They are only maintained by SAP W System table. Contents transportable via separate TR objects The table information, all the additional storage required in Kbytes, the run time for the client copy and the end of processing time are also shown as following example in the client copy log analysis. Selected tables: 5,672 Copied tables: 5,671 Tables deleted: 0 Storage required (Kbytes): 260,444 Program ran successfully Runtime (seconds): 10,123 End of processing: 13:37:24 You can click on the Monitor button and watch the progress of the client copy real time. The Refresh button always refreshes the screen to show you the up to date information. The System log button takes you to the system log screen to show you all the system messages. The next button Resource analysis is a very important utility to show you all the data base resources you need to run the client copy in the table space level. In the resource analysis utility you can get realistic picture of deletes and inserts calculation for the database. Memory requirements can also be found out by this utility. Tips: You should always check SM21 (the system log) for all the client copy problems. Ten 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.

Simple method for copying VARIANTS The VARI, VARID and VARIT tables contain all the variants in the SAP system. Those variants can be copied in the client copy time using an appropriate client copy profile. If you just want to copy the variants then R3trans can be used to copy those very quickly. To copy the variants from one client to another in a system using R3trans, follow the following procedure: First create a control file with the following contains: clientcopy source client = <source client number> target client = < target client number> select * from VARI select * from VARIT select * from VARID The second step is to logon as <sid>adm and use the controls file with R3trans as shown in the client export and import section of this chapter. This procedure will copy all the variants from the source client to the target client as defined in the control file. To copy all the variants between clients between two different systems: First create a control file for R3trans with the following contents to create a data file: export client = <source client> file = <the path for the data file and the file name> select * from VARI select * from VARIT select * from VARID The second step is to logon as <sid>adm in the source system and use R3trans as shown before to execute the control file. The process will create a data file as defined in the control file. The third step is to define a import control file for R3trans with the following contents: Import client = <target client> file = <the path for the data file and the file name> After the control file is created, logon as <sid>admin the target system and execute R3trans command with the control file to import all the variants to the target system. Important client management tips We recommend deleting the large cluster tables first from a client using R3trans client remove command before going for the deletion of entire client. To increase the client copy performance it is also better to copy the cluster tables first using the R3trans command. Then use the RSCCEXPT report to exclude all the cluster tables before doing the client copy. To get a list of cluster tables use transaction SE85, then chose other objects -> select pooled/cluster tables. The following control files are for both the above examples: To copy the cluster tables: clientcopy source client = xxx target client = YYY select * from BSEG select * from .. To delete the cluster table before deleting the whole client: client remove client = XXX select * from BSEG (XXX and YYY represent the client numbers) Refer to chapter 10 to understand how to execute a R3trans command.

In each database, the rollback segments needs to be extended so that the largest table in the system can be copied without any problem. In release it only applies to client transports or copies and deleting the tables. In release 4.0 it only applies to transports. SAP does not support a non-numeric client. If you get a message The client copy is locked by another run and you want to kill the current process to start a new client copy then call transaction SM12 and check the entry RSCLICOP and then delete it. Make sure to check if any clientcopy job is running in the background before deleting the lock. If a job is still running, you should wait till it finishes because you can not start another client copy run. After the client export is done, the command file might not be created for the SAPscript objects in /usr/sap/trans/cofiles directory, you only find the data file in /usr/sap/trans/data directory. Sometimes the SAPscript objects can be locked properly and the transport request does not get released. To release the SAPscript change request, logon to the source client and execute SE01. Then enter the transport number and try to release it from there. If there is a lock problem then solve it and then release the request. Transporting from 4.0 to 3.0: You have to be very careful while doing the transport of a logical database in 4.0. In release 4.0 the buffer of the logical database is changed. Always run RSLDB400 after the import of a logical database. Before transporting the repository objects from release 4.0 to 3.1 you need to know that the names of the repository objects in release 4.0 are extended. Always check the current version of R3trans; you might need for your system to transport objects from 4.0 to 3.1 releases. If your system has SAP release other than 3.1I; you can not transport SAPscript objects from 4.0 to 3.0. The internal buffer is also changed in release 4.0, so GUI screens can not be transported from 4.0 to 3.0. Not all SAP Notes can be applied via the SNOTE transaction. Some are information only, providing no code corrections. Others entail corrections that can only be done manually. This latter type of SAP Note should be applied to your SAP system in conjunction with a trained ABAP programmer. Also, SAP recommends that SNOTE change requests NOT be transported into other systems. Use the SNOTE transaction in each SAP system that needs the correction, and delete the generated change requests since they should never be transported and could lock resources during application of other SAP Notes and support package application. If you do not have a working OSS connection, you can download an OSS note from the SAP Marketplace using the SAP Download Manager and use the upload feature in SNOTE to load it into the SAP instance instead. 1. Log on to client 000 in the appropriate SAP system. 2. Go to transaction SNOTE. 3. On the Note Assistant - Version XXX/XXXX: Worklist screen, on the top-most menu bar click Goto SAP Note download. 4. On the Note Assistant: Download Note popup, type the number of the SAP note in the Note number box and click the clock picture-icon. A SAP Note XXXXXX is being downloaded message will appear in the bottom status bar. If you get a communications error message, verify that saprouter is up and try again. 5. Once the SAP Note has been downloaded, it will appear on the Assistant - Version XXX/XXXX: Worklist screen under the SAP Notes New navigation tree. The SAP Note can only be applied if there is a blue box with a black arrow to the left of the note number. If there is a gray diamond instead, the downloaded note cannot be applied or is not application for this SAP system. 6. To apply the SAP Note, on the Note Assistant - Version XXX/XXXX: Worklistscreen double click on the downloaded SAP Note number. 7. On the Note Assistant Display Note XXXXXX screen, read the note text to see if there are any necessary manual tasks to be performed after the note is applied. When you are ready to apply the note, click on the clock picture-icon. 8. If there are any prerequisite SAP Notes which need to be applied to the SAP system before the downloaded SAP Note can be applied, a list will appear in a Load the following notes into your SAP system popup will appear. Click the clock picture-icon to download these prerequisite SAP Notes as

well. If any of the prerequisite SAP Notes must be applied in parallel with the original downloaded SAP Note, a list will appear in a SAP Note queue to be Imported popup. Click the clock picture-icon to apply all the listed SAP Notes. 9. Before applying any SAP Notes to your SAP system, a Confirmation: SAP Noteread popup will appear. Once you have read the information contained in this popup, click the Yes button. 10. A standard Make repairs in foreign namespaces popup will appear. Click the green to continue. 11. On the Prompt for transportable Workbench request popup, click the blank page picture-icon to create a new change request. On the Create Requestpopup, fill in the Short description and click the Save picture-icon. You will be returned to the Prompt for transportable Workbench request popup which contains the generated change request number for this system change. Click the green to continue. 12. On the Confirm changes popup, click the green to continue. 13. After the SAP Note has been applied to the SAP system, you will be returned to the Note Assistant - Version XXX/XXXX: Worklist screen. There is no completion message. Click the green and pencil picture-icon. 14. On the Set Processing Status for Note XXXXXX popup, click on the Completedline to turn on the radio button. Click the green . You can now leave the SNOTE transaction. Modified programs, functions, etc. may require recompilation. 15. If the OSS note you applied changed a ABAP program, you must go to the SE38transaction and manually recompile the program. If it changed a function, go to transaction SE37 and click the Single Test button this is enough to force the function to rebuild and you can back out of the SE37 transaction. 1. Log on to the SAP Marketplace using an OSS ID with Administration rights http://service.sap.com/message. 2. On the Create Customer Messages screen, click on the Start Message Wizardbutton. 3. On the Customer messages Create screen, click the Select a Systembutton. 4. On the System Selection popup, click on the + sign next to Show systemsto see a list of your SAP systems registered with SAP. From the expanded list of system, click on the radio button just left of the <SID> for which you are reporting the problem. Click the Choose button and you will be returned to the Customer messages Create screen. 5. On the Customer messages Create screen, click on the radio button to the left of the System type which has the problem: development system,test system, or production system. From the Release dropdown, select the appropriate SAP software release. Click the Continue hyperlink. 6. On the next Customer messages Create screen, scroll down to the bottom of the screen. If the problem involves an add-on, select the appropriateAdd-on and Add-on release from the dropdowns; if an add-on is not involved, leave these dropdowns blank. Verify that the information showing in theOper. System, Database, and Frontend dropdowns is correct. If it is not correct, selection your SAP systems information from the appropriate dropdowns. Click the Continue hyperlink. 7. On the next Customer messages Create screen, scroll down to the bottom of the screen. From the Priority dropdown, select the appropriate priority of Low, Medium, High, or Very High. From the Component dropdown, select which SAP component is having the problem. Once you select a component, a secondary Component dropdown will appear. Select a secondary component and a third component as well. Do the best you can to make all three component pieces fit your problem as closely as possible. Click the Continuehyperlink. 8. On the next Customer messages Create screen, scroll down to the bottom of the screen. Select a language from the Language dropdown, type a short but descriptive summary of your problem in the Short description box, and type a more detailed description of your problem in the Long test box. 9. If there are logs or other files which might assist SAP in resolving the issue, rename them all so that they have a suffix of .log and use the Add attachment hyperlink and the Attachments popup to attach them to the message. After attaching all the necessary files, click the Closehyperlink to return to the Customer messages Create screen.

10. When you have provided as much information as possible, click the Send to SAP hyperlink. 11. You will receive a confirmation screen with a generation problem number. Write this problem number down for later use. 12. You may now leave the Message Wizard and close the web browser window. 1. Log on to the SAP Marketplace using an OSS ID with Administration rights http://service.sap.com/sscr. 2. In the navigator tree on the right-hand side of the SSCR screen, click onRegistration. 3. On the SSCR Registration screen, click the Register developer radio button and click an Installation hyperlink. Make sure you select the correct Installation Number for the SAP flavor you need or the generated key will not work. 4. On the SSCR Register Developer screen, type in the developers SAP user ID and click the Register button. 5. A new Details section will appear. Note the generated developers key or cut-and-paste for other storage. 6. You may now close your web browser session. Opening a Service Connection for SAP Support Before opening a service connection for SAP, be sure that the SAPAG client has been added to the appropriate SAP system and Client, and that a Security Audit Trace has been activated for the SAPAG ID. Before a Service Connection to a SAP server via your saprouter can be created, the saprouter must run the LOP Line Opener Program to initiate the mode of SAP connection. Please LOPInstalltion.exe on your saprouter server before trying to add and open any Service Connections. 1. Log on to the SAP Marketplace using an OSS ID with Administration rights http://service.sap.com/serviceconnection. 2. On the Service Connections screen, click the Service Connections button. 3. On the Service Connections Overview screen, scroll down the page and find the SAP instance you want to open. Click on the red X in that instances line. 4. In the Enter Data for the systems semi-automatic opening popup, set the days, hours, and minutes you want the service connection to stay open. Click the Continue button. What is a SAP Instance? A SAP instance is all the components created by the SAPinst program who all share the same database. There are three mandatory sub-instances; the Database Instance (DB), the Central Instance (CI), and the Dialog Instance (DI) aka Application Server. This is the minimum configuration of any SAP instance. There can be multiple DIs but only one DB and only one Active CI which means that a copy of the CI can exist for High Availability but only one of the CIs can be active at any given time. You will hear about SAP being multi-tiered and that term is referancing these three layers. Sometimes you might see other SAP tiers like ITS but that really isnt a separate tier, it used to be an additional piece of software working with IIS, and now ITS is part of Basis/WAS so it is part of the CI Tier. These layers, plus other SAP written software, are also known as the SAP Business Framework. You can probably guess at what the DB contains. There are any number of tables in a SAP instance, from 21,000 to 38,000. Many have four or five character names that are usually abbreviations of things like USR for user, MANDT for client, etc. You could guess that USR is short for user. But MANDT? So, we add one more variable to the equation those four or five character names are abbreviations of German words. Needless to say, trying to look at SAP from a typical DBA prospective is almost impossible. Fortunately, SAP supplies the tools for you to manage all these tables.

The Central Instance is a lump term for all the SAP executables, the installed OS file structure, and anything that is placed on the OS to support and communicate with the SAP instance. It talks to the database, handles requests made by the application server(s), and sends back the information. Other software products often call this the middleware layer. The Dialog Instance connects the users to the CI, passes the issued requests to the CI, and sends the returned results to the users session. SAP uses a client piece called SAPGui which handles the userto-DI communication on the users workstation. These are the three main pieces of a SAP instance installation. There are other parts that can be added for various sub-access and external tasks. For a Development SAP instance or a Quality & Assurance or Test SAP instance, all three layers are normally installed on the same server. For a Production SAP instance, the DB/CI are often installed on one server and the DI on another server for load balancing purposes. It should be noted that the installation of a CI instance automatically installs a DI which can be used by everyone if needed, be used only as needed by Basis staff, or never be used. Instance can be a difficult term to understand almost every major database applies this term to the installation of the database software. So if you see reference to an Oracle instance, this means the installation of the Oracle software. An Oracle database is the creation of a new empty database within that Oracle instance. Understanding the Startup and Shutdown prodedures may help solidify this layer concept. The normal SAP instance start up consists of three parts: starting the SAP OS Collector, starting the Oracle Listener, and starting the SAP instance. The process mainly goes like this: ora<sid> logs on and starts the Oracle Listener then <sid>adm logs on and runs the startsap script. Creating a Local Frontend Printer or Desktop Printer Local or frontend printing is sometimes confusing in concept but actually very easy to understand. As a rule, local printer is simply another way of saying that the user is going to print to the default printer designated on his/her workstation. You probably do this all the time with Windows to printerspreadsheets, Word documents, etc without thinking about it. You can do the same thing using SAP. 1. Log on to any client in the appropriate SAP system. 2. Go to transaction SPAD. 3. On the Spool Administration: Initial Screen screen, click the Output Devices button. 4. On the Spool Administration: List of Output Devices screen, click the Change button and then the Create button. 5. On the Spool Administration: Create Output Device screen, fill in the Output Name and Short name - I normally use a short name of DESK for Desktop Printing but alot of people use a Short name SWIN or LOCL as well. Use the following DeviceAttributes fields: Device type = SWIN Device Class = standard printer And the following Access Method fields: Host spool access method = F: Printing on frontend computer Host printer = __DEFAULT. That is _ _ D E F A U L T Save the printer. 6. You may now leave the SPAD transaction. Using this printer will cause print to go to SAPLPD which will use the default printer of the current workstation. 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

SAP Troubleshooting - BASIS Issues 1. What has changed since the performance is poor? System Parameter Changes (RZ10)? Increase in the number of users? Kernel patch? Support Packages? Linux and Oracle patches? Hardware Changes? 2. Any signs of general problems in the System Log - SM21? 3. Places to look: SM50: Process Trace Components is there a Trace level set? Is it greater than 1? What is the utilization of the work processes? Click the white clock picture-icon. Is the total CPU for the last dialog process > 10 minutes? ST04: Is the database monitor activated? If yes, it should deactivated it in normal operation. ST02: Check the buffering quality. If paging occurs in a buffer, the corresponding parameter should be increased. Also refer to SAP Note 121625 in this context. ST03: Select a server Todays Workload: What are the response times? In the case of poor response times, where is most of the time needed? Button Top Time: Are there a lot of different transactions with poor response times or are there only a few? Is a certain transaction always slow or only sometimes? ST06: Detail analysis menu Hardware Info. To which extent are the hardware resources utilized? CallST06 at times with poor system performance. What is the CPU utilization? Goto Current Data Snapshot Top CPU processes and display the main CPU consumers. What is the utilization of the disks? How high is the paging in the base pool? 4. If only few transactions are affected by the performance problem, you should additionally note the following points: 1. Check whether modifications were made in the affected or related transactions. 2. ST03: Display the corresponding performance records. 3. SE30: Carry out a runtime analysis for the affected transactions. 4. ST05: If the database times are high, you should generate an SQL trace of the affected transactions to find out whether the database access is carried out in a useful way. 5. Look for tables that have experienced unusual monthly growth. 1. DB02 Space Statistics button 2. Press Enter on the Tables and Indexes popup 3. History All objects off/on 4. Click the Months button 5. Click on the first number under the Rows Chg/Month header and click the Sort button. 6. The sorted results shows the top tables when it comes to rows changes per month. These tables are your database hogs. 6. What is considered normal response time?

Performance Standards: Response time 1 second (dialog), < 1 second (update) CPU time approx 40% of average response time Wait time < 1% of average response time Load time < 10% of average response time DB request time approx 40% of average response time Database Standards: Direct reads < 10 ms Sequential reads < 40 ms Changes < 25 ms High Value Indications: DB request time - Database or index problems Load time Buffer problems Wait time Not enough work processes Locked tasks Long running transactions Whether you are trying to start a brand new SAP instance, or an old one, there are some very specific places to look for information. If this is a brand new SAP instance, and the installation completed 100% successfully, you know that the instance itself must be viable. If your installaion was never able to complete due to the instance not being able to start up, the issue is probably due to lack of resources. Use the sapinst directory to search the installation logs and find your problem. Sort them with ls ltr is see the list sorted in descending order for the ease of viewing. If you have a test searching tool, look for error in all files with the suffix .log. If your SAP instance has been up and running fine for a good while, then something has probably changed that makes it not come up. have you changed any instance paramters? did you do a kernel replacement for some reason? have there been SAP Support Packages applied that might necessitate a kernel replacement? have there been OS patches? is the database archiver stuck or hosed? has a crucial directory run out of space? has a semaphore or ipc segment gotten stuck from a previous run? is your memory so fragmented that it cant get enough primary space to start the instance? has someone changes the directory privileges? To investigate an unsuccessful start up, look at the logs in the /home/<sid>adm directory. Sort them with ls ltr is see the list sorted in descending order for the ease of viewing. If nothing obvious is found, go to the /usr/sap/<SID>/DVEBMGS00/work directory and do the same thing in this directory. The most useful information can be found in the dev_wx, dev_ms, dev_disp, dev_rfcx, and stderrx files. If all else fails, zip the contains of the /usr/sap/<SID>/DVEBMGS00/work directory, open a problem with SAP, and attach the zipped file to it. Also provide them with the answers to the above questions as well as your current hardware and database platforms, patch level for SAP support packages, kernel, and the OS, and anything else you might think useful. The Delicate Art of SAP Note Search How often have you seen a posted message saying I have searched through SAP Notes and can find nothing related to this matter.? And how often have you gone to SAP Marketplace and done a search yourself and found a hit? If we only had a had a nickle Searching SAP Notes (formerly known as OSS notes) is a science as well as an art. Lets use this error message as an example: BR051I BRBACKUP 6.10 (80) BR055I Start of database backup: bdmsqjbi.anf 2004-02-27 00.05.42 BR602W No valid SAP license found - please contact SAP

First, you should search the specific error message BR602W No valid SAP license found. If you get at least one hit, you should read the SAP Note even if it didnt look as if it pertained 100%. Why? Because it might contain information leading to other notes that did pertain, or give you new ideas for more search terms to help narrow the scope of my query. If you didnt find a note that matched the problem, you could make your next search a little less specifc, like brbackup No valid SAP license found. First you could search for the phrase, and if you had no luck, you could search for all words. And if that produced nothing tangible, you could make it even less specific as in brbackup SAP license error or SAP license error. Normally a very specific query will get you the results you need. But sometimes things get lost in translation. For example, you are applying support packages and get an import error with the following message Panic! Panic! Panic! theres no object header. Since we speak English and we realize that the SAP product was designed and implemented in Germany, we have to guess that the English word Panic! somehow was translated from the German word Warning! and that we can temporarily delay a panick attack until we can research the error. Moral of the story? Realize that some things just dont translate correctly from language to language, and search accordingly. If you searched for Panic! Panic! Panic! and got no hits, you could try warning message no object header. Last, and not least, read and become familiar with your SAP Notes. There are certain notes that you pull over and over again due to some task that needs fresh, current and precise information. These are mostly lists of supported printer devices, known problems with applying patches, etc. If a user seems to be experiencing SAPGui errors, several things need to be checked: Is the operating system on the users workstation patched to the level recommended by SAP? Is the user using a version of SAPGui that is too old for his workstation? Is the user using a version of SAPGui that is not certified for his operating system? Is the users workstation having resource problems? Is the users workstation connected to the LAN? Can a different user reproduce the same error on the same workstation? Are there any SAPGui patches that have not been applied? Most SAPGui problems can be solved by either a) deleting and reinstalling SAPGui on the workstation, or b) deleting and installing a newer version of SAPGui. Make sure that these lines were added to the services file on the users workstation: After you have successfully configured your SAPGui, add these three lines to the bottom of your \Windows\system32\drivers\etc\services file: sapdp00 3200/tcp sapmsR3I 3600/tcp # If you have SAP Instances using System Numbers other than 00, you will have to add their equivalents to the services file as well. Also, check if you are having connection problems due to firewall restrictions. And, be sure that your Insert Key is set so that you can type your password in properly you can delete whatever is in the password field in order to enter your password. If you have never tested connectivity to a SAP instance on the workstation having the connection problem, first you need to make sure that the workstation can connect to the SAP server in some non-SAPGui way. Lets say your user us trying to connect to System ID (SID) DEV, System Number 00, and IP address 10.1.10.11. Open a DOS-Windows and type this: telnet 10.1.10.11 3200 If the screen rolls and goes totally blank then your dispatcher is reachable. You can close the DOS session. If your window never goes completely blank and you set a Connecting To 10.1.10.11 Could not open connection to the host, on port 3200: Connect failed error message right under the command you entered, the dispatcher is not reachable. Also, make sure the \Windows\system32\drivers\etc\hosts file on the workstation is correct. For information regarding operating system, resource, and hardware requirements for running SAPGui, see SAP Note 26417 -SAP GUI Resources: Hardware and software. the CUA Parent Client

If CUA stops sending changes from DEV to QAS or PRD, something in the RFC setup has changed. Either the password or the user type for RFC_USER was changed, or the SM59 RFC connection to was changed and is no longer working. Use SCUL in DEV in your DEV CUA parent to list the errors that are occurring. Look for the user you tried to transport but could not. You might see You are not authorized to change users in group or No authorization for group users in role. This does not mean that YOU are not authorized, it means that the RFC_USER doing the ALE communication between the SAP systems is not authorized. First, reset the RFC_USER password in DEV, QAS, and PRD. And make sure that the user type is Communication and not dialog. Now go to sm59 and do remote logins using the QAS RFC connections. If they work (ie nothing seems to happen after you click the remote logon button) everything should now be fixed. If you get a logon screen for QAS, change the password in the sm59 screen to the same password you changed RFC_USER to in DEV and QAS. Retry your user change. If it still doesnt go to QAS, maybe the QAS system is hosed and down. Important SAP Marketplace Links Inbox http://service.sap.com/inbox Read messages from SAP to you Installation Guides http://service.sap.com/instguides Download SAP product installation License Keys http://service.sap.com/licensekey Request New Permanent License Key Messages to SAP http://service.sap.com/message Open problems with SAP QuickLinks Page http://service.sap.com/quicklinks An index of SAP links Oracle DBA Page http://service.sap.com/dbaora Page for Oracle DBA Material OSS Notes http://service.sap.com/notes Search the SAP Notes Database Patches http://service.sap.com/patches Download SAP software patches Remote Connection http://service.sap.com/remoteconnection Learn about the OSS connection and order it from SAP Service Connection http://service.sap.com/serviceconnection Open a Service Connection for SAP to access your SAP landscape Software Distribution http://service.sap.com/swdc Download new images of Installation CDs & DVDs SSCR http://service.sap.com/sscr Register Developers and Changes made against SAP objects User Administration http://service.sap.com/user-admin Add/Change OSS ID user information Job profile for SAP BASIS Administrator 1. SAP Administration Starting and Stopping SAP instance/(s) User Administration Setup & Maintenance Authorization/Role/ Profiles Setup & Maintenance Setup SAP Security Maintenance of Systems Health Monitor System Performance and Logs Spool and Print Administration Maintain System Landscape Transport Management Systems Manage Change Requests Create/Manage Batch Jobs Backup Schedule,run & Monitor Backup of SAP Apply Patches,Kernel & OSS Notes 2. Database Administration Database Space Management

Database Backup Database Recovery Database log (Redo log, Archive Log) management Database Performance Tunning

3. Operation System Administration Operation System Security Operation System Performance Tunning OS Space management OS level background Job Management OS level backup and recovery

4. Overall System Monitoring Monitoring R3 Servers and Instances Monitoring Users and Authorizations Monitoring Security Part Monitoring workload analysis Monitoring Processes Monitoring Buffers Monitoring Operating system Monitoring Database Monitoring Backups

Answers for the SAP Basis Certification Sample Questions

Question: When creating a logon group for Logon Load Balancing, which of the following CANNOT be specified? Answer: A. Maximum allowable response time. B. Maximum number of users who may be logged on to the instance. C. Name of the instance defined for the logon group. D. Maximum number of sessions per user. E. Name of the logon group Question: Which R/3 System user is used for starting external programs using SAP background jobs? Answer: A. DDIC B. SAP* C. SAPR3 D. SAPCPIC E. <sid>adm

Question: Name the R/3 System transaction used for mointoring a spool requests. Answer: A. SM50 B. SM51 C. SPAD D. SP01 E. SM37 Question: Which of the following is authorized to maintain R/3 user id parameters? Answer: A. Only the R/3 system administrator. B. All R/3 users having an account in the same R/3 client. C. Only the user himself. D. Only the R/3 system administrator and the user.

Question: Given a LAN with an R/3 Central Instance with database (Node: host1, Instance Name:DVEBMGS01, SAPSID:C11), and R/3 Dialog Instance (Node: host2), and several R/3 Frontend PC's what is the name of the profile where the SAPDBHOST parameter is defined? Answer: A. C11_DVEBMGS00_host1 B. The SAPDBHOST parameter is defined in the database startup profile. C. TEMU.PFL D. DEFAULT.PFL E. START_DVEBMGS01_host1 Question: Given and R/3 Central Instance with all services installed, using Instance ID01, and having the SAP ID of C11. What is the name of the directory where the work process trace files are written (for Windows NT replace the "/" with "\")? Answer: A. /usr/sap/C11/DVEBMGS01/data B. /usr/sap/C11/DVEBMGS01/log C. /usr/sap/C11/DVEBMGS01/work D. The trace files are written in internal database tables. E. The trace files are written in the home directory of the database. Question: Which of the following functions is NOT possible using the SAP Online Service System (OSS)? Answer: (All is possible) A. Execute online searches for R/3 Notes. B. Register problems with the SAP Hotline. C. Lookup SAP training dates and course offerings. D. Register changes to SAP objects. E. Apply for official Internet address from SAP.
What is data Dictionary? What is the difference between open sql &amp; native sql ? Difference between Pooled, cluster &amp; transparent tables? What is Primary key, foreign key ? what is primary index? secondary index? how many indexes can be created for a table? what is a value table? what are the components of a table? what is a domain? what is a data element? what is data class? can you create a table with out a data element? can you create a field with out a data element? What approach you prefer for creating a table? Give few names of cluster tables in sap? Give few names of pooled tables in sap? give few names of transparent tables? what is a buffer and how many types? what is table maintenance generator and how to create that? What is the transaction code? How to add new fields to a standard sap table ?

1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20.

21. 22. 23. 24. 25.

How many types of table joins are there? difference between inner join & outer join? Difference between "select * from mara" and "select single * from mara"? what is a match code ? Lock objects ? what are views? what are logical tables/database? what is the difference bet'n table and a structure?

SAP BASIS Interview Questions 1. What are Homogenous system copy and Heterogeneous system copy and how you will
do that?

Homogeneous copy is done when the source and target system are on the same OS and Databse.

Heterogeneous Copy is done when the source and target system differ either in OS or Database. Any ONE difference needs a heterogeneous copy. Homogenous copy is done by export/import technique. Heterogenous copy is done by system migration. It is same as export/import except that it will ask for target OS and DB type and needs a key to be entered. 2. How to import the OSS notes? OSS notes a ".car" file. To work with a CAR File do the following at OS Level: Get into OS as <sapsid>adm Copy the .CAR file to a Temporary Directory. Uncompress the file with SAPCAR Copy the the data file generated in the data transport directory ( ej: = /usr/Sap/trans/data). Copy the the cofile file generated in the cofiles transport directory ( = ej: /usr/Sap/trans/cofiles). Run transaction STMS Upload the support package with SPAM transaction and the support package will show "New support packages".

How to apply OSS notes to my R/3 system? In order to fix one of the problem in R/3 system, SAP will asked you to download an OSS notes which is a ".car" file. To work with a CAR File do the following at OS Level: Get into OS as <sapsid>adm Copy the .CAR file to a Temporary Directory. Uncompress the file with SAPCAR Copy the the data file generated in the data transport directory ( ej: = /usr/Sap/trans/data). Copy the the cofile file generated in the cofiles transport directory ( = ej: /usr/Sap/trans/cofiles). Run transaction STMS Upload the support package with SPAM transaction and the support package will show "New support packages". ********** Examples of CAR command :1) UNIX only: Log on as user <sapsid>adm. cd /usr/sap/trans CAR -xvf tmp/<ARCHIVE_NAME>.CAR -V 2) Windows NT only: Log on as user <SAPSID>ADM. , cd \USR\SAP\TRANS CAR -xvf TMP\<ARCHIVE_NAME>.CAR This Will create two(2) FILES After you run SPAM you MUST run STMS and check the transport queues ********** As per 315963 note you can direct made the changes in the program or you can apply the support pack. a) If you want to apply correction then first you need to register the object in SAP, so that you will get the Access key and then you can make the changes. b) If you want to import the support pack then you need to down load from SAP market-place. and this is in CAR file. and then you need extract the same using CAR utility. ex: CAR -xvf abc.car or you can directly apply the patch from SAPGUI, login to 000 client and then you can load the patch from Presentation server. Also check what is your current basis patch level? For example if you want to apply patch 07 and you are having 05 then you need to apply 06 and then apply 07.
3. What is OCS and How to apply OCS Patches ? OCS PATCH THROUG SNOTE.. Using the concept of operation modes, you can define an operation mode with additional background work processes in transaction RZ04. You can then perform a manual operation mode switch using transaction

RZ03. You do not need to restart your system when doing this. online correction system.Using SPAM ou can apply OCS patches 4. What is Transport domain and Domain controller? transport domain contains copy of reference configuration. domain controller contains reference configuration transport domain consists of all systems that you plan to manage using stms. within transport domain all systems must have unique system ids and only one of these systems is identified as the domain controller the transport domain controller is the system where all TMS configuration settings are maintained. any changes in to the configuration settings are distributed to all systems in the landscape a transport group is one or more systems that share a common transport directory

5. Why do we need to apply support package thru client 000? Why can't we do it through
some other client? We apply support packages through 000 client only because in this client "cross client object changes" options set to "changes to repository and cross client objects are allowed". Remaining client is set to "no changes to repository objects are allowed".
000 is the master Client. If Support packages are uploaded thru that client it is updated in all other clients. So no individual updating is needed

6. What is Consolidation route and delivery routes? The route between development to quality is called consolidation route. The route between quality to production is called delivery route. It is used to transport data dev-->qua-->prod. DELIVERY ROUTE : The route between quality to production is called delivery route. 7. How to define Logon groups? And what is Logon load balancing? Logon group are set using SMLG transaction. Load blancing: During the request message server check for the least loaded instance in the group and route the request to that instance. If instead of logon group we specify the instance then the request is routed to that instance only. Means no load balancing occur in this case. Logon group are set using SMLG transaction. Load blancing: During the request message server check for the least loaded instance in the group and route the request to that instance. If instead of logon group we specify the instance then the request is routed to that instance only. Means no load balancing occur in this case. 8. For an ABAP only system, do we have to SSL? 9. What is the procedure involved in doing a system-copy? 10. How to handle the situation where-in SAP* isn't available? 11. What is the difference between Synchronous and asynchronous transports? 12. How to configure regular transactions such as MM01 to view archived data? 13. How to set the trace level for file dev_rd? 14. How to increase tables space, resizing, backups and in what situation are these done? 15. How to schedule background jobs at OS level? 16. How to define instances and operation modes? 17. How to trace the user who moved the transport request from DEV to QUA? 18. Explain the upgrade process. 19. What is the information derived from OSS notes? 20. What is the procedure to lock a client? 21. What is the procedure to delete a client? 22. What is the importance of early watch client? 23. What are the steps to configure TMS? 24. How to prevent other users to send mails from SAP? 25. What is transport domain? 26. How to determine the authorization a user-required for executing particular transaction(s)? 27. What is the difference between Set deletion flag and set deletion indicator? 28. What is SAPS? 29. What is the database backup strategy? 30. What is the procedure to apply Patches? 31. What are the .sca files and their importance? 32. What is the importance of the clients 000,001 and 006? 33. How to monitorUser accessed transactions (Tcode) day wise?

34. What are common transport errors? 35. If a background job runs more than the time it should be completed normally then what are the actions to be performed? 36. What are the differences between application server and central instance? 37. How to make security authorization reports? 38. What SAP tools you use to install SAP patches? 39. What JAVA tools to install JAVA Patches? 40. What is early watch report? 41. Why https is considered safer than http? 42. What is supplementation language? 43. ABAP Service Pack level can be found in SPAM, but how to find the Java Stack Level? 44. How to install multiple Central Instances on the same physical machine? 45. What is the relevance of the Deletion Flag/Indicator in the archiving process? 46. Can SAP Patches be installed when other users are online? 47. What is the importance/need of Virtual system? 48. How to transport users from one client to another? 49. What are the differences between system refresh and client refresh? 50. How to know whether a system is Unicode or non Unicode?

1. what are steps to install sap ? Install os load the VGA and LAN drivers after increase the SWAP Memory 3 times of physical RAM and Assign IP Address . Install Kernel patches and java files Install dialog and central instance (Start Programs SAP system setup of install Dialog and Central and Database instance . install central and database instance. PARAMETERS: 1.Memory 2.Number of parallel process 3.Instance number 4.SID 5.Central Transport host 6.Data base name 7.Sap data.. Up1 to Data six locations . 2.What is the folder it will ask to install oracle ? Orahome81 path=\Oracle 3.What is you allocate disks to different areas in SAP ? a. Disk1,Disk2,(Raid 1 min 4 GB) winnt, Saparch b. Disk3,Disk4( Stripe Min 4 GB) swap c. Disk5 (min 4 gb) Origilog A, Mirror log B, TRANS: d. Origlog B , Mirror log A, SAPREORG. e. Sapdata1, Sapdata2 ,Sapdata3 , up to Sapdata6 4.How much Swap memory should be in the system ? Three times of main Memory at least 2GB 5.On which system you installed SAP ? QAS (Quallity) 6.How many types of work processes ? 7 types ( Dialog , Enque , Update , Background,Spool,Message server,Gateway) 7.What Is difference between CENTRAL INSTANCE AND DIALOG INSTANCE ? Central Instance have message server installed on it where as Dialog Instance do not have message server. 8.How to see the work process status ? SM50 9.How many types of printer you have configured ? how do you differentiate between them ? 4 types of printers Production Printing , Mass Printing ,Test Printing, Desktop Printing .

10.Where printer port(LPT) is running on the system ? Network and Desktop printers 11.What is the transaction code for creating Roles and how to users and what is method you will follow ? PFCG , then we generate the profile after that assign roles to users 12.Have u applied patches what is the transaction code ? yes, SPAM 13.What are the two files present while importing patches from OS level to SAP level ? .PAT,.ATT 14.Do you see Sao Notes before applying patches if so what are the two steps in SAP notes that we have to follow the before the applying patches? 15.On which system you have applied patches ? DEV and QA 16. Have you applied OSS Notes? No 17.how many types of client copies and which method do you prefer ? we prefer mainly remote Client Copy 18.What is the difference between remote client copy and client export ? RemoteCopy Using RFC connection we will perform remote copy ClientExportUsing TMS configuration we will perform client export and then we have to import client to copy the client STMS has to be created first for doing Client Export. 19.How mucn time it will take to copy a client of size 650Gb More than 17 hours 20.Do you have faced any problems while connecting to OSS some time is not connected , some time it requires authentication 21.What Is your landscape (how many no of application server which production , with specifications( Ram connected, some time it requires authentication ) 22.No of work Process 7 work process (Dialog ,Enque , Background ,Spool, Update, Message, Gateway . 23.What is the job of Application Server It takes the request from the user and if the request requires data than it connects to database server and gives output. 24.What is difference- Central Instance and Application Server (Dialog Server) Central Instancehas a message server and work processes Application server has no message server, having work processes. 25.What are the Daily Activates Background job logs, Spool Logs, Work Processes Overview , Users Overview, All Application Servers active or not . 26.What will you observe in ST06 ? CPU, SWAP , Memory , Hard Disk Space 27.What is ST03 ? Workload Analysis 28.What is the difference between ST06 and ST03 ST06 is OS Monitoring

ST03 is used for - Monitor OS and Database and SAP System 29.What will observe in ST03? Hit Ratio and Buffer Fillers and Roll Memory and Swap memory . 30.What is table buffer and single record buffer ? 31.What will observe with respect to buffer ? 32.Have you configured operation modes yes (RZ04,SM63,RZ03) 33.Where will you change the parameters in three Profiles? Instance Profile ,RZ10 34.Can you change the profile parameter in the OS Level? Which one is advisable why ? We can change the profile parameter from OS level. Its not recommended . 35.If you see the same parameter value in all instance profiles what will you do ? 36.What is Development Class ? Why to Create the Development Class ? Group of requests under one logical name is development class. When ever we changein R3 repository it should be assigned to development calss and it internally assigned to transport layer . 37.I have a created one ABAP program I want to transport. How will you do that ? 38.What is transport domain and what is target Transport Group? 39.I Have three Servers and two application Servers to QAS if I Want to Transport to one application server in QAS and to production system how will do that ? 40.How to create Transport Groups? Through STMS 41.I Have transported one object then how do u know that it has been applied , And if it is not transported what will you do ? How to Create that Object is not yet transferred? IF the request is not in the queue of target system it means it has been applied . If it is there the object is not yet applied . 42.What is difference between transport layer and development class? Development class is assign to transport layer . 43.Do you know about OSS what do you do with OSS? Yes it is online system service. 44.Do you know Logon Groups at which situation will be created Logon group ? Yes, If we find load on application server then we have to create logon group (If the production department users are more than we have to create logon group for that department ) 45.Howmany no of users have been connected to that particular logon group ? 100 to 150 users 46.What is the purpose of Enqueue processor ? Enque work process makes sure that database in consistent state 47.if you have observed enque overflow ? what will you do ? No 48.What is your landscape ? 3 system Landscape

49.If a back ground job is aborted then will you do ? how to rectify that? 50.What are the stats of back ground job ? 5 state 1. Scheduled 2. Ready 3.Released 3. Active 4. Finished 5. Cancelled 51.How many background jobs are running in your production system ? 52.What is the difference between spool request and print request ? 53.what is the job of Spool work Process? 54.IF a user complaints that he could not execute some of the transaction codes then what will you do ? Use T-code SU53 , This will show which authorization is missing in his profile. 55.What are the Daily transactions ? AL03, SM04, SM37, SP01, SM21 etc 56.If there is performance problem how will you analyze the problem ? 57.How will you delete Locks? 58. Have you maintained roles Naming Conventions? 59. If geteway process is failed then can u connect to other R/3 ? 60.How to configure TMS ? 61. What is your landscape ? 62. How transport the request ? 63.What are patches you applied ? SAP_BASIS,SAP_ABAP,SAP_HR,SAP_SD 64.Kernel patches ? 65.Procedure for Appling patches ? SPAM 66.Did you apply patches form OS level ? YAS 67.What are job you assigned jobs ? 69.How Many profiles Total 3 Profiles 1.Default 2.Start 3.Instance

70.Diff between Start and Instance Profile ? 71.ST03 For Load Analysis 72.Read Buffer write Buffer 73.Temse Temporary Sequential Object 74.SE11 Database clearing 75.ST22 Abab Dump

76.What are real-time problems you got ? 77.What are the transactions you used? 78.What is the responsibility in your Company ? 79.Operatin modes configurations on assigning time table? 80.Maintaining user Profiles 81.Background job Configuration and Troubleshooting 82.Background job configuration 83.Applying Packages 84.Performancemonitoring of R/3 systems? 85.what is purpose of logon load balance? To distributed the workload between application servers. 86.Which Tcode is using Logon load Balance ? SMLG 87.I am having two application servers the logon load balance is there ; if the user wants to connect to application server which will connected first. Messages server is will assign the Application server automatically. 88.How do you distribute the load. Depend upon the load, according to module we have to configure logon groups. 89. You have done Documentation for Various tasks ? 90.How to analysis ABAP dumps ? * By seeing ABAP dump error we come to know that whether the error or developer technique If belongs to insufficient memory dump error display at which stage the transaction terminate and how much memory requires. So that we have to increase the memory (Through Instance profile) If belongs to table space error it displays the table name so that we increase the table space through the SAPDBA If belongs to program error we have analysis the ABAP program through se30 If belongs to developer technique cancel the ABAP program 91.Each and every work processor is full even though the user wants to execute the program. Then whats the solution ? If u dont have second applicaitno server than we have to cancel te particular work processor (through SM50) If u have second application server than we have to configure the logon groups 92.At what stages we need to transport the requests Whenever we need the change the objects and need to transport we have to perform transports like user request , client transport etc.. 93.How to perform the transport? Through STMS_IMPORT or through FTP. 94.Whenever I Suppose to start the MMC , The message server is starting , but the dispatcher and work process is unable to start ? what could be the problem ?

95. If the Gateway service failed , can you connect to other r/3 System? 96.I tried to cancel a job with Cancel Active Job but I got the message Job is not active I killed the process in SM50 , but my SM37 is still showing ACTIVE . What can I do to fix this ? In SM37 select job name and user Execute Second screen on the top select job Check status Start STMS and double click on the request it self, you will see which type of request it is (Workbenchclient Independent or Customizingclient dependent). I recommend you to import every request on which client without looking inside the request. 97.What are the Background job you applied ? Checking the spool logs, Background job logs, Client Copies , etc 98.I Applied one background job Logs ,Client Copies etc.. 99.what is the procedure to applying Patches ? first we will download the patches from the service .sap.com to Trans Directory . In the trans Directory extract the patches using CAR command after that using SAPM we have to import patches into sap level and apply. 100.How to configure TMS ? Select all systems in a landscape and select for domain controller and type stms and give domain name and go to reaming systems and configure the same and come to dc and select configure and distribute option .Create transport route and paths .
SAP BASIS Backup Interview Questions Your Companys Take on Backups Backup and recovery for a SAP instance is best handled along with the other backup and recovery needs of your companys computer systems. But for those companys who do not yet possess a solid backup and recovery solution, or who simply want to segragate the SAP landscape from all other internal IT solutions, here are a few things you need to know. Online versus offline, high availability, frequency, are all decisions your IT staff need to make based on their history with similar procedures at your company, the recommendations of SAP, and the guidance of your implementation Basis consultant. Enforced backups, and detailed and tested recovery procedures should be part of any Disaster Recovery plan, and a documented part of any SAP implementation project. If your company falls into the latter category, SAP does supply tools for your uses which can be used in either line command form or from within the SAP instance. If you SAP server contains a tape drive or has access to the network tape unit, transaction DB13 can be used to schedule periodic backups. This is the same transaction where weekly statistics, log cleanup, and database verification jobs are scheduled in the postinstallation work after installation of a new SAP instance. DB13 scheduled BRCONNECT runs which can also be CRONed in command line form by the IT staff. For more information, please see the SAP Online Documentation for DB13 by going to the DB13 transaction and clicking Help -> Application Help or referring to the section Creating Database Statistics, Index Rebuilds, and Log Backup Jobs Oracle. More information regarding BRCONNECT can be found in the SAP BRCONNECT Guide which can be found at http://service.sap.com/instguides. What Needs to Be Backed Up? The PRD Instance Daily backup should be made for these SAP specific directories: /usr/sap/<SID> /sapmnt/<SID> /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/<SID> 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/<SID> /sapmnt/<SID> 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/<SID> 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. Working with saprouter Starting saprouter (OSS Link) 1. Log on to the appropriate server as <sid>adm. 2. Click Start Administrative Tools Services to open a Services window. 3. Right-click on the SAPROUTER service and click Start. 4. You may now log off the server. Verifying the Status of saprouter If you have previously successfully established SAPNet (OSS) communications with SAP via saprouter in the past, there can only be three reasons for a broken SAPNet connection to SAP: the SAP VPN is down (which rarely happens); your saprouter configuration has been incorrectly changed (also very rare); or your saprouter is not running (happens all the time). 1. Log on to the appropriate server as <sid>adm. 2. Click Start Administrative Tools Services to open a Services window. 3. Look at the SAPROUTER service. If is not started, right-click to start the service. If it is started, right-click & Stop the service and then right-click & Start the service. This should bounce your saprouter instance. 4. You may now log off the server. Return to Index... Stopping saprouter 1. Log on to the appropriate server as <sid>adm. 2. Click Start Administrative Tools Services to open a Services window. 3. Right-click on the SAPROUTER service and click Stop. 4. You may now log off the server. SAP BASIS Client Interview Questions ....add a client? ....add a logical system ID to be assigned to a client? ....change a client? ....copy one client to another in the same R/3 system? ....copy one client to another in different R/3 systems? ....copy only user master data from one client to another? ....delete a client? ....lock a client so configuration changes cannot be made? ....verify that a client copy ran successfully? ....view all past client copies for a client? SAP BASIS Communication Interview Questions

1. Creating, Modifying, and Deleting RFC Connections

Creating a RFC Connection 1. Log on to any client on the appropriate SAP system. 2. Go to transaction SM59. 3. On the Display and maintain RFC destinations screen, click the Create button. 4. On the RFC Destination screen, type in a RFC destination name. This name should contain meaningful information such as the SID of the SAP system and/or any client numbers. Select the Connection type from the connection type dropdown, and type the connection specifics in the Description box. If the connection type is a 3 (another SAP system), fill in the necessary client logon information in the Logon section. Fill in the Language, Client, User, and Password for an existing user in the target RFC SAP system. This user should be a system or communication user (ie RFC_USER or ALEREMOTE), not a dialog user. Once all this information is provided, press Enter.

5. In the Technical settings section of the RFC Destination screen, type in the name or IP address of the Target host. If the target is another SAP system, enter the number of System number (00 for all SAP systems except BW QAS which needs a 01). Press Enter. 6. On the RFC Destination screen, click the Save picture-icon. You will receive a Destination saved message in the status bar at the bottom of the screen. You may now leave the SM59 transaction. Modifying a RFC Connection 1. Log on to any client on the appropriate SAP system. 2. Go to transaction SM59. 3. On the Display and maintain RFC destinations screen, expand the appropriate RFC destination navigation level and double click the RFC destination to be changed. 4. On the RFC Destination screen, make any necessary changes. Once the information is changed, click the Save picture-icon. 5. You will receive a Destination saved message in the status bar at the bottom of the screen. You may now leave the SM59 transaction. Deleting a RFC Connection This document is the intellectual property of Jo Spencer and may not be edited without permission. 1. Log on to any client on the appropriate SAP system. 2. Go to transaction SM59. 3. On the Display and maintain RFC destinations screen, expand the appropriate RFC destination navigation level and click the RFC destination to be deleted. Click the Delete button. 4. On the Delete destination popup, click the Yes button. 5. You will not receive a confirmation message. You may now leave the SM59 transaction. Testing a RFC Connection SAP BASIS DB Interview Questions Creating Database Statistics, Index Rebuilds, and Log Backup Jobs MS SQL Server Database statistics refresh jobs should be scheduled to run twice daily on all the SAP systems. But occasionally a manual refresh needs to be done due to table reorganization, index rebuild, etc. 1. Log on to the server using the <sid>adm user ID. 2. Open the MS SQL Server Enterprise Manager. 3. Expand the navigator tree until you see the Management entry. Expand it. 4. Right-click on Database Maintenance Plans and click New Maintenance Plan. 5. Use the wizard to create the job you need. 6. You may now close the Enterprise Manager session and log off the server. Creating Database Statistics, Index Rebuilds, and Log Backup Jobs Oracle 1. Log on to the appropriate SAP instance any client. 2. Go to transaction DB13. 3. On the DBA Planning Calender for Oracle Database <SID>: Maintain screen, double-click on a blank line on any day in the future. 4. On the Schedule Action for <Day>. DD.MM.YYYY popup, use the radio button to turn on the task you want to do. For each action, you need to fill in the Start Time in military time format, the Period (Weeks) which is how many weeks between running of this job blank for one time only, 1 for weekly, 2 for bi-weekly, etc. and Calender if you want to use any calendar except the SAP supplied standard Factory calendar. These are the details for each action: Whole database offline + redo log or Whole database offline backup or Whole database online + redo log or Whole database online backup Generic tape names for database backup Database backup profile usually init<SID>.sap Options for ReDo log backup Redo log backup Generic tape names for database backup Options for ReDo log backup Partial database offline backup or Partial database online backup Tablespace names to be included in the back up This document is the intellectual property of Jo Spencer and may not be edited without permission. Generic tape names for database backup Database backup profile usually init<SID>.sap Check and update optimizer status

Tablespace names to be included in the statistics run Adapt next extents Tablespace names for next extents adaption Check database N/A Verify database Tablespace names to be verified Database backup profile usually init<SID>.sap Cleanup logs N/A 5. You may now leave the DB13 transaction. SAP BASIS DB Interview Questions Scheduling a New Job 1. Log on to the appropriate SAP instance and client using BATCH_USER. 2. Go to transaction SM36. 3. On the Define Background Job screen, fill in the Job name field with the new job name. Select a Job Class priority of A for High, B for Medium, and C for Low. It is SAPs recommendation that all client-owned jobs begin with a Z for identification purposes. And most Basis people recommend the next two characters be the initials for the SAP module for which the SAP instance runs. Like ZBC* for a Basis job, and ZHR* for a Human Resources job. Click on the Specify start condition button or press F5. 4. On the Start Time popup, click the Immediate button to start the job right away, or click the Date/Time button to specify a date/time in the future for which the job run. Click on the Periodic job radio button and then click the Period values button if you want to schedule to job to run on a periodic basis. Provide the periodic values and click Save back to the main Define Background Job screen. 5. On the main Define Background Job screen, click the Step button. 6. On the Create Step 1 popup, fill in the ABAP program Name and any Variant needed to run the program you had to have created the variant using BATCH_USER before using it here. Then click Save once more. 7. Back on the Define Background Job screen, check that all the job information is correct and then click the Save button one last time. Return to Index... Modifying a Released or Scheduled Job 1. Log on to the appropriate SAP instance and client as either the user ID owning the job or an administrator ID. 2. Go to transaction SM37. 3. On the Simple Job Selection screen, fill in the Job name field or use any of the screens filtering options to produce a list from which you can see the job to be changed. In order for a job to be changed, it has to have a status of Schedule or Released so turn those statuses on and turn the rest off. Click on the Execute button. 4. On the Job Overview screen, click on the line containing the job to be changed and then click Job Change. This document is the intellectual property of Jo Spencer and may not be edited without permission. 5. On the Change Job screen, make your changes and then click Save. If you have more than one occurance of the same job in your list, you must change each job scheduled to run earlier than that job you just changed. Once the job you changed runs, all occurences of the jobs running after that date will be changed as well. Return to Index... Deleting a Released of Scheduled Job 1. Log on to the appropriate SAP instance and client as either the user ID owning the job or an administrator ID. 2. Go to transaction SM37. 3. On the Simple Job Selection screen, fill in the Job name field or use any of the screens filtering options to produce a list from which you can see the job to be deleted. In order for all occurances of a job to be deleted, all statuses of the job should be checked on. And enter an all-encompassing date like 01-01-1990 through 12-31-2010. Click on the Execute button. 4. On the Job Overview screen, click on all the perpetent line containing the job(s) to be deleted and then click on the Delete job from database button. 5. On the Delete Scheduled Jobs? popup, confirm the deletion. Return to Index... Viewing the Job Queue 1. Log on to the appropriate SAP instance and client as either the user ID owning the job or an administrator ID. 2. Go to transaction SM37.

3. On the Simple Job Selection screen, fill in the Job name field or use any of the screens filtering options to produce a list from which you can see the job you want to view. In order for all occurances of a job to be viewed, all statuses of the job should be checked on. Click on the Execute button. Return to Index... Deleting an Active aka Runaway Job Opinions on this topic vary so these are good guidelines to use. These are pretty much in the order they should be tried: 1. Kill the session via SM37 or SM04. 2. Try End session through SM50 or cancel program from SM66. 3. If the Work Process in SM50 is in stopped state then killing it will not help much or quickly, you need to identify why it is stopped (running a program on another server, runing in parallel etc.) Try and end those. 4. Kill Work Process in SM50 without core. 5. Kill process or PID via program RSBDCOS0. 6. If all else fails, restart the SAP instance server. The most important things to remember when killing a WP are: 1. Change to restart = no as otherwise the session can jump back in sometimes as most of its memory is not actually living in the WP. 2. Allow it a long time to stop, there is no need to do it twice or 50 times as I have seen some people do, the poor old thing is just trying to recover rollback and reinitialize itself. This document is the intellectual property of Jo Spencer and may not be edited without permission. Return to Index... Cleaning the Job Log 1. Log on to the appropriate SAP instance and client. 2. Go to transaction SE38 and type in Program name RSBTCDEL and click on the Execute button. 3. On the Delete batch jobs screen, fill in the filtering information you need. It is suggested that Delete with forced mode be on. Click on the Execute button. 4. A status message will appear in the bottom Status Bar as the list of job logs to be deleted is built. Once all the specified job logs have been deleted, a final total of jobs logs cleaned will appear in the bottom Status Bar. SAP BASIS Printer Interview Questions Creating, Modifying, Deleting, Transporting, and Resetting Print Devices Creating a Print Device 1. Log on to any client in the appropriate SAP system. 2. Go to transaction SPAD. 3. On the Spool Administration: Initial Screen screen, under the Devices/servers tab click the Output devices button. This document is the intellectual property of Jo Spencer and may not be edited without permission. 4. On the Spool Administration: List of Output Devices screen, click the pencil picture-icon to switch into change mode. The easiest way to create a new printer is to copy an existing one. Click on a similar printer in the output devices screen then click the create with template picture-icon. 5. On the Spool Administration: Create Output Device screen, fill in the Output device and Short name. Make any changes that are unique for the new printer on the Device Attributes and Host Spool Acc Method tabs. When all the required data has been changed/added, click the Save picture-icon. 6. You will receive an Output device was saved message in the status bar at the bottom of the screen. Click the lit match picture-icon to activate the printer. 7. You may now leave the SPAD transaction. Return to Index... Modifying a Print Device 1. Log on to any client in the appropriate SAP system. 2. Go to transaction SPAD. 3. On the Spool Administration: Initial Screen screen, under the Devices/servers tab click the Output devices button. 4. On the Spool Administration: List of Output Devices screen, click the pencil picture-icon to switch into change mode. Double click on the output device to be changed. 5. On the Spool Administration: Output Device (Change) screen, make any necessary changes on the Device Attributes and Host Spool Acc Method tabs. When all the required data has been changed/added, click the Save picture-icon. 6. You will receive an Output device was saved message in the status bar at the bottom of the screen. Click the lit match picture-icon to activate the printer. 7. You may now leave the SPAD transaction. Return to Index... Deleting a Print Device 1. Log on to any client in the appropriate SAP system. 2. Go to transaction SPAD.

3. On the Spool Administration: Initial Screen screen, under the Devices/servers tab click the Output devices button. 4. On the Spool Administration: List of Output Devices screen, click the pencil picture-icon to switch into change mode. Click on the output device to be deleted and then click the trash can picture-icon. 5. On the Spool admin.: Delete screen, verify that the correct printer is about to be deleted. Click the Yes button. 6. You will receive an Output device deleted message in the status bar at the bottom of the screen. You may now leave the SPAD transaction. Return to Index... Transporting a Printer or a Group of Printers 1. Log on to any client in the appropriate SAP system. 2. Go to transaction SPAD. This document is the intellectual property of Jo Spencer and may not be edited without permission. 3. On the Spool Administration: Initial Screen screen, under the Devices/servers tab click the Output devices button. 4. On the Spool Administration: List of Output Devices screen, click the pencil picture-icon to switch into change mode. 5. Click on an output device to be transported and then click the truck picture-icon. 6. On the Spool Administration: List of Output Devices (Change) popup, click the green picture-icon. 7. On the Prompt for Workbench request popup, click the blank page picture-icon to create a new change request. On the Create Request popup, fill in the Short description and click the Save picture-icon. You will be returned to the Prompt for transportable Workbench request popup which contains the generated change request number for this system change. Click the green to continue. 8. You will receive an Entry is made in transport request message in the status bar at the bottom of the screen. Repeat steps 11 through 14 as many times as necessary, using the same transport request for all printers. 9. You may now leave the SPAD transaction. Return to Index... Resetting the Cache for a Printer If resetting the printer cache does not clear your printing problem, try using some a non-SAP application to print to it to see if it working correctly on the network. This should at least narrow down the possibilities. 1. Log on to any client in the appropriate SAP system. 2. Go to transaction SPAD. 3. On the Spool Administration: Initial Screen screen, under the Devices/servers tab click the Output devices button. 4. On the Spool Administration: List of Output Devices screen, double click on the printer you need to reset. 5. On the Spool Administration: Output Device (Display) screen, click on the pencil picture-icon to switch from display mode to change mode. 6. On the Administration: Output Device (Change) screen, on the top-most menu bar click Edit Reactivate. 7. On the same Administration: Output Device (Display) screen, on the top-most menu bar click Edit Reset Cache. 8. On the same Administration: Output Device (Display) screen, on the top-most menu bar click Edit NI Reset. 9. You may now leave the SPAD transaction. Return to Index... Printer Output Creating a Local aka Frontend Printer aka Desktop Printer Local or frontend printing is sometimes confusing in concept but actually very easy to understand. As a rule, local printer is simply another way of saying that the user is going to print to the default printer designated on his/her workstation. You probably do this all the time with Windows to printer spreadsheets, Word documents, etc without thinking about it. You can do the same thing using SAP. 1. Log on to any client in the appropriate SAP system. This document is the intellectual property of Jo Spencer and may not be edited without permission. 2. Go to transaction SPAD. 3. On the Spool Administration: Initial Screen screen, click the Output Devices button. 4. On the Spool Administration: List of Output Devices screen, click the Change button and then the Create button. 5. On the Spool Administration: Create Output Device screen, fill in the Output Name and Short name - I normally use a short name of DESK for Desktop Printing but alot of people use a Short name SWIN or LOCL as well. Use the following DeviceAttributes fields: Device type = SWIN Device Class = standard printer

And the following Access Method fields: Host spool access method = F: Printing on frontend computer Host printer = __DEFAULT. That is _ _ D E F A ULT Save the printer. 6. You may now leave the SPAD transaction. Using this printer will cause print to go to SAPLPD which will use the default printer of the current workstation. Return to Index... Viewing a List of Pending Printer Output Requests for All Printers 1. Log on to any client in the appropriate SAP system. 2. Go to transaction SP01. 3. On the Output Controller: Spool request selection Screen screen, click on the Output requests tab. 4. On the Output Controller: Output request selection Screen screen, fill in any information needed to filter the selection results. Then click on the clock picture-icon. 5. A list of all pending output requests will be displayed. 6. You may now leave the SP01 transaction. Return to Index... Viewing a List of Output Requests for a Specific Printer 1. Log on to any client in the appropriate SAP system. 2. Go to transaction SPAD. 3. On the Spool Administration: Initial Screen screen, under the Devices/servers tab click the Output devices button. On the Spool Administration: List of Output Devices screen, click on the printer where you need to check the output requests. Then click on the printer and page picture-icon. 4. A list of all pending output requests for the selected printer will be displayed. 5. You may now leave the SPAD transaction. Return to Index... Reprinting a Document This document is the intellectual property of Jo Spencer and may not be edited without permission. 1. Log on to any client in the appropriate SAP system. 2. Go to transaction SP01. 3. On the Output Controller: Spool request selection Screen screen, fill in any information needed to filter the selection results. Then click on the clock picture-icon. 4. A list of all spool requests will be displayed. Double click on the spool request that is to be reprinted. 5. Click on the printer picture-icon. An Output request created message should appear in the bottom status bar. 6. You may now leave the SP01 transaction. Return to Index... Re-routing Print to a Different Printer 1. Log on to any client in the appropriate SAP system. 2. Go to transaction SP01. 3. On the Output Controller: Spool request selection Screen screen, fill in any information needed to filter the selection results. Then click on the clock picture-icon. 4. A list of all spool requests will be displayed. Double click on the spool request that is to be reprinted. 5. Click on the printer with a box outline picture-icon. On the Output controller: Print spool request XXXX screen, tab down to the line reading Output device and select a new printer. Click on the printer picture-icon. 6. On the Output control: Save attributes popup, click the Yes button. 7. On the Confirm redirection of output popup, click the Yes button. An Output request created message should appear in the bottom status bar. 8. You may now leave the SP01 transaction. SAP BASIS Security Interview Questions Creating a User Role The easiest way to create a new user role is to copy an already existing user role, either one of your own or one of the ones provided to you in the installation of SAP. So lets assume that you have none of your own and use one This document is the intellectual property of Jo Spencer and may not be edited without permission. of the SAP role templates provided. It might assist you with picking one of these roles if you have someone dump the appropriate information into a spreadsheet containing the Role Name, Role Description, Transactions contained in the Role, and the Transaction description. The SQL query would be something like this: SELECT AGR_TEXTS.AGR_NAME, AGR_TEXTS.TEXT, AGR_TCODES.TCODE, TSTCT.TTEXT FROM

AGR_TEXTS, AGR_TCODES, TSTCT WHERE AGR_TEXTS.MANDT = '000' AND AGR_TEXTS.SPRAS = 'E' AND AGR_TEXTS.LINE = 0 AND AGR_TCODES.MANDT = '000' AND AGR_TCODES.AGR_NAME = AGR_TEXTS.AGR_NAME AND TSTCT.SPRSL = 'E' AND TSTCT.TCODE = AGR_TCODES.TCODE ORDER BY AGR_TEXTS.AGR_NAME, AGR_TCODES.TCODE; This query should be changed based on the details of your SAP instance. Identify the roles(s) to be used as the source for your role copy. 1. Log on to client needing the role. 2. Go to transaction PFCG. 3. On the Role Maintenance screen, either type in the role name to be copied or select it from a dropdown. Press Enter to confirm that the role exists. 4. Click the Copy role button or press Shift+F11. 5. One the Query popup box, fill in the to role field with the name to be given the new role. Come up with a standard that everyone follows so the base original role is designated in some way so you dont forget where you got the original. The name must begin with Z or Y. Most people will add a Z- in the first two characters of the role name. If you want to only select specific roles from a Composite role, you would click the Copy selectively button, otherwise click the Copy all button. 6. Once the role has been copied, you will be taken back to the original PFCG screen where you will see the name of your new role. Change you Role description and save the new role before working with it any further Return to Index... Modifying a User Role 1. Log on to client needing the role change. 2. Go to transaction PFCG. 3. On the Role Maintenance screen, either type in the role name to be changed or select it from a dropdown. Press Enter to confirm that the role is found. 4. Click the Change Role little yellow pencil button role button or press F6. 5. Click the Authorizations tab and then the Change Authorization Data button. 6. On the Change Role: Authorizations screen, expand and change the authorizations you need to adjust. When finished click first the Save button and then the Generate button looks like a little red and white beachball. 7. Back out to the Change Roles screen and click the User tab. Click on User Comparison and then Complete Comparison. Once the comparision is done, click Save one more time and you are done! Return to Index... Deleting a User Role This document is the intellectual property of Jo Spencer and may not be edited without permission. 1. Log on to client needing the role deletion. 2. Go to transaction PFCG. 3. On the Role Maintenance screen, either type in the role name to be changed or select it from a dropdown. Press Enter to confirm that the role is found. 4. Click the Role Delete button or Shift+F2. 5. On the Delete Role popup, confirm that you wish to delete the deletion. If you get an Information popup, confirm it also. 6. Your deletion will return a successful message in the bottom status bar. Return to Index... Transporting User Roles between Clients (Transport System Method) When a modification is made to a role in the 100 client, the roles must be transported to the 800 client. One role, several roles, or all roles can be done if needed. They can all be added to the same transport change request. After the roles have been moved to other clients, you will need to log on to each of those clients and do a user comparison. You will also need to do a text comparison in client 100 of the appropriate SAP system. 1. Log on to client 100 of the appropriate SAP system. 2. Go to transaction PFCG. 3. On the Role maintenance screen, type in the Role name of the first role to be transported. Click the Truck picture-icon. 4. You will see an Information popup. Click the green picture-icon. 5. In the Choose objects popup, unclick the s beside User assignment and Personalization. If you want to transport the users along with the role, profiles, and authorizations, you can the to the left of User assignment. Click the green picture-icon. 6. On the Prompt for Customizing request popup, click the blank page picture-icon to create a new change request. On the Create Request popup, fill in the Short description and click the Save picture-icon. You will be returned to the Prompt for Customizing request popup which contains the generated change request number for this system change. Click the green to continue. 7. You will see a Data entered in change request message in the status bar at the bottom of the screen. Now enter the name of the next role to be transported and click the Truck picture-icon. 8. You will see an Information popup. Click the green picture-icon.

9. In the Choose objects popup, unclick the s beside User assignment and Personalization. If you want to transport the users along with the role, profiles, and authorizations, you can the to the left of User assignment. Click the green picture-icon. 10. On the Prompt for Customizing request popup, continue to use the same transport you created in step 6. Click the green to continue. 11. Continue to perform steps 7 through 10 until all the roles you need to transport have been attached to the transport change request. 12. The generated transport can now be released and transported into the clients needing the modified roles. 13. You may now leave the PFCG transaction. Return to Index... Transporting User Roles between Clients (Upload/Download Method) Central User Administration distributes clients and their information to the other clients connected to the Distribution Model. It does not, however, do the This document is the intellectual property of Jo Spencer and may not be edited without permission. same for roles and role authorizations. So when a modification is made to a role in the 100 client, the roles must be transported to the 800 client. One role, several roles, or all roles can be done if needed. They can all be added to the same transport change request. After the roles have been moved to other clients, you will need to log on to each of those clients and do a user comparison. You will also need to do a text comparison in client 100 of the appropriate SAP system. 1. Log on to client 100 of the appropriate SAP system. 2. Go to transaction PFCG. 3. On the Role maintenance screen, type in the Role name of the first role to be transported. Click the Truck picture-icon. 4. You will see an Information popup. Click the green picture-icon. 5. In the Choose objects popup, unclick the s beside User assignment and Personalization. If you want to transport the users along with the role, profiles, and authorizations, you can the to the left of User assignment. Click the green picture-icon. 6. On the Prompt for Customizing request popup, click the blank page picture-icon to create a new change request. On the Create Request popup, fill in the Short description and click the Save picture-icon. You will be returned to the Prompt for Customizing request popup which contains the generated change request number for this system change. Click the green to continue. 7. You will see a Data entered in change request message in the status bar at the bottom of the screen. Now enter the name of the next role to be transported and click the Truck picture-icon. 8. You will see an Information popup. Click the green picture-icon. 9. In the Choose objects popup, unclick the s beside User assignment and Personalization. If you want to transport the users along with the role, profiles, and authorizations, you can the to the left of User assignment. Click the green picture-icon. 10. On the Prompt for Customizing request popup, continue to use the same transport you created in step 6. Click the green to continue. 11. Continue to perform steps 7 through 10 until all the roles you need to transport have been attached to the transport change request. 12. The generated transport can now be released and transported into the clients needing the modified roles. 13. You may now leave the PFCG transaction. Return to Index... Performing a User Comparison on the Modified Roles 1. Log on to client 100 of the appropriate SAP system. 2. Go to transaction PFCG. 3. On the Role maintenance screen, type in the Role name of the first role to be transported. Click the Change button. 4. On the Change Roles screen, click the User tab. 5. On the User tab, click the User compare button. 6. On the Compare Role User Master Record popup, click the Complete compare button. 7. You will receive a User master record for role was adjusted message in the status bar at the bottom of the screen. You may now leave the PFCG transaction. Return to Index... Performing a Text Comparison to Refresh Role Selection Lists This document is the intellectual property of Jo Spencer and may not be edited without permission. 1. Log on to client 100 of the appropriate SAP system. 2. Go to transaction SU01. 3. On the User Maintenance: Initial Screen screen, type in the user model_user. Click the pencil picture-icon. 4. On the Maintain User screen, click the Text comparison from child Syst. button. 5. On the CUA: Text comparison from Child Systems screen, type LSDEV100 for the Receiving system and LSQAS800 for the to system. This is a range, and since LSPRD300 falls alphabetically between LSDEV100

and LSQAS800, all three systems will have the text comparison performed. Click the clock picture-icon. 6. On the CUA: Text comparison from Child Systems results screen, you will see a list of the systems compared and the compare results. Click the white arrow on green picture-icon 3 times, or until you have left the SU01 transaction. Return to Index... Users, Roles, and Authorizations SAP security is based on authorization objects and authorizations. An authorization object is used to indicate that a user can perform a certain activity. An authorization is used to limit the scope of that activity. For example, a profile contains the S_DEVELOP authorization object. This authorization object allows a user to perform ABAP workbench activities. Some users will need to do all ABAP activites while others will only need to perform a few. So S_DEVELOP has a selection of authorizations you can use: ACTVT, DEVCLASS, OBJNAME, OBJTYPE, and P_GROUP. The authorizations are set to the appropriate values as needed. A tree view of the S_DEVELOP authorization object can be seen below: S_DEVELOP ACTVT Create or generate Change Display Delete Activate, generate Execute Create in DB Delete in DB Convert to DB Administer Copy All Functions Deactivate Mod. assistant DEVCLASS Single Value or Value Range OBJNAME Single Value or Value Range OBJTYPE Single Value or Value Range P_GROUP Single Value or Value Range The S_DEVELOP authorization object in a profile lets a user perform ABAP workbench activities. But having a S_DEVELOP authorization object with the ACTVT This document is the intellectual property of Jo Spencer and may not be edited without permission. authorization value set to Display (03) means that the user is limited to display only in the ABAP workbench transactions. Thus we see that authorization objects grant while authorizations limit. It is important to remember, however, that a user with a profile having a S_DEVELOP with full authorizations still cannot access an ABAP workbench transaction until a matching S_TCODE (start up transaction code) has been added as well. In other words, a user may have the rights to add, modify and delete ABAP programs but until an entry for SE38 has been added to the S_TCODE authorization object, he cannot access transaction SE38 which is the ABAP Editor. All authorization objects and authorizations are grouped into profiles before being attached to users. Profiles use a combination of authorization objects and their respective authorizations, and their creation can be complex as well as tedious. In order to simplify the creation of profiles, the Profile Generator (transaction PFCG) was created. Roles are created via a more user-friendly interface which generates profiles based on the information added via this interface. Manually creating profiles is the old way of doing things. There are times, such as the start of a new SAP landscape where no roles exist, that the use of profiles is handy. But once the landscape has been completed all users, with the exception of the Basis team, should be attached to roles. There should never be a need to manually create a SAP new profile. To add a new role, the easiest method is to copy an existing role that matches your needs as closely as possible and make the changes you need for the new role. This documentation covers changing user security via both methods. Adding Authorization Objects and/or Authorizations to a Profile Remember that profiles are NOT the standard way to implement SAP security 1. Log on to the appropriate client in the appropriate SAP system. 2. Go to transaction SU02. 3. In the Manually edit authorization profiles section of the Profile: Initial Screen screen, enter the Profile you want to change. Make sure the Active only is checked. Click the Create work area for profiles button. 4. On the Profile List screen, double-click the profile to be changed.

5. A profile can contain authorization objects only (single profile) or one or more other profiles (collective profile). If the next screen is titled Maintain Profile, this is a single profile, and you should proceed to the next step. If the next screen is titled Collect Profiles, this is a collective profile and you should skip to step 13. 6. On the Maintain Profile screen, you must decide if you need to add a new authorization object and one or more of its authorizations, or add a new authorization to an authorization object already in the profile. If you need to add a new authorization to an authorization object already in the profile, skip to step 7. Otherwise, scroll down the Consisting of authorizations list until you find a blank line. Type the authorization object you need to add and press Enter. You will need to scroll through the list again until you find the authorization object you just added (it is was to find since the Authorization column should still be blank). Once you find the new entry line, use the drop down to fill in the Authorization column. Click on the Save picture-icon. 7. If you need to add another authorization to an authorization object already in the profile list, click on the +Add authorization button. 8. From the Maintain Profiles: Object Classes screen, double-click the Object class of the authorization you are adding. 9. On the Maintain Profiles: List of Authorizations screen, select the authorization you need to add by doubleclicking the appropriate line. This This document is the intellectual property of Jo Spencer and may not be edited without permission. will return you to the Maintain Profile screen where you can see that your authorization has been added. 10. On the Maintain Profile screen, click the Save picture-icon. Then click the lit match picture-icon to activate the new profile changes. 11. On the Activate Profile: Execution Screen screen, click on the lit match picture-icon to complete the profile activation process. 12. You may now leave the SU02 transaction. 13. In order the change a profile collection, you must make the changes in one or more of the dependent profiles, save the changes in the dependent profile(s), activate the dependent profile(s), save the collection owner profile, and activate the collection owner profile. On the Collect Profiles screen, double-click on the profile you want to change. 14. You will be taken to the Maintain Profile screen. Perform steps 6 to 11. Then use the white arrow on green picture-icon to go back. 15. On the Collect Profiles screen, click the Save picture-icon. Then click the lit match picture-icon to activate the new profile changes. 16. On the Activate Profile: Execution Screen screen, click on the lit match picture-icon to complete the profile activation process. 17. You may now leave the SU02 transaction. Return to Index... Adding Authorization Objects and/or Authorizations to a Role 1. Log on to client 100 in the DEV SAP system. 2. Go to transaction PFCG. 3. On the Role Maintenance screen, enter the Role you want to change. Click the Change button. 4. On the Change Role screen, click the Authorizations tab and then click the pencil picture-icon. 5. If you are only adding a start up transaction to the role, skip to step 10. Otherwise, the assumption is that a new authorization object is to be added. On the Change role: Authorizations screen, click the +Manually button. 6. On the Manual selection of authorizations popup, enter the authorizations objects that need to be added (ie S_DEVELOP, S_PROGRAM, etc.) Click the green when you are finished. 7. Back on the Change role: Authorizations screen, if all the displayed signal lights are green, skip to step 8. Otherwise, fully expand the lines that are yellow and/or red and supply the necessary information. All signal lights should be green before moving to the next step. 8. On the Change role: Authorizations screen, click the Save picture-icon. You will receive a Data saved confirmation message in the status bar at the bottom of the screen. 9. On the Change role: Authorizations screen, click the red-and-white beach ball picture-icon to generate a profile from the saved role. Reply affirmatively if any confirmation popups. You will receive a Profile(s) created message in the status bar at the bottom of the screen. If you do not need to add any start up transactions to the profile, you may now leave the PFCG transaction. 10. On the Change Role: Authorizations screen, expand the Cross-application Authorization Objects Authorization Check for Transaction Start Authorization Check for Transaction Start until you see the Transaction code entry line. Double-click on the entry portion of the Transaction code line. 11. In the Maintain Field Values popup, scroll down the list until you find a blank From and To line. Enter the transaction(s) to be added, and click the Save picture-icon when you have finished. This document is the intellectual property of Jo Spencer and may not be edited without permission. 12. On the Change role: Authorizations screen, click the Save picture-icon. You will receive a Data saved confirmation message in the status bar at the bottom of the screen. 13. On the Change role: Authorizations screen, click the red-and-white beach ball picture-icon to generate a profile from the saved role. Reply affirmatively if any confirmation popups. You will receive a Profile(s) created message in the status bar at the bottom of the screen.

14. You may now leave the PFCG transaction. Return to Index... Granting Transaction Access to a User via Profile *** Since SAP R/3 4.5, this is not the standard for user authorizations. *** Return to Index... Granting Transaction Access to a User via Role 1. Log on to the applicable SAP instance and client. 2. Go to transaction SU01. 3. On the User Maintenance: Initial Screen screen, fill in the User ID for the user you want to change, either by typing it in or choosing it from the drop down. Click the little yellow pencil Change button. 4. On the Maintain User screen, click on the Roles tab. Fill in the new role in the first available Role field. Press ENTER to confirm that the role exists. Click the Save button. 5. Make sure to use transaction PFCG to run a user comparion to rebuilt the role-to-user connections. 6. You may now leave the PFCG transaction. Return to Index... Revoking Authorizations from a User via Profile *** Since SAP R/3 4.5, this is not the standard for user authorizations. *** Return to Index... Revoking Authorizations from a User via Role Use the same procedure as Adding Authorization Objects and/or Authorizations to a Role Return to Index... Revoking Transaction Access from a User via Profile *** Remember that profiles are NOT the standard way to implement SAP security. *** Return to Index... This document is the intellectual property of Jo Spencer and may not be edited without permission. Attaching a Profile to a User *** Since SAP R/3 4.5, this is not the standard for user authorizations. *** Return to Index... Attaching a Role to a User 1. Log on to the applicable SAP instance and client. 2. Go to transaction SU01. 3. On the User Maintenance: Initial Screen screen, fill in the User ID for the user you want to change, either by typing it in or choosing it from the drop down. Click the little yellow pencil Change button. 4. On the Maintain User screen, click on the Roles tab. Fill in the new role in the first available Role field. Press ENTER to confirm that the role exists. Click the Save button. 5. Make sure to use transaction PFCG to run a user comparion to rebuilt the role-to-user connections. 6. You may now leave the PFCG transaction. SAP BASIS Support Package Interview Questions In order to apply new support packages and kernel patches to a SAP system, several preparation steps are required: Checking for new SPAM updates, support packages and kernel patches Downloading the new SPAM updates, support packages, and kernel patches Preparing the new SPAM updates, support packages, and kernel patches for application Applying the new SPAM updates, support packages, and kernel patches Mass recompiling all programs used in patched components Be aware that SPAM/SAINT update and support package application occurs within the SAP system using the SPAM transaction. These corrections are changes to ABAP program code and must be handled in a special way by SAP. Kernel patches, on the other hand, are fixes to SAP executables found on the SAP server. Kernel patches must be applied when the SAP instance is down. Please refer to the Check for New SPAM Updates, Support Packages and Kernel Patches. Return to Index... Checking for New SPAM Updates, Support Packages and Kernel Patches To check if SAP has released any new software fixes for your release of SAP, you need to know your current support package and kernel release levels. The patching process consists of: - finding you current patch levels - finding what patches you should be applying - downloading the patches

- unCARing the patches - loading the patches into the patching EPS queue - applying the patches Return to Index... Find your Current SPAM Update and Support Package Level Method One: 1. Log on to your SAP instance, any client. 2. On any SAP screen, click System -> Status 3. On the System: Status popup, click the Component Information button. 4. On the System: Component Information popup, you will see the support package level for each component installed in your current SAP instance. Method Two: 1. Log on your SAP instance, any client. 2. Go to transaction SPAM. 3. On the Support Package Manager screen, turn on the radion button beside the Imported Support Packages in the Directory section of the screen, and then click Display button. 4. On the OCS Package Directory: Imported Packages screen, you will see a list of all SAP Support Packages imported into your current SAP instance. Return to Index... Find your Current Kernel Patch Level Method One: 1. Log on to your SAP instance, any client. 2. Go to transaction SM51. 3. On the SAP Servers screen, click on the server for which you need the information and then click on the Release Notes button. 4. On the SAP Release Information from Server screen, look down the SAP R/3 Kernel information section until you find Kernel Patch number. To the right, you will find the current patch level of your current SAP instance. Method Two: 1. Log on to the SAP instance sever using a Telnet session as user <sid>adm. 2. Change the Telnet windows properties to use a Screen Buffer Size of 9999. 3. At the Linux prompt, type: disp+work v and press ENTER. 4. Scroll back up the listing to where you entered the command in step c. 5. Scroll down the listing untill you find a line beginning patch number. To the right is the patch number for the SAP instance hosted on this server. Return to Index... Find the Most Current SAP Support Packages It should be noted here that sometimes an older SAP may run on a newer SAP Basis level. For example, CRM 4.0 has a Basis level of a 6.20 instance but runs on a 6.40 kernel. So make sure that the kernel patches you download match the SAP R/3 Kernel located via SM51. 1. Log on to the SAP Marketplace using an OSS ID with Administration rights http://service.sap.com/patches. This document is the intellectual property of Jo Spencer and may not be edited without permission. 2. In the navigator tree on the right-hand side of the My Application Components screen. For example, to find new patches for CRM Basis expand as follows: Support Packages and Patches My Companys Application Components SAP CRM SAP CRM 4.0 Entry by Component CRM Server SAP BASIS 6.20 3. Scroll down the Download screen until you find your current package level. Any support packages after your current level will need to be applied to your SAP System. 4. You may now leave the SAP Marketplace. Return to Index... Find the Most Current SAP SPAM Update 1. Log on to the SAP Marketplace using an OSS ID with Administration rights http://service.sap.com/patches. 2. In the navigator tree on the right-hand side of the My Application Components screen. For example, to find

new patches for SPAM/SAINT for CRM 6.20 expand as follows: Support Packages and Patches My Companys Application Components SAP SPAM/SAINT UPDATE SPAM/SAINT UPDATE 6.20 SPAM/SAINT UPDATE 6.20 3. Click the Download tab of the SPAM/SAINT UPDATE screen. Find the SPAM/SAINT Update Version XXX value. If this SPAM version is higher than you current SPAM version, you will need to download and apply the latest SPAM update. 4. You may leave the SAP Marketplace. Return to Index... Find the Most Current SAP Kernel Patches 1. Log on to the SAP Marketplace using an OSS ID with Administration rights http://service.sap.com/patches. 2. In the navigator tree on the right-hand side of the My Application Components screen. For example, to find new patches for CRM 4.0 expand as follows: Support Packages and Patches My Companys Application Components SAP KERNEL 32-BIT SAP KERNEL 6.40 32-BIT Linux on IA32 32bit ORACLE & #Database independent 3. Scroll down the Download screen until under the File Name column you find SAPEXEDB*.SAR files. Unless SAP has instructer you to use a different This document is the intellectual property of Jo Spencer and may not be edited without permission. kernel, the most recent SAPEXEDB*.SAR is the one you need to download. You may leave the SAP Marketplace. 4. Now go to the @Database independent section in the same list as ORACLE was displayed. Scroll down the page until you find the SAPEXE*.SAR that matches the same number as the SAPEXEDB*.SAR you found in the previous step. These two files will give you a complete kernel replace. 5. You may leave the SAP Marketplace. Return to Index... Download SPAM/SAINT Updates 1. Log on to the SAP Marketplace using an OSS ID with Administration rights http://service.sap.com/patches. 2. In the navigator tree on the right-hand side of the My Application Components screen. For example, to find new patches for SPAM/SAINT for CRM 6.20 expand as follows: Support Packages and Patches My Companys Application Components SAP SPAM/SAINT UPDATE SPAM/SAINT UPDATE 6.20 SPAM/SAINT UPDATE 6.20 3. To download a SPAM/SAINT update, click on the SPAM/SAINT Update Title hyperlink. Click the Download button. On the File Download popup, click the Save button. On the Save As popup, select a location to store the SPAM/SAINT update and click the Save button. Alternatively, you may add the patch to your SAP Download Manager and download all patches in one batch group. 4. Once you have downloaded your SPAM/SAINT updates, you may leave the SAP Marketplace. Return to Index... Download SAP Support Packages 1. Log on to the SAP Marketplace using an OSS ID with Administration rights http://service.sap.com/patches. 2. In the navigator tree on the right-hand side of the My Application Components screen. For example, to find new patches for CRM Basis expand as follows: Support Packages and Patches My Companys Application Components SAP CRM SAP CRM 4.0 Entry by Component CRM Server SAP BASIS 6.20 3. To download a support package, click on the package Title hyperlink. Click the Download button. On the File Download popup, click the Save button. On the Save As popup, select a location to store the support package and click the Save button. Alternatively, you may add the patch to your SAP Download Manager and

download all patches in one batch group. 4. Once you have downloaded as many support packages as you need to apply, you may leave the SAP Marketplace. This document is the intellectual property of Jo Spencer and may not be edited without permission. Return to Index... Download SAP Kernel Patches 1. Log on to the SAP Marketplace using an OSS ID with Administration rights http://service.sap.com/patches. 2. In the navigator tree on the right-hand side of the My Application Components screen. For example, to find new kernel patches for CRM 4.0 expand as follows: Support Packages and Patches My Companys Application Components SAP KERNEL 32-BIT SAP KERNEL 6.40 32-BIT Linux on IA32 32bit ORACLE 3. To download a kernel patch, click on the SAPEXEDB_<version>.SAR hyperlink. Click the Download button. On the File Download popup, click the Save button. On the Save As popup, select a location to store the kernel patch and click the Save button. Alternatively, you may add the patch to your SAP Download Manager and download all patches in one batch group. 4. Now backup a step and instead of clicking ORACLE, click #Database independent. The full path would look like this: Support Packages and Patches My Companys Application Components SAP KERNEL 32-BIT SAP KERNEL 6.40 32-BIT Linux on IA32 32bit #Database independent 5. This produces a list of database independent kernel patches. Scroll down the Download screen until under the File Name column you find SAPEXE_<version>.SAR. Use the same instructions in step 5 to download the patch. Make sure that the version number of your database independent files matches the version number of your MS SQL Server dependent file. 6. Once you have downloaded the kernel patch, you may leave the SAP Marketplace. Return to Index... Download Other SAP Binary Patches Unlike SPAM/SAINT updates, support packages, and kernel patches, the storage location for other SAP binary patches can be either SAP Marketplace or sapserv1. SAP Marketplace is the normal respository but if you cant find your patch there, go look on sapserv1. ***Due to the shutdown of the sapserv1x servers in April, this section has been discontinued. Everything should now to accessible via SAP Marketplace.*** Return to Index... Prepare a SPAM/SAINT Update or Support Package for Application Once you have downloaded your SPAM/SAINT Update and/or support package(s), they must be moved to the appropriate transport directory and uncompressed. This document is the intellectual property of Jo Spencer and may not be edited without permission. 1. For a SAP instance, move the downloaded K*.?AR file to the /usr/sap/trans/tmp directory on the SAP Transport Domain Server which is normally the DEV server of a SAP Flavor. 2. Log on to the appropriate server as <sid>adm. 3. Type the following: cd /usr/sap/trans SAPCAR.EXE -xvf tmp\*.?AR This will unCAR all CAR and SAR files in the \usr\sap\trans\tmp directory to the /usr/sap/trans/EPS/in. 4. Log off the server. 5. Log on client 000 of the appropriate SAP system. 6. Go to transaction SPAM. 7. From the menu bar of the Support Package Manager screen, click Support Package Load Packages From application server. 8. On the SPAM: Confirm upload popup, click the green picture-icon. The progress of the support package loads will show in the status bar at the bottom of the screen. 9. Scroll down the SPAM: Uploading Packages from the file system screen to make sure your SPAM/SAINT update is listed. Use the Go Back icon to return to the previous screen. 10. You may now leave the SPAM transaction.

Return to Index... Prepare a Kernel Patch for Application Kernel patches must be applied on the SAP server. The SAP instance must be down before a kernel patch can be applied. 1. Logon the server to be patched as <sid>adm. 2. The downloaded SAPEXE*.SAR and SAPEXEDB.SAR files must be uncompressed using SAPCAR.EXE. You can place the SAPEXE*.SAR files in any directory and use the SAPCAR.EXE xvf *.?AR to unCAR the files. 3. You may now leave the server. Return to Index... Prepare other SAP Binary Patches for Application Use the same procedure as Preparing a Kernel Patch for Application. Return to Index... Application of SPAM/SAINT Updates Before you apply the most current SPAM/SAINT, please pull the OSS Note 484219 - Known problems with transaction SAINT in Basis Release 6.20 or for whatever version you are using and review any problems you may have adding the SPAM/SAINT patch. Once you have loaded the latest SPAM/SAINT update into your support Package manager buffer, you need to apply the update to your SAP system. 1. Log on client 000 of the appropriate SAP system. This document is the intellectual property of Jo Spencer and may not be edited without permission. 2. Go to the SPAM transaction. 3. From the menu bar of the Support Package Manager screen, click Support Package Import SPAM/SAINT update. Click the green picture-icon to continue. 4. The progress of the SPAM/SAINT update application will be displayed in the status bar at the bottom of the screen. These messages look very similar to the messages generated during a change request transport. 5. When the Restart SPAM popup appears, click the green picture-icon to leave the SPAM transaction. 6. Go to the SPAM transaction. You may notice programs compiling in the status bar at the bottom of the screen. This is normal. 7. Once you are again on the Support Package Manager screen, verify that the SPAM status in the Status section of the screen contains a green light. 8. You may now leave the SPAM transaction. Return to Index... Application of SAP Support Packages Before applying any support packages to your SAP system, release all repair change requests to prevent error messages due to locked resources. Repairs are usually advanced corrections obtained from SAP Notes that are eventually accumulated into support packages. So the same objects repaired in the advanced corrections will be repaired during the application of the support package. Releasing the repair change requests allows the support package to overlay the temporary advanced correction fix. Before you apply the most current SPAM/SAINT, please pull the OSS Note 782140 - OCS: Known problems with Support Packages in Basis Rel.6.20 or for whatever version you are using and review any problems you may have adding the SPAM/SAINT patch. Once you have loaded the latest support packages into your support Package manager buffer, you need to apply the packages to your SAP system. 1. Log on client 000 of the appropriate SAP system using a adminitrator user ID that is not DDIC or SAP*. 2. Go to the SPAM transaction. 3. On the Support Package Manager screen, click the Display/Define button to build your import queue. On the Component Selection popup, click on the Comp. ID having support packages you want to install. The component order support packages should be applied is SAP_BASIS, SAP_ABA, SAP_APPL, and PI. 4. A list of all application support packages for the selected component will appear in the Define Queue popup. Select the support packages you want to apply. See SAP Note 782140 for information on restrictions to grouping support packages into queues. The Package ID with the green to the left is the highest support package to be placed in the queue. All lower number support packages for this component will be applied as well. Click the green picture-icon to confirm the queue. 5. From the menu bar of the Support Package Manager screen, click Support Package Import queue. 6. On the SPAM: Import Queue popup, read the displayed information and then click the green picture-icon to continue. 7. The progress of the support package application will be displayed in the status bar at the bottom of the screen. These messages look very similar to the messages generated during a change request transport. This document is the intellectual property of Jo Spencer and may not be edited without permission. 8. When the Imported successfully Information popup displays, click the green picture-icon to continue. 9. On the Support Package Manager screen, verify that the SPAM status in the Status section of the screen

contains a yellow light and the Next action value is Confirm queue. To confirm that your support packages applied completely, click the green picture-icon. A Support Package queue was confirmed message will appear in the status bar at the bottom of the screen. 10. You are ready to build another support package queue, or if you have applied all the necessary support packages, you may now leave the SPAM transaction. Return to Index... Application of SAP Kernel Patches *** It is recommended that the /usr/sap/<SID>/SYS/exe/run directory be copied to /usr/sap/<SID>/SYS/exe/backup_run before replacing the kernel *** 1. Log on to the appropriate server as <sid>adm. 2. Double check that the SAP instance, SAPOSCOL, and SAP<SID>_00 services are stopped. 3. To apply the new kernel patch to a R/3 instance, copy the new files into usr\sap\<SID>\SYS\exe\run directory. If prompted for overwrites, say yes to all. 4. After the new kernel has been copied make sure that the following file ownerships are correct: All files in /usr/sap/<SID>/SYS/exe/run <sid>adm /usr/sap/<SID>/SYS/exe/run/saposcol root /usr/sap/<SID>/SYS/exe/run/br* ora<sid> /usr/sap/<SID>/SYS/exe/run/sapdba ora<sid> 5. After the successful completion of the kernel patch, you may bring the instance back up and log off the server. Return to Index... Application of other SAP Binary Patches Use the same procedure as Application of SAP Kernel Patches. SAP BASIS System Interview Questions Creating System Parameters 6. Log on to any client in the appropriate SAP system. 7. Go to transaction RZ10. 8. On the Edit Profiles screen, select the <SID>_DVEBMGS00_SAP<SID> 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. 9. On the Maintain R/3 Profile screen, click the Add Parameter button. 10. On the next Maintain R/3 Profile screen, type in the new Parameter name and Parameter val. Click the Copy button. Click the white arrow on green picture-icon twice. 11. On the Maintain R/3 Profile popup, click the Yes button to save your changes. 12. On the Edit Profiles screen, click the Save picture-icon. 13. On the Save profile popup, click the No button. 14. On the Activate profile popup, click the Yes button. 15. On the Edit Profiles popup, click the green button. 16. On the Caution! Caution! Caution! popup, click the green button. 17. If you receive a Possible Inconsistencies in OP Modes screen, double click over the <No> unless you are unsure of why this message has been displayed. 18. You will not get a confirmation message. You may now leave the RZ10 transaction. Return to Index... Modifying System Parameters 1. Log on to any client in the appropriate SAP system. 2. Go to transaction RZ10. This document is the intellectual property of Jo Spencer and may not be edited without permission. 3. On the Edit Profiles screen, select the <SID>_DVEBMGS00_SAP<SID> 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. 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 under Parameter 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 <No> unless you are unsure of why this message has been displayed. 11. You will not get a confirmation message. You may now leave the RZ10 transaction.

Return to Index... Deleting System Parameters 1. Log on to any client in the appropriate SAP system. 2. Go to transaction RZ10. 3. On the Edit Profiles screen, select the <SID>_DVEBMGS00_SAP<SID> 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. 4. On the Maintain R/3 Profile screen, locate the parameter you need to delete and click on the Parameter name to high-bright it. On the top-most menu bar, click Parameter Delete. 5. On the next Maintain R/3 Profile popup, make sure that the parameter listed is the one you need to delete. Click the Yes button to delete the parameter. You will receive a Parameter was deleted message in the status bar at the bottom of the screen. Click the Copy button. 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 <No> unless you are unsure of why this message has been displayed. 12. You may now leave the RZ10 transaction. Return to Index... Overview of All Work Processes Running on a SAP System 1. Log on to any client in the appropriate SAP system. 2. Go to transaction SM50. 3. On the Process Overview screen, all processing threads for the SAP system are displayed. If a thread is being used, the name of the report running will be displayed as well as the number of seconds that the report has been running, the client in which the report is running, the action the report is currently doing, and, if applicable, the table the report is currently accessing. This document is the intellectual property of Jo Spencer and may not be edited without permission. 4. Click on the blue arrow circle picture-icon to refresh the process data appearing on the screen. 5. Click the white clock picture-icon to display the amount of CPU time consumed by each process thread so far. 6. Double click any display line containing a report name in order to see more detailed information about the running report. This information includes database access statistics and timings. Use the white arrow on green picture-icon to go back to the Process Overview screen. 7. Click on any process thread and then click the blue cylinder with glasses picture-icon. This will display the Trace Data screen which shows the actual communication between SAP, the operating system, and the database server. This information is useful when tracking process thread problems. Use the white arrow on green picture-icon to go back to the Process Overview screen. 8. You may now leave the SM50 transaction. Return to Index... Stopping Run-Away or Bad Work Processes 1. Log on to any client in the appropriate SAP system. 2. Go to transaction SM50. 3. On the Process Overview screen, find the process which must be stopped. Place a in the to the left of the process number to be stopped by pressing Space. On the top-most menu bar, click the Process Cancel without core. 4. Click the blue arrow circle picture-icon to refresh the Process Overview screen until the stopped process has cleared from the display. 4. You may now leave the SM50 transaction. If this does not kill the process, you can go to transaction SM04 and kill the users session. If this does not kill the process, you can log on to the server, open a Task Manager session, and End the Process. If this does not kill the session, there is an executable in the RUN directory on the server called sapntkill.exe. Run it providing the process ID number. If none of the above work, you have no choice but to bounce the SAP instance and/or possibly the serve. Return to Index... 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 <SID>_DVEBMGS00_SAP<SID> 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_dia line 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. This document is the intellectual property of Jo Spencer and may not be edited without permission. 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 <No> 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

SAP BASIS Transport Interview Questions Configuring TMS - Transport Management System - for the First Time Note: if you already have a TMS configured, do not use this section to add a new instance to the existing TMS configuration. You could severely damage any pre-existing transports, making them untransportable. Instead, use the following section Adding New Instance to TMS Setup. 1. Log on to client 000 of the SAP instance to serve as the Domain Controller. 2. Go to transaction SE06. 3. Click on the Perform Post Installation Actions button. 4. Go to transaction STMS. 5. You should see a popup box with the title TMS: Configure Transport Domain. If the popup doesn't say that, press F6 to change to the correct popup box. 6. Fill in the TMS: Configure Transport Domain popup with the Description, Name of DOMAIN_<SID>, and the description of the Transport Domain. Then click Save. 7. On the Transport Management System screen (if you arent there, back out until you are), assuming that this is the first SAP instance and there are no other installed SAP instances in your landscape yet, and assuming that you want your transport requests to be transportable and not local only, click on Overview Systems. 8. On the System Overview Domain Domain_<SID> screen, click SAP System Create External System. Fill in QAS if you are going to have a three system configuration or PRD if you are going to have a two system configuration, or make up a <SID> if you are never really going to have another SAP system. Fill in the rest of the information including the Path which is assumed to be \\<current server>:\usr\sap\trans for NT or /usr/sap/trans for UNIX. Click Environment Transport Routes. 9. On the Display Transport Routes screen, click the User Settings button, turn on the Hiergraphical List Editor, and click the Continue button. Back out This document is the intellectual property of Jo Spencer and may not be edited without permission. of the screen and then go back in you should see the list in a text mode which makes it easier to handle. 10. On the Display Transport Routes screen, click the Display<>Change button to toggle into Change Mode. 11. On the Change Transport Routes screen, click Configuration Standard Configuration Development and Production System. 12. Fill in the Development and Production System popup, using your current SAP system SID as the Development system and the SAP instance you created in step #8 as the Production system. Click the mark to Continue. 13. Back on the Change Transport Routes screen, click the Save icon and confirm all the popup questions. 14. On the Change Transport Routes screen, back out until you can once more see the Transport Management System screen. Click Overview Systems. 15. On the Display TMS Configuration: System XXX screen, double-click the TMS Domain domain controller SAP instance. 16. On the Display TMS Configuration: System XXX screen, click the Display<>Change button to toggle into Change Mode. Click the Communication tab and make sure that the Transport Group Name is correct. It should contain of the Domain Controller in the format of DOMAIN_<SID> where <SID> is the System ID of the SAP Domain controller. Use the dropdown to find the correct entry it the field is blank. Click the Transport Tool tab. Verify that the information on the tab is correct and click the Insert

Row button. Add a Parameter of CTC and a Value of 1. Click the Save button. 17. Do step #16 for every system in your TMS Domain, making sure to change all Transport Group Names are the same and the CTC row is added to each with a value of 1. 18. Save your way back the the main STMS screen. 19. You may now leave STMS. Return to Index... Adding a New SAP Instance to an Existing TMS Domain Controller 1. Log on to client 000 in the SAP instance you want to add to the existing TMS Domain. 2. Go to transaction SE06. 3. Click on the Perform Post Installation Actions button. 4. Go to transaction STMS. 5. You should see a popup box with the title TMS: Configure Transport Domain. Press F6 until you see a TMS: Include System in Transport Domain popup. 6. Fill in the TMS: Include System in Transport Domain popup with the Description, Target Host, and System number of the TMS Domain Controller then click Save. 7. You should see a message that says SAP System waiting to be included in the Transport Domain. 8. on to client 000 of the Transport Domain Controller and go to transaction Log STMS, keeping your original session in the other SAP instance open. 9. On the Transport Management System screen, click Overview Systems. Highlight the System you just added and then click SAP System Approve. Then confirm all the messages. 10. Back on the Transport Management System screen, click Environment Transport Routes. 11. On the Display Transport Routes screen, click the Display<>Change button to toggle into Change Mode. Click on Edit Transport Route Create. 11. On the Create Transport Route popup, use the Consolidation boxes to enter the SID of the transport domain, create a Z* transport layer, and the SID This document is the intellectual property of Jo Spencer and may not be edited without permission. of the system you are adding. Click Save and confirm. Back out to the main Transport Management Screen. 12. Back on the Transport Management System screen, click Overview Systems. Double-click on the new system, and click on the Communications tab. Make sure that the Transport Group name is the name of the original transport domain. If not, change it. Click the Transport Tool tab. Verify that the information on the tab is correct and click the Insert Row button. Add a Parameter of CTC and a Value of 1. Click the Save button. 13. You can switch back to the new instance, and confirm that the SAP System waiting to be included in the Transport Domain has disappeard. 14. You may now log out of both SAP instances. Return to Index... Make a Local Transport into a Transportable Transport Sometimes, mistakes just happen. For this example, we will use a transport SM1K00047 as the erroneous change request. Make sure to release SM1K00047 before beginning this procedure. 1. Log on to the client who is the owner of the local transports that needs fixed. 2. Go to SE03. 3. On the Transport Organizer List screen, click on Merge Object Lists which is in the Requests/Tasks section. 3. On the Merge Objects List screen, put SM1K00046 in the first Request/Task field. Make sure that the Released check box is "on" in the Request Status section and click the Execute icon. 4. On the Merge Objects List screen, click on the Merge icon. 5. On the Enter Transport Request popup, click the Create Request icon. 6. On the Select Request Type popup, click "on" radio buttion Workbench Request. 7. On the Create Request popup, fill in the necessary information and make sure that the fill in the Target field so that the transport request is NOT local. Click the Save, OK, icon, etc. until everything is done. You will get a new transport request number, in our case SM1K00050. This new request can be released using one of the transport organizer Transactions like SE10,

etc. Once it is released, you can go to /usr/sap/trans on the OS level and in directory cofiles copy K00050.SM1 to K00046.SM1, and in directory data copy R00050.SM1 to R00046.SM1. 8. You may now leave SE03. Once you have control of your session again, the transports are done. Verify their return code in the Import Queue list. It shoud have been updated automatically. Return to Index... Transporting Change Requests To manually transport change requests from DEV/QAS to PRD: 1. Make sure the change request(s) has been released via Se10 or one of the other Transport Organizer Transactions. 2. Go to transaction STMS and click Overview Imports. Double-click the PRD queue. 3. Click the refresh button to make sure you have the most current view of the PRD queue. Make sure the change request(s) you want to transport shows in the queue. This document is the intellectual property of Jo Spencer and may not be edited without permission. 4. Using the F9 button, highlight all the transactions you want to manually transport. 5. Click on Extras Activate Inactive Requests. Confirm the popup. This bypasses the STMS_QA process. 6. Leave the change requests highlighted. Click Request Import. On the popup, make sure that the target is client 300. Make sure that Synchronous radio button is "on" in the Execution tab. Make sure that the first three options are checked "on" in the Options tab. When you are done, click on the green and confirm the next popup. Once you have control of your session again, the transports are done. Verify their return code in the Import Queue list. It shoud have been updated automatically. Return to Index... Adding a Change Request to a Transport Queue 1. Make sure the change request(s) has been released via Se10 or one of the other Transport Organizer Transactions. 2. Go to transaction STMS and click Overview Imports. Double-click the PRD queue. 3. Click on Extras Other Requests Add. Fill in the Number of the Transport Request to be added to the queue and then press Enter. 4. Confirm the Add Transport Request popup. The transport request should now appear at the bottom of the queue list. Return to Index... Viewing the Transport Queue History 1. Go to transaction STMS and click Overview Imports. Double-click the queue for which you want to view the history. 2. Click on the Import History button or press Ctrl+F7. The resulting list can be sorted and filtered to produce a more exacting report if needed. Return to Index... Re-Transport Several Change Requests at Once 1. Go to transaction STMS and click Overview Imports. Highlight the queue into which the transport(s) to be moved again were originally transported the FROM queue - and click the Import History button or press Ctrl+F7. 2. If your SAP instance is older, you may have a very long Import History list in the next screen. Use some of the available filters and sort options to create a more controllable list of transports. Use the F9 to select and/or unselect as many as you need to transport. 3. Once all choices have been made, click Request Forward System. Fill in the TO system and click on the Execute green mark. 4. Now you can go to the TO queue and refresh the list. Your imports should all be there. Return to Index... Transport Tool System Confirmation This document is the intellectual property of Jo Spencer and may not be edited without permission. 1. Go to transaction STMS and click Overview Imports. 2. On the Import Overview screen, click Import Queue Check Transport Tool. You

may get a message asking if you want to check the the transport tool for all systems. If only want to check a limited subset of the SAP instances, use F9 to select and/or deselect those systems before you click Transport Tool. 3. On the TMS: Check Transport Tool screen, a list of all selected SAP instances to be checked will appear. If you see any thing but red green Oks, expand all the lines with the non-OK marks and look for more information. Correct these problems and then run this report again until it comes back clean. Return to Index... Use Target Groups to Transport to Mulitple Clients in Two Different Instances 1. Log on to client 000 of your TMS Domain Controller SAP Instance. 2. Go to transaction STMS. 3. On the Transport System Management screen, click Overview -> Transport Routes. 4. On the Display Transport Routes screen, click the Display<>Change button to toggle into Change mode. Click on the Target Groups line and click the Create button. 5. In the Create Transport Group popup, fill in the Target Group as /XXXCLNTS/, give a Short Description and click the Client Assignment button. Be aware that the Target Group name must start and end with a /. 6. Enter each Target system and Target client you need. For our example, we will DEV 100, QAS 200, and QAS 210. Click the green check mark to Transfer. You now have a target group. Now you must create a Consolidation Layer. 7. Back on the Change Transport Routes screen, click on Transport Routes and click Create. 8. In the Create Transport Route popup, click the Extended Transport Control button at the bottom of the popup. Make sure Consolidation is "on" and fill in the information using our Target Group as the Consolidation Target. 9. Click the green check button to Save the change. 10. You now have a Transport Group. Confirm the Disturbution of it to the other SAP Instances. Return to Index... Configure TMS to Use SAP's Quality Assurance Functionality A Quality Assurance system must have a) a delivery route leading from it to another instance, and b) be the target of a consolidation route. See topic Using Target Groups to Transport to Mulitple Clients in Two Different Instances to fulfill the a) requirement. 1. Log on to client 000 of your TMS Domain Controller SAP Instance. 2. Go to transaction STMS. 3. On the Transport System Management screen, click Overview -> Transport Routes. 4. On the Display Transport Routes screen, click Display<>Change button to toggle into change mode. Click on the instance in which you want to control QA. Normally, this is QAS and the instance to be controlled is PRD. Under Transport Routes, click on the QAS instance and click Create. 5. On the Create Transport Route screen, make sure Delivery is "on" and fill in Source and Delivery systems with QAS and PRD. Click the green check mark to save. Now you have met condition a. 6. Back on the Change Transport Routes screen, click on the QAS instance and click the single pencil Change button. You will see a Change System This document is the intellectual property of Jo Spencer and may not be edited without permission. Attributes popup. Click "on" Quality Assurance - Delvery After Confirmation. If you want to change the people who OK the transports, click the Procedure button and make your changes. Then back out. Click the green check to Transfer your changes. 7. Back on the Change Transport Routes screen, click on the Target Groups line and click the Create button. 8. In the Create Transport Group popup, fill in the Target Group as /XXXCLNTS/, give a Short Description and click the Client Assignment button. Be aware that the Target Group name must start and end with a /. Enter each Target

system and Target client you need. Click the green check mark to Transfer. You now have a target group. Now you must create a Consolidation Layer. 9. Back on the Change Transport Routes screen, click on Transport Routes and click Create. 10. In the Create Transport Route popup, click the Extended Transport Control button at the bottom of the popup. Make sure Consolidation is "on" and fill in the information using our Target Group as the Consolidation Target. Click the green check button to Save the change. 11. You now have a Transport Group. Confirm the Disturbution of it to the other SAP Instances. 12. You may now leave the STMS transactions. Return to Index... Automate the Transport Process 1. Log on to client 000 of your TMS Domain Controller SAP Instance. 2. Go to transaction STMS. 3. On the Transport System Management screen, click Overview -> Imports. Double-click on the queue for the SAP instance are in. 4. On the Import Queue screen, click the Refresh button. Click on the Import All Requests button. 5. On the Start Import popup, fill in the information for the job. Make sure "At Start Time" is on. Although Period appears grayed out, you can still change it to the periodic value you need. I recommend every hour in DEV, 4 times a day in QAS, and once an evening in PRD. Click on the green check mark to Continue. 6. You may now leave tSTMS transaction. If you ever need to change this job, he you must do it via STMS and not SE37.
SAP BASIS Web And Internet Interview Questions

The IGS server (Internet Graphics Server) component displays and generates the graphics used by SAPGui HTML users. For example, the BW users accessing reports via the internet use the IGS server. The ITS server also channels graphics through the IGS server. The IGS server is installed as a started service on each server. Starting the IGS instance 1. Log on to the appropriate server as <sid>adm. 2. Type the following: cd /usr/sap/<SID>/DVEBMGS00/igs ./bin/startigs -p . 3. You may log off the server. Stopping the IGS instance 4. Log on to the appropriate server as <sid>adm. 5. Type the following: cd /usr/sap/<SID>/DVEBMGS00/igs ./bin/stopigs 6. You may log off the server.

Interview Questions for SAP Basis 1 Ask him/her to describe how SAP handles Memory Management? ST02 / ST03 In general via table buffers, you could go into the whole Work Process, roll in, roll out, heap (private) memory, etc. however just as a Unix or DBA admin would know, is you look this up when needed for the exact specifics. Ask him/her to describe where they would look at the buffer statistics, and what steps they would use to adjust them? ST02, RZ10 Ask him/her to describe how to setup a printer in SAP or where they would look to research why a user/users can not print? SPAD, SP01, SM50, SU01 Keep the interview to 3 general areas:

DB (what is the directory structure/ where are the files kept oracle alerts, init.ora, redo logs, archive logs, etc.; possibly some basics stuff like what to do "high level" when the archive directory fills up, etc. Keep this minimal as from a SAP basis admin point of view Oracle is just a big giant bit bucket and SAP can handle to the daily monitoring and maintenance itself. OS (what is the directory structure (what is NFS mounted and why / where are the message files contained for the OS error log; basic commands for the OS eg. Unix, mv, cp, ls, grep, ps-ef, df-k, etc. That is pretty much all the SAP basis admin will need to know. Client/Server architecture. SAP (what is the directory structure / where are files located ie. profiles - start, instance, default (what are they and what is the order of precendence) start is for statup only, instance is the first to be read then the default and if a given parameter cannot be found in the instance or then the default then the internal standard is taken from RZ10 setting. You can ask them to ran Transaction codes to you. Menus constanly change so go with T-codes. He should have a good knowledge of the following areas; transports, user / print / spool / batch management, monitoring, client tools and copies, support packages, kernel patches, workload analysis, Roles and Security, etc. The standard list of t-codes is pretty much SM50, SM51, SM66, SM12, SM13, SM21, DB01, DB02, DB13, ST01, ST02, ST03, ST04, ST05, ST06, SU01, SUIM, PFCG, SCC4, SE01, SE09, SE10, SPAM, SM35, SM36, SM37, SPAD, SP01 SCC3, SCCL, SCC9 this are pretty much you heavy hitters for monitoring and support. I would ask in general how he would troubleshoot the following: - User cannot connect to SAP check SAP logon settings, ping the host, check message server, check dispatcher, etc. - User cannot print check SAP user setup, check SPAD, check spools, check unix queue or print queue at the os level, etc - System seems slow check SM66, SM51, SM50, SM21, ST06, ST03, SMLG, AL08 etc. Some important things to remember is to ask not get specific to your installation or specific system setup as all SAP instances are different, keep your question to general topics and general answers. The most important thing to notice when choosing a candidate is not how they parrot back answers to you, but if they can a) think for themselves and b) they actually like to and will keep on learning as no one knows it all and c) they have a good background and willingness to perform analyis and will keep on digginging until the answer is found or until their resources are exhausted and then they will pull in what is required to figure it out. What is short dump and what do you do with it? Short Dump is nothing but the abap dump which gets displayed when the error occurs. It gives us the log to rectify or fix the problem so that we can move forward in our process.When we see the short dump it gives us the complete solution also which is one of the possible solutions. So by seeing the log we can go to the particular as guided in that log and can fix the problem. How can I able to see that t_code in the user menu? I created a role with some t_code and I assigned it to the user. Then again I change the role with adding one more t_code. When I login to the user the user menu is showing only the first t_codes. It is not showing the later T-code which I added. But the t_code is working. Check the following: 1. Click on the 'Menu' tab and check for the t-codes assigned. 2. If you still find the old t-codes, remove them. 3. Add the new T-code. 4. Save the role. 5. Click on Authorizations Tab., and check S_TCODE. 6. Save and Generate. Than assign them to the user and perform "user comparision" and "complete comparision".

What are the different ways to find who has deleted the data in table? Today I got a complaint from functional team that all their material master data in MARA and all related tables such as MARC, MARD, MBEW got deleted. They want to know who has deleted the records and also tcode executed. I had executed tcode *stad* and gave list of transaction codes exeucted from last 24 hours. Still they are unable to find who has deleted the data. No entry in system log is available. Anyone, who's able to write ABAP programs, has full access to the database and thus can delete all the data. Additionally users with permission can use SE14 to delete table contents completely. It's hard to find out what happened, if not impossible :( How to improve system performance? If users have opened more sessions and no transaction is running and there are many users who have opened more that 2 sessions and left that as it is. How to control those idle sessions? You can control your users by changing the following in your System Profile parameter ( tcode RZ10). rdisp/max_alt_modes ---> controls the number of sessions a user can have at a time. rdisp/gui_auto_logout (optional) --->This is the time the system will wait in seconds for inactive users to automatically logoff in SAP

Configuring the Transport Domain Controller

Prerequisites
You have decided which system should be the Transport Domain Controller.

Procedure
To configure a system as the transport domain controller (and thereby configure a new transport domain): 1. Log on in client 000 in the SAP System that you want to configure as the transport domain controller. 2. Enter Transaction STMS. The dialog box TMS: Configure Transport Domain appears. (This dialog box only appears if you have not yet configured a transport domain.) 3. Enter the name and a short description of the transport domain. The name of the transport domain may not contain blank characters. You cannot change the name of the transport domain afterwards without reconfiguring the domain controller and thereby the entire transport domain. 4. If your SAP System consists of multiple application servers, you can choose one server for the TMS. 5. Save your entries. The following actions are performed automatically in your SAP System: o The user TMSADM is created. o The RFC destinations required for the TMS are generated. o The TMS configuration is stored in the transport directory. o The transport profile for the transport control program tp is generated. o The SAP System is configured as a single system.

Result
The configuration of the transport domain is now complete for this SAP System. The initial screen of Transaction STMS shows that this SAP System is now functioning as the domain controller of the transport domain.

Transport Layers and Transport Routes

All development projects developed in the same SAP System and transported on the same transport routes are grouped together to form a transport layer. Before you start the first development project, you create a transport layer in the TMS transport route editor. This transport layer is assigned to the development system as its standard transport layer. Objects delivered by SAP belong to the transport layer "SAP". Other transport layers are generally only needed when new development systems are included in the system group. After you have set up the transport layer you set up the transport routes. There are two types of transport routes. First you set up consolidation routes, and then you set up delivery routes: 1. Consolidation routes To make your changes transportable, set up a consolidation route for each transport layer. Specify your development system as the starting point (source) of these consolidation routes. Specify the quality assurance system as the transport target (in a two-system landscape, specify the production system as the transport target).

Any modified objects that have a consolidation route set up for their transport layer are included in transportable change requests. After the request has been released the objects can be imported into the consolidation system. If you make changes to objects which have no consolidation route defined for their transport layer, then the changes are made automatically in local change requests (or in Customizing requests without a transport target). You cannot transport them into other SAP Systems. You can set up one consolidation route only for each SAP System and transport layer. When you define consolidation routes, note the additional functions available when you use Extended Transport Control. 2. Delivery routes After you have imported your development work into the quality assurance system, you then want to transport it into your production system. You may even want to transport it into several SAP Systems (for example, additional training systems). To do this, you have to set up delivery routes. Delivery routes have a source system and a target system. When you set up a delivery route, you are making sure that all change requests that are imported into the routes source system are automatically flagged for import into the routes target system. You can set up several delivery routes with the same source system and different target systems (parallel forwarding). You can also set up delivery routes in sequence (multilevel forwarding). CTS transport control makes sure that all requests from the development system are flagged for import into all other SAP Systems in the same order in which they were exported. This is important, since different requests can contain the same Repository object or the same Customizing setting at different development levels, and you must avoid overwriting a more recent version with an older version.

Multilevel Delivery
Here you can activate multiple delivery routes in sequence. You can choose any SAP Systems in the system group as the source systems of the delivery routes; they do not have to be consolidation systems. This allows you to implement complex chains of transport routes.

Multilevel delivery is not required in a two- or three-system group. In more complex system landscapes, particularly in layered development projects that have each other as sources, multilevel delivery may prove to be a suitable solution:

If there are SAP Systems in the system group with releases prior to 4.0, you can only use multilevel delivery under particular conditions. The Transport Management System checks these conditions when you configure the transport routes in a mixed system group.

Use You define logon groups to determine how client requests to certain applications are load balanced when your system setup uses the SAP Web Dispatcher or a third-party

hardware load balancer in front of your application servers. For example, you can define a logon group so that a certain application (such as one with high CPU usage) is accessible only on two instances within your cluster, which are running on machines equipped with extra CPU resources. Features When you use logon groups for load balancing, then the logon group the application is requested with must be present in the request URL. It is presented next to the application alias of the requested application (separated by the zone separator symbol that is configured). The zone separator is configured in the HTTP Provider Service using the Visual Administrator as described in Configuring the Zone Separator.

The logon group definition consists of the following actions:

To request an application called TestApp within the test logon group (provided the default zone separator is used), you can use the following URL: http://<host>:<port>/TestApp~test/<application_resource>.

Activities You can display the overview page of the existing logon groups if you choose System Management Configuration Logon Groups. The Logon Groups frame on the right contains a table that lists all logon groups on all registered systems. If you select a logon group from the list, the configuration settings for it are displayed in the Details frame.

Definition of the instance IDs of the Java instances in the cluster where applications from this group are accessible. Definition of the application aliasesof the applications that are requested with the corresponding logon group.