<?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: NUMC value saved in Database without leading 0 in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/numc-value-saved-in-database-without-leading-0/m-p/380306#M9051</link>
    <description>&lt;P&gt;Welcome to reality &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;&lt;P&gt;NUMC is a semantical dictionary type. On the database it's simply characters. No problem getting "illegal" values in there. Even in ABAP you can easily fill type n fields with alphas and then, when you save those ...&lt;/P&gt;&lt;P&gt;Same for DATS and TIMS. No guarantee for valid values.&lt;/P&gt;&lt;P&gt;In the ABAP world it's mainly the classical Dynpros that care for valid values. That's why batch input was/is so important.&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/abapdocu_751/en/index.htm?file=abenddic_special_character_types.htm"&gt;http://help.sap.com/abapdocu_751/en/index.htm?file=abenddic_special_character_types.htm&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 13 Feb 2017 15:47:06 GMT</pubDate>
    <dc:creator>retired_member</dc:creator>
    <dc:date>2017-02-13T15:47:06Z</dc:date>
    <item>
      <title>NUMC value saved in Database without leading 0</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/numc-value-saved-in-database-without-leading-0/m-p/380305#M9050</link>
      <description>&lt;P&gt;Hello to all,&lt;/P&gt;&lt;P&gt;I've encountered a weird case in which a database field defined as NUMC of length 14 has values stored without the appropiate leading zeroes.&lt;/P&gt;&lt;P&gt;How could this happen? The field is, and has always been, defined as NUMC.&lt;/P&gt;&lt;P&gt;I'm really shocked. Any ideas on how come did this happen?&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;Best regards.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Feb 2017 15:22:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/numc-value-saved-in-database-without-leading-0/m-p/380305#M9050</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2017-02-13T15:22:32Z</dc:date>
    </item>
    <item>
      <title>Re: NUMC value saved in Database without leading 0</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/numc-value-saved-in-database-without-leading-0/m-p/380306#M9051</link>
      <description>&lt;P&gt;Welcome to reality &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;&lt;P&gt;NUMC is a semantical dictionary type. On the database it's simply characters. No problem getting "illegal" values in there. Even in ABAP you can easily fill type n fields with alphas and then, when you save those ...&lt;/P&gt;&lt;P&gt;Same for DATS and TIMS. No guarantee for valid values.&lt;/P&gt;&lt;P&gt;In the ABAP world it's mainly the classical Dynpros that care for valid values. That's why batch input was/is so important.&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/abapdocu_751/en/index.htm?file=abenddic_special_character_types.htm"&gt;http://help.sap.com/abapdocu_751/en/index.htm?file=abenddic_special_character_types.htm&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 13 Feb 2017 15:47:06 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/numc-value-saved-in-database-without-leading-0/m-p/380306#M9051</guid>
      <dc:creator>retired_member</dc:creator>
      <dc:date>2017-02-13T15:47:06Z</dc:date>
    </item>
  </channel>
</rss>

