<?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: NULL and SPACE in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/null-and-space/m-p/887807#M52800</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Richard,&lt;/P&gt;&lt;P&gt;the Requirement to check for NULL corresponds to the definition of the database (field) within the DDIC. Check the flag initialize (it has also some documentation).&lt;/P&gt;&lt;P&gt;This flag is intended to be used if the definition of the db table is changed at SAP while the table already is used at customer side. &lt;/P&gt;&lt;P&gt;After deploying the corresponding patch or upgrade such a changed definition may result into the need to convert all entries. For tables with many entries this would result into inacceptable downtime. So such changes are done without the initialiazation/conversion of existing entries. &lt;/P&gt;&lt;P&gt;The tradeoff is the syntax you noticed.&lt;/P&gt;&lt;P&gt;Kind regards&lt;/P&gt;&lt;P&gt;Klaus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 17 Mar 2005 17:47:00 GMT</pubDate>
    <dc:creator>former_member183804</dc:creator>
    <dc:date>2005-03-17T17:47:00Z</dc:date>
    <item>
      <title>NULL and SPACE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/null-and-space/m-p/887806#M52799</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Gurus:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have had to use BOTH 'null' and 'space' (ofcourse I tried 'initial' too...) when selecting data from PRPS table, otherwise all the required records were not fetched. I had to do this on two different occassions. The first is a SAP provided field and the other is customer's enhancement. I have cut-paste the two code blocks. Any ideas why? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;Sard.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;***********&lt;STRONG&gt;(1)&lt;/STRONG&gt;**************&lt;/P&gt;&lt;P&gt; select posid objnr func_area zzfunct from prps into&lt;/P&gt;&lt;P&gt;                corresponding fields of table it_wbs&lt;/P&gt;&lt;P&gt;                          where func_area is null or&lt;/P&gt;&lt;P&gt;                                func_area eq space.&lt;/P&gt;&lt;P&gt;************&lt;STRONG&gt;(2)&lt;/STRONG&gt;**************&lt;/P&gt;&lt;P&gt; select prps-pspnr prps-posid prps-post1&lt;/P&gt;&lt;P&gt;        ...&lt;/P&gt;&lt;P&gt;   into (wa_test1-pspnr, wa_test1-posid, wa_test1-post1,&lt;/P&gt;&lt;P&gt;         ...)&lt;/P&gt;&lt;P&gt;   from prps &lt;/P&gt;&lt;P&gt;  where prps-posid in s_wbs and&lt;/P&gt;&lt;P&gt;        ...                 and&lt;/P&gt;&lt;P&gt;       ( prps-zzmlind is null or prps-zzmlind eq space ).&lt;/P&gt;&lt;P&gt;                              .&lt;/P&gt;&lt;P&gt; append wa_test1 to it_test1.&lt;/P&gt;&lt;P&gt; clear wa_test1.&lt;/P&gt;&lt;P&gt; endselect.&lt;/P&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;UL&gt;&lt;LI level="34" type="ul"&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Mar 2005 17:15:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/null-and-space/m-p/887806#M52799</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-03-17T17:15:23Z</dc:date>
    </item>
    <item>
      <title>Re: NULL and SPACE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/null-and-space/m-p/887807#M52800</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Richard,&lt;/P&gt;&lt;P&gt;the Requirement to check for NULL corresponds to the definition of the database (field) within the DDIC. Check the flag initialize (it has also some documentation).&lt;/P&gt;&lt;P&gt;This flag is intended to be used if the definition of the db table is changed at SAP while the table already is used at customer side. &lt;/P&gt;&lt;P&gt;After deploying the corresponding patch or upgrade such a changed definition may result into the need to convert all entries. For tables with many entries this would result into inacceptable downtime. So such changes are done without the initialiazation/conversion of existing entries. &lt;/P&gt;&lt;P&gt;The tradeoff is the syntax you noticed.&lt;/P&gt;&lt;P&gt;Kind regards&lt;/P&gt;&lt;P&gt;Klaus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Mar 2005 17:47:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/null-and-space/m-p/887807#M52800</guid>
      <dc:creator>former_member183804</dc:creator>
      <dc:date>2005-03-17T17:47:00Z</dc:date>
    </item>
    <item>
      <title>Re: NULL and SPACE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/null-and-space/m-p/887808#M52801</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Klaus:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you very much. YOU WERE PRECISE, func_area field was changed in the Enterprise version, and I noticed the problem during our upgrade.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Btw, is there a way for me to check the flag initialize for the customer field(zzmlind) added in structure CI_PRPS, without needing the access key to PRPS?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again for your time and the reply.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Mar 2005 21:09:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/null-and-space/m-p/887808#M52801</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-03-17T21:09:14Z</dc:date>
    </item>
    <item>
      <title>Re: NULL and SPACE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/null-and-space/m-p/887809#M52802</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No, by doing so, you are changing the definition of PRPS, hence the reason it is asking for access key.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Rich Heilman&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Mar 2005 21:15:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/null-and-space/m-p/887809#M52802</guid>
      <dc:creator>RichHeilman</dc:creator>
      <dc:date>2005-03-17T21:15:51Z</dc:date>
    </item>
  </channel>
</rss>

