topic Re: Export to database index+debugging in Application Development and Automation Discussions

Export to database index+debugging

kiran_k8 — Thu, 18 Aug 2011 11:35:27 GMT

Hi,

Can anyone here let me know how to check the values in debugging that were exported or imported to database index using Export/Import.

EXPORT itab TO DATABASE indx(aa) ID 'XYZ'.

If it is a memory id I am able to see the values that were exported to memory id in classical debugger using ABAP MEMORY option.Similarly I would like to know where we can see the values that got exported to database index using EXPORT/IMPORT.

Thanks,

K.Kiran.

Re: Export to database index+debugging

Former Member — Thu, 18 Aug 2011 11:39:53 GMT

for the control data, look at table INDX. To see the actual data, import the data into the proper program/internal table from the INDX(AA).

Re: Export to database index+debugging

kiran_k8 — Thu, 18 Aug 2011 11:58:09 GMT

Thanks Davel.

In Classical debugger,if I give INDX in the internal table option,I am seeing the structure of INDX with fields

RELID having the value CO

SRTFD having the value TAB1

CLUSTR having the value 101

CLUSTD having some long value which is alpha numeric.

At the level of debugging how can we interpret these values in INDX.Can we say that if CLUSTD is having some value means the value got exported ?

K.Kiran.

Re: Export to database index+debugging

Sandra_Rossi — Thu, 18 Aug 2011 12:18:08 GMT

Hi K.Kiran.,

I don't understand your question : in your example, you export "itab". So, if you want to know what is exported, just look at "itab".

Could you please give more details?

Sandra

Re: Export to database index+debugging

kiran_k8 — Thu, 18 Aug 2011 12:21:08 GMT

Sandra,

My query is in debugging how to check if the values got exported to database index.Will we be not be able to see the values that got exported just as we are seeing the values of ITAB in debugging ?

Thanks,

K.Kiran.

Re: Export to database index+debugging

Sandra_Rossi — Thu, 18 Aug 2011 12:28:37 GMT

No, you can't, you just have to trust the system. If there's an error, it will return SY-SUBRC <> 0 or even a dump. Otherwise, it does exactly what we see it does (or there's a nice kernel error ).

I'm also surprised that you can see the ABAP memory. In my 7.0 debugger, I can only see the SAP memory (GET PARAMETER/SET PARAMETER)

Sandra

Re: Export to database index+debugging

kiran_k8 — Thu, 18 Aug 2011 12:32:14 GMT

Sandra,

I remember reading it somewhere that ABAP Memory/SAP Memory option is not yet available in New Debugger.

Thanks,

K.Kiran.

Re: Export to database index+debugging

Former Member — Thu, 18 Aug 2011 16:35:40 GMT

Sandra is quite correct....the INDX table rows for your index and ID entries now contain as many rows as needed to store (internal format) what ITAB contained at the time of the export. Trust the export here if you have a good return code. If you import into identical structure/table as ITAB, you will get the exact same table back.

This is completely reliable method of temporarily storing data (SAP calls this semi-persistent data) so that another program, perhaps executed at a later time and on a different APPS server in the same SAP instance, can still read the data that was in ITAB at the time of the export.