topic Re: Import memory id in Application Development and Automation Discussions

Import memory id

Former Member — Fri, 19 Feb 2010 08:53:49 GMT

Dear experts,

I am using one import statements- 'import temp_rate to temp_rate from memory id 'RATE' in one client.It is showing value 0.00 and in other client it is showing value '90'.

Could you please suggest how?

Regards,

Tushar

Re: Import memory id

Former Member — Fri, 19 Feb 2010 08:58:55 GMT

This could be export value of temp_rate in the respective client.

Re: Import memory id

venkat_o — Fri, 19 Feb 2010 08:59:19 GMT

<li>EXPORT and IMPORT are executed in one session. <li>Did you check temp_rate when you are exporting using EXPORT temp_rate TO MEMORY ID 'RATE' . <li>Why are you comparing temp_rate client wise. You should compare what are you EXPORTing and What are importing. Thanks Venkat.O

Re: Import memory id

Former Member — Fri, 19 Feb 2010 09:01:23 GMT

No I am not comparing value client wise....but due to this condition value is coming wrong in one client and value is comming right in other client that's why...

Please suggest thye root cause...

Re: Import memory id

matt — Fri, 19 Feb 2010 09:04:54 GMT

So far you are saying "I'm getting different results in different clients". A little more information is required.

Like: are the clients on the same instance? What transaction are you running - is it standard or custom. Where is the memory ID being set - inside custom or standard ABAP.

Please try to help others to help you by supplying relevant information.

matt

Re: Import memory id

Former Member — Fri, 19 Feb 2010 09:07:38 GMT

Hi Amar,

There might be some condition which gets executed in the second client which clears the ABAP memory. Therefore, the IMPORT statement fetches a null value.

Check if your program has a LEAVE TO TRANSACTION statement. If yes, that may be the reason why ABAP memory is getting cleared.

Please also try memory monitoring if you have debugging rights in the other client. That will help you identify where exactly the memory is getting cleared.

Hope this helps! Please revert if you need anything else.

Cheers,

Shailesh.

Always provide feedback for useful answers


Dear Matt,
Both client are in same instance and using for VF01 transaction..It is used for condition type..Actualy we have putted this condition in include LV61AA47 using enhacements...

Can you please confirm whether you are using only one enhancement for both EXPORTing and IMPORTing, or whether there are separate enhancements for these functions?

The best way would be to set a breakpoint (if allowed) on EXPORT statements. Then see which statement is EXPORTing your RATE variable and proceed from there.

Thanks,

Shailesh

Re: Import memory id

Former Member — Fri, 19 Feb 2010 09:08:35 GMT

Dear Matt,

Both client are in same instance and using for VF01 transaction..It is used for condition type..Actualy we have putted this condition in include LV61AA47 using enhacements...

And I will try to help others thru SDN.....

Re: Import memory id

venkat_o — Fri, 19 Feb 2010 09:12:34 GMT

Amar, <li>When you run VF01 t.code, Did you check EXPORT statement which has been set previously before we import using IMPORT statement. When you execute VF01 transaction, check what is the value at the time of EXPORT and IMPORT . check like that . Thanks Venkat.O

Re: Import memory id

matt — Fri, 19 Feb 2010 11:08:51 GMT

If they're both the same instance, then they're running the same code. Chances are - you've a customising problem. So, logon on to each client, and debug the transaction in each client and see where the differences are. Or run the transaction with SQL Trace on, and see if the SELECTS are different. Or run the transactions via Run Time Analysis, and look for the differences.

But before doing that, make sure that all customising transport have been imported into both clients.

Another approach will be to look at the ABAP loaded, and search for the string "temp_rate". You may find where the value is being EXPORTed TO MEMORY.

matt