<?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: charcter warning in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/charcter-warning/m-p/1768615#M332088</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;there is no need of split, you can directly access the field of wa_itab.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;LOOP AT itab INTO wa_itab.&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;SPLIT itab AT ',' INTO:-- not required&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;a = wa_itab-osek_morsh&lt;/P&gt;&lt;P&gt;b = wa_itab-company_name&lt;/P&gt;&lt;P&gt;c = wa_itab-company_code.&lt;/P&gt;&lt;P&gt;APPEND itab.&lt;/P&gt;&lt;P&gt;ENDLOOP.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 04 Dec 2006 08:05:26 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-12-04T08:05:26Z</dc:date>
    <item>
      <title>charcter warning</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/charcter-warning/m-p/1768613#M332086</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hallow I declare table itab and wa I wont to doing a split action but I have a warning&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That itab must be a charcter type data object&lt;/P&gt;&lt;P&gt;What I doing wrong.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TYPES:BEGIN OF 1_itab,&lt;/P&gt;&lt;P&gt;      osek_morsh(15) TYPE n,&lt;/P&gt;&lt;P&gt;      company_name(30) TYPE c,&lt;/P&gt;&lt;P&gt;      company_code(5) TYPE n,&lt;/P&gt;&lt;P&gt;      END OF 1_itab.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thankes for your answer&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA: itab TYPE TABLE OF 1_itab,&lt;/P&gt;&lt;P&gt;      wa_itab LIKE LINE OF itab.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;LOOP AT itab INTO wa_itab.&lt;/P&gt;&lt;P&gt;    SPLIT itab AT ',' INTO:&lt;/P&gt;&lt;P&gt;       wa_itab-osek_morsh&lt;/P&gt;&lt;P&gt;       wa_itab-company_name&lt;/P&gt;&lt;P&gt;       wa_itab-company_code.&lt;/P&gt;&lt;P&gt;    APPEND itab.&lt;/P&gt;&lt;P&gt;  ENDLOOP.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Dec 2006 07:58:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/charcter-warning/m-p/1768613#M332086</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-12-04T07:58:56Z</dc:date>
    </item>
    <item>
      <title>Re: charcter warning</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/charcter-warning/m-p/1768614#M332087</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi &lt;/P&gt;&lt;P&gt; Split works for character type this way .. so do this way ..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;TYPES:BEGIN OF 1_itab,
osek_morsh(15) TYPE &amp;lt;b&amp;gt;c&amp;lt;/b&amp;gt;,
company_name(30) TYPE &amp;lt;b&amp;gt;c&amp;lt;/b&amp;gt;,
company_code(5) TYPE &amp;lt;b&amp;gt;c&amp;lt;/b&amp;gt;,
END OF 1_itab.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SPLIT f AT g INTO TABLE itab. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Extras: &lt;/P&gt;&lt;P&gt;As with variant 1 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Effect &lt;/P&gt;&lt;P&gt;Similar to variant 1 &lt;/P&gt;&lt;P&gt;The sections of f are placed in the internal table itab. The sytsem creates a table row for each section of f. &lt;/P&gt;&lt;P&gt;Note: If f ends with the separator string g, the system does not create an empty table row at the end. This is in contrast to what happens when g occurs at the beginning of f. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
TYPES: BEGIN OF ITAB_TYPE, 
        WORD(20), 
      END   OF ITAB_TYPE. 

DATA: ITAB TYPE STANDARD TABLE OF ITAB_TYPE WITH 
                NON-UNIQUE DEFAULT KEY INITIAL SIZE 5. 

SPLIT 'STOP Two STOP Three STOP   ' AT 'STOP' INTO TABLE ITAB. 

&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ITAB now has three rows. The first is empty, the second contains ' Two', and the third ' Three'. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Santosh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Dec 2006 08:02:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/charcter-warning/m-p/1768614#M332087</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-12-04T08:02:37Z</dc:date>
    </item>
    <item>
      <title>Re: charcter warning</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/charcter-warning/m-p/1768615#M332088</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;there is no need of split, you can directly access the field of wa_itab.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;LOOP AT itab INTO wa_itab.&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;SPLIT itab AT ',' INTO:-- not required&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;a = wa_itab-osek_morsh&lt;/P&gt;&lt;P&gt;b = wa_itab-company_name&lt;/P&gt;&lt;P&gt;c = wa_itab-company_code.&lt;/P&gt;&lt;P&gt;APPEND itab.&lt;/P&gt;&lt;P&gt;ENDLOOP.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Dec 2006 08:05:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/charcter-warning/m-p/1768615#M332088</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-12-04T08:05:26Z</dc:date>
    </item>
  </channel>
</rss>

