SAP Business Suite is the latest technology to provide solutions to most Organisational needs.SAP technical consultants are required for various development, troubleshooting & support for the client-specific requirement. In this article, We’ve put together the SAP t-codes list of the most used for analyzing & troubleshoot system issues in SAP ABAP.
Introduction of SAP Technical
As we have already covered, Each SAP module has unique functionality to cater to specific business needs & functionality; A SAP technical module can either be one. Now SAP Technical module generally consists of SAP ABAP for Development, Enhancement, Else SAP Basis, which is nothing but system administration.SAP Security is concerned with authorization and roles.
SAP Basis, SAP Security, and other technical modules are based on ABAP technology. SAP ABAP code also shares some common transactions to support various issues. In this article, we will only look at the ABAP portion of it.
How Does SAP Technical Module it Work?
SAP Technical Module is a specific transaction code or tool that helps technical consultants monitor system performance and analyze ABAP code issues for SAP systems. It provides the ability to manage system resources for daily operations. To make our reader life easy for troubleshooting system issues, We have listed few useful transaction codes .
ABAP was initially an abbreviation for Allgemeiner Reports Aufbereitungs Processor, which is the German term for “generic processing for preparing reports” However, it was later changed to Advanced Business Programming.It is one of many fourth-generation language that are specifically designed for applications.The processing logic that is the core that an application programmer writes is in ABAP. The ABAP processor implements the logic for processing of the application program and connects to the database
Transaction codes are used in SAP to access custom applications easily or to call predefined processes. Transaction codes serve as form of shortcut that can be used in various applications. There are various categories of transaction codes that are classified based on the applications and modules. The most commonly used transaction codes are described below.
SE11,ABAP Dictionary Maintenance
SE11 is used to maintain the ABAP Dictionary. The dictionary contains all the Data that SAP uses in its applications code, such as tables, fields & structures. The editor, which SAP Technical consultants or Developers frequently use, can be used to edit this data dictionary or view the technical data for analysis
SE16N,Data Browser
SE16 is used to display data views. The Data views are used to display data from tables. There are many Configuration tables, Database tables & Transaction tables used by the various SAP Module; we also apply various filters and Operators to sort the database entry. Data views can be created using the following methods:
- Using SE16N
- Create a report from the ABAP Query (using multiple tables)
- Create an ABAP Reports program that uses an existing table based on query results (for example, when you want to send an e-mail with results from your query).
SE38,ABAP Editor
SAP SE38 is a transaction code used to edit the source code of an ABAP program; hence it called ABAP Editor.It is used to make changes to the source code of an ABAP program, such as adding or deleting lines in a file. If you want to add new functions, you can use this transaction code to create them by adding them to your existing application files. Also, you will be able to execute any program using ABAP Editor
SE37,Function Builder
SAP Function Builder is a tool for creating Function modules. Function modules enable you to encapsulate and reuse global SAP System functions. They are kept in a centralized function library.It is used to define functions and implement them in ABAP programs.
SM30,Table Maintainance Generators
The transaction code for creating a table maintenance generator is SM30. It is used to display and update table entry data.This transaction is used to maintain (generated) table views and to display the generated table views. It is also possible to use it to create a new table view.
SM34,Maintain View Cluster
SM34,Maintain View Cluster, is used to maintain view clusters. A view cluster is made up of one or more multiple tables that have been joined together to create a single view of data from the various tables in the database
SM35,Batch Input Monitor
The SM35 can be utilized to run batch in-sessions. SM35 is used to monitor the batch input and what is happening with the batch input. Sessions can be created through BDC, LSMW, or any other batch-input ABAP program. The administrator must keep tabs on each session’s Batch Input Logs
SM36,Batch Jobs scheduling
SM36 is used to schedule background jobs, which will be used in the background work process to keep the system performing optimally.
SHDB,Transaction Recorder
SHDB can be described as the Tcode that is used to records the transaction to allow transfer of data. as well as developing the skeleton programs which contain the required code to create batch input sessions.
WE19,Test tool for creating and converting an IDOC.
WE19 is known as an IDOC Testing tool because it creates and simulates an IDOC in the development or quality environment in order to debug or analyse errors and fix them.
BD64,Distribuation models
The distribution model BD64 is used to store the details about the sender , receiver, and the type of data you are sending via IDOC
LSMW,Legacy System Migration Workbench
The Legacy System Migration Workbench (LSMW) is an tools.It is recommended by SAP that it is possible to transfer data only once or at intervals from older systems to the R/3 System. Transaction
BDC,Batch Data Communication
BDC (Batch Data Communication) often referred to as Batch Input can be described as a method to input data in a large quantity in which data input to SAP screens is then simulated.
BDC lets you perform update of databases in the background, using the standard SAP transactions. The resultant entries will look identical to when the user manually entered the information via SAP and will not bypass any of the traditional SAP verifications, consistency checks, authorizations and authorizations, etc.
User Exits
If we require a feature that isn’t available in SAP. What do we do. SAP offers User Exits ,to stop changes, SAP has provide some exit points for customers to integrate their own program .
Exiting users is a routine process that SAP permits you to include to other customized programs without impacting the existing SAP programs.User exits permit developers to access and alter elements of the program as well as data objects that are part of the SAP System in the standard SAP System.
Forms
The Transaction Code for SAP script is SE71 and the transaction code for Smartform is Smartforms .SAPscript along with Smartform are the tools that SAP offers to create layout sets.
Debugger
It allows for inspections and validations of code by showing data objects and aids in examining the flow logic of code.
SAP Notes
provide urgent corrections and solutions for minor issues from SAP Marketplace .
Runtime Analysis
Its shows the time it takes for the system to run ABAP code, from a few statement to a full transaction. It is also helpful to understand the System and data retrieval time from the database. T- Code is SE30.
SQL Trace
It helps to identify the tables used to retrieve data by activating the trace with ST05, and then executing the function.
Conclusion
The SAP Technical Transaction Codes are used for various purposes like to maintain table views, view cluster, batch input monitor and ABAP Dictionary Runtime Analysis.Transaction codes are useful for SAP Technical consultant to perform analysis
What is the difference between se11, SE16, and SE16N?
SE11:Â This transaction is a generic transaction for data dictionary where we can maintain all data dictionary
Â
SE16:This transaction is used to see the content of the table , table maintaince is not possible
Â
SE16N:This Transaction is an SAP enjoy transaction with a much more users friendly appearance .it support custom controls in the Form of ALV
How do I find the complete list of T-Codes within SAP
It’s hard to keep track of all the T-Codes that you require to know in SAP and, even more difficult to keep track of all the possible T-Codes. As per members of the SAP Community you can access the complete list of T-Codes that are available in the SAP application using an overview table
Enter the T-Code “SE16” in the command bar. Press enter.Type in “TSCST” in the field that says “Table Name” and press enter Leave those fields marked “TCODE” along with “Maximum Number. of Hits” empty, Click on the execute button
You might also like the below articles.
