topic issues with unicode system in Application Development and Automation Discussions

topic issues with unicode system in Application Development and Automation Discussions https://community.sap.com/t5/application-development-and-automation-discussions/issues-with-unicode-system/m-p/1943328#M389103 <HTML><HEAD></HEAD><BODY><P>Hi all,</P><P></P><P>what kind of problems we can expect for tables i mean ztables when we go from non unicode system to unicode system</P><P></P><P>also aboutt he table maintenance generator do we need to regenerate the table maintenance.</P><P></P><P>please let me what all things will be effected when we move from non unicode sytem to unicode system</P><P></P><P>thanks</P></BODY></HTML> Sun, 18 Feb 2007 06:43:34 GMT Former Member 2007-02-18T06:43:34Z issues with unicode system https://community.sap.com/t5/application-development-and-automation-discussions/issues-with-unicode-system/m-p/1943328#M389103 <HTML><HEAD></HEAD><BODY><P>Hi all,</P><P></P><P>what kind of problems we can expect for tables i mean ztables when we go from non unicode system to unicode system</P><P></P><P>also aboutt he table maintenance generator do we need to regenerate the table maintenance.</P><P></P><P>please let me what all things will be effected when we move from non unicode sytem to unicode system</P><P></P><P>thanks</P></BODY></HTML> Sun, 18 Feb 2007 06:43:34 GMT https://community.sap.com/t5/application-development-and-automation-discussions/issues-with-unicode-system/m-p/1943328#M389103 Former Member 2007-02-18T06:43:34Z Re: issues with unicode system https://community.sap.com/t5/application-development-and-automation-discussions/issues-with-unicode-system/m-p/1943329#M389104 <HTML><HEAD></HEAD><BODY><P>SAP DB as UNICODE Database </P><P></P><P>SAP DB can be used as a UNICODE database.</P><P></P><P>UNICODE </P><P>Installing a UNICODE-Enabled Database </P><P>UNICODE and SQL </P><P>UNICODE in Programming Languages</P><P>_______________________________________________</P><P></P><P>Data types such as CHAR ASCII and CHAR EBCDIC are mainly suited to English and central European languages. With other character sets, a code attribute is usually used for these data types. This code attribute uses a different presentation code to ASCII and EBCDIC, even for internal storage in the database system. This causes problems if you want to access these database systems using a different character set, or if you want to exchange data between database systems with different character sets. </P><P></P><P>You can avoid these problems by using internal character coding in accordance with UNICODE. Internally, the UNICODE data is stored in UTF-16/UCS-2 format. In UTF-16/UCS-2 format, all characters are two bytes long. </P><P>SAP DB is able to display various presentation codes in UNICODE format (UNICODE code in line with ISO 10646, page 1).</P><P></P><P>Metadata in UNICODE</P><P></P><P>The names of the database objects (such as table or column names) can be stored internally in UNICODE and can therefore then be displayed in the required presentation code in the database tools. </P><P></P><P>Application data in UNICODE</P><P></P><P>SAP DB supports the code attribute UNICODE for the data types CHAR[ACTER], VARCHAR and LONG[VARCHAR].</P><P></P><P>See also: </P><P></P><P>Installing a UNICODE-Enabled Database</P><P></P><P>Reference Manual: SAP DB 7.4, Code attribute</P><P></P><P> Installing a UNICODE-Enabled Database </P><P></P><P>To make storage of metadata and application data in UNICODE , proceed as follows:</P><P></P><P>Metadata in UNICODE</P><P></P><P>When installing the database instance, set the database parameter _UNICODE to YES. </P><P></P><P>Application data in UNICODE</P><P></P><P>When installing the database instance, set the database parameter _UNICODE to YES. </P><P>Enter the code attribute UNICODE. </P><P></P><P></P><P>Please note that SAP DB UNICODE data is stored internally in UTF-16/UCS-2 format. As a result, double the space is required to store the UNICODE data in the database instance.</P><P></P><P>Procedure</P><P></P><P>Setting Database Parameter _UNICODE</P><P></P><P>Setting Code Attribute UNICODE</P><P>Setting the Database Parameter _UNICODE </P><P>In order to install a UNICODE-enabled database, the database parameter _UNICODE must be set to YES.</P><P></P><P></P><P></P><P>Note that you cannot change the database parameter _UNICODE once it has been set.</P><P></P><P>You can use the Database Manager to set the database parameter _UNICODE when you install the database instance.</P><P></P><P>Database Manager GUI</P><P>...</P><P></P><P> 1. Start the Database Wizard.</P><P></P><P> 2. Perform the first five installation steps.</P><P></P><P> 3. In step 6 (Parameters), choose Extended.</P><P></P><P> 4. Set the _UNICODE parameter to YES.</P><P></P><P> 5. Continue with the installation.</P><P></P><P>See also: Database Manager GUI: SAP DB 7.4, section Creating or Initializing a New Database Instance</P><P></P><P>Database Manager CLI</P><P>A script with configuration information for the database instance contains, among other things, lines for definition of the database parameters. You must insert the following line at this point:</P><P></P><P>param_put _UNICODE YES</P><P></P><P>See also: Database Manager CLI: SAP DB 7.4, Changing the Value of a Database Parameter</P><P></P><P> </P><P></P><P> Setting Code Attribute UNICODE </P><P>To be able to store the application data in UNICODE, the database must be UNICODE-enabled and you must set the code attribute UNICODE for the required application data (Installing a UNICODE-Enabled Database). You can set the code attribute in the following ways:</P><P></P><P>· Database parameter DEFAULT_CODE is not set to value UNICODE:</P><P></P><P>...</P><P></P><P>¡ If you specify the code attribute UNICODE in the column definition, then the application data is stored in UNICODE, only for this column.</P><P></P><P>¡ If you do not enter a code attribute, the code entered in the parameter DEFAULT_CODE is used for these column values.</P><P></P><P>· Database parameter DEFAULT_CODE is set to value UNICODE:</P><P></P><P>If you do not specify a code attribute or specify the code attribute UNICODE in the column definition, then the application data is stored in UNICODE for this column.</P><P></P><P>¡ If you specify a different code attribute, the data is stored using this code attribute.</P><P></P><P></P><P></P><P>Database parameter DEFAULT_CODE is set to value UNICODE.</P><P></P><P>Column definition</P><P> Result</P><P> </P><P>CHAR (n) UNICODE</P><P> UNICODE column</P><P> </P><P>CHAR (n) </P><P> UNICODE column</P><P> </P><P>CHAR (n) ASCII</P><P> ASCII column</P><P> </P><P>CHAR (n) BYTE</P><P> Code neutral, that is, the column values are not converted by the database system</P><P> </P><P></P><P>For information on setting database parameters, see the following documentation:</P><P></P><P>· Database Manager GUI: SAP DB 7.4, Displaying and Changing Database Parameters</P><P></P><P>· Database Manager CLI: SAP DB 7.4, Changing the Value of a Database Parameter</P><P></P><P> </P><P></P><P> </P><P>___________________________________________________________________________________________________</P><P></P><P> </P><P> Assignment Between Structures I </P><P></P><P> </P><P></P><P>In this example, includes are handled with group names.</P><P></P><P>Before Unicode conversion</P><P></P><P>types:</P><P></P><P> begin of T_STRUC,</P><P></P><P> F1 type c,</P><P></P><P> F2 type c,</P><P></P><P> F3 type i,</P><P></P><P> F4 type p,</P><P></P><P> end of T_STRUC.</P><P></P><P>data: begin of STRUC1.</P><P></P><P> include type T_STRUC.</P><P></P><P>data: F5 type x.</P><P></P><P>data: end of STRUC1.</P><P></P><P> </P><P></P><P>data: begin of STRUC2.</P><P></P><P> include type T_STRUC.</P><P></P><P>data: F6 type p.</P><P></P><P>data: end of STRUC2.</P><P></P><P> </P><P></P><P>STRUC1 = STRUC2. ß Unicode error</P><P></P><P> </P><P></P><P>In this case, only the contents of the include, that is the components F1 to F4, were to be assigned. The system accepted that the component was overwritten with an invalid value.</P><P></P><P> </P><P></P><P>After Unicode conversion</P><P></P><P> </P><P></P><P>The introduction of group names for the includes and the use of these group names for assignment allows you to simply change this part of the program.</P><P></P><P> </P><P></P><P>types:</P><P></P><P> begin of T_STRUC,</P><P></P><P> F1 type c,</P><P></P><P> F2 type c,</P><P></P><P> F3 type i,</P><P></P><P> F4 type p,</P><P></P><P> end of T_STRUC.</P><P></P><P></P><P>data: begin of STRUC1.</P><P></P><P> include type T_STRUC as PART1.</P><P></P><P>data: F5 type x.</P><P></P><P>data: end of STRUC1.</P><P></P><P> </P><P></P><P>data: begin of STRUC2.</P><P></P><P> include type T_STRUC as PART1.</P><P></P><P>data: F6 type p.</P><P></P><P>data: end of STRUC2.</P><P></P><P>STRUC1-PART1 = STRUC2-PART1. ß ok</P><P></P><P> ________________________________________________________________________________________________________</P><P></P><P></P><P> </P><P> Assignment Between Structures II </P><P></P><P>In this example, offset/length accesses to structures are handled.</P><P></P><P>Before Unicode conversion:</P><P></P><P>data:</P><P></P><P> begin of STRUC1,</P><P></P><P> F1(10) type c,</P><P></P><P> F2(20) type c,</P><P></P><P> F3 type i,</P><P></P><P> F4 type p,</P><P></P><P> end of STRUC1,</P><P></P><P> </P><P></P><P> begin of STRUC2,</P><P></P><P> C1(10) type c,</P><P></P><P> C2(20) type c,</P><P></P><P> C3 type x,</P><P></P><P> C4 type f,</P><P></P><P> end of STRUC2.</P><P></P><P> </P><P></P><P>STRUC1 = STRUC2. ß Unicode error</P><P></P><P> </P><P></P><P>In this example, it is assumed that only the content of the first two components C1 and C2 is transferred to F1 and F2 in the conversion, since the following components F3 and F4 are overwritten with invalid values anyway.</P><P></P><P> </P><P></P><P>After Unicode conversion</P><P></P><P> </P><P></P><P>Since the initial part of the structures, which is relevant to the intended assignment, is purely character-type, the assignment operands can each be selected using offset/length accesses.</P><P></P><P>....</P><P></P><P>STRUC1(30) = STRUC2(30). ß ok</P><P>________________________________________________________________________________________________________</P><P></P><P> </P><P> Assignments Between Structures III </P><P></P><P>*----</P><P>-</P><HR originaltext="-------------------------------------------------------" /><UL><LI level="1" type="ul"><P>MOVE: structure <-> structure (Offset)</P></LI></UL><P>*----</P><P>-</P><HR originaltext="-------------------------------------------------------" /><P></P><P>report ZCH_UNIEXP_3.</P><P></P><UL><LI level="1" type="ul"><P>Before Unicode enabling:</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>data: begin of STRUC1,</P></LI><LI level="1" type="ul"><P> F0 type x,</P></LI><LI level="1" type="ul"><P> F1(10) type c,</P></LI><LI level="1" type="ul"><P> F2(20) type c,</P></LI><LI level="1" type="ul"><P> F3 type i,</P></LI></UL><P> F4 type p,</P><UL><LI level="1" type="ul"><P> end of STRUC1,</P></LI></UL><P></P><UL><LI level="1" type="ul"><P> begin of STRUC2,</P></LI><LI level="1" type="ul"><P> C0 type i,</P></LI><LI level="1" type="ul"><P> C1(10) type c,</P></LI><LI level="1" type="ul"><P> C2(20) type c,</P></LI><LI level="1" type="ul"><P> C3 type x,</P></LI><LI level="1" type="ul"><P> C4 type f,</P></LI><LI level="1" type="ul"><P> end of STRUC2.</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>STRUC1<EM>1(30) = STRUC2</EM>4(30). <---- Unicode error !!</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>After Unicode enabling:</P></LI></UL><P></P><P>types: begin of PART1,</P><P> F1(10) type c,</P><P> F2(20) type c,</P><P> end of PART1,</P><P></P><P> begin of PART 2,</P><P> C1(10) type c,</P><P> C2(20) type c,</P><P> end of PART 2.</P><P></P><P>data: begin of STRUC1,</P><P> F0 type x.</P><P> include type PART1 as PART.</P><P>data: f3 type i,</P><P> f4 type p,</P><P> end of STRUC1,</P><P></P><P> begin of STRUC2,</P><P> C0 type i.</P><P> include type PART2 as PART.</P><P>data: C3 type x,</P><P> C4 type f,</P><P> end of STRUC2.</P><P></P><P>STRUC1-PART = STRUC2-PART.</P><P></P><P> </P><P></P><P>________________________________________________________________________________________________________</P><P></P><P></P><P>Assignments Between Structures IV </P><P></P><P>*----</P><P>-</P><HR originaltext="-------------------------------------------------------" /><UL><LI level="1" type="ul"><P>MOVE: structure <-> structure </P></LI></UL><P>*----</P><P>-</P><HR originaltext="-------------------------------------------------------" /><P></P><P>report ZCH_UNIEXP_4.</P><P></P><UL><LI level="1" type="ul"><P>Before Unicode enabling:</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>data: begin of STRUC1,</P></LI><LI level="1" type="ul"><P> F0(1) type x,</P></LI><LI level="1" type="ul"><P> F1(10) type c,</P></LI><LI level="1" type="ul"><P> F2(20) type c,</P></LI><LI level="1" type="ul"><P> F3 type i,</P></LI><LI level="1" type="ul"><P> F4 type p,</P></LI><LI level="1" type="ul"><P> end of STRUC1,</P></LI></UL><P></P><UL><LI level="1" type="ul"><P> begin of STRUC2,</P></LI><LI level="1" type="ul"><P> C0(1) type c,</P></LI><LI level="1" type="ul"><P> C1(10) type c,</P></LI><LI level="1" type="ul"><P> C2(20) type c,</P></LI><LI level="1" type="ul"><P> C3 type i,</P></LI><LI level="1" type="ul"><P> C4 type f,</P></LI><LI level="1" type="ul"><P> end of STRUC2,</P></LI></UL><P></P><UL><LI level="1" type="ul"><P> begin of STRUC3,</P></LI><LI level="1" type="ul"><P> G0(1) type c,</P></LI></UL><P></P><UL><LI level="1" type="ul"><P> G1(10) type c,</P></LI><LI level="1" type="ul"><P> G2(20) type c,</P></LI><LI level="1" type="ul"><P> end of STRUC3.</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>STRUC1<EM>1(35) = STRUC2</EM>1(35). <---- Unicode error !!</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>STRUC3 = STRUC2.</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>INCLUDE STRUCTURE does not work here:</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>types: begin of PART1,</P></LI><LI level="1" type="ul"><P> F1(10) type c,</P></LI><LI level="1" type="ul"><P> F2(20) type c,</P></LI><LI level="1" type="ul"><P> F3 type i,</P></LI><LI level="1" type="ul"><P> end of PART1,</P></LI></UL><P></P><UL><LI level="1" type="ul"><P> begin of PART2,</P></LI><LI level="1" type="ul"><P> C1(10) type c,</P></LI><LI level="1" type="ul"><P> C2(20) type c,</P></LI><LI level="1" type="ul"><P> C3 type i,</P></LI><LI level="1" type="ul"><P> end of PART2.</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>data: begin of STRUC1,</P></LI><LI level="1" type="ul"><P> F0(1) type x.</P></LI><LI level="1" type="ul"><P> include type PART1 as PART.</P></LI><LI level="1" type="ul"><P>data: F4 type p,</P></LI><LI level="1" type="ul"><P> end of struc1.</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>data: begin of STRUC2,</P></LI><LI level="1" type="ul"><P> C0(1) type c.</P></LI><LI level="1" type="ul"><P> include type PART2 as PART.</P></LI><LI level="1" type="ul"><P>data: C4 type f,</P></LI><LI level="1" type="ul"><P> end of STRUC2,</P></LI></UL><P></P><UL><LI level="1" type="ul"><P> begin of STRUC3, </P></LI><LI level="1" type="ul"><P> G0(1) type c,</P></LI><LI level="1" type="ul"><P> G1(10) type c,</P></LI><LI level="1" type="ul"><P> G2(20) type c,</P></LI><LI level="1" type="ul"><P> end of STRUC3.</P></LI><LI level="1" type="ul"><P>STRUC1-PART = STRUC2-PART.</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>STRUC3 = STRUC2. <---- new Unicode error !!</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>Due to the insertion of include PART2 in STRUC2, there is a </P></LI><LI level="1" type="ul"><P>new alignment gap between STRUC2-C0 and STRUC2-C1</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>After Unicode enabling:</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>Please use MOVE-CORRESPONDING if the fieldnames do match, </P></LI><LI level="1" type="ul"><P>otherwise move single fields</P></LI></UL><P></P><P>data: begin of STRUC1, </P><P> F0(1) type x,</P><P> F1(10) type c,</P><P> F2(20) type c,</P><P> F3 type i,</P><P> F4 type p,</P><P> end of STRUC1,</P><P></P><P> begin of STRUC2,</P><P> C0(1) type c,</P><P> C1(10) type c,</P><P> C2(20) type c,</P><P> C3 type i,</P><P> C4 type f,</P><P> end of STRUC2,</P><P></P><P> begin of STRUC3,</P><P> G0(1) type c,</P><P> G1(10) type c,</P><P> G2(20) type c,</P><P> end of STRUC3.</P><P></P><P>STRUC1-F1 = STRUC2-C1.</P><P>STRUC1-F2 = STRUC2-C2.</P><P>STRUC1-F3 = STRUC2-C3.</P><P></P><P>STRUC3 = STRUC2.</P><P></P><P> </P><P></P><P> </P><P>________________________________________________________________________________________________________</P><P></P><P></P><P>Assignment Between Structure and Single Field I </P><P></P><P>*----</P><P>-</P><HR originaltext="-------------------------------------------------------" /><UL><LI level="1" type="ul"><P>MOVE: structure <-> single field </P></LI></UL><P>*----</P><P>-</P><HR originaltext="-------------------------------------------------------" /><P></P><P>report ZCH_UNIEXP_5.</P><P></P><P>data: begin of STRUC,</P><P> YEAR(4) type n,</P><P> MONTH(2) type n,</P><P> DAY(2) type n,</P><P> F4 type p,</P><P> end of STRUC,</P><P></P><P> DATE type d.</P><P></P><UL><LI level="1" type="ul"><P>Before Unicode enabling</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>date = struc. <---- Unicode error</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>After Unicode enabling</P></LI></UL><P>date = struc(8).</P><P></P><P> ________________________________________________________________________________________________________</P><P></P><P> </P><P> Assignment Between Structure and Single Field II </P><P></P><P>*----</P><P>-</P><HR originaltext="-------------------------------------------------------" /><UL><LI level="1" type="ul"><P>MOVE: structure <-> single field </P></LI></UL><P>-</P><P>-</P><HR originaltext="------------------------------------------------------------" /><P></P><P>report ZCH_UNIEXP_6.</P><P></P><P>data: begin of STRUC,</P><P> NUMBER(20) type n,</P><P> F2 type p,</P><P> end of STRUC,</P><P></P><P> NUMBER(20) type n.</P><P></P><UL><LI level="1" type="ul"><P>Before Unicode enabling</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>NUMBER = STRUC. <---- Unicode error</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>After Unicode enabling</P></LI></UL><P></P><P>NUMBER = STRUC-NUMBER.</P><P></P><P> __________________________________________________________________</P><P></P><P>Assignment Between Structure and Single Field III </P><P></P><P>*----</P><P>-</P><HR originaltext="-------------------------------------------------------" /><UL><LI level="1" type="ul"><P>MOVE: structure <-> single field </P></LI></UL><P>*----</P><P>-</P><HR originaltext="-------------------------------------------------------" /><P></P><P>report ZCH_UNIEXP_7.</P><P></P><P>data: begin of TAB,</P><P> X(1) type x value '09',</P><P> end of tab,</P><P></P><P> C(10) type c.</P><P></P><UL><LI level="1" type="ul"><P>Before Unicode enabling:</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>c+5(1) = tab. <---- Unicode error</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>After Unicode enabling</P></LI></UL><P></P><P>class cl_abap_char_utilities definition load.</P><P>c+5(1) = cl_abap_char_utilities=>horizontal_tab</P><P></P><P> </P><P></P><P> _____________________________________________________________</P><P></P><P>Assignment Between Structure and Single Field V </P><P></P><P>*----</P><P>-</P><HR originaltext="-------------------------------------------------------" /><UL><LI level="1" type="ul"><P>MOVE: structure <-> single field </P></LI></UL><P>*----</P><P>-</P><HR originaltext="-------------------------------------------------------" /><P></P><P>report ZCH_UNIEXP_9.</P><P></P><UL><LI level="1" type="ul"><P>types: begin of T_VALUE_WA,</P></LI><LI level="1" type="ul"><P> TABNAME(30) type c,</P></LI><LI level="1" type="ul"><P> DUMMY_ALIGN type f,</P></LI><LI level="1" type="ul"><P> CONTAINER(1000) type c,</P></LI><LI level="1" type="ul"><P> end of T_VALUE_WA,</P></LI><LI level="1" type="ul"><P> T_VALUE_LIST type table of T_VALUE_WA.</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>data: L_VALUES type T_VALUE_LIST,</P></LI><LI level="1" type="ul"><P> L_VALUE_WA type T_VALUE_WA,</P></LI><LI level="1" type="ul"><P> L_D010SINF type D010SINF,</P></LI><LI level="1" type="ul"><P> L_CO2MAP type CO2MAP.</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>L_VALUE_WA-TABNAME = 'D010SINF'.</P></LI><LI level="1" type="ul"><P>L_D010SINF-DATALG = 41.</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>L_VALUE_WA-CONTAINER = L_D010SINF. <---- Unicode error</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>append L_VALUE_WA to L_VALUES.</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>L_VALUE_WA-TABNAME = 'CO2MAP'.</P></LI><LI level="1" type="ul"><P>L_CO2MAP-ID = 42.</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>L_VALUE_WA-CONTAINER = L_CO2MAP. <---- Unicode error</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>append L_VALUE_WA to L_VALUES.</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>Pass L_VALUES to processing routine ...</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>Do something</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>data: L_DFIES_TAB type table of DFIES.</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>field-symbols: <DT> type DFIES,</P></LI><LI level="1" type="ul"><P> <VALUE_WA> type T_VALUE_WA,</P></LI><LI level="1" type="ul"><P> <f>.</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>clear L_VALUES_WA.</P></LI><LI level="1" type="ul"><P>loop at L_VALUES assigning <VALUE_WA>.</P></LI></UL><P></P><UL><LI level="1" type="ul"><P> call function 'DDIF_NAMETAB_GET'</P></LI><LI level="1" type="ul"><P> exporting</P></LI><LI level="1" type="ul"><P> tabname = <VALUE_WA>-TABNAME</P></LI><LI level="1" type="ul"><P> tables</P></LI><LI level="1" type="ul"><P> DFIES_TAB = L_DFIES_TAB.</P></LI></UL><P></P><UL><LI level="1" type="ul"><P> loop at L_DFIES_TAB assigning <DT>.</P></LI><LI level="1" type="ul"><P> assign <VALUE_WA>-CONTAINER+<DT>-OFFSET(<DT>-INLEN)</P></LI><LI level="1" type="ul"><P> to <F> type <DT>-INTTYPE.</P></LI><LI level="1" type="ul"><P> write <F>.</P></LI><LI level="1" type="ul"><P> endloop.</P></LI><LI level="1" type="ul"><P>endloop.</P></LI></UL><P></P><UL><LI level="1" type="ul"><P>After using (Unicode enabled) new reference technique </P></LI><LI level="1" type="ul"><P>and EXPORT TO DATA BUFFER:</P></LI></UL><P></P><P>types: begin of T_VALUE_WA,</P><P> TABNAME(30) type c,</P><P> XWA type xstring,</P><P> CONTAINER(1000) type c,</P><P> end of T_VALUE_WA,</P><P></P><P> T_VALUE_LIST type table of T_VALUE_WA.</P><P></P><P>data: L_VALUES type T_VALUE_LIST,</P><P> L_VALUE_WA type T_VALUE_WA,</P><P> L_D010SINF type D010SINF,</P><P> L_CO2MAP type CO2MAP.</P><P></P><P>L_D010SINF-DATALG = 41.</P><P>L_VALUE_WA-TABNAME = 'D010SINF'.</P><P>export WA from L_D010SINF to data buffer L_VALUE_WA-XWA.</P><P>append L_VALUE_WA to L_VALUES.</P><P></P><P>L_CO2MAP-ID = 42.</P><P>L_VALUE_WA-TABNAME = 'CO2MAP'.</P><P>export WA from L_CO2MAP to data buffer L_VALUE_WA-XWA.</P><P>append L_VALUE_WA to L_VALUES.</P><P></P><UL><LI level="1" type="ul"><P>Pass L_VALUE to processing routine ...</P></LI><LI level="1" type="ul"><P>Do something</P></LI></UL><P></P><P>data: DREF type ref to data,</P><P> L_NUMBER type i,</P><P> L_TYPE type c.</P><P></P><P>field-symbols: .</P><P> enddo.</P><P>endloop.</P><P></P></BODY></HTML> Sun, 18 Feb 2007 07:02:56 GMT https://community.sap.com/t5/application-development-and-automation-discussions/issues-with-unicode-system/m-p/1943329#M389104 SantoshKallem 2007-02-18T07:02:56Z