Batch Input BDC_CURSOR values : Win XP <> Win 7 ?

[Former Member]

Hi,

We've switched from Windows XP to Windows 7. Now a program which uses a batch input call transaction to modify role authorizations in PFCG doesn't work anymore. I did some tests, recording new sessions in SM35, and it seems the command BDC_CURSOR which positions the cursor gets different values in Windows XP than in Windows 7???

I guessed there would be an SAP note if that would really be the case, but I didn't find any. Did anybody else already encounter this problem? If so, is there any other solution than re-recording all Batch Inputs which use BDC_CURSOR?

Joë

[Former Member]

Wow, i have never encountered this my self and i have worked with BDC's on both XP and 7. the bdc cursor is purely to position the cursor on a field in a particular screen which should remain the same regardless of the OS you use on your computer. It is totally SAP dependent which would be set up on a remote server if i m not mistaken, it has nothing to do with the OS you personally run.

This is news to me though. Strange.

[dietrich_ebert]

Hi Joël,

it's been a Long time ago, but how did you get it repaired?

Regards Dietrich

[Sandra_Rossi]

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)).

[Former Member]

We adapted the Batch input, still no idea what the problem was.

[dietrich_ebert]

Thank you for your answers Sandra and Joël. We will try to use the option "standard screen size" as you proposed Sandra.

Regards Dietrich