topic Does EXPORT to MEMORY ID work in background in Application Development and Automation Discussions

Does EXPORT to MEMORY ID work in background

Former Member — Tue, 10 Mar 2009 09:02:08 GMT

Hi,

I'm exporting an internal table to a memory ID which will then be used in another program which will be called from the current program with a SUBMIT and RETURN statement.

When i use the SUBMIT online, it seems to EXPORT and IMPORT the internal table correctly.

but, when i SUBMIT to the program in background, it does not seem to do whatever i expect, which makes me think eventually there is some problem with the data I've been EXPORTing and IMPORTing.

Can anyone shed any lights on this one please?

Thanks,

Tabraiz

Edited by: Tabraiz Ali Khan on Mar 10, 2009 10:04 AM

Re: Does EXPORT to MEMORY ID work in background

matt — Tue, 10 Mar 2009 09:09:09 GMT

If the same memory space is being used, then yes. Otherwise no. If you've a late enough version, you can set an external breakpoint and check the values in memory through the debugger.

How are you SUBMITting in background?

Re: Does EXPORT to MEMORY ID work in background

Former Member — Tue, 10 Mar 2009 09:15:05 GMT

I used the below statement:

SUBMIT zsecondprogram AND RETURN

USER sy-uname

VIA JOB gv_jobname

NUMBER gv_job_number

TO SAP-SPOOL

SPOOL PARAMETERS gs_user_print_params

ARCHIVE PARAMETERS gs_user_arc_params

WITHOUT SPOOL DYNPRO.

Re: Does EXPORT to MEMORY ID work in background

Former Member — Tue, 10 Mar 2009 09:36:49 GMT

I guess i need to use a shared buffer for this.

Re: Does EXPORT to MEMORY ID work in background

Former Member — Tue, 10 Mar 2009 12:27:13 GMT

Shared buffer works