I doubt that the issue comes from windows 7/XP. If the issue is with the cursor in a table control, most probably the issue would come from the number of lines in table controls that can be rendered in the SAP GUI (even though it runs in background). So that to have a stable behavior, the screen size must be fixed by recording and playing the batch input with the option "standard screen size" (see the abap doc of CALL TRANSACTION CTU_PARAMS-DEFSIZE for more info, and also the SAP note 11788 (Batch input, variable step loop or table control)).
↧