Get Example source ABAP code based on a different SAP table
System Fields in ABAP Release 6.10 ITOC
ABAP_MODIFICATION_NN Content of the System Field sy-calld> >
The field sy-calld> should contain space> if the program is the first and only program in a call sequence>. sy-calld> should contain X> if the program is a called program in a call sequence. Previously, sy-calld> was always set to X> for SUBMIT> without RETURN>, even though this meant that the ABAP_ISESS > or the position in the call sequence of the caller is replaced by the called program. If the calling program was the first program in the call sequence, this produced errors in the application logic. From now on, sy-calld> is not affected by SUBMIT> without RETURN >, and retains the value of the calling program whose ABAP_ISESS is being replaced.
ABAP_MODIFICATION_NN Replacement of the System Field sy-repid >>
The system field sy-repid> is no longer a component of the structure SY> in the ABAP program or the structured type SYST > in ABAP Dictionary. Instead, from ABAP_RELEASE 6.10, every program contains the built-in constants sy-repid> and syst-repid>, which both contain the name of the current program. There are also two built-in types sy-repid> and syst-repid>. The obsolete type references LIKE syst-repid>> and TYPE sy-repid> > are, therefore, still possible. In addition to considerable performance improvements in the external procedure call, this new feature also has the advantage that sy-repid> can now also be passed as a parameter to external procedures>. The formal parameter is set to the name of the caller and not to the name of the compilation unit>, which means that a helper variable is no longer required. This incompatible change can cause problems if ABAP programs refer to the previous structure syst>, for example: