Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

(internal) Tables obsolete as parameter in function modules in ECC 6.0

Former Member
0 Likes
882

Hi All,

I followed Steps 1 and 2 in the thread but when I use the following select statement I get a dump with the error enclosed.

Step1. Created a structure ZDFKKCOHI which is a replica of DFKKCOHI.

Step2. Created a table type ZDFKKCOHITABLE with line type as ZDFKKCOHI.

Step3. In my function module I have a changing parameter ZDFKKCOHIPARAM of type ZDFKKCOHITABLE.

Step 4. When I use the following select clause I am getting a dump.

DATA: wa_zdfkkcohi LIKE LINE OF zdfkkcohiparam.

SELECT *

FROM dfkkcohi

INTO CORRESPONDING FIELDS OF TABLE zdfkkcohiparam

WHERE cotyp EQ zcotyp

AND gpart EQ zgpart

AND corr_status EQ zcorr_status.

LOOP AT zdfkkcohiparam INTO wa_zdfkkcohi.

*Move IT_ZDFKKCOHI to ZDFKKCOHIOUT.

*Append ZDFKKCOHIOUT.

*Clear IT_ZDFKKCOHI.

ENDLOOP.

Error: Das laufende ABAP-Programm wollte eine Open SQL-Anweisung ausführen,

bei der die Treffermenge mit 'INTO CORRESPONDING FIELDS' in

namensgleiche Felder der Zielbereichs gestellt werden soll. Hierbei

müssen die namensgleichen Felder des Zielbereichs einen flachen Typ

haben, oder vom Typ STRING oder XSTRING sein.

Im vorliegenden Fall enthält der Zielbereich " " aber ein

namensgleiches Feld "MANDT " mit dem verbotenen internen Typ "l".

What could be wrong?

Thanks for all your help in advance.

Regards,

Divya

7 REPLIES 7
Read only

Former Member
0 Likes
814

Translating the error message -;)


The running ABAP-program wanted to carry out an opus SQL-direction, with which the hit quantity with 'INTO
CORRESPONDING FIELDS' is supposed to be placed into name same fields the goal area.  Herewith the name same
fields of the goal area must have be a flat type, or of the type STRING or XSTRING.  

In the existing case, the goal area "" contains however a name same field "MANDT" with the forbidden internal type "l".

You should check you structures and assign the correct TYPE to the fields -:)

Greetings,

Blag.

Read only

0 Likes
814

Hi Alvaro,

I had translated this message earlier as well but they all seem to have the correct data types.

Thanks,

Divya

Read only

0 Likes
814

Check the CLIENT.

Rob

Read only

0 Likes
814

Rob,

The problem was with the structure having the required type checked for the first 5 parameters. Hence if this is checked it does not recognize the data types of these fields and hence causes the dump.

Thanks a bunch to both of you.

Divya

Read only

0 Likes
814

Actually -;) I translate for all the guys out there who doesn't speak German...Like me -:)

Greetings,

Blag.

Read only

Former Member
0 Likes
814

if you have a field MANDT in your internal table zdfkkcohiparam, make sure it is declared as a client data type and not integer.

Rob

Read only

Former Member
0 Likes
814

The problem was with the structure having the required type checked for the first 5 parameters. Hence if this is checked it does not recognize the data types of these fields and causes the dump.