For instance, an instructor-led course that lasts 3 days can cost several thousand US dollars. Therefore, many individuals who want to learn SAP prefer to gain knowledge through self-study using books or tutorials published online.
However, in the global education we starting to see more and more trends towards democratization of education and free availability of training courses from one of the best universities in the world. For instance, the projects like Coursera bring training classes from the top universities to everyone with an internet connection.
Have not heard about Coursera yet? Try to Google it because it is a really interesting initiative. They still earn a lot of money on SAP training courses and it does not really make sense to offer video versions of those courses for free. Nevertheless, the situation is slowly changing and the first indicator of this change was the introduction of SAP Learning Hub. Overall, it consists of more than 2, manuals and handbooks as well as a selection of live courses.
SAP Learning Hub was originally introduced in and now counts more than customers and 13, subscribers. Subscribers of the hub can engage with SAP instructors, subject matter experts and peer students in a convenient social learning environment using their access credentials. Before this learning hub became available, there was no way to purchase SAP training books separately.
It was definitely not the most customer-friendly and convenient way for distributing the text-books and manuals. Especially, if one did not want to pay the high price of the SAP training and only wanted to download PDF versions of the books. At the moment SAP Education offers four types of subscriptions:.
The different types or editions of the subscription are intended for diverse segments of people. Show related SlideShares at end. WordPress Shortcode. Share Email. Top clipped slide. Education Technology Real Estate. Related Books Free with a 30 day trial from Scribd.
Related Audiobooks Free with a 30 day trial from Scribd. SAP Basis Training 2. Transaction AL All the following transactions explored using the Menu tree under Tools.
Transaction SM02 In this transaction you can send messages to users who are logged in and new users logging to the client. This message is a client specific and can also be language specific or generic. In the first 3 lines you maintain the text to be communicated, then server name is the chosen from the list, in Client you maintain the number of the client for which the message to be sent and the language can be maintained so that only to those users who are logged in that language will receive the message.
By default the system has Expiry date and time of the current day and Deletion date. This can be changed according to requirement. Transaction SM01 This transaction is used for the control of transaction code in case the business requires that the users who are authorized to carry the transactions are to be stopped temporarily.
Transaction SM28 This transaction is to perform check the SAP system installation does not contain errors during the process of installation, which if any needs to be attended. This is one time activity after the installation only. This is setup according to the requirements and type of connection.
Client number User name Password On maintenance after save, the connection Test can be performed to check the connectivity is properly established and the time taken. Again this is a onetime operation after the SAP system installation. This is a controlled transaction which is to be authorized userid only. A client has various characteristics that are maintained considering for which purpose the client is used.
In the picture above, the client is means the transactions that are carried in this client is only accessible for users assigned to this client. Logical system is a value which has dependency in the transactions as it gets tagged with the transaction data, if any change is done then the relevant data will be lost even though exists in the system.
Hence making a change of the logical system once defined is not to be done in Production system. Client role defines for which purpose the client is used for, it can be In Development the client is set as Customizing client, client set as Test client and client as test client.
We also control here whether in this client changes can be carried out by authorized consultant, it can client dependent objects or client independent objects. Does the client is protected or not protected for over writing.
The checkbox at the bottom can be set according to the requirements. To protect from changes during client copy and performing a upgrade of software. Firstly the with test run checked in the program is executed in frontend or in background to verify the system has sufficient resources in terms of space, memory for completing a successful client copy.
Transaction SCC3 This can be used to monitor the process of client copy that is running in background or check the log of front end process. Transaction SMGW In this transaction we can monitor the status of the gateway service sapgw00 on the SAP system for all clients, it is a status at that point of time and is dynamic in nature.
The change request containing client dependent objects that are modified in one customizing client be imported to testing client You enter the source client number from where it is to be imported and enter the transport request, check include request Subtasks. This lists all the work process with their type, current status, and program, user id, action being performed at that point of time.
This is always dynamic and a good screen view is to have work processes free waiting so that any call by a user can be taken up immediately without any delay in response time. Transaction SM51 In this transaction, we can monitor the sap system instance whether it is active and the various types of work processes are configured on the system. This Kernel lists all those errors that were fixed by SAP in this patch level. Transaction SM04 By this transaction we can check how many users are logged into the system and in which client and how many session each user is generated and in each session what transaction is being executed.
We also have the time when this session was started. The terminal used by the User, type of connection and the amount of storage space utilized by the user depending upon the transaction and selection options. In this transaction we can pick particular user and end the session if required. Transaction SM13 In this transaction we keep track of the status of the Update service is Active, in case it is not active then we activate from the Update Administrator.
To monitor the list of updates that have failed we can choose the period using From date and execute either F8 or click the execute button. If any updates failed records are found then, we can determine reason for the failure and contact the user and provide information. After fixing the reason for error, the record status can be reset and Repeat Update can be executed for entry in database Else the record can also be deleted from the listed and the user can post the same transaction for the same data set to get desired update in the database.
Transaction SM12 By this transaction we monitor the master data or transaction data that is locked exclusively for a particular SAP user id for performing modifications at that point of time. In such case, other users who try to access the same data set will be stopped by the Enqueue service giving information of the data being locked by the User id.
The related table and other information is provided also the time from when this is locked. If you double click a line then we get further details like in below picture. A decision can also be made in case under certain circumstances it makes to delete the lock for the data set. Then we can do it using the icon Delete. Transaction SM35 To monitor the batch sessions that are created by the users from different modules transactions.
In this transaction we can start the processing of a session, release a session that has stopped with error and delete a session if required. As shown in the screen filter on date, created by can be applied to reduce the list of sessions to review. In case a session is ended with error, then using the Flag icon the session can be released for re-processing. The session can be processed in the front end mode where the data set of the session can be viewed how it is being processed by the program in different screens depending upon the transaction code for which the session was created.
The values that can be maintained is the From Date The list can be restricted for Problems Only, Problems and message and All messages. The information in this list can further used to analyze the errors which are indicated with Red sign under Priority. Also we get information of Tcode that was used by the user when the error got generated. This each record indicates the reason for the error, transaction code, variables that caused the error.
The types of error can be of various kinds for which action is to be taken to fix this error from happening again after analysis. Transaction ST01 By this transaction, we can set the system trace on to analyse by checking the required parameters and activate the trace ON for a period. The trace is normally kept off as this involves the storage space, it is activated for a short period of analysis and then Trace is set to OFF.
After this using the analysis can be made on the data that is recorded during the Trace period. Transaction ST05 This transaction is used to set performance trace for a user or all. With this on activation of the trace the user transactions gets captured in to the trace file with information on the program name, table name, records fetched against each SQL command the system performed with the variables according to transactions and values.
The data captured in the trace is used for analysis and see duration taken for the execution of each SQL, table accessed, program name, Action, number of records, return code. Here we have different variants which can be used for analyzing the data that is captured on a daily basis, then weeks and Month basis. Transaction ST02 By this transaction we monitor the various parameter setting and utilization factors in size or percentage that is maintained for buffering.
Doris Karapici. Hi Marco This is very helpful. Thanks for sharing with us. Br, Doris. Like 0 Share. Right click and copy the link to share this comment. Fabian Runge. Hi Marco, a colleague and me tried the same method as you but our viewer looks a bit different and doesn't offer the download option.
Hello, I suspect this is related to the edition. Regards Marco. Marian Pcolinsky.
0コメント