2010 Mar 19 5:43 AM
Hi,
Some times we use EXPORT to MEMORY ID and some times we EXPORT to DATABASE IDX table, pls. let me know,
1) When we use EXPORT to MEMORY ID?
2) When we use EXPORT to DATA BASE IDX table?
3) I knew that in the (1) case, data wuld be stored in shared memory for session live.......but, what about (2) case,Where its stored, is it storeas really in data base? like other data (say, sales order data) this exported data also persists for ever in the Oracle data bse? or this table (idx) is a logical data base?
Thank you
2010 Mar 19 8:29 PM
Essentially, I would export to a memory id if I have a process that will immediate follow what I'm doing right now and will be executed in the same user context.
The problem arises when we launch something that might not end up on the same APPS server, due to load balancing, or when I need to store the data and come back later, with another program, to retrieve that data, for instance, an extract that stores data that is put together with something else for a report, or something. In this case, writing to INDX or a custom transparent table of the same structure will result in what SAP calls semi-persistent data....
Research shared objects or semi-persistent data for an understanding of the various methods of passing data between objects.
Hi,
Some times we use EXPORT to MEMORY ID and some times we EXPORT to DATABASE IDX table, pls. let me know,
1) When we use EXPORT to MEMORY ID?
2) When we use EXPORT to DATA BASE IDX table?
3) I knew that in the (1) case, data wuld be stored in shared memory for session live.......but, what about (2) case,Where its stored, is it storeas really in data base? like other data (say, sales order data) this exported data also persists for ever in the Oracle data bse? or this table (idx) is a logical data base?
Thank you
2010 Mar 19 5:51 AM
First of make it a point to read the SAP documentation if you have any doubts: [http://help.sap.com/abapdocu_70/en/ABAPEXPORT_DATA_CLUSTER_MEDIUM.htm#!ABAP_ALTERNATIVE_4@4@|http://help.sap.com/abapdocu_70/en/ABAPEXPORT_DATA_CLUSTER_MEDIUM.htm#!ABAP_ALTERNATIVE_4@4@]
SAP has defined a predefined DB table INDX as a reference (you can create your custom table similar to INDX if you want). When you EXPORT the data to this table, a new record is created in the table & the data exported will be stored in RAW format.
This data remains in the INDX table even after the session is terminated.
BR,
Suhas
2010 Mar 19 6:04 AM
Thank you. I dont know for some reason at this time, system is not allowing me to give rewards, so will asign after soem time.
Could you let me know that, in Which case data willl be exported to memori ID (1)? in wht cases we export data to data base INDX table?
thnak you
2010 Mar 19 6:22 AM
Hello,
When using EXPORT TO MEMORY ID the data is available in the ABAP memory. You cannot access the data beyond this area.
But this is not the case with EXPORT TO DATABASE
BR,
Suhas
PS: I am not sure if there are any limitations to the amount (read size) of data which can be transferred via both the statements.
2010 Mar 19 8:29 PM
Essentially, I would export to a memory id if I have a process that will immediate follow what I'm doing right now and will be executed in the same user context.
The problem arises when we launch something that might not end up on the same APPS server, due to load balancing, or when I need to store the data and come back later, with another program, to retrieve that data, for instance, an extract that stores data that is put together with something else for a report, or something. In this case, writing to INDX or a custom transparent table of the same structure will result in what SAP calls semi-persistent data....
Research shared objects or semi-persistent data for an understanding of the various methods of passing data between objects.
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |