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