Here is an overview of the most significant changes in the context of ABAP core development scenario that relate to the:
Automatic Syntax Check*
The automatic syntax check is activated in the preferences by default.
More on this: Checking ABAP Syntax
Automatic code completion*
The automatic code completion is activated in the preferences by default.
More on this: Getting Support from the Content Assist
Developer and SAP object registration
For registering a developer and manual changes to SAP objects like database procedure proxies, SAP HANA transport container, external views, Core Date Services (CDS) entities in an ABAP system an access key is required.
Converting local variables to attributes
Moving a definition of a local variable, type or constant to the private section of the current class. This enables you, to make the variables available for all methods within an ABAP class. More on this: Converting Locals to Class Members
Declaring inline variables explicitly
Converting inline declarations of one or several variables to a local variable in the corresponding method definition.More on this: Declaring Variables from Usage
Changing visibility of members
Moving a member definition between the public, protected and private section to change its visibility in your source code. More on this: Changing Visibility of Members
Extracting constants
More on this: Extracting Constants
Extracting variables
More on this: Extracting and Converting Variables
Creating method implementations from the method definition
Generating the implementation part of a method from an existing declaration in the definition part of an ABAP class
More on this: Creating Method Implementations from the Method Definition
Creating Method Definitions from Implementation Parts
Generating the declaration of a method directly out of the implementation part of the corresponding method of an ABAP class
More on this: Creating Method Definitions from Implementation Parts
Creating Implementation Parts for Unimplemented Methods
In SAP NetWeaver 7.0 EHP3 / 7.31, you can only create the implementations for unimplemented interface methods.
In SAP NetWeaver 7.4 and subsequent releases, you can only create the method implementations in certain situations.
Creating Methods from Method Calls
In an ABAP class, generating the missing method definition and implementation part from the method call
More on this: Creating Methods from Method Calls
Creating classes or interfaces from the source code
In the source code of an ABAP program, triggering the creation of a global ABAP class or interface directly from the usage of the missing class or interface
More on this: Creating ABAP Classes or ABAP Interfaces from Usage
Providing source code in another system
Now, the Transport Organizer view is integrated with the basic functions of the SAP GUI-based Transport Organizer. For each system node, it provides access to the complete object list of the logged-on user. This allows you, to perform the basic developer operations such as running consistency checks or releasing transport requests and tasks.
More on this: Transport Organizer
Documenting ABAP source code
ABAP doc comments are additional information that can be added or imported to ABAP classes, ABAP interfaces, ABAP programs, or ABAP function groups. ABAP doc comments are added with ''! in the ABAP source code and can be rendered in the ABAP element info view or in a tooltip.
More on this: Editing Comments in ABAP Source Code
Analyzing call sequence with the Call Timeline tool
The ABAP Profiler comes along with a Call Timeline tool, which visualizes the trace events and time consumed in form of a diagram. In general, the appearance of the trace events in this graphical tool corresponds to those in the Call Tree tool. The horizontal of the diagram displays the temporal sequence of each trace event measured, whereas the horizontal represents the call depth within a call hierarchy. In contrast to the Call Tree, the trace events however are represented not as discrete tree nodes, but as a continuous sequence. The advantage of the new tool is the graphical representation and a quick detection of eye-catching patterns.
Displaying call stack aggregation
The ABAP Profiler provides you with a further analysis feature, which is especially relevant for central or framework components. Starting from the Hit List, you can Display All Executions of a performance hotspot in the list. The resulting view displays more details for each individual trace event execution. The new property Stack Id allows you to analyze the executions in relation to their call stack. Furthermore, the context menu action Show Stack Aggregation allows you find out how, for each individual stack, the trace event executions are distributed.
Analyzing database accesses
Whenever the database portion of the overall runtime distribution is (unexpected) high, you may want to find out, which database accesses cause it to happen. The Database Accesses tool allows you to identify and analyze the top consumers during the database accesses. It provides you with a list of tables that are used when running the application in question. In addition, detailed information for each database access (such as, access type, buffer settings, duration of table accesses) is provided.
More on this: Analyzing Database Accesses
Analyzing ABAP exceptions in the debugger
The Variables view of the Debugger now allows you to open an ABAP Exception view to analyze details of a selected ABAP exception object.