topic Re: internal table data issue in Application Development and Automation Discussions

internal table data issue

Former Member — Tue, 22 May 2007 10:28:42 GMT

i have a internal table i_final in program 1 and this internal table data need to be input of other program, so how i need to pass the i_final data to other program.

Re: internal table data issue

former_member225631 — Tue, 22 May 2007 10:31:24 GMT

Use submit.

submit prg_name.

Declare same internal table in target proram also.

Re: internal table data issue

Former Member — Tue, 22 May 2007 10:31:55 GMT

If you don't have a chance to use perform routines you'll have to use 'EXPORT TO MEMORY' and in the other program 'IMPORT FROM MEMORY'.

Regards

Nicola

Re: internal table data issue

Former Member — Tue, 22 May 2007 10:32:15 GMT

do u have any ex for this .

Re: internal table data issue

former_member225631 — Tue, 22 May 2007 10:50:38 GMT

Simply use submit statement.

submit test. (test is target program).

declare the same internal table in target program.

Use the data in target program.

Re: internal table data issue

Former Member — Tue, 22 May 2007 10:51:15 GMT

Sure,

e.g.:

EXPORT lt_table TO MEMORY ID 'ZFTABLE'.

IMPORT lt_table FROM MEMORY ID 'ZFTABLE'.

in both reports the table definition and the name of the ID has to be the same (you can choose any name you like).

Hope that helps!

Nicola

Re: internal table data issue

former_member225631 — Tue, 22 May 2007 10:52:09 GMT

Simply use submit statement.

submit test. (test is target program).

declare the same internal table in target program.

Use the data in target program.

Re: internal table data issue

Former Member — Tue, 22 May 2007 10:53:47 GMT

it doesn't work with submit, at least not up to release 4.7

With submit you can transfer a selection table but not an internal table with data.

Regards

Nicola

Re: internal table data issue

Former Member — Tue, 22 May 2007 11:01:23 GMT

hi nicolas,

i have tried using export and import its not working.

Re: internal table data issue

Former Member — Tue, 22 May 2007 11:03:23 GMT

this is the code in program 1:

ENDIF.

**appending work area to internal table.

APPEND wa_final TO i_final.

ENDLOOP.

EXPORT i_final to memory id 'zfinal'.

this is the code in program 2:

TYPES: BEGIN OF t_final,

bukrs TYPE bkpf-bukrs,

belnr TYPE bkpf-belnr,

blart TYPE bkpf-blart,

xblnr TYPE bkpf-xblnr,

ebeln TYPE ekbe-ebeln,

ebelp TYPE ekbe-ebelp,

belnr1 TYPE ekbe-belnr,

xblnr1 TYPE ekbe-xblnr,

ebeln1 TYPE ekko-ebeln,

exnum TYPE ekko-exnum,

lands TYPE ekko-lands,

stceg_l TYPE ekko-stceg_l,

END OF t_final.

DATA: i_final TYPE STANDARD TABLE OF t_final WITH HEADER LINE.

DATA: wa_final TYPE t_final.

IMPORT i_final from memory ID 'zfinal'.

write: i_final.

its giving Dump.

Re: internal table data issue

Former Member — Tue, 22 May 2007 11:09:13 GMT

Hmmm, I tried it and it worked fine:

Report 1:

DATA: BEGIN OF lt_test OCCURS 0.

INCLUDE STRUCTURE bkpf.

DATA: END OF lt_test.

I've added a line in debug mode.

EXPORT lt_test TO MEMORY ID 'zftest'.

Submit report2.

Report 2:

DATA: BEGIN OF lt_test OCCURS 0.

INCLUDE STRUCTURE bkpf.

DATA: END OF lt_test.

IMPORT lt_test FROM MEMORY ID 'zftest'.

Please check of the table definition is the same and both reports. If so, please let me know your release and the text of the dump.

Regards

Nicola

Re: internal table data issue

Former Member — Tue, 22 May 2007 11:21:29 GMT

tks nicola my problem is solved

Re: internal table data issue

Former Member — Tue, 22 May 2007 11:22:40 GMT

You're welcome )

Nicola