ABAP Tutorials, Guides, Training, Manuals
The following program will help you to search the SMARTFORMS either Standard or Customer created in your compatiable language.
With introduction of ECC6.0, there goes some function modules/BAPIs with the old version. The following procedure defines the steps for displaying Obsolete BAPIs.
Obsolete BAPIs
Hard-coding has been very much an integral part of ABAP coding. Many a times lot of text is hard coded in programs right from select statements to selection screen parameters to more complicated case statements and other conditional statements. The more deadlier hard coding is found in user exits or BTE’s.
Typically during roll-outs the existing programs may have to be modified to include the new company code etc. However it might take lot of debugging to figure out what went wrong if we missed a small exit where very important code was written.
Program Initial Screen
The SQL Trace function is an on-demand log of selected SQL statements that are issued against the database through the Open SQL Engine. The SQL Trace can be switched on or off dynamically. The log format is database independent. Besides the SQL statement text, each log record contains information about the point in time when the statement was executed, its duration, its input parameters and results (where applicable) as well as context information.
The SQL Trace is especially useful for Development and Performance analysis.
ABAP programs are checked statically when they are created and dynamically when they are running. Error states, which are not statically predictable and only occur at runtime are dynamically identified by the ABAP runtime environment. States of this type lead to exceptions. If an exception is not handled or cannot be handled, a runtime error occurs.
