<?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: cluster table in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/cluster-table/m-p/3191423#M760256</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;to read and writing the data to cluster tables and pool tables  &lt;/P&gt;&lt;P&gt;we use import and export statement we use,.............&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;syntax will be like this.....&lt;/P&gt;&lt;P&gt;Storing Data as Clusters &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;New variants of the IMPORT and EXPORT statements are available to support heterogeneous Unicode environments. They allow you to store data as a cluster in an XSTRING in a cross-platform format You can use the following variants:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Storage in the DATA BUFFER&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EXPORT {pi = dobji | pi FROM dobji } TO DATA BUFFER dbuf.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EXPORT (itab) TO DATA BUFFER dbuf.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Stores the objects dobj1 ... dobjn (fields, flat structures, complex structures, or tables) as a cluster in the data buffer, dbuf, which must be of type XSTRING. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IMPORT {pi = dobji | pi FROM dobji } FROM DATA BUFFER dbuf.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IMPORT (itab) FROM DATA BUFFER dbuf.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Imports the data objects dobj1 ... dobjn (fields, flat structures, complex structures, or tables) from a data cluster in the data buffer entered, dbuf¸ which must be of type XSTRING. The system reads all the data that was previously stored in the data buffer dbuf using the EXPORT ... TO DATA BUFFER statement. Again, the system does not check that the structures in the EXPORT and IMPORT statements match. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the data objects are specified dynamically, the parameter list in the two-column index table, itab, is passed. The columns in this table must be of type C or STRING. The first column of itab contains the name of each parameter, while the second lists the data objects. If the first column of itab is empty, an exception that cannot be handled occurs, with the runtime error DYN_IMEX_OBJ_NAME_EMPTY. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TYPES:&lt;/P&gt;&lt;P&gt;    BEGIN OF ITAB_TYPE,&lt;/P&gt;&lt;P&gt;      CONT TYPE C LENGTH 4,&lt;/P&gt;&lt;P&gt;    END OF ITAB_TYPE. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  DATA: &lt;/P&gt;&lt;P&gt;    XSTR TYPE XSTRING, &lt;/P&gt;&lt;P&gt;    F1 TYPE C LENGTH 4, &lt;/P&gt;&lt;P&gt;    F2 TYPE P, &lt;/P&gt;&lt;P&gt;    ITAB TYPE STANDARD TABLE OF ITAB_TYPE. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  EXPORT P1  = F1 &lt;/P&gt;&lt;P&gt;         P2  = F2 &lt;/P&gt;&lt;P&gt;         TAB = ITAB TO DATA BUFFER XSTR.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The New CODE PAGE HINT Addition&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You use this addition in conjunction with ambiguous code pages in the EXPORT obj1 ... objn TO &lt;A href="https://community.sap.com/DATABASE"&gt; DATA BUFFER &lt;/A&gt; statement. It specifies the code page, f1, which is to be used to interpret the import data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 20 Dec 2007 04:26:04 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-12-20T04:26:04Z</dc:date>
    <item>
      <title>cluster table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/cluster-table/m-p/3191422#M760255</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Anybody tell me where we can use cluster table and pooled table?what is the use?how to enter the data into this tables?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Dec 2007 04:18:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/cluster-table/m-p/3191422#M760255</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-20T04:18:09Z</dc:date>
    </item>
    <item>
      <title>Re: cluster table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/cluster-table/m-p/3191423#M760256</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;to read and writing the data to cluster tables and pool tables  &lt;/P&gt;&lt;P&gt;we use import and export statement we use,.............&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;syntax will be like this.....&lt;/P&gt;&lt;P&gt;Storing Data as Clusters &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;New variants of the IMPORT and EXPORT statements are available to support heterogeneous Unicode environments. They allow you to store data as a cluster in an XSTRING in a cross-platform format You can use the following variants:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Storage in the DATA BUFFER&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EXPORT {pi = dobji | pi FROM dobji } TO DATA BUFFER dbuf.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EXPORT (itab) TO DATA BUFFER dbuf.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Stores the objects dobj1 ... dobjn (fields, flat structures, complex structures, or tables) as a cluster in the data buffer, dbuf, which must be of type XSTRING. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IMPORT {pi = dobji | pi FROM dobji } FROM DATA BUFFER dbuf.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IMPORT (itab) FROM DATA BUFFER dbuf.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Imports the data objects dobj1 ... dobjn (fields, flat structures, complex structures, or tables) from a data cluster in the data buffer entered, dbuf¸ which must be of type XSTRING. The system reads all the data that was previously stored in the data buffer dbuf using the EXPORT ... TO DATA BUFFER statement. Again, the system does not check that the structures in the EXPORT and IMPORT statements match. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the data objects are specified dynamically, the parameter list in the two-column index table, itab, is passed. The columns in this table must be of type C or STRING. The first column of itab contains the name of each parameter, while the second lists the data objects. If the first column of itab is empty, an exception that cannot be handled occurs, with the runtime error DYN_IMEX_OBJ_NAME_EMPTY. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TYPES:&lt;/P&gt;&lt;P&gt;    BEGIN OF ITAB_TYPE,&lt;/P&gt;&lt;P&gt;      CONT TYPE C LENGTH 4,&lt;/P&gt;&lt;P&gt;    END OF ITAB_TYPE. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  DATA: &lt;/P&gt;&lt;P&gt;    XSTR TYPE XSTRING, &lt;/P&gt;&lt;P&gt;    F1 TYPE C LENGTH 4, &lt;/P&gt;&lt;P&gt;    F2 TYPE P, &lt;/P&gt;&lt;P&gt;    ITAB TYPE STANDARD TABLE OF ITAB_TYPE. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  EXPORT P1  = F1 &lt;/P&gt;&lt;P&gt;         P2  = F2 &lt;/P&gt;&lt;P&gt;         TAB = ITAB TO DATA BUFFER XSTR.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The New CODE PAGE HINT Addition&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You use this addition in conjunction with ambiguous code pages in the EXPORT obj1 ... objn TO &lt;A href="https://community.sap.com/DATABASE"&gt; DATA BUFFER &lt;/A&gt; statement. It specifies the code page, f1, which is to be used to interpret the import data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Dec 2007 04:26:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/cluster-table/m-p/3191423#M760256</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-20T04:26:04Z</dc:date>
    </item>
    <item>
      <title>Re: cluster table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/cluster-table/m-p/3191424#M760257</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/cf/21f083446011d189700000e8322d00/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/cf/21f083446011d189700000e8322d00/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;check this link...&lt;/P&gt;&lt;P&gt;Hope this helps u...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points if Helpful&lt;/P&gt;&lt;P&gt;Jgds&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Dec 2007 04:48:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/cluster-table/m-p/3191424#M760257</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-20T04:48:16Z</dc:date>
    </item>
  </channel>
</rss>

