Get Example source ABAP code based on a different SAP table
Runtime and Load Size in ABAP Release 6.10 ITOC
ABAP_MODIFICATION_NN 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_NN 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 raised.
ABAP_MODIFICATION_NN 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_NN Number of Global Segments>
The number of global segments in the program memory is now unrestricted. Previously, a maximum of 2**15 global segments was allowed.
ABAP_MODIFICATION_NN 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 more decimal places> 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_NN 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 many decimal places 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_NN Paging Out of the Structure SCREEN>>
Until now the structure of the data object SCREEN> was generated automatically in every program. In ABAP_RELEASE 6.10 this structure description was paged out into the type pool> SYSCR>. Instead of data NAME type %_CX_SCREEN-Name> the code should now be data NAME type SYSCR_SCREEN-NAME>
ABAP_MODIFICATION_NN 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.>