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 BAPI SAP directories structure 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 SE03 SE09 SE11 Transport Organizer (extended view) Transport Organizer Tools (change package/dev class etc..) Workbench organizer ABAP Dictionary

Data browser. view/add table data Business Add-ins(BADI’s): Definition transaction Business Add-ins(BADI’s): Implementation transaction Class builder Program Editor Split screen editor Menu Painter Screen Painter Document maintenance Form painter (SAP script) SE80 Object Navigator ( SAP Development workbench.SE14 SE16 SE18 SE19 SE24 SE38 SE39 SE41 SE51 SE61 SE71 Database utility: Adjust after change to definition. delete…. Recording SM36 Create background job . Enter name of transaction plus name of new/existing variant. SHDB Batch input recorder SLIN ABAP program extended syntax check (full check of programs syntax) SM04 User overview SM12 Lock entries SM13 Update Requests SM21 Online system log analysis SM30 Maintain table views SM31 Table maintenance SM35 Batch input i.e. most development functionality is available from this transaction ) SE81 SE84 SE91 SE93 Application Hierarchy (leads to SE84 for desired area) Repository info system Message Maintenance Maintain Transaction code SHD0 Create Transaction Variant.

add/ mod images(used to put in screen containers) SMX View background jobs SNOTE SAP note assistant (if installed)..) SXDA SAP Data transfer workbench . usually removes the need for manual code changes SNRO Maintain number ranges (use FM 'NUMBER_GET_NEXT' to retrieve next number in range. IMG SQ01 ST02 ST04 Sap Query development Database Tune Summary DB Performance Monitor STMS Transport Management system SU01 SU53 SUIM User Maintenance Retrieve authorization data for object. Select background jobs SM49 External Commands SM50 Process overview (within current server) SM51 Server overview SM59 Display and Maintain RFC destination SM64 Display/maintain Events SM66 Process(session) overview across all servers SM69 External commands(Maintain) SMW0 SAP WEB Repository(binary data) . Installs OSS notes for you. Authorizations. Roles.) SO10 SP01 SP02 Standard text editor Spool list Display your own spool list SPAD SAP Spool Administrator SPAM Support package manager SPAU Modification adjustment SPRO SAP System Customizing. execute after error message is displayed(/nsu53) User info system (New user. User t codes etc.SM37 Background job monitor.

SALE IDoc and ALE development VOK2 Output determination by functional area / output type (Output programs) WEDI IDoc and EDI Basis .

Sign up to vote on this title
UsefulNot useful