<?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: changes in SD order in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/changes-in-sd-order/m-p/1443070#M210534</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;You can create a custom authorizations and add them to the user profile.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then insert the code you need to check those authorizations in a user-exit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe it's better use USEREXIT_MOVE_FIELD_TO_VBAK or USEREXIT_MOVE_FIELD_TO_VBAP, because if you use USEREXIT_SAVE_DOCUMENT_PREPARE you can send an error message only at the end of modification.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Max&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 23 Jun 2006 13:46:45 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-06-23T13:46:45Z</dc:date>
    <item>
      <title>changes in SD order</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/changes-in-sd-order/m-p/1443068#M210532</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 am facing following isue :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Users with role X mustn't be able to change the values in sales order type Y except for the field "FPLT-FAKSP".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can this be done with standard authorisation management ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If not, can i use 'USEREXIT_SAVE_DOCUMENT_PREPARE' in include 'MV45AFZZ' and would should the code be like ? Can SAP detect changes ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;with regards&lt;/P&gt;&lt;P&gt;Erik&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Jun 2006 12:52:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/changes-in-sd-order/m-p/1443068#M210532</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-06-23T12:52:54Z</dc:date>
    </item>
    <item>
      <title>Re: changes in SD order</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/changes-in-sd-order/m-p/1443069#M210533</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Erik,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Standard authorization will not be possible as this is at order type level. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The user exit you mention can be used. Old data of the order will be in the "y&amp;lt;name of the table&amp;gt;" while new data will be in the "x&amp;lt;name of the table&amp;gt;", e.g. xvbap[] will hold the order positions with their changes while yvbap[] holds the original data.&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;John.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Jun 2006 13:25:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/changes-in-sd-order/m-p/1443069#M210533</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-06-23T13:25:52Z</dc:date>
    </item>
    <item>
      <title>Re: changes in SD order</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/changes-in-sd-order/m-p/1443070#M210534</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;You can create a custom authorizations and add them to the user profile.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then insert the code you need to check those authorizations in a user-exit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe it's better use USEREXIT_MOVE_FIELD_TO_VBAK or USEREXIT_MOVE_FIELD_TO_VBAP, because if you use USEREXIT_SAVE_DOCUMENT_PREPARE you can send an error message only at the end of modification.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Max&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Jun 2006 13:46:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/changes-in-sd-order/m-p/1443070#M210534</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-06-23T13:46:45Z</dc:date>
    </item>
  </channel>
</rss>

