<?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: data type issue in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-type-issue/m-p/4483254#M1061371</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;Try with the domain type WERTV6&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;Surinder&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 11 Sep 2008 06:04:15 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-09-11T06:04:15Z</dc:date>
    <item>
      <title>data type issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-type-issue/m-p/4483250#M1061367</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;This might sound very silly to u.but i am finding it a  difficult. I have a field which is to enter interest rate in percentage.it might be a whole number or it might be a decimal number.i have tried giving this type using data elements with curr,quan etc...how do i proceed?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Sep 2008 05:55:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/data-type-issue/m-p/4483250#M1061367</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-09-11T05:55:07Z</dc:date>
    </item>
    <item>
      <title>Re: data type issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-type-issue/m-p/4483251#M1061368</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hii&lt;/P&gt;&lt;P&gt;it is not wrong to ask such questions...&lt;/P&gt;&lt;P&gt;coming to the answer...&lt;/P&gt;&lt;P&gt;TRANSLATE&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Variants&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. TRANSLATE c TO UPPER CASE.&lt;/P&gt;&lt;P&gt;2. TRANSLATE c TO LOWER CASE.&lt;/P&gt;&lt;P&gt;3. TRANSLATE c USING c1.&lt;/P&gt;&lt;P&gt;4. TRANSLATE c FROM CODE PAGE g1 TO CODE PAGE g2.&lt;/P&gt;&lt;P&gt;5. TRANSLATE c FROM NUMBER FORMAT n1 TO NUMBER FORMAT n2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Variant 1&lt;/P&gt;&lt;P&gt;TRANSLATE c TO UPPER CASE.&lt;/P&gt;&lt;P&gt;Variant 2&lt;/P&gt;&lt;P&gt;TRANSLATE c TO LOWER CASE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Effect&lt;/P&gt;&lt;P&gt;In the field c , converts all lower case letters to upper case or all upper case letters to lower case, as specified.&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;DATA LETTERS(3).&lt;/P&gt;&lt;P&gt;MOVE 'abc' TO LETTERS.&lt;/P&gt;&lt;P&gt;TRANSLATE LETTERS TO UPPER CASE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The field LETTERS now contains 'ABC' .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Variant 3&lt;/P&gt;&lt;P&gt;TRANSLATE c USING c1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Effect&lt;/P&gt;&lt;P&gt;Replaces the letters in the field c according to the contents of c1 .&lt;/P&gt;&lt;P&gt;If a character in c also exists in c1, it is replaced by the letter that f o l l o w s it in c1. If a character from c is not found in c1, it remains unchanged.&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;DATA: LETTERS(10) VALUE 'abcX',&lt;/P&gt;&lt;P&gt;CHANGE(6) VALUE 'aXBY'.&lt;/P&gt;&lt;P&gt;TRANSLATE LETTERS USING CHANGE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The field LETTERS now contains 'XbcX' .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Variant 4&lt;/P&gt;&lt;P&gt;TRANSLATE c ...FROM CODE PAGE g1 ...TO CODE PAGE g2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TRANSLATE F TO CODE PAGE G2.&lt;/P&gt;&lt;P&gt;TRANSLATE F FROM CODE PAGE G1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Effect&lt;/P&gt;&lt;P&gt;Performs a character code conversion in the field F . To achieve this, the SAP character code is determined from the conversion table G1 and a new character code derived from G2 . You can use the Transaction SPAD to maintain the conversion tables TCP00 - TCP02 .&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;DATA F(72).&lt;/P&gt;&lt;P&gt;TRANSLATE F FROM CODE PAGE '1110' TO CODE PAGE '0100'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;translates the contents of F from the HP character set to EBCDIC ( IBM 274).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note&lt;/P&gt;&lt;P&gt;Type I , P , F and X fields remain unchanged. Field strings and work areas of internal tables are converted to the correct type for each individual field. At present, table work areas (as defined in TABLES ... ) are not treated according to type, but are converted as a whole. If necessary, declare a field string with INCLUDE STRUCTURE and then perform a conversion.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Variant 5&lt;/P&gt;&lt;P&gt;TRANSLATE c ...FROM NUMBER FORMAT n1 ...TO NUMBER FORMAT n2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TRANSLATE F TO NUMBER FORMAT N1.&lt;/P&gt;&lt;P&gt;TRANSLATE F FROM NUMBER FORMAT N1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Effect&lt;/P&gt;&lt;P&gt;Performs a number format conversion in the field F . The number formats supported at present are '0000' ( HP , SINIX , IBM ) and '0101' ( DEC alpha OSF ). Any attempt to enter formats other than these results in a runtime error. If you omit FROM NUMBER FORMAT or TO NUMBER FORMAT , the system number format is used for the omitted part.&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;DATA: F TYPE F,&lt;/P&gt;&lt;P&gt;HEX (2) TYPE X,&lt;/P&gt;&lt;P&gt;NFORM LIKE TCP00-CPCODEPAGE.&lt;/P&gt;&lt;P&gt;...&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;In /ARCHIV was stored by another platform from HEX and F.&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;HEX contains the valid number format and can be read on all&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;platforms.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;READ DATASET '/ARCHIV' INTO HEX.&lt;/P&gt;&lt;P&gt;READ DATASET '/ARCHIV INTO F.&lt;/P&gt;&lt;P&gt;NFORM = HEX. "Conversion of machine-independent HEX to NUMC(4)&lt;/P&gt;&lt;P&gt;TRANSLATE F FROM NUMBER FORMAT NFORM.&lt;/P&gt;&lt;P&gt;&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;Converts the contents of F from the format NFORM of a platform to the system format.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note&lt;/P&gt;&lt;P&gt;Type I and F fields are converted. Field strings and work areas of internal tables are converted to the correct type for each individual field. Table work areas (as defined with TABLES ... ) are treated as type C at present and are not converted. If necessary, declare a field string with INCLUDE STRUCTURE and then perform a conversion.&lt;/P&gt;&lt;P&gt;In the interests of storing additional information for archiving purposes, you can use the function module SYSTEM_FORMAT to display the system code page and system number format.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note&lt;/P&gt;&lt;P&gt;Performance&lt;/P&gt;&lt;P&gt;Converting lower case letters to upper case letters or upper case letters to lower case letters in a 10-byte long character field takes approx. 7 msn (standardized microseconds).&lt;/P&gt;&lt;P&gt;Replacing two letters in a 10-byte long field with the variant ... c USING c1 ... takes approx. 9 msn.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note&lt;/P&gt;&lt;P&gt;Runtime errors&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TRANSLATE_WRONG_NUM_FORMAT : Invalid number format.&lt;/P&gt;&lt;P&gt;hope this hepls you...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Sep 2008 06:00:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/data-type-issue/m-p/4483251#M1061368</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-09-11T06:00:24Z</dc:date>
    </item>
    <item>
      <title>Re: data type issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-type-issue/m-p/4483252#M1061369</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;try it with&lt;/P&gt;&lt;P&gt;...type PRZ31&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;or&lt;/P&gt;&lt;P&gt;....type ABWERT_PRZ&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Nicole&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Sep 2008 06:01:47 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/data-type-issue/m-p/4483252#M1061369</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-09-11T06:01:47Z</dc:date>
    </item>
    <item>
      <title>Re: data type issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-type-issue/m-p/4483253#M1061370</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;try with DEC data Type where length is 5 with 2 decimal places&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Sep 2008 06:03:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/data-type-issue/m-p/4483253#M1061370</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-09-11T06:03:16Z</dc:date>
    </item>
    <item>
      <title>Re: data type issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-type-issue/m-p/4483254#M1061371</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;Try with the domain type WERTV6&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;Surinder&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Sep 2008 06:04:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/data-type-issue/m-p/4483254#M1061371</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-09-11T06:04:15Z</dc:date>
    </item>
    <item>
      <title>Re: data type issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-type-issue/m-p/4483255#M1061372</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;try this...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DDPERCENT data elt&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Sep 2008 06:07:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/data-type-issue/m-p/4483255#M1061372</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-09-11T06:07:30Z</dc:date>
    </item>
  </channel>
</rss>

