Problem while performing async RFC call between select endselect

[Former Member]

Hello,

i have got a problem using the following code in an async rfc sender scenario:

SELECT * FROM coss INTO TABLE it_coss PACKAGE SIZE 20000.

  CALL FUNCTION 'ZF_HELLO_WORLD_RFC' IN BACKGROUND TASK
    DESTINATION 'Z_RFC_HELLO_WORLD_DEST'
    EXPORTING
      ip_result = result.

   COMMIT WORK.

ENDSELECT.

i always get an exception at the commit work call as it is not allowed to call commit work between select and endselect.

is there any possibility to send the data asynchronous to the xi without the commit work call.

br,

martin

Message was edited by:

Martin Koch

[MichalKrawczyk]

hi,

try:

select

endselect

without call function

and then

loop at it_coss into result.

CALL FUNCTION...

endloop.

Regards,

michal

[Former Member]

hi,

i need the call function in the select.

because i need xi to start processing my messages as far as practicable because it's needed in an xi performance test.

the full select would take to long when calling it before the first function call, as the table i read from has approx. 2 million rows

maybe you have an alternative solution for me !!

br,

martin

[MichalKrawczyk]

hi,

>>>>maybe you have an alternative solution for me !!

of course I do - if you don't want to kill your XI machine

send a whole table at once (after select)

do you want to have 2 milion messages in XI ?

if you want a performance test only

do a loop over an internal tables with 2 mln records

and put the rfc call inside.... you don't need a select to do a performance test

Regards,

michal

[Former Member]

hi,

it's not just a performance test. the customer wants to test the overall time the xi needs to process the messages. and thereafter they want to use it in a production system. it's currently 4.6C - otherwise i would use proxies.

>>>do you want to have 2 milion messages in XI ?

no - i group the message to a size of 2000 entries - as i found out, that in my case 2000 messages are perfect for processing in xi (message size ~1.5Mb)

regards,

martin