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?

you can log in to EP using host name:port#/ <service name> and user name and password 4. What is difference between these? 1. Web AS: Web Application Server is the platform for ABAP and J2EE stacks in Netweaver. SAP -XI: Exchange Infrastructure is used to establish a cross system connections between system by different vendors and versions 5. SAPNW . gets filled frequently and we add datafile to that? PSAPBTABD/I. 2. Q. .Netweaver is a web based technology includes java. What is SAP NETWEAVER. PSCAPLUCD etc. based on your installation choices during software installation. SAP WAS and SAP BI. Which table space. EP: Enterprise portal provides web based secure access to all the application. BI: It is an OLAP (on line analytical processing). It includes BI/XI/EP and different level of it’s configuration. SAP BIW. services and information. PSAPSTABD/I. SAP XI. which provides a plate form to collect the data and user extract the data from BI or BW (older version) to analyze it 3.The SAP Application Performance Standard (SAPS) is a hardware-independent unit that describes the performance of a system configuration in the SAP environment. Q.

1. it should deactivated it in normal operation. If paging occurs in a buffer. What is the utilization of the disks? How high is the paging in the base pool? .SM21? 3. * ST03: → Select a server → Today’s Workload: What are the response times? In the case of poor response times. where is most of the time needed? Button ‘Top Time’: Are there a lot of different transactions with poor response times or are there only a few? Is a certain transaction always slow or only sometimes? * ST06: → Detail analysis menu → Hardware Info. Any signs of general problems in the System Log . To which extent are the hardware resources utilized? CallST06 at times with poor system performance. 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. the corresponding parameter should be increased. 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. What is the CPU utilization? → Goto → Current Data → Snapshot → Top CPU processes and display the main CPU consumers. ST02: Check the buffering quality. Also refer to SAP Note 121625 in this context. Is the total CPU for the last dialog process > 10 minutes? * ST04: Is the database monitor activated? If yes.

What is considered “normal” response time? Performance Standards: Response time – 1 second (dialog). ST03: Display the corresponding performance records. SE30: Carry out a runtime analysis for the affected transactions. 5. ST05: If the database times are high. If only few transactions are affected by the performance problem. 1. 3. DB02 → Space Statistics button Press Enter on the Tables and Indexes popup History → All objects off/on Click the Months button 5. you should generate an SQL trace of the affected transactions to find out whether the database access is carried out in a useful way.4. The sorted results shows the top tables when it comes to rows changes per month. Look for tables that have experienced unusual monthly growth. < 1 second (update) . 3. Check whether modifications were made in the affected or related transactions. 2. 2. 4. 6. Click on the first number under the Rows – Chg/Month header and click the Sort button. These tables are your “database hogs”. you should additionally note the following points: 1. 6. 4.

and the installation completed 100% successfully. If your installaion was never able to . or an old one.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 –.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. there are some very specific places to look for information. you know that the instance itself must be viable. If this is a brand new SAP instance.

The most useful information can be found in the dev_wx. . Sort them with “ls – ltr” is see the list sorted in descending order for the ease of viewing. dev_rfcx.log”. look for “error” in all files with the suffix “. dev_disp. Use the sapinst directory to search the installation logs and find your problem. and stderrx files. · · · 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.complete due to the instance not being able to start up. Sort them with “ls – ltr” is see the list sorted in descending order for the ease of viewing. go to the /usr/sap/<SID>/DVEBMGS00/work directory and do the same thing in this directory. the issue is probably due to lack of resources. If your SAP instance has been up and running fine for a good while. dev_ms. If you have a test searching tool. then something has probably changed that makes it not come up. If nothing obvious is found. look at the logs in the /home/<sid>adm directory.

But sometimes things get lost in translation.42 BR602W No valid SAP license found . Moral of the story? Realize that some things just don’t translate correctly from language to language. Why? Because it might contain information leading to other notes that did pertain. and search accordingly. If you searched for “Panic! Panic! Panic!” and got no hits. you could search for all words. you are applying support packages and get an import error with the following message “Panic! Panic! Panic! there’s no object header”. And if that produced nothing tangible. First you could search for the phrase. like “brbackup No valid SAP license found”.please contact SAP” First. you should search the specific error message “BR602W No valid SAP license found”. you could make your next search a little less specifc. Since we speak English and we realize that the SAP product was designed and implemented in Germany. 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 try “warning message no object header”. and attach the zipped file to it. If you get at least one hit. 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. Also provide them with the answers to the above questions as well as your current hardware and database platforms. and if you had no luck. zip the contains of the /usr/sap/<SID>/DVEBMGS00/work directory. If you didn’t find a note that matched the problem. you could make it even less specific as in “brbackup SAP license error” or “SAP license error”. 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.If all else fails.05. open a problem with SAP.10 (80) BR055I Start of database backup: bdmsqjbi. or give you new ideas for more search terms to help narrow the scope of my query. patch level for SAP support packages. Normally a very specific query will get you the results you need.anf 2004-02-27 00. you should read the SAP Note even if it didn’t look as if it pertained 100%. . For example. kernel. and anything else you might think useful.

Last. There are certain notes that you pull over and over again due to some task that needs fresh. add these three lines to the bottom of your \Windows\system32\drivers\etc\services file: . current and precise information. and not least. or b) deleting and installing a newer version of SAPGui. read and become familiar with your SAP Notes. 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. If a user seems to be experiencing SAPGui errors. Make sure that these lines were added to the services file on the user’s workstation: After you have successfully configured your SAPGui. known problems with applying patches. etc. These are mostly lists of supported printer devices.

first you need to make sure that the workstation can connect to the SAP server in some non-SAPGui way. on port 3200: Connect failed” error message right under the command you entered. the CUA Parent Client If CUA stops sending changes from DEV to QAS or PRD. Also. If your window never goes completely blank and you set a “Connecting To 10.1. Either the password or the user type for RFC_USER was changed.10. the dispatcher is not reachable. you will have to add their equivalents to the services file as well.1.sapdp00 sapmsR3I # 3200/tcp 3600/tcp If you have SAP Instances using System Numbers other than 00. or the SM59 RFC connection to was changed and is no longer working. and IP address 10. Let’s say your user us trying to connect to System ID (SID) DEV. make sure the \Windows\system32\drivers\etc\hosts file on the workstation is correct.11. . see SAP Note 26417 -SAP GUI Resources: Hardware and software. and hardware requirements for running SAPGui. For information regarding operating system. Also. check if you are having connection problems due to firewall restrictions. System Number 00. 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. And.11 3200¬ If the screen rolls and goes totally blank then your dispatcher is reachable.10. resource.10. If you have never tested connectivity to a SAP instance on the workstation having the connection problem.11… Could not open connection to the host. Open a DOSWindows and type this: telnet 10.1. You can close the DOS session. something in the RFC setup has changed.

Look for the user you tried to transport but could not. ii. Logon to SAP server Use Transaction Code SCC4 Go to change mode Create a new client. First. reset the RFC_USER password in DEV. 6. And make sure that the user type is Communication and not dialog. and PRD. QAS. 1. If you get a logon screen for QAS. Login to newly created client using the following credentials : i. This does not mean that YOU are not authorized. change the password in the sm59 screen to the same password you changed RFC_USER to in DEV and QAS. Local Client Copy . If they work (ie nothing seems to happen after you click the remote logon button) everything should now be fixed. 2. maybe the QAS system is hosed and down. 4. You might see “You are not authorized to change users in group” or “No authorization for group users in role”. Retry your user change. 5. Now go to sm59 and do remote logins using the QAS RFC connections. 3. 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 . If it still doesn’t go to QAS. assign client number & description as per request Logoff from current client.SCCL----------------------------Step by Step Procedure to create a copy of a client locally in the same SAP server. iii.Use SCUL in DEV in your DEV CUA parent to list the errors that are occurring.

. In case some tables are different. Always check the database space before performing a client copy. The transport system and the transport management system of 4. 7.7. 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. you can use SE11 to compare and adjust the table structure in both the system before the client copy.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.0 are the only proper tool to be use to keep multiple systems in sync by transporting development and customizing changes to another instance. 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. It is always better to schedule the client copy job in the background for the night run when normal work is not taking place. 8. Golden rules for CLIENT Copies 1. If you are not in release 2. Make sure that the client exists in T000 table and you can logon to that client. 10. 3. 2. A remote test client copy also can be executed to know the differences between source client and target client. Application data (transactional and master) should not be copied without copying configuration data. 5. 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. 4. 6. Master data can not be copied without copying transactional data and transactional data can not be copied without copying master data. 9. 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. After executing this program and getting successful results you can ensure that the client copy will have no problems. 8. 9.

click the Process → Cancel without core. Place a √ in the □ to the left of the process number to be stopped by pressing Space. Go to transaction SM50. you can log on to the server. open a Task Manager session. If this does not kill the process. 4. You may now leave the SM50 transaction. there is an . On the Process Overview screen. If this does not kill the session. and End the Process. you can go to transaction SM04 and kill the user’s session. On the top-most menu bar. If this does not kill the process. 2. 3.Kill the Work process-------------------------- Stopping Run-Away or “Bad” Work Processes 1. Log on to any client in the appropriate SAP system. Click the blue arrow circle picture-icon to refresh the Process Overview screen until the stopped process has cleared from the display. 5. find the process which must be stopped.

exe. Give Description for the RFC Connection – Generally the purpose of the connection is mentioned here 7. 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. Run it providing the process ID number. Creating RFC Connection This procedure should allow the Basis team to create a RFC connection in any SAP server. give RFC destination name – Name by which the connection would be identified 5. you have no choice but to “bounce” the SAP instance and/or possibly the serve. 3. Give IP address/Host name and system number for destination server in Technical Settings tab 9. Click SAVE 10. give user credentials in “Logon/Security” tab . 2. If Trusted RFC connection is required. 1. Click SAVE 8. Logon to SAP server Use Transaction Code SM59 On SM59 screen click on “Create” button 4. 11. Use “Test Connection” to check RFC. On the new screen. If none of the above work.

For example DEVKT0001 <sid>KX<no> for the SAPscript objects as Texts and forms. 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). <sid>KT<no> for the client-specific data. After the process starts.DEV For SAPscript data of a client: /usr/sap/trans/data/SX00011. In the client transport screen you can select a copy profile that matches your requirements and the target system in your CTS pipeline. 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 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 Tips: Make sure that all the cofiles and the datafiles exist in the data and cofile directories before starting the import phase. For example if the client export is done from development client 100 then the file will look like DEVKO0001. Then you can execute the client export in the background or online. Before the client export starts.DEV For client independent customizing data: /usr/sap/trans/data/RO00001. The output of the export includes the name of the COMMFILE that has to be imported.DEV /usr/sap/trans/data/DX00001. 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. 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.

In that screen the transport from the last tp import is proposed. During this process. If there are inconsistencies. According to the above example devkx00001. Up to release 3. <sid>KO<no>: For the client-independent data (if the copy profile selected includes client independent data: .DEV (using the above example) You can choose the import option from the “mode” option.0.>Client admin ->Client transport->client import or transaction SCC7.0 after the client is exported from the source system using transaction SCC8 as we have seen in the client export section. You can also use SCC2 to execute the same process as in transaction SCC7. the SAPscript texts are imported and application reports are generated. activities in order to adapt the runtime environment to the current state of the data. 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. RSCLIEXP program can be used to create the command files. 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. you must perform post-processing. In this screen you can enter the transport request for the SAPscript object. the following transport files are created.0 In 4. To execute post-processing. Transaction SCC7 will take you to the client import post-processing screen . choose Tools -> Administration. If you get any problem importing the SAPscript objects then use the RSTXR3TR program in the target client to import those. Then you can continue to execute the program and it will successfully complete the import of SAPscript objects to the target client. Using the transport procedure in 4.tp addtobuffer devko00001 qas tp addtobuffer devkx00001 qas Then logon as <sid>adm to the target system and then use then import the transports as following: tp import devkt00001 qas client100 u148 – For the client dependent data tp import devko00001 qas client100 u148 – For client independent data (In the above example QAS is the target system and 100 is the target client) After you import a client from another system. you need to repeat the import after checking the log. 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.

the data is exported to the data files of /usr/sap/trans/data directory automatically. 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 . you should perform the post-processing activities by using the following path: Tools ->Administration->Client admin->Client transport->Post-process import. After the client is imported successfully. <sid>KX<no>: For the Texts and forms. Logon to SAP server Use Transaction Code SCC4 Go to change mode Create a new client. The cofiles are also created in the /usr/sap/trans/cofiles directory.<sid>KR<no>: For the client-specific data. we recommend doing table compare between the source client and the target client to check all the client dependent and independent tables for consistency.Change to the transport directory * tp addtobuffer <command file-name> <target-sys-id> . 2. start transaction SCC2 and then execute the import into the target client. 4. This process imports all the SAPscript objects and generates all the programs. assign client number & description as per request . Local Client Copy .SCCL-------------------Step by Step Procedure to create a copy of a client locally in the same SAP server. 1.Adds to the buffer If you are transporting to a new client then the new client should be created in the target system. After the post processing is done. 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. When all the above transports get released from the source system.

Client Number User Id Password : Newly created one : SAP* : PASS 7. 2.0 are the only proper tool to be use to keep multiple systems in sync by transporting development and customizing changes to another instance. It is always better to schedule the client copy job in the background for the night run when normal work is not taking place. 5. Always check the database space before performing a client copy. To avoid data inconsistencies all the users working in the source and target clients should logoff from the system. 6. 8. Master data can not be copied without copying transactional data and transactional data can not be copied without copying master data. ii. . Client copy requires a valid client as the destination client. 8.5. 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. The transport system and the transport management system of 4. Golden rules for CLIENT Copies 1. 4. 6. Login to newly created client using the following credentials : i. 3. We recommend the users to read all the OSS notes regarding client copy that applies to their SAP release. Application data (transactional and master) should not be copied without copying configuration data. 7. Logoff from current client. When you copy a client from one system to another. client-independent tables should only be copied if they are not yet modified in the target system. 9. Make sure that the client exists in T000 table and you can logon to that client. iii.

After executing this program and getting successful results you can ensure that the client copy will have no problems. * RFC Connection should have Target Server as Destination and the test results should say “Connection test OK” . * Logon to destination SAP server * Use Transaction Code SCC4 * Go to change mode * Create a new client. assign client number & description as per request * Logoff from current client. 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. * Login to newly created client in destination SAP server using the following credentials : i. RSCLICHK program should be run in the target system remotely before doing a client export. 10. 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.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. If you are not in release 2.9. In case some tables are different. you can use SE11 to compare and adjust the table structure in both the system before the client copy.

6. 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. In case some tables are different. Application data (transactional and master) should not be copied without copying configuration 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. When you copy a client from one system to another. client-independent tables should only be copied if they are not yet modified in the target system. . 9. Client copy requires a valid client as the destination client. 8. This program will give information about the missing definitions from the data dictionary in the target. After executing this program and getting successful results you can ensure that the client copy will have no problems. you can use SE11 to compare and adjust the table structure in both the system before the client copy. 2.* Use SCC9 Transaction code to go to client copy screen. * Give profile as per the request. 5. The transport system and the transport management system of 4. Make sure that the client exists in T000 table and you can logon to that client. 3. To avoid data inconsistencies all the users working in the source and target clients should logoff from the system. Master data can not be copied without copying transactional data and transactional data can not be copied without copying master data. 4. RSCLICHK program should be run in the target system remotely before doing a client export. We recommend the users to read all the OSS notes regarding client copy that applies to their SAP release. A remote test client copy also can be executed to know the differences between source client and target client. * 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. 7.

i.10. e.2 then do not use R3trans to copy a client. f.sql or controlfile.. Verify the backup is successfully done.trc file in /oracle/P01/saptrance/usertrace directory. a. h. j. Edit the reuse database command with the set database command . Steps for SAP System Copy------------------------------- 1. connect internal d.sql file. Run the following command on source system.sql to target system. If you are not in release 2. Edit the file and replace the entire source SID to target SID. Copy the text from CREATE CONTROLFILE until the (. alter database backup controlfile to trace.) and paste it in to any new . Above command will generate a . Login as adm b. Copy the controlfile.. exit. Take offline backup of both the server (source and target servers) 2. 3. g. svrmgrl c.

From this onwards all the command on the target system only. 6. Once the database is restored login as orasid and run the i. svrmgrl j. connect internal. k.log to target. select Full restore and recovery e. It will take some time to restore. Select the offline backup which you want to restore. After the run the above command it should give the “Statement Processed) . Change all the source to target . select Select backup type f. @controlfile. startup nomount (if the database is already mounted shutdown it using the shutdown command) l. run the following command m. a. c. h. 5. select Restore/Recovery d. Shutdown the target server instance.sql (file name of the control file contains the CREATE CONTROLFILE statement) n. Copy the generated during the backup file from the source system to target system. Login as Orasid b. (/oracle//sapbackup) a. b. g. run the brtools c.4.log file. Copy the above aft file name line from the source back. Only don’t change the backup volume name it must be target system .

On the SAP Web Repository: Objection selection screen. Reconfigure all the printers. On the SAP Web Repository: Object display screen. and if you don’t see your file type . click the Execute icon or press F8. click “on” the radio button for Binary data for WebRFC applications. 8. 1. 7. After this you have to reconfigure the STMS.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. alter database open resetlogs p. 4. jpg.gif. shutdown q. Click Settings -> Maintain MIME types. and click the Find icon or press F8. Look to the far right of the Data Browser: Table MIMETYPES Select Entries screen. All the jobs also you have to reconfigure and reschedule. 3. On the SAP Web Repository: Initial Screen.then you need to add it. But convert it to jpg since that is the smallest available picture type. back out to SAP Web Repository: Object display screen. Store the picture somewhere on your workstation. This picture can be in any valid picture format . Once you at done. 10. first make sure that the mime extension exists for your picture type. Go to transaction SMW0. Identify a picture to replace the existing SAP logo. jpg. bmp.o. 2. 9. Start the database and SAP services using startup. Replace SAP Splash Logo: Change default SAP Logo on front screen. . bmp .

and log on as root and stop saposcol.SAR”. Log on as ora<sid> and stop the TNS listener.I use one called /usr/sap/trans/NewKernel. click New Entries and add an entry called START_IMAGE and set the value to the name of your picture created in step #5. 7.com/patches. 3. Fill in the table name SSM_CUST and click Maintain. You have replaced the SAP splash screen picture. Now you can upload your picture. Log off and back on to view your work! UNIX Kernel Patch: UNIX Kernel Replacement--------- 1. unCAR the files with SAPCAR command “sapcar -xvf “SAPEXE*. 2.SAR and SAPEXEDB. you need to download a SAPEXE. On the Change View “Set Values for the Session Manager / Profile Generator” screen.SAPEXE. Once both files have been downloaded.SAR files is Stack 42. . For example. As <sid>adm. Be careful that your Basis level is high enough to use the patch level of the files you download. There files can be found at http://service. Then press the Save icon. 6. Fill in the name of your picture and a brief description and click the Import icon.sap.SAR from SAP MarketPlace.SAR of a lower level. Download the two necessary archives . Go to transaction SM30. Then provide the location of your picture and load it in.5. log on to the UNIX server as <sid>adm and copy them up to a directory on the UNIX server . stop the SAP instance. Click the Create icon or press F5. if your SAP instance is on Basis level 39 and the description of one of the SAPEXE.

and all the rest to <sid>adm. Change the owner of saposcol to root. 7. Go to transaction se10 and pull up a list containing the main transport. overwrite all. 5. High-light the main transport in the list .not the subtasks contained in the list and click Ctrl+F11. the TNS listeners. You have patched your UNIX SAP kernel. Start saposcol. and the SAP instance. Copy all the files unCARed in step 2 to /usr/sap/<SID>/SYS/exe/run.4. Log on to the client in which the main transport was created. 3. 6. 8. 2. 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. Make a backup of your run directory before patching. stop everything. . If prompted. you must do the following: 1. Add an Object to a Transport----------------------------- To add an object to a existing unreleased transport. If you run into any problems starting your SAP instances. 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. sapdba & all br* files to ora<sid>.

2. On the “Include objects in request” screen.1. 3. Check the saprouttab file : a) you should have only one in your system and b) it should look like this: P 10.106. Click the Execute button or press F8. 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. Install SAP router on a Windows machine. and enter the name of the object to be added to the transport .* 194. You will see a confirmation message in the status bar at the bottom of the screen.117. Install SAPCRYPTOLIB on the same machine. 5.4. 6. Set-up a remote network connection to SAP.130 * . click the “Include Request” button or press F9.* 194.1.1. Turn “on” the radio button “Freely selected objects” that appears in the popup and press Enter or click the Copy button.117.ZPROGRAM in our case.1. 4.106. turn “on” the “Selected Objects in the Selection by type and name” section. 7. In the “Include objects in request” screen.129 * P 10.

7. you can check on the SAP website if the connection is open.1.Server tab do the same thing.129 10.106.117. Test you connection to SAP by DOS cd: ping sapserv1. Go to the Problem Solving tab. To set-up the maximum time for SAP connection.com/system-data. do not enter anything under Additional SAP-Router field. and look for an edit icon to the right.After less than a minute. Double click on your system ID 12. Click on the edit icon. Under DB server tab click on the change icon and enter the NETBIOS name of the server. On a workstation (Windows XP) that has the SAP GUI. click on Semi-Automatic Opening and enter the number of days for connecting to SAP. If you have a system that has the db server and the application server running on it. Install on the same machine LOP (Line Opener program). 13. and enter the saprouter’s NETBIOS name. then the IP address will be the same. Unless you have two saprouters. 19. run first SAPServiceConnector. scroll down to SAP-router. 18. 9. Under Appl. 16. 17.sap. along with the local IP address. . 8.1. Under System tab. and the LOP. Click on Maintain Connections 10. Click on “Display all systems” 11.P 194. 15. Go to the Connecting to SAP tab. and under Service-port enter 3299. The Service Connection-System ID page opens. Click on Systemdata – next to Logbook 14. 6. When you are done installing then. install Service Connector from SAP’s site. Go to http://service.61 3200 5.

The SAP MMC gives you the ability to visually see the system status (green. If one of them or both fail to start.exe). which are stored in the “work” directory.exe). users cannot log in to the system. Dispatcher Monitor (DPMON. 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. Example: \usr\sap\TST\DVEBMGS00\work. This plain-text configuration file is located under %winnt %/system32/drivers/etc.exe). which is located under \usr\sap\<SID>\sys\exe\run. Database logs. For a central SAP instance to start successfully. TROUBLESHOOTING SAP STARTUP PROBLEMS . yellow or red lights). 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. which contains TCP and UDP services and their respective port numbers. EventViewer (EVENTVWR. EventViewer can provide useful information and it may help you pinpoint where the problem resides. view the work processes status and view the developer traces. 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. Windows Task Manager (TASKMGR.

edit the “services” file and check what port the appropriate “sapdp” is using. Dispatcher shows status “stopped” in the SAP MMC. If the instance number is 01 look for sapdp01 and so on. look for sapdp00. 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 there is no firewall client at all.Scenario 1: Dispatcher does not start due to a port conflict Symptoms No work processes (disp+work.c 3936] *** ERROR => NiIDgBind: NiBind (rc=-4) [nixxi. the dispatcher shuts down. Errors found in “dev_disp”: ***LOG Q0I=> NiPBind: bind (10048: WSAEADDRINUSE: Address already in use) [ninti. .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 the instance starts successfully you can enable the client firewall back again.c 1488] *** ERROR => NiIBind: service sapdp00 in use [nixxi. disable it and attempt to start the SAP instance again. Solution If your server has a firewall client. or if disabling it did not resolve the problem.c 3505] *** ERROR => DpCommInit: NiDgBind [dpxxdisp.exe) exist in Task Manager. Due to the conflict.

In the messages above.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. If the system is based on Basis <= 4.c 8437] *** ERROR => W0 (pid 2460) died [dpxxdisp. db_connect (DB-Connect 000256) [thxxhead. This parameter needs to be set in the DEFAULT. action 3. But.7 the database owner should be “dbo”.c 11651] .Scenario 2: Dispatcher dies due to a database connection problem Symptoms No database connections. if the system was installed from scratch and it’s based on the Web AS 6.. No work processes. Solution Set the entry to the appropriate database owner.x to 4. we see that the SQL login ‘tst’ is expected but it does not exist at the database level.pfl system profile (under \usr\sap\<SID>\sys\profile). level 1) [thxxhead. *** ERROR => W11 (pid 2552) died [dpxxdisp.c 1102] M in_ThErrHandle: 1 M *** ERROR => tskh_init: db_connect (step 1. 0 M ***LOG R19=> tskh_init.c 11651] *** ERROR => W1 (pid 2468) died [dpxxdisp. Errors found in “dev_disp”: C setuser ‘tst’ failed — connect terminated C failed to establish conn.c 11651] *** ERROR => W2 (pid 2476) died [dpxxdisp.x the database . SAP MMC -> WP Table shows all processes as “ended”.c 11651] *** ERROR => W12 (pid 2592) died [dpxxdisp..6 or if the system was upgraded from 4. th_errno 13.

That explains the “network path not found” message when attempting to view the developer traces within the SAP MMC. Scenario 4: Users get ‘No logon possible’ messages when they attempt to log in Symptoms Work processes start but no logins are possible.) Problem Analysis The network shares “saploc” and “sapmnt” do not exist. The following error when trying to view the developer traces within the SAP MMC: The network path was not found. create it and give it database ownership to the <SID>. No new developer traces written to disk (under the “work” directory. Solution Re-create the “saploc” and “sapmnt” network shares.c 8163] [Thr 2548] *** ERROR => MsSInit: MsSCommInit [msxxserv. the message server (msg_server. Both need to be created on the \usr\sap directory. The dev_ms file reports these errors: [Thr 2548] *** ERROR => MsCommInit: NiBufListen(sapmsTST) (rc=NIESERV_UNKNOWN) [msxxserv. In the SAP MMC. Instead.owner should match the SID name in lower case. Example: if the SID is TST then the database owner should be “tst”.pfl profile check at the database level if the SQL login exists. 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. Users get the login screen but the system does not log them in. If the parameter is set correctly in the DEFAULT.exe) shows status “stopped”.c 1561] [Thr 2548] *** ERROR => main: MsSInit [msxxserv. If it doesn’t.c 5023] . they get this error: No logon possible (no hw ID received by mssg server).

Make sure you specify the appropriate TCP port (e. re-start the instance. . The reason is because the “services” file is missing the SAP System Message Port entry.c 2580] *** ERROR => DpCommInit: NiDgBind [dpxxdisp. Example: sapdp00 3200/tcp Then. Scenario 5: The message server starts but the dispatcher doesn’t Symptoms The dispatcher shows status “stopped” in the SAP MMC. The dispatcher entry “sapdp00″ is missing in the “services” file. service_unknown (sapdp00) [nixxi.c 5078] Problem Analysis Work processes were able to start but the message server was not. 3600) for the message server. MSStop (Msg Server 2900) [msxxserv.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″.[Thr 2548] ***LOG Q02=> MsSHalt. Then. re-start the instance. Example: sapdp00 3200/tcp Solution Add the necessary entry in the “services” file.g. The “dev_disp” file shows these errors: ***LOG Q0A=> NiIServToNo. Example: SAPmsTST 3600/tcp Solution Edit the “services” file and add the entry. Scenario 6: Work processes die soon after they start Symptoms All work processes die right after the instance is started.

When you have your entry. restart the instance. Display the entry (or entries) you want to modify. Only one work process shows status “wait”. If Code = ‘SHOW’. Here. If not. Most likely the “abap/buffersize” instance profile parameter is set to high. Also. Change Data In Table Without Authorization Using Transaction se16-------------------------------------- There is a way to change entries of a table with SE16 even if you don’t have the authorization: Go in SE16. enter your table Name (ex: USR02). The SAP MMC Syslog shows the following error multiple times: “SAP-Basis System: Shared Memory for PXA buffer not available”. write ‘/h’ to go in debug mode. the system should start once the adequate memory allocation has been set to the the “abap/buffersize” parameter. it’s important to find out if any other memory parameter were changed. you are in the code… Press F7 again to skip some code… Now you should see the code: Refresh Exclude_Tab. Cross the line you want to modify and press F7 (display function). Then. An ABAP dump saying “PXA_NO_SHARED_MEMORY” is generated as soon as a user logs in.The SAP MMC shows work processes with status “ended”. Problem Analysis The instance profile contains misconfigured memory-related parameters. . Set Titlebar ‘TAB’ With Name ‘anzeigen’(100). Solution Edit the instance system profile at the OS level under \usr\sap\<SID>\sys\profile and lower the value assigned to “abap/buffersize”.

3. On the Create new profile popup. click Change FLD Contents. and press F8… or to delete an entry Change the value from SHOW to DELE. Once you have entered all your trace information. click “on” all the auditing functions you need for this profile. Please note that while the user trace profile has been saved. see the next section Activating a User Audit Profile. In the Events section. select the Clients and User names to be traced. You will receive an Audit profile saved in the status bar at the bottom of the screen. From the top-most menu bar on the Security Audit: Administer Audit Profile screen. click Profile -> Create. In the Audit classes section. click the radio button to the left of the level of auditing you need. click Change FLD Contents. 2. On the Filter 1 tab of the Security Audit: Administer Audit Profile screen. type in a new Profile name and click the green √ picture-icon. click the Save picture-icon. click the □ to the left of Filter active to place a √ in the box. it is not yet active. In the Selection criteria section. Go to transaction SM19.Elseif Code = ‘EDIT’. 6. Log on to any client in the appropriate SAP system. 4. 5. To activate the user trace. . and press F8… Here we are… You can change the value to what you want. … Change the value from SHOW to EDIT. and don’t forget to save! Trace a User’s Activity-----------------------Creating a User Audit Profile 1. You may now leave the SM19 transaction. 7.

5. Go to transaction SM19. be sure to include that user’s ID. 2. On the Security Audit: Administer Audit Profile screen. Viewing the Audit Analysis Report 1. In the Selection. Go to transaction SM20. If you need to trace the activities of a specific user. Audit classes. Click the lit match picture-icon to activate it. The resulting list is displayed. 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 SM20 transaction.Activating a User Audit Profile 1. The audit will not begin until after the SAP instance has been recycled. provide your information to filter the audit information. 4. Click the Re-read audit log button. You may now leave the SM19 transaction. Working with saprouter-----------------------Working with saprouter Starting saprouter (OSS Link) . 2. 4. select the audit profile to be activated from the Profile dropdown. Log on to any client in the appropriate SAP system. 3. This list can be printed using the usual methods. and Events to select sections of the Security Audit Log: Local Analysis screen. 3. Log on to any client in the appropriate SAP system.

there can only be three reasons for a “broken” SAPNet connection to SAP: the SAP VPN is down (which rarely happens). Log on to the appropriate server as <sid>adm. You may now log off the server. 2. your saprouter configuration has been incorrectly changed (also very rare). 3. Click Start → Administrative Tools → Services to open a Services window. This should “bounce” your saprouter instance. You may now log off the server. right-click & Stop the service and then right-click & Start the service. Right-click on the SAPROUTER service and click Stop. 3. right-click to start the service. 2. Log on to the appropriate server as <sid>adm. If it is started. 1. Log on to the appropriate server as <sid>adm. 4. 4. Right-click on the SAPROUTER service and click Start. 4. 2. . Look at the SAPROUTER service. Click Start → Administrative Tools → Services to open a Services window. 3.1. If is not started. 1. You may now log off the server. or your saprouter is not running (happens all the time). Click Start → Administrative Tools → Services to open a Services window. Verifying the Status of saprouter If you have previously successfully established SAPNet (OSS) communications with SAP via saprouter in the past.

Click on the red X in that instance’s line. You can do the same thing using SAP. scroll down the page and find the SAP instance you want to open. 2. Click the Continue button. set the days. 1. Please LOPInstalltion. click the Service Connections button. Creating a Local Frontend Printer or Desktop Printer-----------------------Local or frontend printing is sometimes confusing in concept but actually very easy to understand. local printer is simply another way of saying that the user is going to print to the default printer designated on his/her workstation. Word documents.com/serviceconnection. . As a rule.sap. 3. and minutes you want the service connection to stay open. On the Service Connections – Overview screen. Log on to any client in the appropriate SAP system. 1.Opening a Service Connection for SAP Support------------------Before opening a service connection for SAP. You probably do this all the time with Windows to printerspreadsheets. 4. Go to transaction SPAD. Before a Service Connection to a SAP server via your saprouter can be created. and that a Security Audit Trace has been activated for the SAPAG ID. 2. hours. In the Enter Data for the system’s semi-automatic opening popup. be sure that the SAPAG client has been added to the appropriate SAP system and Client. etc without thinking about it. On the Service Connections screen. Log on to the SAP Marketplace using an OSS ID with Administration rights – http://service. the saprouter must run the LOP – Line Opener Program – to initiate the mode of SAP connection.exe on your saprouter server before trying to add and open any Service Connections.

fill in the Output Name and Short name .3. 5. On the Spool Administration: List of Output Devices screen. You may now leave the SPAD transaction. Using this printer will cause print to go to SAPLPD which will use the default printer of the current workstation. 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: Create Output Device screen.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: Initial Screen screen. 4. click the Change button and then the Create button. click the Output Devices button. That is _ _ D E F A U L T Save the printer. 6. SAP R/3 dispatcher and work processes--------------------------Types of work processes: .

* Update : Responsible for consistency in asynchronous data changes. user SAP*. * Enqueue : Single “Central Lock Management Service” that controls the locking mechanism between the different application servers and the database. The commandtp unlocksys «SysID» cancels the lock. Used for Logon purpose and load balancing. If it is true. * 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. anyone can log into the system using the client 066. Often this client does not have master users. * Locking the whole system Using the command tp locksys «SysID» only the user SAP* will be allowed to login. and password PASS. Used for interactive online processing. * Dialog : Interpreting the ABAP code and execute the business logic.* Message : Coordinates the communication between different instances of a single SAP R/3 system. * Batch : For Background jobs. * Dispatcher : Redirect the request from GUI client to free process. Enjoy yourself. .

Thus. . and expst. * Direct input logs The transaction BMV0 (direct input logs) shows all direct input logs. This format can also be used with exp. a job previously defined within R/3 will be released. * Oracle import and export explanations Run the command imp help=yes under user ora«SysID».* 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. * SQL code help Run the command oerr ora «error number» under user ora«SysID».impst.

After moving the mouse to the left side. and ORKS (Cost Center Accounting).* 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 . ORFB (Financial Accounting). * Graphics on SAPscript The program RSTXLDMC can be used to upload graphics (file extension . * Setting up module FI/CO without using IMG Almost all parameters can be set using the transactions ORFA (Asset Accounting). * Long messages on footer Click on the message and hold the mouse button.

The current date is automaticly set. * Correction and transport system . * Filling up an empty date field quickly Strike the key F4 (or click on matchcode symbol) and press ESCAPE. * Displaying check object when not authorized Soon after the lock try to access the transaction SU53.individual standard text. * Deleting cost elements and cost centers Since they have no postings you can use the transaction KA04 for deleting cost elements and KS04 for deleting cost centers. It reports the last objects verified and also the respective values.

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

11. 9. -name filename -print for checking the file in the present directory 5. ls -lrt for listing of files according to the date modified 8. bdf. du -a | sort -k 1n. stopsap/startsap for stopping/starting SAP+ DB. Cdexe for checking the kernel folder 4.. h for listing previous used commands. bdf for checking all file system usages. for individual file usages 7. Ps -ef is to check the how many running process and Kill any running process . 10. jcmon pf=<instance profile path> 6. gzip <file> for zipping the file. rm < file> for removing file.1 for sorting the files in a recursive manner.* 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. Cdpro for checking the profiles path SAPMNT/<SID>/profile 3. df -k. stopsap r3/startsap r3 for stopping/starting R3 2. df -k . find . dpmon pf= <Instance profile path>.

com/inbox Read messages from SAP to you Download SAP Installation Guides product installation guides License Keys License Key http://service. mv mo from one path to another 15. tar -xvzf file name to run the zip folder of file content 14. Make command to effect any coading content 17.sap.12. pwd check the current directory Important SAP Marketplace Links----------------- Inbox http://service.sap.com/instguides http://service.com/licensekey Request New Permanent .sap. make clean to clean the effect of make command 18. Rf remove forcifully any file 16. gunzip to unzip file 13. cp coppy from one location to another 19.

com/swdc Download new images of Installation CDs & DVDs SSCR Changes 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.sap.com/serviceconnection Open a Service Connection for SAP to access your SAP landscape Software Distribution http://service.sap.com/message http://service.com/notes http://service.sap.sap.sap.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.com/user-admin user information Add/Change OSS ID .sap.com/remoteconnection Learn about the OSS order it from SAP Service Connection http://service.sap.com/sscr Register Developers and made against SAP objects User Administration http://service.com/dbaora http://service.

Sign up to vote on this title
UsefulNot useful