topic Re: ABAP Memory in Application Development and Automation Discussions

ABAP Memory

Former Member — Thu, 01 Feb 2007 20:51:12 GMT

Hi,

I'm importing and exporting some data in a user exit.

when I'm running the same transaction in 2 sessions in debug mode I've noticed that the second sessions data in memory is imported in 1 st sessions memory though the values (sales orders ) are different in both sessions.

I'm not freeing the memory in the program.

So to nail this down I've written a small program but the values are not copied.

Can anyone offer any reason for this?

Thanks..

Re: ABAP Memory

RichHeilman — Thu, 01 Feb 2007 20:56:43 GMT

What does your EXPORT/IMPORT statements look like, you are not using the shared buffer are ya?

Regards,

RIch Heilman

Re: ABAP Memory

Former Member — Thu, 01 Feb 2007 21:07:39 GMT

GET PARAMETER ID 'VF' FIELD zbelnr.

IMPORT i_vbrp FROM MEMORY ID 'm_vbrp'.

if sy-subrc ne 0..

do something.

endif.

EXPORT i_vbrp TO MEMORY ID 'm_vbrp'.

after executing this in the 2nd session and I come back to first session in i_vbrp I can see the 2nd sessions data.

Actually this was written by somebody else but we are having problems when we are processing two billing docs at the same time.Issue is the taxes from 2nd doc are copied into 1st doc and when I debugged saw the copy.

How do I know if I'm using shared buffer?

Re: ABAP Memory

Former Member — Thu, 01 Feb 2007 21:15:20 GMT

Hi,

One way to do this,

before assigning the value, check if the memory is filled with a value, if it is then, wait for some time before again assigning value to the memory field.

And in the other program after import, clear the field contents and continue with your processing.

Regards

Subramanian

Re: ABAP Memory

Clemenss — Thu, 01 Feb 2007 21:39:52 GMT

Hi Aries,

if there is any data identifying the document uniquely, you could create a internal table bis the identifier as key and the vbrp as data.

Then, first import from memory, insert into the (possibly) empty table, then export it.

Then, where you import from memory, import the internal table and read with identifier key. Delete the line after processing and export again.

If there is no other key available, cou could create a GUID,

CALL FUNCTION 'GUID_CREATE'

IMPORTING

ev_guid_16 = l_guid.

This is said to be always unique and will help you to identify the right entry.

Regards,

Clemens