<?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: VBKD-BSTKD in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/vbkd-bstkd/m-p/6106672#M1361428</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;May be you can try after warning message, just write a clear statement to clear the fields.&lt;/P&gt;&lt;P&gt;If this is done, then user even though enters incorrect data, they can't save it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 17 Sep 2009 07:12:38 GMT</pubDate>
    <dc:creator>jayanthi_jayaraman</dc:creator>
    <dc:date>2009-09-17T07:12:38Z</dc:date>
    <item>
      <title>VBKD-BSTKD</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/vbkd-bstkd/m-p/6106671#M1361427</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;in a sales order I should check for defined customers the field VBKD-BSTKD if it is filled. If not I should send out a message type E. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I did this in MV45AFZZ with a user exit and the problem is that as consequence of the message type E all fields are blocked, inclusive the fields the user has to correct. There is no other way than to leave VA01/VA02 and loose all the data the user typed in. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One possibility is that I send a W message from the User-Exit, but than the user can store incorrect data. The other solution is to change the PAI processing, but that will mean a modification of the standard SAP coding. That the customer doesnu2019t really want. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible to let the incorrect fields open for input with a E message out of the User-Exit?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Norbert&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Julius Bussche on Sep 17, 2009 10:49 AM&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Please use more meaningfull subject titles&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Sep 2009 07:07:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/vbkd-bstkd/m-p/6106671#M1361427</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-09-17T07:07:30Z</dc:date>
    </item>
    <item>
      <title>Re: VBKD-BSTKD</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/vbkd-bstkd/m-p/6106672#M1361428</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;May be you can try after warning message, just write a clear statement to clear the fields.&lt;/P&gt;&lt;P&gt;If this is done, then user even though enters incorrect data, they can't save it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Sep 2009 07:12:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/vbkd-bstkd/m-p/6106672#M1361428</guid>
      <dc:creator>jayanthi_jayaraman</dc:creator>
      <dc:date>2009-09-17T07:12:38Z</dc:date>
    </item>
    <item>
      <title>Re: VBKD-BSTKD</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/vbkd-bstkd/m-p/6106673#M1361429</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;for those defined customers the fields are mandatory. So a clear statement doesn't help.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Sep 2009 07:35:33 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/vbkd-bstkd/m-p/6106673#M1361429</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-09-17T07:35:33Z</dc:date>
    </item>
    <item>
      <title>Re: VBKD-BSTKD</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/vbkd-bstkd/m-p/6106674#M1361430</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;Just check using an information message and then use leave list-processing.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Sep 2009 07:41:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/vbkd-bstkd/m-p/6106674#M1361430</guid>
      <dc:creator>jayanthi_jayaraman</dc:creator>
      <dc:date>2009-09-17T07:41:18Z</dc:date>
    </item>
    <item>
      <title>Re: VBKD-BSTKD</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/vbkd-bstkd/m-p/6106675#M1361431</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 to put your control in 2 different user_exit:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- USEREXIT_MOVE_FIELD_TO_VBAK: here u can trigger a warning message&lt;/P&gt;&lt;P&gt;- USEREXIT_SAVE_DOCUMENT_PREPARE: here u can trigger en error message&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Max&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Sep 2009 07:44:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/vbkd-bstkd/m-p/6106675#M1361431</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-09-17T07:44:13Z</dc:date>
    </item>
    <item>
      <title>Re: VBKD-BSTKD</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/vbkd-bstkd/m-p/6106676#M1361432</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE level="1"&gt;&lt;/BLOCKQUOTE&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; Hi,&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; for those defined customers the fields are mandatory. So a clear statement doesn't help.&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hi Norbert Bürger,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If that field is Mandatory then system will not allow it as Blank entries by default..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In that case just information/warning message is also suffecient to let the enduser know that they need to fill it...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;OR...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can go for screen Variant as another way...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;OR &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In Configuration if it can be kept as Mandatory Consult your Functional Consultant for it..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Hope it will solve your problem..&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; Regards&lt;/P&gt;&lt;P&gt;ilesh 24x7&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;ilesh Nandaniya&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Sep 2009 09:14:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/vbkd-bstkd/m-p/6106676#M1361432</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-09-17T09:14:15Z</dc:date>
    </item>
    <item>
      <title>Re: VBKD-BSTKD</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/vbkd-bstkd/m-p/6106677#M1361433</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;I found a solution to handle this for limited customers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;in USEREXIT_SAVE_DOCUMENT_PREPARE I call in case of error a popup with FM POPUP_DISPLAY_MESSAGE and after processing the popup I say LEAVE TO SCREEN sy-dynnr. On this I'm comming back to the current screen. All fields are open for input in thatt case. This works also on screens which are not the screens with the valid input. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you all for your ideas and input.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Norbert&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Sep 2009 10:32:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/vbkd-bstkd/m-p/6106677#M1361433</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-09-17T10:32:11Z</dc:date>
    </item>
  </channel>
</rss>

