1.

This is user maintenance tcode where we can maintain users massively whereas in su01 we can maintain one user at a time. SU10 is use to lock/unlock/change/delete users massively in a sap system. This is very use full when u need to assign 10 roles set to say 10 users.

4. SAP CCMS monitor is used to monitor the performance of your SAP R/3 System landscape in a centralized manner. It retrieves and reports metrics using Saps new centralized monitoring architecture, to Computer Center Management System (CCMS). The SAP CCMS Monitor allows you to monitor the performance data for various components of your SAP R/3 landscape. You can monitor multiple parameters or counters with a single monitor instance. This allows you to watch server loading for performance, availability, and capacity planning 5. Using ST03 7. The files are lost you cannot retrieve the same once you restarted. 11. DB01 Analyze exclusive lock waits and SM12 Display delete locks 13. Go to scc4 edit the client change cross-client object changes allowed and protection level 0 14. First of all you cannot apply support pack for ABAP using jspm cause jspm is used for java support pack. For ABAP support pack you can use tcode SPAM. Secondly for applying java support pack you dont need to uncar any java support pack. You just need to copy the files as it is in the /usr/sap/trans/EPS/in folder and apply them using JSPM. But in case of ABAP support pack you need to uncar all the support pack and then apply them using tcode SPAM. 15. You can check early watch report which gives the list of expensive SQL statement. 17. As a best practice you should always take backup of the profile files before making any changes to it. Replace with the original file name and restart the sap 19. You can check early watch report which gives the list of expensive SQL statements and then you can coordinate with your ABAP consultants to get it fine tuned. 20. In ST04 you can monitor all the details related to database like, Cache quality, Disk read, Buffer read and Read / User calls 21. Since /usr/sap/trans is a local file system in QA so the time it takes to transport in QA is very less and since in case of Prod it has to travel over the network it will take more time than QA. And in QA less number of users working and in a PROD huge number of users 23. Use sm21 t-code and under the system log select all remote system log it will show the logs of all application servers. 22. Increase the file system size / take the backup and move it another location 24. SYSTEM, PSAPTEMP, PSAPROLL, PSAPSID<Rel>, PSAPSIDUSR, PSAPSID Ecc5 : - SYSTEM PSAPTEMP, PSAPUNDO, SYSAUX, PSAPDSID PSAPSIDUSR, PSAPSID640 Ecc6 : - SYSTEM, PSAPTEMP, PSAPUNXO, SYSAUX, PSAPSR3 PSAPSR3USR PSAPSR3700 26. SPSTab.xml 32. Just you got the job logs there in the second line you find who triggered the job. 33. Early watch client(066) is used by SAP personal for preventive maintenance. They carried out regular performance check and analyze the system for potential problem and help the system manager and sap administrator to tune the system. Soon after the early watch session SAP sends the customer a report with the result of the analysis and recommendations for avoiding potential problems such as tablespace bottleneck, shortage of system parameter and buffer tuning.

34. Create an iview with any mail service and specify this in a role and assigned to the user, once user login click on the role it will directly connect to the webpage of the service. 36. In OS level we can find in /etc/service | grep I sapms<SID> / we can search in ms/server_port_<xx> parameter in profile. 37. Use T-code SM51 and click on release notes / go to system status in the screen you will find (in SAP system data section) whether it is Unicode or non-unicode 39. In some exceptional cases, we may want to uninstall an SAP Note that we have implemented we can do this by choosing Cancel SAP Note implementation. 40. Check the parameter log_archive_start in init<SID>.ora file if it is set as true then archive is enabled / login to ora<sid> connect to database and issue archivelog status 43. go to service.sap.com (service market place) and login using S-user id and click on keys and request click on SSCR keys click on register developer Provide developer id and choose installation Number and click on register. 44. May be user trying to login using another client or wrong pass type. 47. There are 4 types of TR are available 1. workbench request 2. customizing request 3. transport request and relocation. 48. We can lock/unlock users in either central system or target system, depending on the configuration. You configure lock/unlock in CUA system with following options. Lock/unlock only in central system / client system /both system. 50. The User Management Engine (UME) provides a centralized user management for all java applications and can be configured to work with user management data from multiple data resources. 51. There is no precise way of finding the user details who deleted the printer in SAP but you can shortlist the users by the below steps Look for system log when the printer was deleted and run STAT t-code for that time/date and see who executed the SPAD transaction in SAP 52. Check SPAD settin for user and check spool queue if it is full then you may have to delete old spool request via sp01 and sp02 53. Remote client copy method allows to perform copy at different R3 versions. For export and import method you have to have stms configured and To configure stms should be at the same support pack level. 54. Exporters files need to be maintain in different disks. 55. If you are not having access to SUIM code then it is highly impossible to gather information for a particular user unless you are master in SAP for this you will have to know about backdoor entries and in the same way try to access T-code: OY21,22,24,25,27 these t-codes are not known to your administrator and they are not locked try to access these codes and gather information related to User this called as backdoor entry to access user reports. 56. The purpose of parameter tab in SU01 is to define particular user to access or deny T-codes. Usually a user in SU01 parameter is define SAP_ALL then user can access all the T-codes without any restrictions. 57. if you are applying Java patch in Bulk so use JSPM, SDM is used to apply java patch one by one not in Bulk. Some prerequisites for applying java patches through JSPM(as you want deploy java stack in bulk) Make sure you have admin right and dont do any modification or change in dir or subdir of kernel /usr/sap/<SID>/SYS/exe/run and profile /usr/sap/<SID>/SYS/profile otherwise it will not recognize the kernel and profile dir. 58. SSO, Single Sign On, is a one time activity.

59. System refresh: the process of copying only data from one system to another is called system refresh. System Copy: In this you would take the backup of complete system, in other words you wuld create a replica of the system. 60. RZ20 or DPMON and PFMON. 61. You can see the logs in /usr/sap/trans/logs in OS level. Using se03, se01. When transporting is failed see t-code stms u can see the logs 62. sub dir are /usr/sap/sod/jc<00> some are as below. /usr/sap/<SID>/JC00/SDM/program/RemoteGui /usr/sap/<SID>/JC00/j2ee /usr/sap/<SID>/JC00/SDM /usr/sap/<SID>/JC00/work 63. Reset the PED in VisualAdmin tool 64. JASPM is a tool it is not related to the system wheter system is up or down. 66. Once we will trigger the request, in backend batch JOB RDDIMPDP will also trigger same time. If all the batch WP is running/Hold mode then also a simple request take log time. Once RDDIMPPDP job will complete then the respective transport request will execute successfully. 67. Multiple CI may be of different SIDs. It is possible we have to assign different message server port numbers, system numbers. 71. Consolidate route is defined between dev and qas, Delivery route qas to prd 72. .sca stands for SAP component archive or .sda for SAP deployed archive these two are use to deploy the java components, patches and other development in the form of .sca and .sda .war and .jar 73. We cannot adjust table space using tcode DB02, using brtools can adjust it. 76. Go to SM51, select one server and press ctrl+shift+F7 gives the users, terminal, T-codes using right now. 77.SE16 used to display table and SM30 used to maintain the data in the tables. 79. Fist of all check the work Directory for error Logs. Arrange the work directory by last changed date. Then you will get the latest logs for Error. dev_disp related to dispatcher dev_server0 is related to server0 for java. also check dev_jcontrol and dev_jcom, For detailed trouble shooting of Java Systems, You can go to the Directoty, /usr/sao/<SID>/j2ee/cluster/server0/logs There you can check the default Trace logs.. For Further more logs, goto System Folder inside of Logs.. Any security related issues is there, u can get the exact reason from there itself.

80. Yes we can change the number of work processes in rz10. but to get into use of newly created work processes we should restart the application. 81. Yes we can import the request from the above t-codes but t-codes stms_import is better as it directly takes to the import request screen. 82. First check the available background jobs if they are not free try to kill the long running jobs which will be the free process, if the background job is also free check the job is active or not. If it is not active trigger the corresponding report in se38. 83. One of the most important post client step is client compare using SCU0. It will compare the objects evaluate the differences and check the table entries. Apart from SCUO we need to run the DLS which creates the logical system. 84. Answer is above specified 85. We need to monitory atleast once in a day to check is there any exclusive locks. There are different types of locks which can be put on tables. If it is an exclusive lock then that particular user who put the lock on the table only will be able to access it. If at the same time some other background job which tries to access the same table to hold out and those transactions will be struck until the table is release. If there are many locks see who locked it, then go for t-code al0s and see whether the user is active if he not active then try to communicate from long time and affecting the business then delete the lock after the confirmation from the user. 87. If any application server is down but the CI including message server is running then you start application server directly using sapstart command, if application server is resides on the same host you have to mention the explicitly which application server you want to take up. You can active or deactivate application from sm51 and smms too and even shutdown but its it is not feasible. 88. Go to T-code SPAM go to action log you can find running job 89. If SM50 is not showing any related pid for background job then make use of t-code SMX and it will let you know what are the background jobs running and we can cancel it from there 90. First use the transaction scc4 then double click the target client and select the option no changes allowed 92. First we need to check why the spool process is failed, use sm50 and sap MMC console regarding process, check sm21 for any other information regards to spool 93. Local copy is made with in two clients in a single/same SAP system. Remote client copy can perform with a single sap system or from one system to another sap system using RFC connection method, for which we have to first define RFC communication in sm59. 94. First we need to create the day and night mode using rz04 and set the timings using sm63 more important as per the request we can chage the OP modes using rz03 95. Login/* and rdisk/* there are important. 96. When we create a user by default there will be 2 profiles maintained in SAP R/3 system and these profiles are SAP_ALL AND SAP_NEW 97. In R/3 Level, Mostly missing authorizations, adding authorizations objects manually, adding roles, users validity, su01 level issue, org levels, authorization field valuses, giving full permission, finding solution trough SUIM 98. Gateway server allows the communication between R3, R2 and external applications. Its function is to exchange large amount of data between application servers; in contrast to the message server which only exchanges applications data thus the amount of information is large. 99. One of the daily tasks is to monitor updates in t-code sm13 update failure is very critical thing and should be notified to the user immediately.

100. Lock entries can be handled by SM12 102. using sapdba / brtools we can extend the table space by adding the datafile. 103. Depend upon the situation it needs to be diagnosed. Check communication between user and application server. There can be two possibilities. /usr/sap file system is full in this case increase the file system from OS level. None of the dialog work process is free, in this case first inspect thru dpmon command restart the central instance. 104. Using SMLG we can set the load balancing. 106. Three types of files are created, Client specific data, client specific text and cross client data 110. TSADM is the user created during configuration of TMS by default and his responsibility for monitoring connecting between the system DEV, TST and PRD. You can change the password through SU01 and type TSADM in the filed and press tab to change the password and set the new password. 111. Through SE06 or reconfigure using STMS as like before. 112. RFC stands for remote function call, RFC is done for communicating between 2 servers preset in local network or remote network. 113. Dialog, Background, Update, Spool, Enqueue, Message server and Gateway Type of roles Single and Composite Assigning Role to the user Way1 SU01 Enter User ID Go to Roles tab and enter the role name Way2 PFCG Enter the Role name go to user tab enter user ID 114. Oracle redo log files do not dynamically grow when more space is needed for redo entries thy have a fixed size (on SAP system, typically 50M) when they current online redo log file become full the log writer process closed this file and starts writing into next one. This is called log switch. Offline redo files are written to the oraarch directory. Moreever offline redolog files should be stored on a mirrored disk to prevent loss of redo information A raid system can be use for this purpose if you loose a disk containing redo logs and data files complete recover is no longer possible. Therefore offline redo logs and data files should be on different disks. 115. After client export, Import the client export requests into the target client with TMS. Log on to the target client and active post import processing. Q. Explain Client compare and maintenance tools available in SAP 116. To use compare function choose t-code SCU0, the compare function enables you to compare and adjust the contents of a table or view in two different client. The objects that canbe adjusted are some of the tables and views that can maintained using transaction SM30 116. Export the Client in Background processing with SCC8 To perform a client export, follow these steps: Use SCC8 and indicate the target system to which the client will be copied. The target system must be defined in TMS as part of the transport domain and begin the client export. To check the status of the export use SE01 Logon on the target client and activate post-import processing with scc7. To display client transport logs use the transport organizer transaction code se09

117. Monitor a client copy with SCC3, Verify the database resources are sufficient, Check the tables using database utility or SQL tools. If you discover an unexplained cancellation or error, check copy log (scc3), syslog (sm21), dump analysis (ST22), job overview (sm37) and possible spool (sp02) 118. Create a New client using SCC4 and logon to your new client with user sap* and password pass and choose SCCL select the source client and choose profiles. Create a scheduled job in background. Create and schedule the job in background, the log is displayed in scc3. 120. The J2EE ports are created via the following formula. Port number = 50000+100*instance_number+port_index Example. : inst num=02 HTTP Port = 50200 HTTP SSL port = 50201 IIOP Intial Context port = 50202 IIop ssl port 502 P4 port = 500206 P4 Http tunneling port -50400 P4 SSL port = 50207 Telnet port = 50208 JSM port = 50210 122. Transport Domain consists of all SAP systems jointly administered through TMS and transport path are centrally configured on the domain controller. A transport domain contain at least one transport group, a transport group consists of one or more systems that share a common transport directory. 123. Increase your buffer size. There are two ways to increase the buffer size Use ST02 and set the buffer size under swap. Change the instance parameter using t-code rz10 and set the buffer size. 124. This is because BI / BW handles large amount of data. The background processes that require to fetch the data from R/3 server require lots of time so if you set the work process time to 600 secs the time would not be sufficient to handle the task. 125. SMLI Language import utility and SMLT language transport utility and sr13 to apply the language but by default only germen and English is available. 126. ztta/roll_first Defines the first part of the roll area that is allocated to a dialog process. ztta/roll_area Defines the total roll area per work process rdisp/ROLL_SHM Defines the size of the roll buffer rdsip/ROLL_MAXFS Defines the size of roll buffer and roll file em/initial_size_MB Defines the fixed size of extended memory ztta/roll_extension Defines the user quota for extended memory abap/heap_area_dia Defines the limit for the amount of local memory allocated to dialog work process abap/heap_area_nondia Defines the limit for the amount of local memory allocated

to non-dialog work process abap/heap_area_total Defines the limit for the total amount of heap memory allocated to all work processes 127. Nametab (NTAB) Buffer contains data derived from tables DDNTT(table definitions) and DDNTF (field descriptions), stored in four individual buffer areas. These four buffers are also known as the Repository buffer or the ABAP Dictionary buffer. TTAB, FTAB, IRBD, SNTAB NTAB: rsdb/ntab/entrycount FTAB: rsdb/ntab/ftabsize SNTAB: rsdb/ntab/sntabsize IRBD: rsdb/ntab/irbdsize The NTAB buffer: If the quality of these buffers falls below 95% , you should try to identify reasons for this decrease in hit ratio. Program Buffer (PXA) abap/buffer_size The program buffer is used for storing ABAP program loads before they are executed within individual work processes. It is also known as the ABAP buffer. The PXA should show hit ratios of 95% or more otherwise you will see, for example a high load and generation time on your SAP instance. Generic Table Buffer The quality of the generic key buffer should be greater than 95% and can be upto 99%. This buffer is also known as the generic key table buffer or the generic buffer. CUA Buffer rsdb/cua/buffersize The CUA buffer stores objects used by SAP GUI, including menus and button definitions. The CUA buffer is also known as the Menu buffer. Usually this buffer plays no significant role concerning the performance of your SAP instance. Roll and Paging Buffers rdisp/ROLL_SHM and rdisp/PG_SHM The parameters rdisp/ROLL_SHM and rdisp/PG_SHM are used to allocate the roll and paging buffer in 8KB blocks. Screen Buffer zcsa/presentation_buffer_area The screen buffer or Dynpro buffer stores generated screens, the so-called Dynpro load. Usually this buffer plays no significant role concerning the performance of your SAP instance. Calendar Buffer zcsa/calendar_area The SAP calendar buffer stores all defined factory and public holiday calendars. OTR Buffer The Online Text Repository (OTR) buffer contains texts used by Business Server Pages, Exception Builder and HTTP Services. Usually this buffer plays no significant role concerning the performance of your SAP instance.

Export/Import Buffer The Export/Import buffer is used to store data that must be available to several work process. The system fills or reads the buffers using the ABAP command. EXPORT TO / IMPORT FROM

SHARED BUFFER. Usually this buffer is only of interest for individual processes, such as in some SAP APO functions. Exp./Imp.SHM The Export/Import-Shared-Memory-(ESM)-buffer contains data put there by the using the ABAP statement EXPORT TO SHARED MEMORY. This buffer might become a performance bottleneck when you see heavy swapping activity for this buffer. If you see no swaps, the buffer is perfect. 128. 1.SICK/SM28 TO FIND THE INCONSISTENCY BETWEEN OS KERNEL ,DB KERNEL AND FIND INCONSISTENCY BETWEEN PATCH LEVELS 2.SE06 a.STANDARED INSTALLATION b.SYTEM COPY OR MIGRATION. SELECT STANDARDED INSTALLATION POST INSTALLATION ACTIVITIES SET CTS AND PERFORM MODIFIBLES SET MODIFIBLES.

AND CHECK

PERFORM

3.SE03(MODIFIBLE AND NON MODIFIBLE) MODIFIBLE ALOW IN ONLY IN DEVELOPMENT SYSTEM. NON MODIFIBLE ALOWS IN PRDUCTION AND QUALITY SYSTEMS. 4.TRANSPORT MANAGEMENT CONFIGURATION. 5.CHECK STANDARDED BACKGROUNDJOBS. 6.BY DEFAULT IN PRODUCTION SYSTEM ALSO CONTAIN SAP*,DDIC USERS WE HAVE TO CREATE SUPER USER, AND CHANGE THE STANDRDED PASSWORD. SET THE PRAMATER login/no_automatic_user_sapstar=0(In Rz10) 7.PERFORM CLINT COPIES IN DEVELOPMENT CUSTOMIZING(CUST),SANDBOX(SAND) QUALITY TEST ,PRE TEST (PTST) PRODUCTION PRODUCTION (PRD). 8.IMPORT THE PROFILE PARAMETRERS OS LEVEL TO SAP LEVEL. CHANGE THE WORK PROCESS PARAMETERS,MEMORY PARAMETERS, LOGIN PARAMATERS AND BUFFER PARAMETERS. 9.SGEN SAP Load Genetar.

10.PRINTERS CONFIGURATION. 11.INSTALL SAP LICENSE. 12.SAP ROUTER CONFIGURATION. WE NEED TO COINFIGURE SAP ROUTER PRODUCTION SYSTEM 13.CONFIGURING SAP LIBERARY. 14.BACKUPS (REGISTRY) OS and SAP.

15.CHECK THE USER OPERATIONS PASSWORD NEVER EXPIRES IS SET FOR SAP ACCOUNTS <SID>ADM SAP SERVICE<SID> 16.START AND STOP SAP SYSTEM. 17.CHECK THE SYSTEM LOGS. 130. Dispatcher 3200 Gateway 3300 Message Server 3600 Printer in windows 515 niping 3298 Router 3299 131. Tables, Views, lock objects and domain are important object types in the ABAP directory. 132. Customizing which is reflected to other clients i.e through out the system is called as client customizing, examples measurement, time zone, date and currently. 133. Make the transport directory available, configure the transport domain controller and define the domain, configuration of transport program(tp) is done automatically and must not be done at OS level, in the TMS include all the remaining systems in the domain , define the transport routes, define QA approval procedure , set the system change options according to the role of R/3 system, Create clients and set the client change options for the production system, development system and so on. 134. Offline redo log files are written to the oraarch directory their names are specified with help of Oracle instance configuration parameters, so the name <DBSID>arch1_<LSN>.dbf is just an example. Create a cron job to run a script to check percentage used / capacity of oraarch direcoty. If it exceeds 80% a brarchive command to archive the logs Archive directory contains all of the SAP information for backup restore purpose. So I suggest you doing list out some questions from your system which is the answer my impact the growth size of the archive files in oraarch direcoty. How much transaction happened by day? Do the system doing extraction data from R3 to BW system Are u doing reorganization table Are u doing client copy Are u sure the archive backup (copy-del_save) run well everyday? Or you may analyze by your self the growth of the files in the oraarch by counting the fiels created by system each day. After that you may make calculation how many files average created each day. Example Created files by day (average) are 100 files (each file 20mb by default) So you will need 100 x 20 = 3gb. Always space more space for archive directory, otherwise if the directory full the sap system will stop responding 135. Print request is given by the end user and it mainly contain data which user wants to print. Spool request contain information regarding printer and is also responsible for formatting of the data which is going for printing and it is stored in spool database but it is stored under TemSE(temporal sequential object) area When spool request is processed by spool work process it is converted into ouput request and is passed to host spool system.

136. Logistics is a chapter in SAP Basis and its full name is software logistics and this chapter describes about transport layers in SAP basis. 137. Basis consultant has to monitor R/3 modules, where R stand for RealTime and 3 stand for 3 layers in SAP as presentation, application and database layers 138. The accessed data will sit in the buffer. If someone is trying to access the same data that will be retrieved quickly from the buffer If the buffer is full and some one is retrieving the data which is not there in the buffer then that data will be placed in the bufeer and the oldest data in the buffer will be swapped for this more number of swaps means more DB hits. If there are more swaps can increase the buffer size. 139. There is no such t-codes to lock a particular table but using SE16 we can check the desired tables. We can lock a table in application Level. If you want that user cant access that particular table then do it via S_TABU_DIS. Identify the authorization group and that table belongs to or you can create a new auth group and add all the table you dont want people to have access and dont give access to that auth group to those users. 140. t-code st06 detail analysis menu LAN check 141. Put the parameter in Default.pfl and remove it from remaining profiles. 142. Table buffer is the type of buffering technique in abap/4 in which records of entire table is buffered. While in single record buffer only one record of the table is buffered. 143. Landscape is like a server system or like a layout of the servers or some may even call it the architecture of the servers viz. SAP is divided into three different lanscape DEV, QAS and PROD. - DEV would have multiple clients for ex: 190- Sandbox, 100- Golden, 180- Unit Test. - QAS may again have mutiple clients for ex: 300Integration Test, 700 to 710 Training. - PROD may have something like a 200 Production. Landscape : is the arrangement for the servers DEVELOPMENT ---> QUALITY ----> PRODUCTION DEVELOPMENT : is where the the consultants do the customization as per the company's requirement. QUALITY : is where the core team members and other members test the customization. PRODUCTION : is where the live data of the company is recorded. 145. If a work process is in hold status then one should know that it is a background work process with V2 with scheduled interval of time specified. 146. check in st02 147. if the user context is get copied in buffer in the roll area into local memory of work process is called roll in and roll out save the user data when process finished or switches. 149. drop table schemaname.tablename; 150. Support package location PAT01 AND PAT03. It will read the control file and the profile initSID.ora and then I will take th backup of control files and the datafiles

151. Any clients created in an SAP system (Dev, Qty and Prod) is spawned from the default client 000. The SAP tables in the client 000 is owned by DDIC and only DDIC can modify it. Hence the support packages are applied using client 000 152. SAP Java stack contain installations of Application server Java (AS Java). SiD for all application servers and the database Startup framework/landscape Database (with difference schemas Java) The usage is for web application services. 153. using SE14 or SE16 and enter the table name select the table name and delete it. 154. Java stack can be applied by JSPM or sapinst.exe /usr/sap/<SID>/JC<00>/j2ee/JSPM . The JSPM screen will pop-up and u have to copy all the patches that are downloaded in /usr/sap/tans/EPS/in 155. Killing a job with core means generating log files for that particular job and killing a job without core mean not to generate an log file for that particular job. 156. already specified the answer in the above pages 158. Program buffer hit ratio is <98% indicating less program access, in that case we have to increase the size of the problem buffer(abap/buffersize) in st02 We can also increase the problem buffer in RZ10 using suitable profile parameter name. If the system is having enough disk size. 159. use SE11 t-code and put the table name and then click the index tab, just copy index name from different system to this system and save it. From DB02 select the missing indexes and click crate on DB. 160. DIA 2, ENQ 1, MSG 1 and UPDATE (V1) Only for central instances and application instances different is there no enq only message server. 161. If the background job runs more than two days, confirm with user first. Using sm37 find the job and details find out instance number on which job is running then using SM51 click on the job and select work process cancel without core. 162. If we have 3 or 4 instances, all instance have individual buffers when some data is updated in the first instance same data should be available in other instance in buffer for maintaining same data in all buffer this can be done using buffer synchronization 163. Unicode mean it support almost all the languages and non-Unicode supports only few languages (may be English, German, dutch and chinees 165. You can change the data file location by using BRTOOLS (rename datafile) or oracle level command alter datafile rename datafile absolution location to target loc Prerequisite: take the datfile offline, copy it to new location submit command and remove the old file. 166. The database data is stored in a logical entries known as table spaces. Table spaces are oracle logical storage objects working like folders that contain database table data or indexes. Every table corresponds to one or more physical data files located on one or more disk. Basis table spaces these tables spaces contain the R3 basis environment data. 167. use sm37 t-code find the jobs and select the job and release again. If you get the same problem inform the user that may be a problem with coding. . 168. Through STMS

169. Add request again in the STMS_IMPORT, make a check of the option import again. STMS_IMPORT EXTRAS OTHER REQUEST ADD. 171. I Faced the below mentioned Error : 1. Object Locked !!!!! This was because one object was loacked in one Request. you need to unlock the object through SE03. 2. Back ground job not scheduled!!!!! Schedule the back ground job, RDDIMPDP by using program, RDDNEWPP. 3. Cannot determine the EPS Parcel : This is because, the SPAM Version cant read the EPS Pracel. Just Upgrade the SPAM Version 4. TP_CANNOT_CONNECT_SYSTEM Upgrade tp and R3trans 172. System log provides information about the warning, errors, user errors and system messages. There are 2 type of files in which the data is stored. Local Log: all the application server data is written here these files get over written. Central Log: logs of the selected application server written here. 173. ST04, SM50, SM66 and SM21 and ST06. rdisp/max_wprun_time is the parameter to limit run-time for DIA work processes. 174. Using SE16. Enter the table name usr02 and execute. Enter * in the bname field and again execute to get the list of the user in the client. 175. There is no need to restart sap system after configuration of operation modes the t-codes used operation are RZ04, SM63 AND RZ03. 176. Daily: online backup of Dev and Qas. Weekly: Offline backup of Dev, Qas and Prd.