Transaction Codes General Notes

You can execute the following commands in the transaction code (tcode) field with Enter. You will find some useful transaction codes below to work in tandem with the following commands: To call a transaction - In the same session (window) Enter: /nxxxx (xxxx = transaction code). - In an additional session, Enter: /oxxxx (xxxx = transaction code). If you enter this function before any of the tcodes below, you are able to break out of your current screen/business and begin a completely new session. Otherwise, the current business process has to be terminated, and return to the initial user screen (the main menu) has to be initiated before entering tcode spro). /o tcode saves you the effort of having to do this. To end the current transaction Enter: /n. Caution: Unsaved changes are lost without warning To delete the current session. Enter: /i. To generate a session list Enter: /o. To log off from the system Enter: /nend. From John O'Meara OSS Note 0026171 has additional information on OKCodes in SAP, and is a very useful read

BASIS/ABAP
DI02 ABAP/4 Repository Information System: Tables. OSS1 SAP Online Service System OY19 Compare Tables S001 ABAP Development Workbench S001 ABAP/4 Development Weorkbench. (from john.omeara@syskoplan.ie) S002 System Administration. (from john.omeara@syskoplan.ie) SA38 Execute a program. (from john.omeara@syskoplan.ie) SCAT Computer Aided Test Tool SCU0 Compare Tables SE01 Old Transport & Corrections screen SE09 Workbench Organizer SE10 Customizing Organizer SE10 Customizing organizer requests for user (To release for transport enter user name, press Enter. Select changed object and select Release) (from john.omeara@syskoplan.ie) SE10 New Transport & Correction screen SE11 ABAP/4 Dictionary Maintenance SE12 ABAP/4 Dictionary Display SE13 Maintain Technical Settings (Tables) SE11 ABAP/4 Dictionary. (from john.omeara@syskoplan.ie) SE12 Dictionary: Initial Screen enter object name. (from john.omeara@syskoplan.ie) SE13 Access tables in ABAP/4 Dictionary. (from john.omeara@syskoplan.ie) SE14 ABAP/4 Dictionary: Database Utility. (from john.omeara@syskoplan.ie) SE14 Utilities for Dictionary Tables SE15 ABAP/4 Repository Information System SE15 ABAP/4 Repository Information System. (from john.omeara@syskoplan.ie) SE16 Data Browser SE16 Data Browser: Initial Screen. (from john.omeara@syskoplan.ie) SE16 Display table contents SE17 General Table Display SE30 ABAP/4 Runtime Analysis SE30 ABAP/4 Runtime Analysis: Initial Screen. (from john.omeara@syskoplan.ie) SE30 Run Time Analysis (press Tips and Tricks button for good stuff) SE32 ABAP/4 Text Element Maintenance SE35 ABAP/4 Dialog Modules SE36 ABAP/4: Logical Databases SE37 ABAP/4 Function Library. (from john.omeara@syskoplan.ie) SE37 ABAP/4 Function Modules SE38 ABAP Editor

SE38 ABAP/4 Editor. (from john.omeara@syskoplan.ie) SE38 ABAP/4 Program Development SE39 Splitscreen Editor: Program Compare SE41 Menu Painter SE43 Maintain Area Menu SE51 Screen Painter SE51 Screen Painter: Initial Screen. (from john.omeara@syskoplan.ie) SE54 Generate View Maintenance Module SE61 R/3 Documentation SE62 Industry utilities SE63 Translate Short/Long Text. (from john.omeara@syskoplan.ie) SE63 Translation SE64 Terminology SE65 R/3 document. short text statistics SE66 R/3 Documentation Statistics (Test!) SE68 Translation Administration SE71 SAPscript layout set SE71 SAPScript Layouts Create/Change SE72 SAPscript styles SE73 SAPscript font maintenance (revised) SE74 SAPscript format conversion SE75 SAPscript Settings SE76 SAPscript Translation Layout Sets SE77 SAPscript Translation Styles SE80 ABAP/4 Development Workbench SE80 Repository Browser: Initial Screen. (from john.omeara@syskoplan.ie) SE81 SAP Application Hierarchy SE82 Customer Application Hierarchy SE84 ABAP/4 Repository Information System SE85 ABAP/4 Dictionary Information System SE86 ABAP/4 Repository Information System SE87 Data Modeler Information System SE88 Development Coordination Info System SE91 Maintain Messages SE92 Maintain system log messages SE93 Maintain Transaction Codes SE93 Maintain Transaction. (from john.omeara@syskoplan.ie) SEU Object Browser SHD0 Transaction variant maintenance SM04 Overview of Users (cancel/delete sessions) SM04 Overview of Users. (from john.omeara@syskoplan.ie) SM12 Deletion of lock entries (in the event you have you are locked out). (from john.omeara@syskoplan.ie) SM12 Lock table entries (unlock locked tables) SM21 View the system log, very useful when you get a short dump. Provides much more info than short dump SM30 Maintain Table Views. (from john.omeara@syskoplan.ie) SM31 Table Maintenance SM32 Table maintenance SM35 View Batch Input Sessions SM37 View background jobs SM50 Process Overview. (from john.omeara@syskoplan.ie) SM51 Delete jobs from system (BDC) SM62 Display/Maintain events in SAP, also use function BP_EVENT_RAISE SMEN Display the menu path to get to a transaction SMOD/CMOD Transactions for processing/editing/activating new customer enhancements. SNRO Object browser for number range maintenance. (from john.omeara@syskoplan.ie) SPRO Start SAP IMG (Implementation Guide). (from john.omeara@syskoplan.ie) SQ00 ABAP/4 Query: Start Queries SQ01 ABAP/4 Query: Maintain Queries

SQ02 ABAP/4 Query: Maintain Funct. Areas SQ03 ABAP/4 Query: Maintain User Groups SQ07 ABAP/4 Query: Language Comparison ST05 Trace SQL Database Requests. (from john.omeara@syskoplan.ie) SU53 Display Authorization Values for User. (from john.omeara@syskoplan.ie)

Human Resources
PA03 - Change Payroll control record PA20 Display PA Infotypes PA30 Create/Change PA Infotypes PP02 Quick Entry for PD object creation PU00 Delete PA infotypes for an employee. Will not be able to delete an infotype if there is cluster data assigned to the employee.

Sales and Distribution (SD)

OLSD Config for SD. Use Tools-Data Transfer-Conditions to setup SAP supplied BDC to load pricing data VA01 Create Sales/Returns Order:Initial Screen VB21 - Transaction for Volume Lease Purchases (done as a sales deal) VK15 - Transaction used to enter multiple sales conditions (most will be entered here) VL02 - Deliveries

SAP Office
SO00 - send a note through SAP, can be sent to internet, X400, etc

FI Financial Management
FGRP - Report Writer screen FM12 - View blocked documents by user FST2 Insert language specific name for G/L account. (from john.omeara@syskoplan.ie) FST3 Display G/L account name. (from john.omeara@syskoplan.ie) KEA0 Maintain operating concern. (from john.omeara@syskoplan.ie) KEKE Activate CO-PA. (from john.omeara@syskoplan.ie) KEKK Assign operating concern. (from john.omeara@syskoplan.ie) KL04 Delete activity type. (from john.omeara@syskoplan.ie) KS04 Delete a cost centre. (from john.omeara@syskoplan.ie) KSH2 Change cost centre group delete. (from john.omeara@syskoplan.ie) OBR2 Deletion program for customers, vendors, G/L accounts. (from john.omeara@syskoplan.ie) OKC5 Cost element/cost element group deletion. (from john.omeara@syskoplan.ie) OKE1 Delete transaction data. (from john.omeara@syskoplan.ie) OKE2 Delete a profit centre. (from john.omeara@syskoplan.ie) OKI1 Determine Activity Number: Activity Types (Assignment of material number/service to activity type) (from john.omeara@syskoplan.ie) OMZ1 Definition of partner roles. (from john.omeara@syskoplan.ie) OMZ2 Language dependent key reassignment for partner roles. (from john.omeara@syskoplan.ie)

OLE OLE demo transaction OLI0 C Plant MM06 Flag material for deletion. (from john.omeara@syskoplan.ie) Maintenance Master OLMS- materials management configuration menu, most of the Data stuff under this menu is not under the implementation guide OLI1 Set Up INVCO for Material Movements OLI8 Set Up SIS for Deliveries OLMB-Inventory management/Physical Inventory OLIA C Maintenance OLMD-MM Consumption-Based Planning Processing OLME-MM Purchasing OLIP C Plant OLML- Warehouse Management Maintenance Planning OLMR-Invoice Verification OLIQ New set-up of OLMS - Material Master data QM info system OLMW- MM Valuation/Account Assignment OLIX Set Up Copying/Deleting of Versions OLIY Set Up Deletion of SIS/Inter.Storage OLIZ Stat Set Up INVCO: Invoice Verif OLM2 Customizing: Volume-Based Rebates OLMB C RM-MAT Inventory Management Menu OLMD C RM-MAT MRP Menu OLME C MM Menu: Purchasing OLML C MM Menu for Warehouse Management OLMR C RM-MAT Menu: Invoice Verification OLMS C RM-MAT Master Data Menu OLMW C RM-MAT Valuation/Acct. Assgt. Menu OLPA SOP Configuration OLPE Sales order value OLPF OLPK Customizing for capacity planning OLPR Project System Options OLPS Customizing Basic Data OLPV Customizing: Std. Value Calculation OLQB C QM QM in Procurement OLQI Analysis OLQM Customizing QM Quality Notifications OLQS C QM Menu Basic Data OLQW C QM Inspection Management OLQZ Quality Certificates OLS1 Customizing for Rebates OLSD Customizing: SD OLVA C SD Sales Menu OLVD C SD Shipping Menu OLVF C SD Billing Menu OLVS C SD Menu for Master Data SPRO Start SAP IMG (Implementation Guide). (from john.omeara@syskoplan.ie)

Material Management (MM)

MM configuration transactions

Config Related

Possible Values for OK Code box

R/3 note no. 26171 The design of the R/3 System is such that all programs can be called via menu options. In addition to ergonomic advantages (no need to learn transaction codes), this procedure offers greater security, as the menu path tells the user the work area to which a program belongs. Use of the command field should be limited to exceptions. In particular, there is no guarantee that the functionality of the command field is fully supported.

Possible entries are listed below. These are only meant for experts (System administrator). Some of them (for example. "/nex") are dangerous, because they override safety measures. "Normal" users should avoid using the command field at all. It is often easier to call a known transaction with "/nxxxx", but this can be achieved just as simply via a user menu. Direct call of transactions, session handling: o /nxxxx - This terminates the current transaction, and starts transaction "xxxx", for example, "sa38" for reporting. o /n - This terminates the transaction. This generally corresponds to pressing F15 to go back. o /nend - This termiantes all separate sessions and logs off (corresponds to "System - Log off"). o /nex - This terminates all separate sessions and logs off immediately (without any warning!). o /oxxxx - This opens a new session and starts transaction xxxx in this session. o /o - This lists existing sessions and allows deletion or opening of a new session. o /i - This terminates the current session (corresponds to "System - End session"). o /i1, /i2,... - This terminates the session with the number given. o .xyzw - "Fast path": "xyzw" refers to the underlined letters in the menus. This type of navigation is uncommon and is provided more for emergencies (such as a defective mouse). Batch input: The following commands can be entered in correction mode ("Process in foreground" or "Display errors only") when processing a batch input session: o /n - This terminates the current batch input transaction and characterizes it as "Failed". o /bdel - This deletes the current batch input transaction. o /bend - This terminates batch input processing and sets the session to "Failed". o /bda - This switches from "Display errors only" to "Process in foreground". o /bde - This switches from "Process in foreground" to "Display errors only". ABAP/4 debugging: o /h - This switches into debugging mode. o /hs - This switches into debugging mode and activates the debugging of system functions. Buffer commands: WARNING: Resetting buffers can significantly change the performance of the entire system for a long time. It should therefore only be used where there is a good reason to do so. As of release 3.0B system administator authorization is required (authorization object (S_ADMI_FCD). The action is noted in the system log. o /$SYNC - This resets all buffers of the application server o /$CUA - This resets the CUA buffer of the application server o /$TAB - This resets the table buffers of the application server o /$NAM - This resets the nametab buffer of the application server o /$DYNP - This resets the screen buffer of the application server Out-of-date commands:

o Pxxx - From the menu system: Starts the transaction Pxxx - If an ABAP list is displayed: Sends command Pxxx to the list processor (for example, P+, P--, PRI) - From a transaction screen: Sends command Pxxx to this transaction o xyyy (where x is not 'P', '/', '=' or '.') - From the menu system: Starts the transaction xyyy - Within a transaction: Sends command xyyy to this transaction o /*xxxx - Starts transaction xxxx and skips the first screen. So, it has the same effect as /nxxxx followed by ENTER. o =xxxx - This entry is still possible for compatibility reasons, but is no longer supported. o %sc - Searches character patterns in lists (like "System - List - Find String") o %pc - Downloads lists o %pri - Prints lists R/3 note no. 45507 The note summarizes general rules for processing batch input sessions in the foreground. Processing batch input sessions in the foreground is a correction mode. The operator was consciously given more freedom here. You can, for example, branch to other functions and then jump back to the previous screen, data can be edited, data records can be deleted from the session and so on. As a result, processing of sessions in the foreground is very sensitive to operating errors. You should therefore always known exactly what you are currently doing. User errors can, in the worst case scenario, cause data loss. The following points are of special importance: o The window size of the SAPGUI should be set to the standard size before processing the session and should not be changed when you process the session. A resize can also cause various errors when processing batch input sessions in the foreground! In the background, the batch input automatically assumes the standard size (22 lines, 84 columns). o If the session in the foreground is processed to find the cause of a termination in the background, only the ENTER key should be pressed to get from screen to screen. The point of termination can really only be found this way. o There are some valid OK codes with which batch input processing can be influenced (/n /bend /bdel /bda /bde; see note 26171). These OK codes can also be reached via the menu (System - Services - Batch input). o The keys 'Cancel' <F12 or 'Back' or 'Exit' <F15 in batch input mean: the transaction has been processed successfully and is deleted (see note 16629). As of Release 3.0F, a dialog box appears with a query before the action is actually executed. However, the following generally applies: only cancel the batch input prematurely via the OK code/bend or via the system menu (System - Services - Batch input - Cancel'). The session then appears under 'Incorrect sessions' in the overview.