2007 Sep 27 9:45 AM
Hi,
I came across this in threads and iam also in use of this but why to use sumit xxxx(what is xxxxx mean) and CALL FUNCTION 'LIST_FROM_MEMORY'
DATA: LISTOBJ LIKE ABAPLIST OCCURS 0 WITH HEADER LINE.
DATA: WRITES LIKE LISTZEILE OCCURS 0 WITH HEADER LINE.
SUBMIT XXXXX EXPORTING LIST TO MEMORY
AND RETURN.
CALL FUNCTION 'LIST_FROM_MEMORY'
TABLES
LISTOBJECT = LISTOBJ
EXCEPTIONS
NOT_FOUND = 1.
IF SY-SUBRC = 0.
CALL FUNCTION 'LIST_TO_ASCI'
TABLES
LISTOBJECT = LISTOBJ
LISTASCI = WRITES.
ENDIF.
2007 Sep 27 9:47 AM
Hi
When you wants the report/program to export to Memory
and to access that Program/report from memory we use this Commands/fun modules
see this
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 area remains intact during a whole sequence of program calls. To pass data
to a program which you are calling, the data needs to be placed in ABAP memory before the call is made. The internal session of the called program then replaces that of the calling program. The program called can then read from the ABAP memory. If control is then returned to the program which made the initial call, the same process operates in reverse.
ABAP memory is temporary and values are retained in same LUW.
export itab to memory id 'TEST'.
import itab from memory Id 'TEST'.
Here itab should be declared of same type and length.
http://www.sap-img.com/abap/difference-between-sap-and-abap-memory.htm
ABAP Memmory & SAP Memmory
http://www.sap-img.com/abap/difference-between-sap-and-abap-memory.htm
http://www.sap-img.com/abap/type-and-uses-of-lock-objects-in-sap.htm
Regards
Anji
Message was edited by:
Anji Reddy Vangala
2007 Sep 27 9:47 AM
Hi
When you wants the report/program to export to Memory
and to access that Program/report from memory we use this Commands/fun modules
see this
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 area remains intact during a whole sequence of program calls. To pass data
to a program which you are calling, the data needs to be placed in ABAP memory before the call is made. The internal session of the called program then replaces that of the calling program. The program called can then read from the ABAP memory. If control is then returned to the program which made the initial call, the same process operates in reverse.
ABAP memory is temporary and values are retained in same LUW.
export itab to memory id 'TEST'.
import itab from memory Id 'TEST'.
Here itab should be declared of same type and length.
http://www.sap-img.com/abap/difference-between-sap-and-abap-memory.htm
ABAP Memmory & SAP Memmory
http://www.sap-img.com/abap/difference-between-sap-and-abap-memory.htm
http://www.sap-img.com/abap/type-and-uses-of-lock-objects-in-sap.htm
Regards
Anji
Message was edited by:
Anji Reddy Vangala
2007 Sep 27 9:47 AM
Hi Sravanthi,
This XXXXX is nothing but a report name and no special meaning for XXXXX.
Generally SUBMIT is used to call another report from a transaction or from within a report.
Thanks,
Vinay