ABAP Keyword Documentation → ABAP − Release-Specific Changes → Changes in Release 6.10
Other Changes in Release 6.10
1. Dynamic parameter transfer using CALL FUNCTION
2. New relational expression IS BOUND
3. Rejected/negated operators in logical expressions
4. Unconditional exit from a processing block
5. Extended/advanced search of/in the keyword documentation
6. Runtime analysis
7. Calling predefined arithmetic functions
8. Transformation of XML data into ABAP variables
9. Displaying the generation limits in the program check
10. Increase in line length in the ABAP Editor
11. Enhancement of the MESSAGE statement
12. Displaying exceptions for runtime errors
13. Separate logical units of work for application und generation
14. Minimum and maximum values for elementary data types
15. Indicator for a component in the structure buffer
16. Reading a program title
17. New medium for data clusters
18. Selecting und deleting data clusters
19. New additions for INSERT REPORT
Other versions: 7.31 | 7.40 | 7.54
Modification 1
Dynamic parameter transfer using CALL FUNCTION
By using the PARAMETER-TABLE itab addition you can dynamically fill the interface of a function module with parameters. With the
EXCEPTION-TABLE itab addition, a table of exceptions
is transferred to the called function module. At the same time the numeric value, which is to be assigned
to the system field SY-SUBRC after the exception has been triggered, is transferred with the VALUE component.
Modification 2
New relational expression IS BOUND
The relational expression IS BOUND indicates whether a reference variable contains a valid reference.
Modification 3
Negated operators in logical expressions
A new word order has been introduced for the negation of logical relational operators. Instead of IF NOT (f IS INITIAL) the spelling IF f IS NOT INITIAL is now possible. This word order is available for the following operators:
Modification 4
Unconditional exit from a processing block
Using the new statement RETURN, a processing block will be exited unconditionally.
Modification 5
Enhancement of keyword documentation search
The keyword documentation has been enhanced in such a way, that more general terms like RADIOBUTTON,
INNER JOIN or FOR ALL ENTRIES are now also processed.
Until now the system only searched for keywords like DATA or CLASS.
If a number of documents contain the same term, the search can be limited in the hit list. A further improvement is that the system displays the found document at the relevant point.
Modification 6
Runtime analysis
Now the Runtime analysis can also be called within a program unit, by calling the methods ON/OFF from the class CL_ABAP_TRACE_SWITCH. Additionally, Restrictionsnow has an input help for program types and the Tips and Tricks interface has been completely redesigned and now includes a tree structure and a text editor.
Modification 7
Calling predefined arithmetic functions
In expressions, the arithmetic functions can be used at the same positions as functional methods. The following are supported:
Modification 8
Transformation of XML data into ABAP variables
Another new addition is the CALL TRANSFORMATION statement, which allows the transformation of XML data into ABAP variable contents. The following transformations are possible:
Modification 9
Displaying the generation limits in the program check
If you follow the menu path Program → Check → Generation Limitin the ABAP Editor , then the system displays the load size and the available kernel resources for the selected program.
Modification 10
Increase in line length in the ABAP Editor
In future the maximum line length in ABAP programs will be 255 characters as opposed to the previous 72. Literals or instruction lists that exceed a line of 72 characters now cause a syntax error. However, this only affects programs that are processed in an editor with a line length of more than 72 characters.
Modification 11
Enhancement of the MESSAGE statement
The form MESSAGE msg TYPE t is a new addition to the
MESSAGE statement. It causes a direct output of character
strings or other strings. This option is designed for exception classes, which have exception texts of data type STRING.
You can also now use the addition DISPLAY LIKEto change the icons in the display of the message.
Modification 12
Displaying exceptions for runtime errors
The display of runtime errors now includes the columns Name of Runtime Error and Exception. The same fields are also displayed in the short dump and explained, immediately after a runtime error was not caught.
Modification 13
Separate logical units of work for application und generation
If a program was not changed by its own logical unit of work
(LUW), then when it is first used, generation is started
in a separate work process. The system generates the program in the same work process only if no other is free.
If, for example, changed programs were used in a background process, then these were only accessible to other users after the background process was finished. After the program was generated, the system could not trigger a COMMIT WORK, since this may have caused inconsistencies in the data of the background processing. The separation of application and generation now ensures that a program is available to other applications immediately after it is generated.
Modification 14
Minimum and maximum values for elementary data types
The class CL_ABAP_EXCEPTIONAL_VALUES provides the methods GET_MAX_VALUE and GET_MIN_VALUE, which are used to establish the value ranges of the elementary data types. These methods replace the function module MAXIMAL_VALUE_GET.
Modification 15
Indicator for a component in the structure buffer
Previously, if you used ASSIGN COMPONENT
to access components of a Dictionary structure, then up to now the statement DESCRIBE
FIELD ... HELP-ID returned the name of the corresponding data element. Now the field symbol contains
the actual component name of the dictionary structure. The following program now displays the value TRDIR-NAMEinstead of PROGRAMM.
program TEST_STRUC.
data MYDIR type TRDIR,
HLPID(61) type C.
field-symbols <FS>.
assign MYDIR to <FS>.
assign component 1 of structure <FS> to <FS>.
describe field <FS> HELP-ID HLPID.
write / HLPID.
Modification 16
Reading a program title
Previously you obtained the program title from the ABAP text elements using the READ TEXTPOOL statement. For performance and buffering reasons the program title is now read from the table TRDIRT.
Modification 17
New medium for data cluster
The statements EXPORT
and IMPORT have been
extended by the SHARED MEMORY medium. In contrast to the variant SHARED
BUFFER, whose memory is automatically adapted after a displacement procedure, you must explicitly
manage the memory with this kind of storage. To do this, you can use the statement
DELETE FROM SHARED MEMORY or a method of class CL_ABAP_EXPIMP_SHMEM.
Modification 18
Selecting und deleting data clusters
There are new methods in the following classes for selecting and deleting data clusters.
Modification 19
New additions for INSERT REPORT
The following new additions are available for the INSERT REPORT statement:
... KEEPING DIRECTORY ENTRY
... DIRECTORY ENTRY trdir
... UNICODE ENABLING uc
... FIXED-POINT ARITHMETIC fp
... PROGRAM TYPE pt
... MAXIMUM WIDTH INTO w