<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: (internal) Tables obsolete as parameter in function modules in ECC 6.0 in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables-obsolete-as-parameter-in-function-modules-in-ecc-6-0/m-p/1821829#M351160</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Translating the error message -;)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
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".
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You should check you structures and assign the correct TYPE to the fields -:)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Blag.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 08 Jan 2007 22:00:35 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-01-08T22:00:35Z</dc:date>
    <item>
      <title>(internal) Tables obsolete as parameter in function modules in ECC 6.0</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables-obsolete-as-parameter-in-function-modules-in-ecc-6-0/m-p/1821828#M351159</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;Step1. Created a structure ZDFKKCOHI which is a replica of DFKKCOHI.&lt;/P&gt;&lt;P&gt;Step2. Created a table type ZDFKKCOHITABLE with line type as ZDFKKCOHI.&lt;/P&gt;&lt;P&gt;Step3. In my function module I have a changing parameter ZDFKKCOHIPARAM of type ZDFKKCOHITABLE.&lt;/P&gt;&lt;P&gt;Step 4. When I use the following select clause I am getting a dump.&lt;/P&gt;&lt;P&gt;DATA: wa_zdfkkcohi LIKE LINE OF zdfkkcohiparam.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SELECT *&lt;/P&gt;&lt;P&gt;FROM dfkkcohi&lt;/P&gt;&lt;P&gt;INTO CORRESPONDING FIELDS OF TABLE zdfkkcohiparam&lt;/P&gt;&lt;P&gt;WHERE cotyp EQ zcotyp&lt;/P&gt;&lt;P&gt;AND gpart EQ zgpart&lt;/P&gt;&lt;P&gt;AND corr_status EQ zcorr_status.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;LOOP AT zdfkkcohiparam INTO wa_zdfkkcohi.&lt;/P&gt;&lt;P&gt;*Move IT_ZDFKKCOHI to ZDFKKCOHIOUT.&lt;/P&gt;&lt;P&gt;*Append ZDFKKCOHIOUT.&lt;/P&gt;&lt;P&gt;*Clear IT_ZDFKKCOHI.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ENDLOOP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Error: Das laufende ABAP-Programm wollte eine Open SQL-Anweisung ausführen,&lt;/P&gt;&lt;P&gt;bei der die Treffermenge mit 'INTO CORRESPONDING FIELDS' in&lt;/P&gt;&lt;P&gt;namensgleiche Felder der Zielbereichs gestellt werden soll. Hierbei&lt;/P&gt;&lt;P&gt;müssen die namensgleichen Felder des Zielbereichs einen flachen Typ&lt;/P&gt;&lt;P&gt;haben, oder vom Typ STRING oder XSTRING sein.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Im vorliegenden Fall enthält der Zielbereich " " aber ein&lt;/P&gt;&lt;P&gt;namensgleiches Feld "MANDT " mit dem verbotenen internen Typ "l".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What could be wrong?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for all your help in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Divya&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Jan 2007 21:55:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables-obsolete-as-parameter-in-function-modules-in-ecc-6-0/m-p/1821828#M351159</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-08T21:55:34Z</dc:date>
    </item>
    <item>
      <title>Re: (internal) Tables obsolete as parameter in function modules in ECC 6.0</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables-obsolete-as-parameter-in-function-modules-in-ecc-6-0/m-p/1821829#M351160</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Translating the error message -;)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
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".
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You should check you structures and assign the correct TYPE to the fields -:)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Blag.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Jan 2007 22:00:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables-obsolete-as-parameter-in-function-modules-in-ecc-6-0/m-p/1821829#M351160</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-08T22:00:35Z</dc:date>
    </item>
    <item>
      <title>Re: (internal) Tables obsolete as parameter in function modules in ECC 6.0</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables-obsolete-as-parameter-in-function-modules-in-ecc-6-0/m-p/1821830#M351161</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;if you have a field MANDT in your internal table zdfkkcohiparam, make sure it is declared as a client data type and not integer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Jan 2007 22:02:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables-obsolete-as-parameter-in-function-modules-in-ecc-6-0/m-p/1821830#M351161</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-08T22:02:52Z</dc:date>
    </item>
    <item>
      <title>Re: (internal) Tables obsolete as parameter in function modules in ECC 6.0</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables-obsolete-as-parameter-in-function-modules-in-ecc-6-0/m-p/1821831#M351162</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Alvaro,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I had translated this message earlier as well but they all seem to have the correct data types.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Divya&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Jan 2007 22:04:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables-obsolete-as-parameter-in-function-modules-in-ecc-6-0/m-p/1821831#M351162</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-08T22:04:30Z</dc:date>
    </item>
    <item>
      <title>Re: (internal) Tables obsolete as parameter in function modules in ECC 6.0</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables-obsolete-as-parameter-in-function-modules-in-ecc-6-0/m-p/1821832#M351163</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check the CLIENT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Jan 2007 22:09:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables-obsolete-as-parameter-in-function-modules-in-ecc-6-0/m-p/1821832#M351163</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-08T22:09:05Z</dc:date>
    </item>
    <item>
      <title>Re: (internal) Tables obsolete as parameter in function modules in ECC 6.0</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables-obsolete-as-parameter-in-function-modules-in-ecc-6-0/m-p/1821833#M351164</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Rob,&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks a bunch to both of you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Divya&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Jan 2007 22:11:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables-obsolete-as-parameter-in-function-modules-in-ecc-6-0/m-p/1821833#M351164</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-08T22:11:16Z</dc:date>
    </item>
    <item>
      <title>Re: (internal) Tables obsolete as parameter in function modules in ECC 6.0</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables-obsolete-as-parameter-in-function-modules-in-ecc-6-0/m-p/1821834#M351165</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Actually -;) I translate for all the guys out there who doesn't speak German...Like me -:)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Blag.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Jan 2007 22:12:06 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables-obsolete-as-parameter-in-function-modules-in-ecc-6-0/m-p/1821834#M351165</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-08T22:12:06Z</dc:date>
    </item>
    <item>
      <title>Re: (internal) Tables obsolete as parameter in function modules in ECC 6.0</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables-obsolete-as-parameter-in-function-modules-in-ecc-6-0/m-p/1821835#M351166</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;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.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Jan 2007 22:12:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables-obsolete-as-parameter-in-function-modules-in-ecc-6-0/m-p/1821835#M351166</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-08T22:12:25Z</dc:date>
    </item>
  </channel>
</rss>

