ABAP Transaction Codes

ABAP Transaction Codes

A transaction in SAP terminology is the execution of a program. The normal way of executing ABAP code in the SAP system is by entering a transaction code (for instance, SE51 is the code for the ABAP workbench). Transactions can be accessed via system-defined or user-specific, role-based menus. They can also be started by entering their transaction code (a mnemonic name of up to 20 characters) in the special command field, which is present in every SAP screen. Transactions can also be invoked programmatic ally by means of the ABAP statements CALL TRANSACTION and LEAVE TO TRANSACTION. Transaction codes can also be linked to screen elements or menu entries. Selecting such an element will start the transaction. The term "transaction" must not be misunderstood here: in the context just described, a transaction simply means calling and executing an ABAP program. In application programming, "transaction" often refers to an indivisible operation on data, which is either committed as a whole or undone (rolled back) as a whole. This concept exists in SAP but is there called a LUW (Logical Unit of Work). In the course of one transaction (program execution), there can be different LUWs.

Let us see some of the commonly used ABAP Transaction Codes.

AL11
SAP directories structure

BAPI
BAPI Explorer, view all sap BAPI's

BUSP
Project management of SAP enhancements

FILE
Maintain Logical file path definitions

GRANT_CUSTOMIZE
Customize Grant management screens via SAP's BDT(business data toolset) - Must have permission from SAP to use this method of modification

OAOR
Business document navigator (edit ENJOYSAP_LOGO etc for ALV Tree)

OLE
Examples for OLE Processing



PFTC
  Work flow task maintain

SA38
Execute SAP ABAP program

SCC1
Client Copy, copy transport

SCDO
Change Document / Change History

SCOT
SAP connect Administration

SE01
Transport Organizer (extended view)

SE03
Transport Organizer Tools (change package/dev class etc..)

SE09
Workbench organizer

SE11
ABAP Dictionary

SE14
Database utility: Adjust after change to definition, delete….

SE16
Data browser, view/add table data

SE18
Business Add-ins(BADI’s): Definition transaction

SE19
Business Add-ins(BADI’s): Implementation transaction

SE24
Class builder

SE38
Program Editor

SE39
Split screen editor

SE41
Menu Painter

SE51
Screen Painter

SE61
Document maintenance

SE71
Form painter (SAP script)

SE80
Object Navigator ( SAP Development workbench, most development functionality is available from this transaction )

SE81
Application Hierarchy (leads to SE84 for desired area)

SE84
Repository info system

SE91
Message Maintenance

SE93
Maintain Transaction code

SHD0
Create Transaction Variant. Enter name of transaction plus name of new/existing variant.

• < Prev
• Next >