topic Re: Transporting parameters when calling a transaction. in Application Development and Automation Discussions

Transporting parameters when calling a transaction.

Former Member — Mon, 17 Mar 2014 12:21:05 GMT

Hi everyone,

I want to transport some parameters to the transaction that I call. Currently I’m using this way of calling a transaction (CALL TRANSACTION ‘NAME’ MODE 'N' UPDATE 'S' MESSAGES INTO messtab. Using batch input (bdcdata)). When I use this I’m not able to call another transaction. So is there another way to transport parameters when calling a transaction (module pool)?.

Thanks in advanced.

Best regards.

Re: Transporting parameters when calling a transaction.

Former Member — Mon, 17 Mar 2014 12:33:48 GMT

Hi Arben,

What do you mean by "call another transaction"?

If your concern is about the hard coded parameters you can use a constant table like STVARV and pass the parameters according to your needs.

Check the CALL TRANSACTION documentation if you have any doubts about the command

https://help.sap.com/abapdocu_70/en/ABAPCALL_TRANSACTION.htm

Regards,

Felipe

Re: Transporting parameters when calling a transaction.

Former Member — Mon, 17 Mar 2014 12:35:39 GMT

Hi, try to look towards using SUBMIT if you call executable program.

Another way - use export/import from/to Memory ID to transport some parameters between different programs

Re: Transporting parameters when calling a transaction.

Former Member — Mon, 17 Mar 2014 12:54:52 GMT

Hi Felipe,

With "call another transaction" I mean calling the same transaction in another session in the same computer. I used export/import from/to Memory ID to transport parameters but when I call it twice or more parameters confuse and then I get no right values, but values that are stored in local memory from the first execution.

I mean everything goes right, but only the first time.

Any idea?

Thank you!

Re: Transporting parameters when calling a transaction.

Former Member — Mon, 17 Mar 2014 12:55:47 GMT

Hi Maxim,

I used export/import from/to Memory ID to transport parameters but when I call it twice or more parameters confuse and then I get no right values, but values that are stored in local memory from the first execution.

I mean everything goes right, but only the first time.

Any idea?

Thank you!

Re: Transporting parameters when calling a transaction.

Former Member — Mon, 17 Mar 2014 12:56:03 GMT

Use Export Memory ID, IMPORT Memory Id if you are accessing in same session.

Or use, SET parameter ID, GET parameter ID if you want to store and retrieve in come other session.

Re: Transporting parameters when calling a transaction.

Former Member — Mon, 17 Mar 2014 13:34:41 GMT

Arben,

could you describe the flow that you programs should be executed?

Re: Transporting parameters when calling a transaction.

Former Member — Mon, 17 Mar 2014 14:38:24 GMT

after geting data from memory id you should do FREE MEMORY ID