<?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 Problem in Smartforms after SAP patch upgrade in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/problem-in-smartforms-after-sap-patch-upgrade/m-p/1706499#M309372</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi ,&lt;/P&gt;&lt;P&gt;We have recently upgraded the SAP_APPL component from SAPKH47020 to SAPKH47026.&lt;/P&gt;&lt;P&gt;After this upgrade, we have observed a syntax error in one of the Z smartforms. This smartform uses an element called SECTION which gives the syntax error. My understanding is that this element is no longer supported after the upgrade.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If any of you has faced such an issue with respect to obsolete elements, please let me know the issue resolution steps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;Ashish&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 24 Nov 2006 10:47:17 GMT</pubDate>
    <dc:creator>aaparanjpe</dc:creator>
    <dc:date>2006-11-24T10:47:17Z</dc:date>
    <item>
      <title>Problem in Smartforms after SAP patch upgrade</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/problem-in-smartforms-after-sap-patch-upgrade/m-p/1706499#M309372</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi ,&lt;/P&gt;&lt;P&gt;We have recently upgraded the SAP_APPL component from SAPKH47020 to SAPKH47026.&lt;/P&gt;&lt;P&gt;After this upgrade, we have observed a syntax error in one of the Z smartforms. This smartform uses an element called SECTION which gives the syntax error. My understanding is that this element is no longer supported after the upgrade.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If any of you has faced such an issue with respect to obsolete elements, please let me know the issue resolution steps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;Ashish&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Nov 2006 10:47:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/problem-in-smartforms-after-sap-patch-upgrade/m-p/1706499#M309372</guid>
      <dc:creator>aaparanjpe</dc:creator>
      <dc:date>2006-11-24T10:47:17Z</dc:date>
    </item>
    <item>
      <title>Re: Problem in Smartforms after SAP patch upgrade</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/problem-in-smartforms-after-sap-patch-upgrade/m-p/1706500#M309373</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've never seen a case where objects are not supported after the application of support packs. It quite often (almost aways) happens after a true upgrade (say from 4.6C to 4.7).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You might find in transactin SPAU that one of the includes you are using was overwritten and some custom code is gone. I'd be looking at your code rather than SAPs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If your sure it's in their code, then there should be a note on it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Nov 2006 20:27:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/problem-in-smartforms-after-sap-patch-upgrade/m-p/1706500#M309373</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-11-24T20:27:39Z</dc:date>
    </item>
  </channel>
</rss>

