This action might not be possible to undo. Are you sure you want to continue?
Central instance have message server and dialog, update, spool, enque, gateway, background work processes. Application server has only Dialog, update, spool, gateway and Background workprocess. Note: SAP server has only one message server and Enque 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 don’t 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?
2. . What is SAP NETWEAVER. It includes BI/XI/EP and different level of it’s configuration. PSAPSTABD/I. services and information. gets filled frequently and we add datafile to that? PSAPBTABD/I. SAP XI. BI: It is an OLAP (on line analytical processing). SAP BIW. based on your installation choices during software installation. What is difference between these? 1. Which table space. which provides a plate form to collect the data and user extract the data from BI or BW (older version) to analyze it 3. Q.The SAP Application Performance Standard (SAPS) is a hardware-independent unit that describes the performance of a system configuration in the SAP environment. SAP -XI: Exchange Infrastructure is used to establish a cross system connections between system by different vendors and versions 5. you can log in to EP using host name:port#/ <service name> and user name and password 4. PSCAPLUCD etc. Web AS: Web Application Server is the platform for ABAP and J2EE stacks in Netweaver. Q. EP: Enterprise portal provides web based secure access to all the application.Netweaver is a web based technology includes java. SAP WAS and SAP BI. SAPNW .
ST02: Check the buffering quality. Also refer to SAP Note 121625 in this context.SM21? 3. What is the utilization of the disks? How high is the paging in the base pool? . If paging occurs in a buffer. the corresponding parameter should be increased. What is the CPU utilization? → Goto → Current Data → Snapshot → Top CPU processes and display the main CPU consumers. Any signs of general problems in the System Log . it should deactivated it in normal operation. 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. 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 pictureicon.1. Is the total CPU for the last dialog process > 10 minutes? * ST04: Is the database monitor activated? If yes. What has changed since the performance is poor? * o System Parameter Changes (RZ10)? o Increase in the number of users? o Kernel patch? o Support Packages? o Linux and Oracle patches? o Hardware Changes? 2. * ST03: → Select a server → Today’s Workload: What are the response times? In the case of poor response times. To which extent are the hardware resources utilized? CallST06 at times with poor system performance.
6. 3. 2. 6. you should additionally note the following points: 1. What is considered “normal” response time? Performance Standards: Response time – 1 second (dialog). These tables are your “database hogs”. 4. ST05: If the database times are high. The sorted results shows the top tables when it comes to rows changes per month. you should generate an SQL trace of the affected transactions to find out whether the database access is carried out in a useful way. 1. 3. If only few transactions are affected by the performance problem. Click on the first number under the Rows – Chg/Month header and click the Sort button. SE30: Carry out a runtime analysis for the affected transactions. 5.4. Look for tables that have experienced unusual monthly growth. Check whether modifications were made in the affected or related transactions. 2. 4. < 1 second (update) . ST03: Display the corresponding performance records. DB02 → Space Statistics button Press Enter on the Tables and Indexes popup History → All objects off/on Click the Months button 5.
Database or index problems Load time Wait time – Buffer problems – 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.CPU time Wait time Load time – approx 40% of average response time – < 1% of average response 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 –. If your installaion was never able to . you know that the instance itself must be viable. and the installation completed 100% successfully. If this is a brand new SAP instance.
If your SAP instance has been up and running fine for a good while. the issue is probably due to lack of resources. dev_disp. The most useful information can be found in the dev_wx. then something has probably changed that makes it not come up. If you have a test searching tool. and stderrx files. dev_ms. 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. . dev_rfcx. look for “error” in all files with the suffix “. go to the /usr/sap/<SID>/DVEBMGS00/work directory and do the same thing in this directory. · · · 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 can’t 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.log”. Sort them with “ls – ltr” is see the list sorted in descending order for the ease of viewing. If nothing obvious is found.complete due to the instance not being able to start up.
. 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. 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. you could search for all words. and if you had no luck.05. you could make your next search a little less specifc. Moral of the story? Realize that some things just don’t translate correctly from language to language.please contact SAP” First. But sometimes things get lost in translation. and search accordingly. Since we speak English and we realize that the SAP product was designed and implemented in Germany. you should read the SAP Note even if it didn’t look as if it pertained 100%. like “brbackup No valid SAP license found”.anf 2004-02-27 00. If you get at least one hit. you could make it even less specific as in “brbackup SAP license error” or “SAP license error”. and attach the zipped file to it. Why? Because it might contain information leading to other notes that did pertain.42 BR602W No valid SAP license found . kernel. If you searched for “Panic! Panic! Panic!” and got no hits. And if that produced nothing tangible. you are applying support packages and get an import error with the following message “Panic! Panic! Panic! there’s no object header”.If all else fails. and the OS. or give you new ideas for more search terms to help narrow the scope of my query. zip the contains of the /usr/sap/<SID>/DVEBMGS00/work directory.”? 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. and anything else you might think useful. First you could search for the phrase. For example. patch level for SAP support packages. Lets use this error message as an example: ”BR051I BRBACKUP 6. Also provide them with the answers to the above questions as well as your current hardware and database platforms. If you didn’t find a note that matched the problem. open a problem with SAP. you should search the specific error message “BR602W No valid SAP license found”. you could try “warning message no object header”.10 (80) BR055I Start of database backup: bdmsqjbi. Normally a very specific query will get you the results you need.
and not least. or b) deleting and installing a newer version of SAPGui. There are certain notes that you pull over and over again due to some task that needs fresh. known problems with applying patches. These are mostly lists of supported printer devices. If a user seems to be experiencing SAPGui errors. etc. read and become familiar with your SAP Notes. Make sure that these lines were added to the services file on the user’s workstation: After you have successfully configured your SAPGui. several things need to be checked: · Is the operating system on the user’s 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 user’s workstation having resource problems? Is the user’s 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. current and precise information. add these three lines to the bottom of your \Windows\system32\drivers\etc\services file: .Last.
10.1. see SAP Note 26417 -SAP GUI Resources: Hardware and software. If you have never tested connectivity to a SAP instance on the workstation having the connection problem.11 3200¬ If the screen rolls and goes totally blank then your dispatcher is reachable. And. and hardware requirements for running SAPGui. Also. resource. the dispatcher is not reachable. first you need to make sure that the workstation can connect to the SAP server in some non-SAPGui way.10. Also. 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. or the SM59 RFC connection to was changed and is no longer working.1. something in the RFC setup has changed.sapdp00 sapmsR3I # 3200/tcp 3600/tcp If you have SAP Instances using System Numbers other than 00.1. You can close the DOS session. make sure the \Windows\system32\drivers\etc\hosts file on the workstation is correct. and IP address 10.10.11… Could not open connection to the host. Either the password or the user type for RFC_USER was changed. on port 3200: Connect failed” error message right under the command you entered. you will have to add their equivalents to the services file as well. Open a DOSWindows and type this: telnet 10. check if you are having connection problems due to firewall restrictions. If your window never goes completely blank and you set a “Connecting To 10. Let’s say your user us trying to connect to System ID (SID) DEV. . For information regarding operating system. the CUA Parent Client If CUA stops sending changes from DEV to QAS or PRD.11. System Number 00.
it means that the RFC_USER doing the ALE communication between the SAP systems is not authorized. 3. You might see “You are not authorized to change users in group” or “No authorization for group users in role”. Look for the user you tried to transport but could not. assign client number & description as per request Logoff from current client. iii. Local Client Copy .Use SCUL in DEV in your DEV CUA parent to list the errors that are occurring. If they work (ie nothing seems to happen after you click the remote logon button) everything should now be fixed. First. 6. Login to newly created client using the following credentials : i. This does not mean that YOU are not authorized. QAS. 2.SCCL----------------------------Step by Step Procedure to create a copy of a client locally in the same SAP server. Retry your user change. 1. And make sure that the user type is Communication and not dialog. change the password in the sm59 screen to the same password you changed RFC_USER to in DEV and QAS. If it still doesn’t go to QAS. Client Number User Id Password : Newly created one : SAP* : PASS . reset the RFC_USER password in DEV. 4. 5. ii. Logon to SAP server Use Transaction Code SCC4 Go to change mode Create a new client. If you get a logon screen for QAS. and PRD. Now go to sm59 and do remote logins using the QAS RFC connections. maybe the QAS system is hosed and down.
In case some tables are different. RSCLICHK program should be run in the target system remotely before doing a client export. A remote test client copy also can be executed to know the differences between source client and target client. 10. It is always better to schedule the client copy job in the background for the night run when normal work is not taking place. Always check the database space before performing a client copy. 6. 9. To avoid data inconsistencies all the users working in the source and target clients should logoff from the system. After executing this program and getting successful results you can ensure that the client copy will have no problems. 7. 8. When you copy a client from one system to another. The transport system and the transport management system of 4. 5.2 then do not use R3trans to copy a client. 4. Golden rules for CLIENT Copies 1. client-independent tables should only be copied if they are not yet modified in the target system. 3. 8. Use Transaction Code SCCL for local client copy Give reference client for copy and profile as per the request Use SCC3 Transaction code to monitor progress of Client Copy. This program will give information about the missing definitions from the data dictionary in the target. We recommend the users to read all the OSS notes regarding client copy that applies to their SAP release. you can use SE11 to compare and adjust the table structure in both the system before the client copy. If you are not in release 2.7. Master data can not be copied without copying transactional data and transactional data can not be copied without copying master data.0 are the only proper tool to be use to keep multiple systems in sync by transporting development and customizing changes to another instance. . Application data (transactional and master) should not be copied without copying configuration data. 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. 2. 9.
5. you can log on to the server. Place a √ in the □ to the left of the process number to be stopped by pressing Space. find the process which must be stopped. you can go to transaction SM04 and kill the user’s session. On the Process Overview screen. Log on to any client in the appropriate SAP system. click the Process → Cancel without core. On the top-most menu bar. If this does not kill the process. Click the blue arrow circle picture-icon to refresh the Process Overview screen until the stopped process has cleared from the display. Go to transaction SM50. You may now leave the SM50 transaction. and End the Process. 3. If this does not kill the process.Kill the Work process-------------------------- Stopping Run-Away or “Bad” Work Processes 1. 4. If this does not kill the session. there is an . 2. open a Task Manager session.
Click SAVE 8. give RFC destination name – Name by which the connection would be identified 5. Use “Test Connection” to check RFC. If Trusted RFC connection is required. Run it providing the process ID number. 2. 1. you have no choice but to “bounce” the SAP instance and/or possibly the serve. Give IP address/Host name and system number for destination server in Technical Settings tab 9. give user credentials in “Logon/Security” tab . Click SAVE 10. Creating RFC Connection This procedure should allow the Basis team to create a RFC connection in any SAP server. If none of the above work. Give Description for the RFC Connection – Generally the purpose of the connection is mentioned here 7. 3.exe. 11. On the new screen. Give Connection Type ( 3 for any SAP to SAP communication ) F4 Help will list down all possible types of connections 6.executable in the RUN directory on the server called sapntkill. Logon to SAP server Use Transaction Code SM59 On SM59 screen click on “Create” button 4.
DEV For SAPscript data of a client: /usr/sap/trans/data/SX00011. 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. 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). The output of the export includes the name of the COMMFILE that has to be imported. Then you can execute the client export in the background or online. For example if the client export is done from development client 100 then the file will look like DEVKO0001.DEV /usr/sap/trans/data/DX00001.DEV Tips: Make sure that all the cofiles and the datafiles exist in the data and cofile directories before starting the import phase. In the client transport screen you can select a copy profile that matches your requirements and the target system in your CTS pipeline. <sid>KT<no> for the client-specific data. a popup screen shows all the information about the command files that will be created after the client export is done.Transporting a Client: ---------- Procedure: To transport clients from one system to another. After the client export procedure is completed. You can watch the export process in client copy log using transaction SCC3. For example DEVKX0001 The data export is performed automatically. After the process starts.DEV For client independent customizing data: /usr/sap/trans/data/RO00001. For example DEVKT0001 <sid>KX<no> for the SAPscript objects as Texts and forms. go to System Administration then choose Tools -> Administration -> Client admin->Client transport -> Client export or transaction SCC8. Before the client export starts. 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) .
If there are inconsistencies. 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. Up to release 3. RSCLIEXP program can be used to create the command files. Then you can continue to execute the program and it will successfully complete the import of SAPscript objects to the target client. the following transport files are created. 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. activities in order to adapt the runtime environment to the current state of the data. <sid>KO<no>: For the client-independent data (if the copy profile selected includes client independent data: .0. You can also use SCC2 to execute the same process as in transaction SCC7. During this process. you must perform post-processing. the SAPscript texts are imported and application reports are generated. The tp command is used to do the import as we have seen before and the RSCLIIMP program is executed for the post-processing activities and the consistency of data.0 after the client is exported from the source system using transaction SCC8 as we have seen in the client export section. choose Tools -> Administration. If you get any problem importing the SAPscript objects then use the RSTXR3TR program in the target client to import those. To execute post-processing. In this screen you can enter the transport request for the SAPscript object.>Client admin ->Client transport->client import or transaction SCC7. Transaction SCC7 will take you to the client import post-processing screen . Using the transport procedure in 4. According to the above example devkx00001.0 In 4. In that screen the transport from the last tp import is proposed.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.DEV (using the above example) You can choose the import option from the “mode” option. you need to repeat the import after checking the log.
1. 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 . assign client number & description as per request . Local Client Copy . <sid>KX<no>: For the Texts and forms. start transaction SCC2 and then execute the import into the target client.Adds to the buffer If you are transporting to a new client then the new client should be created in the target system. 2.Change to the transport directory * tp addtobuffer <command file-name> <target-sys-id> . you should perform the post-processing activities by using the following path: Tools ->Administration->Client admin->Client transport->Post-process import. we recommend doing table compare between the source client and the target client to check all the client dependent and independent tables for consistency. This process imports all the SAPscript objects and generates all the programs. 3.SCCL-------------------Step by Step Procedure to create a copy of a client locally in the same SAP server. When all the above transports get released from the source system. After the client is imported successfully. After the post processing is done. Logon to SAP server Use Transaction Code SCC4 Go to change mode Create a new client. 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. the data is exported to the data files of /usr/sap/trans/data directory automatically. 4.<sid>KR<no>: For the client-specific data.
4. To avoid data inconsistencies all the users working in the source and target clients should logoff from the system. Application data (transactional and master) should not be copied without copying configuration data. 6. Master data can not be copied without copying transactional data and transactional data can not be copied without copying master data. 7.5. 9. It is always better to schedule the client copy job in the background for the night run when normal work is not taking place. Golden rules for CLIENT Copies 1. Always check the database space before performing a client copy. Use Transaction Code SCCL for local client copy Give reference client for copy and profile as per the request Use SCC3 Transaction code to monitor progress of Client Copy. 5. When you copy a client from one system to another. 8. Client copy requires a valid client as the destination client. We recommend the users to read all the OSS notes regarding client copy that applies to their SAP release. The transport system and the transport management system of 4. client-independent tables should only be copied if they are not yet modified in the target system. Logoff from current client. 2. 3. 8. ii. Make sure that the client exists in T000 table and you can logon to that client. iii. . Client Number User Id Password : Newly created one : SAP* : PASS 7. Login to newly created client using the following credentials : i. 6.0 are the only proper tool to be use to keep multiple systems in sync by transporting development and customizing changes to another instance.
In case some tables are different. If you are not in release 2.9. After executing this program and getting successful results you can ensure that the client copy will have no problems. RSCLICHK program should be run in the target system remotely before doing a client export. * Logon to destination SAP server * Use Transaction Code SCC4 * Go to change mode * Create a new client. This program will give information about the missing definitions from the data dictionary in the target. 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. you can use SE11 to compare and adjust the table structure in both the system before the client copy. * RFC Connection should have Target Server as Destination and the test results should say “Connection test OK” .2 then do not use R3trans to copy a client. A remote test client copy also can be executed to know the differences between source client and target client. ii iii Client Number User Id Password : Newly created one : SAP* : PASS * Use Transaction Code SM59 to create a RFC Connection for client copy if does not exist already. 10. Creating Remote Client Copy SCC9--------------- Step by Step Procedure to copy a Client to the Remote SAP Server.
0 are the only proper tool to be use to keep multiple systems in sync by transporting development and customizing changes to another instance. Master data can not be copied without copying transactional data and transactional data can not be copied without copying master data. client-independent tables should only be copied if they are not yet modified in the target system. 4. 8. you can use SE11 to compare and adjust the table structure in both the system before the client copy.* Use SCC9 Transaction code to go to client copy screen. * 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. 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. In case some tables are different. After executing this program and getting successful results you can ensure that the client copy will have no problems. We recommend the users to read all the OSS notes regarding client copy that applies to their SAP release. Always check the database space before performing a client copy. RSCLICHK program should be run in the target system remotely before doing a client export. Application data (transactional and master) should not be copied without copying configuration data. A remote test client copy also can be executed to know the differences between source client and target client. To avoid data inconsistencies all the users working in the source and target clients should logoff from the system. . This program will give information about the missing definitions from the data dictionary in the target. 5. 3. Client copy requires a valid client as the destination client. When you copy a client from one system to another. Make sure that the client exists in T000 table and you can logon to that client. The transport system and the transport management system of 4. 2. 6. * Give profile as per the request. 9.
Login as adm b. connect internal d.sql file. Edit the file and replace the entire source SID to target SID.trc file in /oracle/P01/saptrance/usertrace directory. e. g.sql or controlfile. i.. h. exit. Steps for SAP System Copy------------------------------- 1. j. 3.10. f.sql to target system. Run the following command on source system. If you are not in release 2. alter database backup controlfile to trace. Verify the backup is successfully done. Above command will generate a . Copy the controlfile. Copy the text from CREATE CONTROLFILE until the (. a.. Take offline backup of both the server (source and target servers) 2.2 then do not use R3trans to copy a client.) and paste it in to any new . svrmgrl c. Edit the reuse database command with the set database command .
log to target. 5. It will take some time to restore. (/oracle//sapbackup) a.4. c. select Select backup type f.sql (file name of the control file contains the CREATE CONTROLFILE statement) n. a. Copy the generated during the backup file from the source system to target system. run the following command m. Login as Orasid b. connect internal. select Restore/Recovery d. Once the database is restored login as orasid and run the i. k. g. Shutdown the target server instance. startup nomount (if the database is already mounted shutdown it using the shutdown command) l. Only don’t change the backup volume name it must be target system . Change all the source to target . Select the offline backup which you want to restore. b. Copy the above aft file name line from the source back. From this onwards all the command on the target system only. After the run the above command it should give the “Statement Processed) . h.log file. select Full restore and recovery e. svrmgrl j. 6. run the brtools c. @controlfile.
Store the picture somewhere on your workstation. 8.o. and if you don’t see your file type . bmp . This picture can be in any valid picture format . shutdown q. All the jobs also you have to reconfigure and reschedule. back out to SAP Web Repository: Object display screen. Replace SAP Splash Logo: Change default SAP Logo on front screen. 2. and click the Find icon or press F8. click the Execute icon or press F8. . 4. Once you at done. jpg. Start the database and SAP services using startup. jpg. 10. On the SAP Web Repository: Objection selection screen. Reconfigure all the printers. Look to the far right of the Data Browser: Table MIMETYPES Select Entries screen. bmp. 1. After this you have to reconfigure the STMS. Go to transaction SMW0. alter database open resetlogs p. 7. 9. On the SAP Web Repository: Object display screen. Identify a picture to replace the existing SAP logo.then you need to add it. But convert it to jpg since that is the smallest available picture type. first make sure that the mime extension exists for your picture type. click “on” the radio button for Binary data for WebRFC applications.gif.gif. 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. 3. On the SAP Web Repository: Initial Screen. Click Settings -> Maintain MIME types.
Log on as ora<sid> and stop the TNS listener. You have replaced the SAP splash screen picture. 3. you need to download a SAPEXE. . As <sid>adm.5. Go to transaction SM30.SAR of a lower level. Download the two necessary archives . stop the SAP instance. if your SAP instance is on Basis level 39 and the description of one of the SAPEXE. unCAR the files with SAPCAR command “sapcar -xvf “SAPEXE*.SAR from SAP MarketPlace. click New Entries and add an entry called START_IMAGE and set the value to the name of your picture created in step #5. Be careful that your Basis level is high enough to use the patch level of the files you download. 7. Now you can upload your picture.sap. 6. 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.SAR and SAPEXEDB. 2. Log off and back on to view your work! UNIX Kernel Patch: UNIX Kernel Replacement--------- 1. log on to the UNIX server as <sid>adm and copy them up to a directory on the UNIX server .SAR files is Stack 42. For example. Once both files have been downloaded. Click the Create icon or press F5. and log on as root and stop saposcol. Fill in the table name SSM_CUST and click Maintain.I use one called /usr/sap/trans/NewKernel.com/patches. There files can be found at http://service. On the Change View “Set Values for the Session Manager / Profile Generator” screen.SAR”.SAPEXE. Then press the Save icon.
6. Log on to the client in which the main transport was created. Copy all the files unCARed in step 2 to /usr/sap/<SID>/SYS/exe/run. 5. 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. High-light the main transport in the list . Change the owner of saposcol to root. 7. 2. If you run into any problems starting your SAP instances.4. stop everything. Make a backup of your run directory before patching. and the SAP instance. the TNS listeners. Go to transaction se10 and pull up a list containing the main transport. and all the rest to <sid>adm. . You have patched your UNIX SAP kernel. If prompted. Start saposcol. overwrite all.not the subtasks contained in the list and click Ctrl+F11. Add an Object to a Transport----------------------------- To add an object to a existing unreleased transport. sapdba & all br* files to ora<sid>. you must do the following: 1. 3. 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. 8.
* 194. You will see a confirmation message in the status bar at the bottom of the screen.ZPROGRAM in our case.1. Turn “on” the radio button “Freely selected objects” that appears in the popup and press Enter or click the Copy button. 2. Set-up a remote network connection to SAP.106. Install SAP router on a Windows machine. On the “Include objects in request” screen.129 * P 10. 7.1. turn “on” the “Selected Objects in the Selection by type and name” section. 3. Check the saprouttab file : a) you should have only one in your system and b) it should look like this: P 10. 4. Click the Execute button or press F8.117. 5.* 194.4. click the “Include Request” button or press F9. In the “Include objects in request” screen.117.1. and enter the name of the object to be added to the transport . Check “on” the check box on the appropriate line.130 * . 6.106. Now you can release your transport and let it move to QAS! How to set-up and open a REMOTE SERVICE CONNECTION WITH SAP----------------------- 1.1. Install SAPCRYPTOLIB on the same machine.
Under Appl. When you are done installing then. 16. Click on “Display all systems” 11. Go to the Connecting to SAP tab. Go to the Problem Solving tab. Click on Systemdata – next to Logbook 14. 15. Go to http://service.117. 8. scroll down to SAP-router.1. do not enter anything under Additional SAP-Router field. click on Semi-Automatic Opening and enter the number of days for connecting to SAP. 9. and the LOP. you can check on the SAP website if the connection is open. Under System tab. If you have a system that has the db server and the application server running on it. install Service Connector from SAP’s site.129 10. 7. 19.Server tab do the same thing. On a workstation (Windows XP) that has the SAP GUI.sap. Click on the edit icon. Under DB server tab click on the change icon and enter the NETBIOS name of the server. then the IP address will be the same.P 194. . Unless you have two saprouters.61 3200 5. 17. 18.After less than a minute. Double click on your system ID 12. 13. along with the local IP address. and enter the saprouter’s NETBIOS name.1. and look for an edit icon to the right.106.com/system-data. 6. and under Service-port enter 3299. Test you connection to SAP by DOS cd: ping sapserv1. The Service Connection-System ID page opens. Click on Maintain Connections 10. To set-up the maximum time for SAP connection. Install on the same machine LOP (Line Opener program). run first SAPServiceConnector.
users cannot log in to the system. The SAP MMC gives you the ability to visually see the system status (green. 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.exe).exe). If one of them or both fail to start. which are stored in the “work” directory. The following scenarios will illustrate possible causes of why an SAP instance might not start and the reason of the message: “*** DISPATCHER EMERGENCY SHUTDOWN ***”. both the message server and the dispatcher need to start. For a central SAP instance to start successfully. Dispatcher Monitor (DPMON. view the work processes status and view the developer traces. which is located under \usr\sap\<SID>\sys\exe\run. EventViewer can provide useful information and it may help you pinpoint where the problem resides. Database logs. yellow or red lights).exe).SAP Startup Problems in Windows-----------------------Troubleshooting SAP Startup Problems in Windows----There’s 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. TROUBLESHOOTING SAP STARTUP PROBLEMS . EventViewer (EVENTVWR. which contains TCP and UDP services and their respective port numbers. Example: \usr\sap\TST\DVEBMGS00\work. This plain-text configuration file is located under %winnt %/system32/drivers/etc. Windows Task Manager (TASKMGR. Here are the two places you will definitely need to check: EventViewer (Application and System logs) and the SAP Management Console (MMC).
Due to the conflict.Scenario 1: Dispatcher does not start due to a port conflict Symptoms No work processes (disp+work. . If the instance starts successfully you can enable the client firewall back again. or if disabling it did not resolve the problem. Errors found in “dev_disp”: ***LOG Q0I=> NiPBind: bind (10048: WSAEADDRINUSE: Address already in use) [ninti. Solution If your server has a firewall client. edit the “services” file and check what port the appropriate “sapdp” is using. 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.c 1488] *** ERROR => NiIBind: service sapdp00 in use [nixxi. look for sapdp00.c 3936] *** ERROR => NiIDgBind: NiBind (rc=-4) [nixxi. Dispatcher shows status “stopped” in the SAP MMC. disable it and attempt to start the SAP instance again.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. If the instance number is 00. If there is no firewall client at all. If the instance number is 01 look for sapdp01 and so on. the dispatcher shuts down.c 3505] *** ERROR => DpCommInit: NiDgBind [dpxxdisp.exe) exist in Task Manager.
*** ERROR => W11 (pid 2552) died [dpxxdisp. Errors found in “dev_disp”: C setuser ‘tst’ failed — connect terminated C failed to establish conn.Scenario 2: Dispatcher dies due to a database connection problem Symptoms No database connections. Solution Set the entry to the appropriate database owner. if the system was installed from scratch and it’s based on the Web AS 6. SAP MMC -> WP Table shows all processes as “ended”. But.c 1102] M in_ThErrHandle: 1 M *** ERROR => tskh_init: db_connect (step 1.c 11651] *** ERROR => W2 (pid 2476) died [dpxxdisp... th_errno 13. action 3. level 1) [thxxhead.c 11651] *** ERROR => W1 (pid 2468) died [dpxxdisp. db_connect (DB-Connect 000256) [thxxhead. In the messages above. This parameter needs to be set in the DEFAULT. No work processes. If the system is based on Basis <= 4.c 8437] *** ERROR => W0 (pid 2460) died [dpxxdisp.x to 4.7 the database owner should be “dbo”.c 11651] *** ERROR => W12 (pid 2592) died [dpxxdisp.pfl system profile (under \usr\sap\<SID>\sys\profile).x the database .c 11651] my types changed after wp death/restart 0xbf –> 0×80 *** 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.6 or if the system was upgraded from 4. we see that the SQL login ‘tst’ is expected but it does not exist at the database level.c 11651] . 0 M ***LOG R19=> tskh_init.
they get this error: No logon possible (no hw ID received by mssg server). create it and give it database ownership to the <SID>. Users get the login screen but the system does not log them in. Scenario 4: Users get ‘No logon possible’ messages when they attempt to log in Symptoms Work processes start but no logins are possible.exe) shows status “stopped”.c 8163] [Thr 2548] *** ERROR => MsSInit: MsSCommInit [msxxserv. The following error when trying to view the developer traces within the SAP MMC: The network path was not found.c 1561] [Thr 2548] *** ERROR => main: MsSInit [msxxserv. In the SAP MMC. Both need to be created on the \usr\sap directory. the message server (msg_server.c 5023] .) Problem Analysis The network shares “saploc” and “sapmnt” do not exist. No new developer traces written to disk (under the “work” directory. Solution Re-create the “saploc” and “sapmnt” network shares. Example: if the SID is TST then the database owner should be “tst”. 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 dev_ms file reports these errors: [Thr 2548] *** ERROR => MsCommInit: NiBufListen(sapmsTST) (rc=NIESERV_UNKNOWN) [msxxserv. If it doesn’t. Instead.owner should match the SID name in lower case. That explains the “network path not found” message when attempting to view the developer traces within the SAP MMC.pfl profile check at the database level if the SQL login exists. If the parameter is set correctly in the DEFAULT.
. Make sure you specify the appropriate TCP port (e. Scenario 6: Work processes die soon after they start Symptoms All work processes die right after the instance is started. re-start the instance. Example: sapdp00 3200/tcp Solution Add the necessary entry in the “services” file. The “dev_disp” file shows these errors: ***LOG Q0A=> NiIServToNo. The dispatcher entry “sapdp00″ is missing in the “services” file. Scenario 5: The message server starts but the dispatcher doesn’t Symptoms The dispatcher shows status “stopped” in the SAP MMC. Then. Example: SAPmsTST 3600/tcp Solution Edit the “services” file and add the entry. Example: sapdp00 3200/tcp Then. re-start the instance.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″.c 5078] Problem Analysis Work processes were able to start but the message server was not.g. MSStop (Msg Server 2900) [msxxserv.[Thr 2548] ***LOG Q02=> MsSHalt.c 2580] *** ERROR => DpCommInit: NiDgBind [dpxxdisp. service_unknown (sapdp00) [nixxi. 3600) for the message server. The reason is because the “services” file is missing the SAP System Message Port entry.
Set Titlebar ‘TAB’ With Name ‘anzeigen’(100). If Code = ‘SHOW’. Then. Only one work process shows status “wait”.The SAP MMC shows work processes with status “ended”. An ABAP dump saying “PXA_NO_SHARED_MEMORY” is generated as soon as a user logs in. write ‘/h’ to go in debug mode. Solution Edit the instance system profile at the OS level under \usr\sap\<SID>\sys\profile and lower the value assigned to “abap/buffersize”. When you have your entry. Cross the line you want to modify and press F7 (display function). The SAP MMC Syslog shows the following error multiple times: “SAP-Basis System: Shared Memory for PXA buffer not available”. Most likely the “abap/buffersize” instance profile parameter is set to high. it’s important to find out if any other memory parameter were changed. the system should start once the adequate memory allocation has been set to the the “abap/buffersize” parameter. . Here. Change Data In Table Without Authorization Using Transaction se16-------------------------------------- There is a way to change entries of a table with SE16 even if you don’t have the authorization: Go in SE16. Display the entry (or entries) you want to modify. you are in the code… Press F7 again to skip some code… Now you should see the code: Refresh Exclude_Tab. enter your table Name (ex: USR02). Also. Problem Analysis The instance profile contains misconfigured memory-related parameters. restart the instance. If not.
Elseif Code = ‘EDIT’. it is not yet active. In the Audit classes section. click Change FLD Contents. click the radio button to the left of the level of auditing you need. You may now leave the SM19 transaction. click the Save picture-icon. see the next section Activating a User Audit Profile. In the Selection criteria section. 3. and don’t forget to save! Trace a User’s Activity-----------------------Creating a User Audit Profile 1. 4. … Change the value from SHOW to EDIT. Please note that while the user trace profile has been saved. You will receive an Audit profile saved in the status bar at the bottom of the screen. On the Create new profile popup. . 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. From the top-most menu bar on the Security Audit: Administer Audit Profile screen. click Change FLD Contents. In the Events section. and press F8… or to delete an entry Change the value from SHOW to DELE. click “on” all the auditing functions you need for this profile. and press F8… Here we are… You can change the value to what you want. Go to transaction SM19. 7. type in a new Profile name and click the green √ picture-icon. 5. To activate the user trace. 2. Log on to any client in the appropriate SAP system. 6. select the Clients and User names to be traced. Once you have entered all your trace information. click Profile -> Create.
You may now leave the SM20 transaction. Go to transaction SM19. and Events to select sections of the Security Audit Log: Local Analysis screen. This list can be printed using the usual methods. Go to transaction SM20. provide your information to filter the audit information. Audit classes. If you need to trace the activities of a specific user. 3. Log on to any client in the appropriate SAP system. You will receive an Audit profile activated for next system start in the status bar at the bottom of the screen. You may now leave the SM19 transaction. Click the lit match picture-icon to activate it. In the Selection. be sure to include that user’s ID. 3. Click the Re-read audit log button. On the Security Audit: Administer Audit Profile screen. The audit will not begin until after the SAP instance has been recycled. The resulting list is displayed. Log on to any client in the appropriate SAP system. select the audit profile to be activated from the Profile dropdown. Viewing the Audit Analysis Report 1. Working with saprouter-----------------------Working with saprouter Starting saprouter (OSS Link) . 4. 5. 2. 2. 4.Activating a User Audit Profile 1.
3. Right-click on the SAPROUTER service and click Start. You may now log off the server. This should “bounce” your saprouter instance. You may now log off the server. Log on to the appropriate server as <sid>adm. Click Start → Administrative Tools → Services to open a Services window. 2. If is not started. . Log on to the appropriate server as <sid>adm. Look at the SAPROUTER service. Verifying the Status of saprouter If you have previously successfully established SAPNet (OSS) communications with SAP via saprouter in the past. 3. 1. right-click & Stop the service and then right-click & Start the service. You may now log off the server. 2. Click Start → Administrative Tools → Services to open a Services window. right-click to start the service. Click Start → Administrative Tools → Services to open a Services window. If it is started. Log on to the appropriate server as <sid>adm. 1. 4. or your saprouter is not running (happens all the time). 3. 4. Right-click on the SAPROUTER service and click Stop. there can only be three reasons for a “broken” SAPNet connection to SAP: the SAP VPN is down (which rarely happens). 4.1. 2. your saprouter configuration has been incorrectly changed (also very rare).
1.com/serviceconnection. You can do the same thing using SAP. click the Service Connections button. Word documents. and that a Security Audit Trace has been activated for the SAPAG ID.exe on your saprouter server before trying to add and open any Service Connections. local printer is simply another way of saying that the user is going to print to the default printer designated on his/her workstation. Click on the red X in that instance’s line. hours. be sure that the SAPAG client has been added to the appropriate SAP system and Client. scroll down the page and find the SAP instance you want to open. Log on to any client in the appropriate SAP system. On the Service Connections – Overview screen. 1. On the Service Connections screen. Please LOPInstalltion. As a rule. etc without thinking about it. 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. You probably do this all the time with Windows to printerspreadsheets.sap. Log on to the SAP Marketplace using an OSS ID with Administration rights – http://service. 4. . Creating a Local Frontend Printer or Desktop Printer-----------------------Local or frontend printing is sometimes confusing in concept but actually very easy to understand. and minutes you want the service connection to stay open. In the Enter Data for the system’s semi-automatic opening popup. Click the Continue button. 2. set the days. Go to transaction SPAD. 3. 2.Opening a Service Connection for SAP Support------------------Before opening a service connection for SAP.
I normally use a short name of “DESK” for “Desktop Printing” but alot of people use a Short name “SWIN” or “LOCL” as well. On the Spool Administration: Create Output Device screen. On the Spool Administration: Initial Screen screen. You may now leave the SPAD transaction. fill in the Output Name and Short name . Using this printer will cause print to go to SAPLPD which will use the default printer of the current workstation. click the Change button and then the Create button. 5. click the Output Devices button. That is _ _ D E F A U L T Save the printer. SAP R/3 dispatcher and work processes--------------------------Types of work processes: . On the Spool Administration: List of Output Devices screen.3. 4. 6. 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.
and password PASS. * Gateway : Used for transport of bigger amount of data between application servers as well as external (non SAP) systems that communicate with SAP Some Usefull Tips------------------- * Logging on without being authorized Client 066 usually exists in a SAP system because of EarlyWatch services. * Dispatcher : Redirect the request from GUI client to free process. If it is true.* Message : Coordinates the communication between different instances of a single SAP R/3 system. * Locking the whole system Using the command tp locksys «SysID» only the user SAP* will be allowed to login. . Used for Logon purpose and load balancing. * Batch : For Background jobs. Often this client does not have master users. Used for interactive online processing. * Enqueue : Single “Central Lock Management Service” that controls the locking mechanism between the different application servers and the database. Enjoy yourself. anyone can log into the system using the client 066. * Update : Responsible for consistency in asynchronous data changes. * Dialog : Interpreting the ABAP code and execute the business logic. The commandtp unlocksys «SysID» cancels the lock. user SAP*.
and expst. * Direct input logs The transaction BMV0 (direct input logs) shows all direct input logs.* 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.impst. . * SQL code help Run the command oerr ora «error number» under user ora«SysID». Thus. * Oracle import and export explanations Run the command imp help=yes under user ora«SysID». a job previously defined within R/3 will be released. This format can also be used with exp.
* Graphics on SAPscript The program RSTXLDMC can be used to upload graphics (file extension . After moving the mouse to the left side.* Table analyses between two systems The contents of a table between two systems can be checked through the transaction OY19. * Long messages on footer Click on the message and hold the mouse button. * Setting up module FI/CO without using IMG Almost all parameters can be set using the transactions ORFA (Asset Accounting). and ORKS (Cost Center Accounting).tif on PC files) into . ORFB (Financial Accounting).
individual standard text. * 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. * 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. * Correction and transport system . * 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.
. * 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.The transaction SE10 provides the easiest way to manage any request/transport and corrections. You have to choose the desired patch and click on delete entry. Use the transaction SM31 to modify table PAT03.
bdf. for individual file usages 7. rm < file> for removing file. bdf for checking all file system usages. -name filename -print for checking the file in the present directory 5.* 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 UNIX commands used for SAP administration:----------------------------1. 9. df -k. gzip <file> for zipping the file. h for listing previous used commands. Cdpro for checking the profiles path SAPMNT/<SID>/profile 3. 11. df -k .1 for sorting the files in a recursive manner. jcmon pf=<instance profile path> 6. Ps -ef is to check the how many running process and Kill any running process . stopsap r3/startsap r3 for stopping/starting R3 2. dpmon pf= <Instance profile path>. ls -lrt for listing of files according to the date modified 8. stopsap/startsap for stopping/starting SAP+ DB. Cdexe for checking the kernel folder 4. find . 10.. du -a | sort -k 1n.
com/instguides http://service. Rf remove forcifully any file 16.com/inbox Read messages from SAP to you Download SAP Installation Guides product installation guides License Keys License Key http://service.sap. pwd check the current directory Important SAP Marketplace Links----------------- Inbox http://service.sap. make clean to clean the effect of make command 18.12. tar -xvzf file name to run the zip folder of file content 14. Make command to effect any coading content 17. gunzip to unzip file 13. mv mo from one path to another 15. cp coppy from one location to another 19.com/licensekey Request New Permanent .sap.
Messages to SAP QuickLinks Page Oracle DBA Page Material OSS Notes Database Patches patches Remote Connection connection and http://service.com/user-admin user information Add/Change OSS ID .com/remoteconnection Learn about the OSS order it from SAP Service Connection http://service.sap.com/dbaora http://service.com/message http://service.sap.com/quicklinks http://service.sap.sap.sap.sap.com/notes http://service.com/patches Open problems with SAP An index of SAP links Page for Oracle DBA Search the SAP Notes Download SAP software http://service.sap.sap.com/sscr Register Developers and made against SAP objects User Administration http://service.com/serviceconnection Open a Service Connection for SAP to access your SAP landscape Software Distribution http://service.sap.sap.com/swdc Download new images of Installation CDs & DVDs SSCR Changes http://service.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue listening from where you left off, or restart the preview.