SAP R/3 SUPER TECH
SAP TIPS ON TRANSACTION CODES

Created By Debra Olson Copyright © 1998 1999

SAP Super Tech

Do you have tran tips you would like to share? Send me an email LEEOLSON@aol.com

A list of transaction codes may be found in table TSTC. The list with a description of the transaction codes is in table TSTCT (note the 'T' added at the end of table TSTC indicates the text description for the data in table TSTC is in TSTCT.  SAP follows this standard most of the time). The data in the tables may be viewed in TRAN: SE16. Remember, when searching that the description field in table TSTCT is case sensitive.

SEARCH FOR A TRANSACTION WITH TEXT
To search for a transaction code based on the text name of the transaction, use
TRAN: SDMO
This search is not case sensitive in its search criteria so it is much easier to use than searching the TSTCT table.
I received this tip from another SAP'er, by the name of Anju. Thanx for the tip.

COMMAND LINE
The command line is the white box on the upper left of the screen where you may type transaction codes. If your cursor is on the SAP screen, the <CTRL> key will tab the cursor up to the command line.  Sometimes it takes two or three tabs to pop the cursor into the command line.

In the SAP command line, if you want to use a transaction,  type /n<TRANCODE>, for example /nMR00. You do not need to prefix the transaction with a /n, if you are at the main SAP menu. If you want to get back to the main menu, type /n by itself.

If you want to go to the transaction but in a new window of SAP, type /o<TRANCODE>. If you just want a new window of SAP, type /o in the command line. If you have lots of SAP windows open in different clients, be sure you check which client you are in before entering data or you might enter a test invoice in the production system.

If you want to start the transaction in debugging mode - that's where you can step through the code as it executes - type /h<TRANCODE>. You can also type '/h', without the transaction code, from  within any screen of the transaction code to start up the debugger at that point in the transaction code. If you are in debug mode, use /n to end the debug mode.

To end a session, in the command line type /I.

The command line has a drop down box. If you click on the drop down arrow on the command line (or hit F4), you will see a list of the last few transaction codes that you have keyed in the command line. You may click on any one in the list to initiate it. The list in the drop down, is a list of commands that you have keyed in the comman line, not a list of all the transactions you have executed. The list does not contain transaction codes that you have executed via menu paths, or the IMG.

DYNAMIC MENU
From the screen at the main menu in R/3, there is a DYNAMIC MENU button.The DYNAMIC MENU is a hierarchy listing of the menu paths in R/3.  If you click on the DYNAMIC MENU button and expand the nodes below it, the transaction codes are listed next to the menu path node.

DETERMINING A TRANSACTION CODE
To find the transaction code for the process you are in at the time in R/3, go to SYSTEM -> STATUS from the menu and in the pop-up screen, the transaction code will be listed among many other items of interest.

NAMING STANDARDS
SAP loosely uses standards when assigning numbers and letters to create a transaction code . These standards are followed mostly for functional transactions and not for configuration transactions. These standards are not always followed. This is a guideline of how the standards usually work, to give you a starting point on how transaction codes are organized.
A transaction that ends in the number below usually has the function of If a transaction ends in a number, it may perform the function as listed to the left. For example 
00 = main menu

1 = ADD

2 = MODIFY

3 = DISPLAY

MR00 - INVOICE VERIFICATION MAIN MENU

MR01 - ADD AN MM INVOICE

MR02 - MODIFY A MM INVOICE

MR03 - DISPLAY A MM INVOICE

ME00 - PURCHASING MAIN MENU

ME21 - CREATE A PURCHASE ORDER

ME22 - CHANGE A PURCHASE ORDER

ME23 - DISPLAY A PURCHASE ORDER

MB00 - GOODS RECEIPT MAIN MENU

VA00 - SALES MAIN MENU

VF00 - BILLING MAIN MENU

XK01 - CREATE A VENDOR CENTRALLY

XD01 - CREATE A CUSTOMER CENTRALLY

FS01 - CREATE A GENERAL LEDGER ACCOUNT

Transacations Beginning in are these types of transactions
F

M

V

FK

MK

XK

XD

MB

MR

ME

ME1

ME2

MM

VA

VF

FS

FB

O

FINANCIAL 

MATERIALS MANAGEMENT 

SALES AND DISTRIBUTION 

FINANCIAL VENDOR MASTER 

MATERIAL VENDOR MASTER

CENTRAL VENDOR MASTER

CENTRAL CUSTOMER MASTER

GOODS RECEIPT - INVENTORY MANAGEMENT

MM INVOICE VERIFICATION

PURCHASING

PURCHASE REQUISITION

PURCHASE ORDER

MATERIAL MASTER

SALES ORDERS

BILLING

LEDGER ACCOUNTS

SHARED FINANCIAL TRANSACTIONS (SHARED BETWEEN A\P A\R ASSETS G\L)

USUALLY CONFIGURATION TRANSACTIONS (config transactions begin with various letters)


 

Within transactions the following letters have meaning.  These letters also refer to General Ledger account types and are used in naming system tables.
A - assets (first letter fo the German word Anlagengegenstand)
D - customer/ debit type transactions (first letter of German word Debitor)
K - vendor/credit type of transactions (first letter of German word Kredit)
M - material (first letter of German word Material)
S  - ledger (first letter of the German word Soll)

    Deutsch <-> Englisches Wörterbuch  German / English translations
    An Introduction to German for ABAP/4 Programmer

Examples of D, K, M, and S used in transactions - fill # in with D, K, M, or S.
F#01 - CREATE FINANCIAL CUSTOMER, VENDOR, OR LEDGER,
    The F at the beginning denotes a financial transaction,
    The 1 at the end denotes CREATE.
FD01 is create financial level customer accounts.
FK01 is create financial level vendor accounts
FS01 is create financial ledger accounts.

SYSTEM TABLES - note in which letter the table ends
BSIS        Open ledger items
BSAS        Closed ledger items
BSI       Open customer items
BSAD        Closed customer items
BSI       Open vendor items
BSA       Closed vendor items

FINANCIAL MAIN MENUS

F#MN - MAIN MENU where # = D for A\R (customer), K for  A\P (vendor), S for G\L (ledger)
FDMN ACCOUNTS RECEIVABLE (note the 2nd character is a D for customer)
FKMN ACCOUNTS PAYABLE (note the 2nd character is a K for vendor)
FSMN GENERAL LEDGER (note the 2nd character is a S for ledger)

MISCELLANEOUS CONFIGURATION TRANSACTIONS
ORFB - MAIN FINANCIAL CONFIG TRANSACTION VERSION 2.2

This transaction is from version 2.2 and does not contain paths to higer versions of SAP R/3 configuration. For higher versions SAP stresses that you use the IMG (TRAN: SPRO). Nonetheless, TRAN: ORFB is a fast and easy way to get to a lot of the configuration that you need. OLMB - MM INVENTORY MANAGEMENT CONFIGURATION MAIN MENU (NOTE - this transaction ends in MB which is the code for goods receipt)

OLME - MM PURCHASING CONFIGURATION MAIN MENU (NOTE - this transaction ends in ME which is the code for purchasing)

OLMR - MM INVOICE VERIFICATION MAIN CONFIG MENU.(NOTE - this transaction ends in MR which is the code for MM Invoice Verfication)

WEDI - EDI configuration and other EDI stuff.

Please remember that the IMG is the best place to find and document all the configuration transactions - although most implementors I have met, prefer transaction codes.

CALLING A TRANSACTION IN A BDC
Command syntax
CALL TRANSACTION <trancode>
        {and skip first screen}
    using bdc_table
   {MODE <display mode>}
   {UPDATE <update mode>}

    MODE
        A - default, show all of the steps
        E - show only the errors
       N - do not show anything

    UPDATE
        A - calling program continues while the called transaction processes in the background
        S - calling program waits until called transaction code is completed, then the program resumes.

I need a break from SAP

LOCKING A TRANSACTION
A transaction may be locked so that no userid can perform the transaction - even if the userid has authority to perform the transaction. If a locked transaction is performed, an error message pops up stating that the transaction is locked. To lock and unlock transactions and to see which transactions are locked, use TRAN: SM01.

MAINTAINING A TRANSACTION CODE
TRAN: SE93

OSS
OSS1 is the transaction code that takes you into the OSS system which is where you can find information on hot packages, patches, Y2K in R/3, and where you can write to SAP to report a bug. You must get an OSS ID from your system administrator. If something is not working quite right or running long, check out OSS first before spending a lot of time trying to figure out the problem yourself. IT doesn't take long and may save you time.

ONLINE TESTING - Computer Aided Testing Tool CATT
Create test strings, create large amounts of test data = TRAN: SCAT
 
 

Do you have tran tips you would like to share? Send me an email.
 

D. Lee Olson - SAP trainer & implementor:  functional and technical. Working on SAP since early 1996.
15 years information technology experience.
Send e-mail to LEEOLSON@aol.com


Last updated June 23, 1999
Created By Debra Olson Copyright © 1998 1999
http://www.oocities.org/SiliconValley/Program/8650/trantips.htm
For personal non-commercial use only. All rights reserved.