Hello Shwetha,
I know it is not difficult, but I need to be sure because I have more that 750 Update Routine to migrate, varying from field routine to start routine.
for example, this is a start routine, how could I change the FORM ENDFORM part?
assume, I will build this one with 7.4 according to the new concept, Subroutine are obsolete in 7, so should I use methods here instead of FORM ENDFORM, and what about PERFORM part?
The first part will be automatically generated as a definition of start routine, what about the code itself.
For this Start Routine for instance, I will omit the part of FORM ENDFORM and just copy PERFORM part into the new Routine (7.4) and instead of DATA_PACKAGE will be SOURCE_PACKAGE? is that right?
regards, sherif
PROGRAM UPDATE_ROUTINE.
*$*$ begin of global - insert your declaration only below this line *-*
* TABLES: ...
INCLUDE rsbctci_km_update_rules_vkm.
* DATA: ...
*$*$ end of global - insert your declaration only before this line *-*
* The follow definition is new in the BW3.x
TYPES:
BEGIN OF DATA_PACKAGE_STRUCTURE.
INCLUDE STRUCTURE /BIC/CS80CI_KMCA1.
TYPES:
RECNO LIKE sy-tabix,
END OF DATA_PACKAGE_STRUCTURE.
DATA:
DATA_PACKAGE TYPE STANDARD TABLE OF DATA_PACKAGE_STRUCTURE
WITH HEADER LINE
WITH NON-UNIQUE DEFAULT KEY INITIAL SIZE 0.
FORM startup
TABLES MONITOR STRUCTURE RSMONITOR "user defined monitoring
MONITOR_RECNO STRUCTURE RSMONITORS " monitoring with record n
DATA_PACKAGE STRUCTURE DATA_PACKAGE
USING RECORD_ALL LIKE SY-TABIX
SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS
CHANGING ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel update
*
*$*$ begin of routine - insert your code only below this line *-*
* fill the internal tables "MONITOR" and/or "MONITOR_RECNO",
* to make monitor entries
PERFORM ci_check_gn_cat_sal_for_update
TABLES MONITOR
DATA_PACKAGE
using RECORD_ALL
changing ABORT.
* if abort is not equal zero, the update process will be canceled
*$*$ end of routine - insert your code only before this line *-*
*
ENDFORM.