topic Re: IMPORT MEMORY ID issue in Application Development and Automation Discussions

IMPORT MEMORY ID issue

Former Member — Thu, 05 May 2016 05:30:28 GMT

Dear Experts ,

Here i am facing an issue that i have to run two programs at a time with only one input that is giving to program-A through parameter.

Here i need to run program-B after 5 seconds to execution of program-A . By using JOB_OPEN ,JOB_SUBMIT , JOB_CLOSE it is running successfully .

i am using EXPORT AND IMPORT MEMORY ID's to transfer the input value from Program-A to program-B . But input value is not transferring properly to Program-B it is giving output which is not related input that i provided in program-A .

please share your experience to resolve this issue.

Thank You.

Re: IMPORT MEMORY ID issue

prajeshdesai — Thu, 05 May 2016 05:50:59 GMT

You can you SET/GET PARAMETER for the same,

Try below,

SUBMIT program VIA JOB and SET/GET parameter | SCN

Hope this helps.

Re: IMPORT MEMORY ID issue

matt — Thu, 05 May 2016 05:55:05 GMT

Program B's memory is entirely independent of A, so EXPORT/IMPORT to MEMORY ID won't work.

Options:

1. Add selection options/parameters to B and fill the variant from A before using the JOB_ FMs

2. Use SUBMIT instead of the JOB_ FMs.

Re: IMPORT MEMORY ID issue

Former Member — Thu, 05 May 2016 06:03:38 GMT

Thank you sir for responding.

here the problem is i have to run that 2nd program in background that is it is not possible to use submit.

and i used SET/GET parameters now its coming exact output when i run 2nd program independently but in SM37 in spool output it is showig again wrong output .

please guide me sir how to do this .

Thank you.

Re: IMPORT MEMORY ID issue

Former Member — Thu, 05 May 2016 06:05:08 GMT

thanks for your response .

i used SET/GET parameters now its coming exact output when i run 2nd program independently but in SM37 in spool output it is showing again wrong output .

please guide me if you know.

thank you.

Re: IMPORT MEMORY ID issue

Former Member — Thu, 05 May 2016 06:37:01 GMT

This could be a very stupid answer.

Let the Program A save the param to a lookup table.

Let Program B read the value from lookup table...

Helps?

Re: IMPORT MEMORY ID issue

Former Member — Thu, 05 May 2016 06:37:58 GMT

Hi venkatesh,

it may be possible that your system has many application server and your program A and B are running on different application server. so one way is to force your program to run on same application server by providing sy-host.

you can use shared buffer in place of memory id.

to export.

export ITAB to shared buffer indx(st) id 'YOURKEY'.

to import

import imara from shared buffer indx(st) id 'YOURKEY'.

to free buffer.

delete from shared buffer indx(st) id 'YOURKEY'.

we have another solution to use DATABASE instead of SHARED BUFFER in EXPORT and IMPORT statements.

EXPORT itab FROM itab TO DATABASE indx(ar) CLIENT sy-mandt ID job_number in program1 where job number is unique.

Then
IMPORT itab TO itab FROM DATABASE indx(ar) CLIENT sy-mandt ID job_number in program2 where job number is passed from program1 to program2 while submit job.

Then DELETE FROM DATABASE indx(ar) CLIENT sy-mandt ID job_number.

Re: IMPORT MEMORY ID issue

Former Member — Thu, 05 May 2016 06:52:25 GMT

Thank you for your response .

if i use EXPORT and IMPORT , the input value is not transferring from program-A to program-B .

so i am using SET and GET parameters now output is coming properly when program-B is executed independently .

but when i check it in background job(SM37) its showing wrong output .

what to do know ?

THANK YOU.

Re: IMPORT MEMORY ID issue

Former Member — Thu, 05 May 2016 07:06:58 GMT

is your both program are running by the same user??

because this SET/GET parameter are user specific.

Re: IMPORT MEMORY ID issue

Former Member — Thu, 05 May 2016 07:09:53 GMT

yes i am only running that two programs

Re: IMPORT MEMORY ID issue

matt — Thu, 05 May 2016 07:17:14 GMT

Don't use SET/GET. To limited. And what will you do if something changes those parameters before job B runs?

Use a selection screen in program B. Simplest, safest, easiest solution.

Re: IMPORT MEMORY ID issue

Former Member — Thu, 05 May 2016 07:27:17 GMT

Hi,

you can try this. may be this will help you.

Pass parameter to background job from report | SCN

Re: IMPORT MEMORY ID issue

Former Member — Thu, 05 May 2016 11:56:29 GMT

thank you all its done