<?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: SD_VARIANT_MAINTAIN in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/sd-variant-maintain/m-p/6282644#M1388536</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Have you checked the SMP ( &lt;A href="https://service.sap.com/notes" target="test_blank"&gt;https://service.sap.com/notes&lt;/A&gt; ) and the forum here for this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is a note and discussions here which explain how this works (and where the user can then determine for themselves whether they are authorized or not to change a variant).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also keep an eye out for custom system variants and a user protection in transaction VARCH as a solution....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Julius&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 09 Nov 2009 16:40:05 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-11-09T16:40:05Z</dc:date>
    <item>
      <title>SD_VARIANT_MAINTAIN</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sd-variant-maintain/m-p/6282643#M1388535</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I need helt understanding the difference between the options for SD_VARIANT_MAINTAIN (A,X and U)&lt;/P&gt;&lt;P&gt;Shoulud i give end users anything else than value U?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If i have value X can i create variants for the whole client or just the company code?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Nov 2009 15:06:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sd-variant-maintain/m-p/6282643#M1388535</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-11-09T15:06:21Z</dc:date>
    </item>
    <item>
      <title>Re: SD_VARIANT_MAINTAIN</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sd-variant-maintain/m-p/6282644#M1388536</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Have you checked the SMP ( &lt;A href="https://service.sap.com/notes" target="test_blank"&gt;https://service.sap.com/notes&lt;/A&gt; ) and the forum here for this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is a note and discussions here which explain how this works (and where the user can then determine for themselves whether they are authorized or not to change a variant).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also keep an eye out for custom system variants and a user protection in transaction VARCH as a solution....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Julius&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Nov 2009 16:40:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sd-variant-maintain/m-p/6282644#M1388536</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-11-09T16:40:05Z</dc:date>
    </item>
  </channel>
</rss>

