Icons/Buttons used in SAP
Take a look at all the icons in SAP using transaction ICON. A technical view can be found via the include named ’ICON‘. Sequences of characters begin and finish with the symbol @. Even plain files under the operating system can contain those strings.
If you have a sufficient level of authorisation, you can change the characteristics of a particular client on a server. Even if you are unable to change the settings, it can be useful to display the details. The transaction code is SCC4. It will give you a listing of all the clients available on a server. Double-click on any one to take you to the characteristics for each client. You will see the client role or status of the chosen client, how changes to the system are set for transports, whether client independent changes are allowed, what protection levels are in place and what restrictions are placed on the client for CATT procedures, client copies and system upgrades.
The data browser is a useful and well known tool for looking at data held on SAP. The transaction code to use is SE16. You will be asked to enter the table in which the data resides. The PA data viewed on each infotype is held on table PA0008 for infotype 8, PA0001 for infotype 1 etc. The org mgt. data is held on tables HRP1000 for infotype 1000, HRP1001 for infotype 1001 etc.
It is useful to change your default settings for viewing the data output. At the bottom of the screen you will see the default for the width of output list and the max. no of hits. Change these values using the menu path Settings 
User Parameters. You can also toggle the field title between field text (normal name) and field name (technical name).
Click on the icon "number of entries" to give you an indication of the maximum number of hits that could be output. Your query will only output the maximum stipulated in the default "max no. of hits".
Use the menu path Edit > Download, to download the file into an excel spreadsheet.
Remember that there is an alternative data browser available in SAP called by transaction SE16N.
To get an overview of all the users currently logged on, you can use transaction code SM04 or menu path:
Tools
You will see all the users. Clicking on the user name and then the icon "user info" will give you the name, department and extension of the chosen user. Clicking on the icon "sessions" will give you an idea of what transactions the user is busy with in each session. Click on a session, then click on the icon "end session" to eliminate a particular session for that user. You can use this for a session that might have hung for some reason. You may not have sufficient security access to end a user's session.
If you wish to terminate your own session, which may have hung for some reason, you can always click on the Windows button at the top left hand side of screen. You will then get an option to stop the transaction.
If the system gives you an ABAP runtime error or short dump as it is commonly known, you can retrieve these for either the current or previous day for any user. You will see how many short dumps have taken place over the 2 day period. The resultant output gives all the users who have encountered a short dump. You can use the search option to find your entries.
Transaction code: SPAM
Using this transaction you can apply various LCP's (patches) to your system and, in addition, see the latest patch level which has been applied.
You can see the following details:
- component ID
- release
- patch level
- highest support package
- short description of the component
You are able to see the different patches within the directory structure including all patches which have been applied, aborted and those that are new. If you wish to see what is contained in an LCP, double-click on any once you have displayed it.
Having problems pointing to the SAP help files - look at the file sapdoccd.ini and change the necessary file paths.
If you can't access the help files and can access the Internet, you can log on to the web site http://help.sap.com to get all the available SAP help files.
You can create system messages using the transaction code SM02. You can create, modify, display and delete messages. The system displays a message only once to each user during a logon session. Messages are displayed to users as each user logs on or as soon as you post a message, for users who are already logged on. A user must clear a system message from his or her screen before continuing to work. Messages can be set to expire on a certain date at a certain time.
If you wish to insert a permanent message on the front end screen on the SAP GUI you can do so for version 4.6 onwards.
Before Release 4.6 the logon screen, program SAPMSYST screen 0020, modified for this. As of Release 4.6, no modification is necessary any longer.
As of Release 4.6 it is possible to display user-defined texts on the SAPGui logon screen. Go to Transaction SE61 and select the document 'General text' (selection via F4 help), and create a text with the name ZLOGIN_SCREEN_INFO in the language defined with profile parameter zcsa/system_language. If the text does not exist in the system language, no output is made. There is space for 16 lines with 45 fixed-font characters each or for approximately 60 proportional space font characters on the logon screen.
Title lines (recognized by means of format keys starting with a 'U') are highlighted in the display.
You may also output icons at the beginning of lines by using an icon code (for example, @1D@ for the STOP icon). You can get a list of icon codes from Report RSTXICON. Pay attention to the codes with two '@' symbols displayed by the report. You cannot include text symbols. The 'include indicator' cannot be used for this function.
Creating/changing this text requires a changeable system. Therefore, for production systems, SAP recommends maintaining the text in the upstream system and then transporting it. To do this, select a transportable (customer) development class when you create the text and save the active version prior to the export. The transport is done via the transport object R3TR DOCT ZLOGIN_SCREEN_INFO
Warning
If you modify screen SAPMSYST 0020 (in older releases), then note that you may only insert text elements. Changes to the flow logic, for example, by inserting subscreen, force a change in program SAPMSYST. SAP strongly recommends not changing the system program SAPMSYST because by doing so, serious problems may arise (for example, the dialog logon is no longer possible!)
If you would like to keep a log of all report starts, you can do so by inserting the relevant report in table V_T599R. After inserting the report, you have the option of ticking the checkboxes "record online" and "prot batch". The first tickbox relates to reports started in foreground, whilst the second relates to reports started in background.
To view the statistics of any report starts (where the reports have been inserted in step above) use the report RPUPROTD (display option).
To delete any of the logs use the report RPUPROTU (update option).
To retrieve a previous short dump output on the screen, use transaction code ST22. This gives you an indication of the number of short dumps for the current and previous day. Click on the jigsaw icon (selection) to specify the following:
- Date
- Time
- Machine
- User
- Client
- X=Keep - save a particular short dump which will be kept on the system for longer than 2 days
- Error
Output Controller - Viewing Spooled Print Jobs
To view print jobs that were not printed immediately, use the transaction code SP01. This takes you to the screen which defaults your user ID. Change any of the settings to get a specific print. You can then select one and print it out. The resultant output gives you the status for each print - wait, process, completed, failed etc.
To get a view of background jobs on the system use transaction code SM37. The selection screen allows you to select on job, user, start date, end date as well as the possible status that a job may have.
From the resultant output, click on the job and then on the icon "job log". This will let you know when the job was started, when it finished and what variant was used.
To see the specific entries for the variant, click on the report and then click on the icon "steps". Click on the program and then use the menu path Goto > Variant. If you click on the icon "change" you will get to see the same selection screen for the program that was used to run it.
Finding the Menu Path from the Transaction Code
If you wish to know what the menu path is, for any given transaction code, you can use the transaction code "SEARCH_SAP_MENU". This allows you to insert either the transaction code or a free text entry. This only works for versions 4.6 onwards.
Modification Adjustment: Object Selection - used in conjunction with SPAM. Also use transaction code SPDD which is run in addition to SPAU after Support Packages have been loaded.
Checking whether OSS notes have been applied
You may want to know if a specific OSS note has been applied. You can do so by checking to see which support package the note is contained and then checking on SAP what the latest support package (HRSP) has been applied to your system. You can do this by using the menu path: System Status and then clicking on the magnifying glass under your version of SAP.
Specific notes can be applied using the transaction code SNOTE. Using this same transaction code, you can check to see whether an individual note has been applied. Once having entered the transaction code SNOTE, use the menu option: Goto SAP Note Browser. Enter your selection criteria and you will see the status of the note in question.
For the most detailed documentation within SAP, you could use command SE38 and execute program RPDSYS00. Accept the defaults and execute the program. This will give you the HR System Documentation.
Select PRCL.* for Processing Classes. The key XXYY is XX=Country number YY=Processing Class number. Canada Processing Class 01 will be 0701.
If you want to know about processing classes used in Time Evaluation (Overtime) SAP Labs Inc HR team have written an excellent analysis of setting up overtime and the use of Processing Classes for that.
Integrating SAP with MS Outlook
Wanting to know how to Integrate SAP R/3 Human Resources Module to MS Outlook.
Install SAP MAPI Service provider in Outlook and provide the R/3 connection details. In Outlook use the menu path:
Tools
Choose SAP MAPI Service Provider. It comes with the R/3 Presentation Server.
Newer versions of SAP make use of SAP Connect. See the article on SAP Connect elsewhere in the Knowledge Base.
Applying new Patches to your SAP GUI
If you need to apply certain patches to the GUI on your laptop or desktop then after having downloaded the patches from SAPNET, create a DOS session - to do this you need to go to the Start icon of Windows and choose the menu path Run. Type cmd in the dialogue box. This then opens up the DOS session. Type in the following after the prompt c:\Programme\SAPpc\netinst\sapsetup /patch
Use a different path if your SAP GUI has been loaded into a different sub-directory.
If you wish to find out the following information on a particular user: what reports they have executed, which transactions they have been into on a particular date, etc.
You can find out all this sort of information by using transaction ST03
Choose Performance DataBase. Choose "TOTAL". Choose any particular month. The workload overview report appears. Choose Transaction profile. Transaction report appears with the transaction names and usage - listed in descending order. Double click on any transaction to find the different users who accessed that particular transaction code.
No comments:
Post a Comment