topic Re: explain about import statement.. in Application Development and Automation Discussions

explain about import statement..

subbarao_ilam — Fri, 22 Jan 2010 16:06:21 GMT

Hi All,

what is happening for the below code, pls explain.

import mdpsx release_9400 block_9400 upd_mro_9400 route_9400 mdvux

from database indx(zb) id indx_key.

below is the information

mdpsx - Internaltable

release_9400 - Internaltable

block_9400 - Internaltable

upd_mro_9400 - Internaltable

route_9400 - Internaltable

mdvux - Internaltable

indx - Database Table

indx_key is the structure and have the below files in that structure:

matnr like matvp-matnr

werks like matvp-werks

subbu.

Re: explain about import statement..

Former Member — Fri, 22 Jan 2010 16:12:15 GMT

semi-persistent data (data stored by somebody's program for subsequent use) is being retrieved from table INDX. Research "semi-persistent data" or "shared memory objects, shared memory buffers", etc., to see how/why this is done. Storing the data in INDX makes the data available to other programs, without having to worry about the next data user being on a different Apps server via load-balancing. This is particularly useful if the data will be used in another user context (not the current user session).

Re: explain about import statement..

former_member770378 — Fri, 22 Jan 2010 16:19:05 GMT

you do an IMPORT to get data stored in the system for your current sap session.

you can load these data only if an export has been done for the same data.

remember that the import and export commands are session dependant

Re: explain about import statement..

Former Member — Mon, 25 Jan 2010 06:02:08 GMT

hi,

import will not work unless you use an export statement both are dependent on each other and also they are session dependent.

rgds

shivraj

Re: explain about import statement..

Former Member — Mon, 25 Jan 2010 06:12:22 GMT

Hi Subbu,

In simple language,

ABAP memory is a memory area that all ABAP programs within the same internal session can access using the EXPORT and IMPORT statements.

Data within this memory area remains throughout a sequence of program calls, with the exception of LEAVE TO TRANSACTION. To pass data to a program that you are calling, the data needs to be placed in ABAP memory before the call is made from the internal calling session using the EXPORT statement.

The internal session of the called program then replaces that of the calling program. The program called can then read from the ABAP memory using the IMPORT statement.

Let me know if you need any more idea.

Manas M.

Re: explain about import statement..

Former Member — Mon, 25 Jan 2010 06:49:56 GMT

you wrote..


> what is happening for the below code, pls explain.
> 
> 
>   import mdpsx release_9400 block_9400 upd_mro_9400 route_9400 mdvux
>       from database indx(zb) id indx_key.
> 
> below is the information
> 
> mdpsx - Internaltable
> release_9400 - Internaltable
> block_9400 - Internaltable
> upd_mro_9400 - Internaltable
> route_9400 - Internaltable
> mdvux - Internaltable
> indx - Database Table
> 
> indx_key is the structure and have the below files in that structure:
> 
> matnr like matvp-matnr
> werks like matvp-werks
> 
> 
> subbu.

NOTE :-IMPORT nad EXPORT is use to importing exporting data to or from the ABAP memory

import mdpsx release_9400 block_9400 upd_mro_9400 route_9400 mdvux

from database indx(zb) id indx_key.

in the above statement mdpsx release_9400 block_9400 upd_mro_9400 route_9400 mdvux is import from the from the ABAP memory database indx(zb)

hope this helps

Regards

Ritesh