SUBMIT PROGRAM with export-import internal tables issue

[ricky_shaw]

Hi ,
I have a z*prog in se38 which has 1 parameter on selection screen p_file (say) for file input &
a check box to submit for no of jobs.
This prog reads that file with huge data into an internal table (say)itab_out which we normally  loop thru this itab_out to carry out further process.

Now, when i choose to schedule this program for Batch job submission, i break up that itab_out based on number of jobs chosen & build another itab_out2 & then call FM's JOB_OPEN, SUBMIT PROGRAM, JOB_CLOSE.

I am writing export itab_out2 followed by submit & return program stmt(same current prog) to pass the new table itab_out2.

1)export itab = itab_out2 to memory id 'MEM1'.
submit (lv_prog) via job lv_jobname number lv_jobnumber
with p_subjob = ''
with p_nojobs = p_nojobs
and return.

2) calling this import statement in beginning of same prog
 import itab = itab_out2 from memory id 'MEM1'.

However, i am not sure if this export import is working properly.

How do i determine if this SUBMIT, EXPORT & IMPORT is working properly or not?

[Sandra_Rossi]

The ABAP memory (IMPORT/EXPORT MEMORY) cannot be shared between the calling program and a called program via SUBMIT VIA JOB (it works only if you don't use VIA JOB).

[RaymondGiuseppi]

As this is a NO-DISPLAY parameter, you could give it the same definition than your internal table (type table of)

• You could also EXPORT data in a permanent medium such as DATABASE or SHARED MEMORY/BUFFER

[ricky_shaw]

Ok..I can see that its NOT working.

I changed the code to have a parameter on sel screen with :

Parameters : p_itab type string_table no-display.

SUBMIT  Zmyprog** WITH p_tab = p_tab.

This is passing the data from SUBMIT to p_tab.

But p_tab holds plain string data type. How do i break this p_itab to hold 10 different columns like my  itab_out2?

[Sandra_Rossi]

You can pass any type of variable through a program parameter (internal table and so on, except references) by defining it as NO-DISPLAY