Runtime and Load Size in Release 6.10
1 Restrictions on the statement STOP
2 Addition ON ROLLBACK for subroutines
3 Overwriting of untyped field symbols
4 Number of global segments
5 Passing of c literals to numeric parameters
6 c literals as default values for parameters of type p
7 Paging out of the structure SCREEN
8 Syntax revisions in LOOP AT SCREEN and MODIFY SCREEN
ABAP_MODIFICATION_1 Restrictions on the Statement STOP
The statement STOP can no longer be used
outside of reports or in dynpros called using
CALL SCREEN . Such actions previously
produced a runtime error or, in rarer cases, a non-traceable program
flow.
ABAP_MODIFICATION_2 Addition ON ROLLBACK for Subroutines
The addition ON ROLLBACK is now available
for subroutines, similar to PERFORM ... ON COMMIT . This stops
FORM routines of this type from being executed until a
ROLLBACK WORK or a
MESSAGE of type A is triggered.
ABAP_MODIFICATION_3 Overwriting of Untyped Field Symbols
Untyped field symbols no longer lose their ready-only status when
being read for the first time. Also, the fields %_DUMMY and
%_SPACE are now constants.
ABAP_MODIFICATION_4 Number of Global Segments
The number of global segments in a roll area is now unrestricted.
Previously, a maximum of 2**15 global segments was permitted.
ABAP_MODIFICATION_5 Passing of c Literals to Numeric
Parameters
When passing c literals to parameters of type p , it was
previously possible for a number to have a larger
fractional portion than the formal
parameter. Due to rounding and the associated loss of information loss,
the passing of c literals to parameters of types I, INT1 ,
and INT2 also caused problems. For example, the literal
'1245.6789' could be passed to a formal parameter of type
p DECIMALS
2 or type i , and the rounding was performed in accordance with
the associated conversion rule .
Now the system ensures that the formal parameter has as large as a
fractional portion as required by the literal. In the case of programs
without fixed point arithmetic, the size of the fractional portion must
be an exact match.
ABAP_MODIFICATION_6 c Literals as Default Values for
Parameters of Type p
If, in the case of generic parameters of type p , a c
literal is specified as the default value (for example in the form
'12.345'), a field of type p with Decimals 0 was created
and the literal value converted to this field. This could also result in
information loss due to rounding.
Now a field of type p is created with as large a fractional
portion as specified in the literal. For example, for a c literal
with the value '12.345', a P field with Decimals 3 is created.
ABAP_MODIFICATION_7 Paging Out of the Structure SCREEN
Until now the structure of the data object SCREEN was generated
automatically in every program. In Release 6.10 this structure
description was paged out into the type group
SYSCR . Instead of
data NAME type %_CX_SCREEN-Name
the code should now be
data NAME type SYSCR_SCREEN-NAME
ABAP_MODIFICATION_8 Syntax Revisions in LOOP AT SCREEN and
MODIFY SCREEN
The following changes were made to the statements
LOOP AT SCREEN and
MODIFY SCREEN .
To ensure independence from global definitions, the additional variants
LOOP AT SCREEN INTO wa and MODIFY SCREEN FROM wa were
introduced.
LOOP AT SCREEN with an internal table SCREEN defined
locally in the program is no longer possible. The following program,
previously not terminated until runtime, now produces a syntax error:
PROGRAM loop_test.
PERFORM test.
FORM test.
DATA screen TYPE STANDARD TABLE OF spfli.
LOOP AT SCREEN.
ENDLOOP.
ENDFORM.
Documentation extract taken from SAP system, � Copyright SAP AG. All rights reserved