Showing posts with label abap tutorial. Show all posts
Showing posts with label abap tutorial. Show all posts

Thursday, 28 March 2013

Abap Transaction Codes List

Transaction List for Transactions from SE01 to SE100.


Transaction Code Program Name
SE01 Transport Organizer (Extended View)
SE02 Does Not Exist
SE03 Transport Organizer Tools
SE04 Does Not Exist
SE05 Does Not Exist
SE06 Post installation actions for Transport organizer
SE07 Import Monitor
SE08 Does Not Exist
SE09 Transport Organizer
SE10 Transport Organizer
SE11 ABAP Data Dictionary
SE12 ABAP Data Dictionary
SE13 Technical Settings for dictionary
SE14 Dictionary: Database Utility
SE15 Object navigator
SE16 data browser initial screen
SE17 general table display
SE18 BADI builder: initial screen for definition
SE19 BADI builder: initial screen for implementation
SE20 enhancement initial screen
SE21 package builder
SE22 Does Not Exist
SE23 Does Not Exist
SE24 class builder
SE25 Does Not Exist
SE26 Does Not Exist
SE27 Does Not Exist
SE28 Does Not Exist
SE29 application packets
SE30 ABAP Runtime analysis
SE31 Does Not Exist
SE32 Does Not Exist
SE33 context builder
SE34 Does Not Exist
SE35 maintain dialog module
SE36 logical database builder
SE37 function module
SE38 ABAP Editor
SE39 split screen editor
SE40 menu printer
SE41 menu printer: initial screen
SE42 Does Not Exist
SE43 Area menu maintained
SE44 Does Not Exist
SE45 Does Not Exist
SE46 Does Not Exist
SE47 Does Not Exist
SE48 Does Not Exist
SE49 Does Not Exist
SE50 Does Not Exist
SE51 screen printer
SE52 Does Not Exist
SE53 Does Not Exist
SE54 generate table maintenance
SE55 generate table maintenance
SE56 generate table maintenance
SE57 generate table maintenance
SE58 Does Not Exist
SE59 Does Not Exist
SE60 Does Not Exist
SE61 Document maintenance
SE62 short text activation
SE63 standard translation environment
SE64 Does Not Exist
SE65 Does Not Exist
SE66 Does Not Exist
SE67 Does Not Exist
SE68 Does Not Exist
SE69 Does Not Exist
SE70 Does Not Exist
SE71 form printer
SE72 style request
SE73 Does Not Exist
SE74 SAP script format conversion
SE75 SAP script format conversion setting
SE76 sap script form translation
SE77 sap script style conversion
SE78 form graphic
SE79 Does Not Exist
SE80 ABAP Work bench
SE81 application hierarchy display
SE82 application hierarchy display
SE83 Does Not Exist
SE84 object navigator
SE85 object navigator
SE86 Does Not Exist
SE87 Does Not Exist
SE88 Does Not Exist
SE89 R/3 repository maintenance
SE90 object navigator
SE91 message maintained
SE92 system log message maintenance
SE93 maintain transaction
SE94 simulation: customer
SE95 modification browser: object selection
SE96 Does Not Exist
SE97 maintained transaction call authorization in call transaction
SE98 Does Not Exist
SE99 Does Not Exist
SE100 Does Not Exist

Wednesday, 20 March 2013

SAP Architecture



The SAP system is based on the three-tier client-server architecture. SAP called it as SAP R/3 architecture (R refers to “real-time data processing” and 3 represents the 3-tiers or layers of it).


SAP R/3 Architecture


Client/Server Environment
- Server – In SAP terminology, a service means a set of task performed by a software component.  This component can consist of process or a group of processes and is thus called a Server for that service. Also, in other words a Server is nothing but a hardware/software combination that can provide services to a group of clients.
- Client – A software component that uses services is called client. or a hardware/software environment that can make a request for services is client.


Three-tier structure

The SAP three-tier structure consists of Presentation server, Application server and Database server.

The Presentation Server comprises mainly of the graphical user interface or web interface. SAPgui is the presentation server in SAP.  It accepts the input from user in the form of mouse clicks , keystrokes, function keys etc and send these requests to the Application server for processing. The Application Server sends back the result of processing to Presentation server which is showed to user as Output by presentation server itself.
The Application Server interprets and executes the ABAP programs and manages the I/p and O/p. All the ABAP programs runs on the Application server only. The communication with the database server and the presentation server is carried here only. There can be more than one Application server depending on the workload.
The Database Server accepts the requests for data from application server and passes it further to the RDBMS. The RDBMS in turn queries the database and send the result to Database server which then passes the result to Application Server. The DB server consist of One Single database repository for the whole organization.

Based on one’s business requirement, we can configure the servers in different ways. For smaller applications we can place all the servers in the single system itself. Such a configuration is mainly useful for Single user purpose. Also we can have configurations like the presentation and application servers are combined and the database server is separate or the application and database servers are combined on one computer and the presentation servers run separately or all the three Database, application and presentation servers running separately on different systems. The last configuration is most common among the all.




Data Processing @ Application Server
 As by now we know that all the data processing and execution of ABAP programs occurs at its App-server end. Now we will take a look into what exactly happens inside app-server.

SAP Application server architecture

User input is received by the SAP presentation program SAP GUI, converted into SAP standard format and is then sent to the Application server. At application server the input is received by the Dispatcher.
SAP Dispatcher is a Control Agent of the R/3 applications and it along-with the operating system manages the resources of R/3 system. Its main task is to manage the I/p tasks forwarded by presentation server by allocating them the work processes. It also manages the R/3 application resources like buffer areas, work processes etc.
The Dispatcher here adds all the incoming requests to the queue first. It then retrieves the requests from the Queue on FIFO (First In First Out) basis and allots them to the work process(WP). There could be ‘N’ number of work processes in a App-server. Each WP handles a single request at a time. After a WP finishes its task dispatcher allocates another task to the WP. All the communication with DB server and processing and execution of data is carried out by WP itself. Once the data is processed by WP it is sent back to the presentation server through dispatcher. The SAP GUI interprets the data and converts it into user form and displays it as output. 
For processing of tasks work processes requires memory called as Roll Area Memory. Roll area memory is the memory required by WP to execute a particular request. This memory is allocated by WP for that particular request. The contents stored in it includes the variable values, pointers to memory location etc.

The R/3 Database Interface

To handle large chunks of data, usually RDBMS are used which stores the logically related in tables and index them using some primary key. To access the data stored in RDBMS SAP ABAP provides OPEN SQL statements. The R/3 database interface coverts these Open SQL statements into native SQL statements of underlying DB to fetch the records. When interpreting Open Sql statements the R/3 DB system checks the syntax and also optimally utilize the local SAP buffers to store the frequently accessed records.