<?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: Variant Configuration in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/variant-configuration/m-p/6931834#M1485856</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Indeed, we want to remove some variant classes from the material master and replace them with a new one. I've seen that in order to achieve the above, ECM is needed. So far so good though.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But here's where my concern is: there are still transaction data (sales orders, deliveries etc.) containing the configuration based on the old variant classes. And that 'old' configuration should be replaced as well. Mind you, removing the old variant classes from the material master does not remove the configuration (characteristics values) from the transaction data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For historical transaction data (closed documents etc.) that's not a a problem. But for the open documents we want to see only the new configuration (characteristics). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm currently investigation the possibilities of removing the 'old' configuration data from said transaction data. But if someone has some ideas on it or has actually done this before, i would love to hear about it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 18 May 2010 07:16:48 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2010-05-18T07:16:48Z</dc:date>
    <item>
      <title>Variant Configuration</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/variant-configuration/m-p/6931831#M1485853</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For our client the project team decided that there should be an overhaul of the current variant configuration. Basically this means that an existing class X and class Y (both class type 300) will be replaced by a new class Z of class type 300. Class Z contains most characteristics from class X and Y, renamed characteristics from X and Y and includes some new characteristics as well.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With the 'standard' classification i have no problem in making these kinds of changes in classified objects. With the variant configuration it's a different kind of story as there are also things like variant tables etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am performing an impact analysis to determine whether making this change is possible and how it should be done (from a developer's perspective as without any doubt ABAP will be needed).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Knowing the complexity of the variant configuration (dependencies etc.) i was wondering if anybody ever did a conversion like this or knows if it even is possible.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 May 2010 07:52:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/variant-configuration/m-p/6931831#M1485853</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-05-14T07:52:13Z</dc:date>
    </item>
    <item>
      <title>Re: Variant Configuration</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/variant-configuration/m-p/6931832#M1485854</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Are you talking about variant configuration via CU41 ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And if i understand correctly you want to remove the classes X &amp;amp; Y and replace them with a new class Z. Now you want to know if this is feasible technically. Correct ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 May 2010 08:49:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/variant-configuration/m-p/6931832#M1485854</guid>
      <dc:creator>SuhaSaha</dc:creator>
      <dc:date>2010-05-14T08:49:02Z</dc:date>
    </item>
    <item>
      <title>Re: Variant Configuration</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/variant-configuration/m-p/6931833#M1485855</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;there are chances for the feasibilty of your requirement. Just explore and debug CL30N . there will be a standard FM to filter materials as per the characteristics chosen. If we can do some R&amp;amp;D on that FM, we could conclude your requirement's feasibility.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &lt;/P&gt;&lt;P&gt;Seema&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 May 2010 13:19:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/variant-configuration/m-p/6931833#M1485855</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-05-14T13:19:02Z</dc:date>
    </item>
    <item>
      <title>Re: Variant Configuration</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/variant-configuration/m-p/6931834#M1485856</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Indeed, we want to remove some variant classes from the material master and replace them with a new one. I've seen that in order to achieve the above, ECM is needed. So far so good though.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But here's where my concern is: there are still transaction data (sales orders, deliveries etc.) containing the configuration based on the old variant classes. And that 'old' configuration should be replaced as well. Mind you, removing the old variant classes from the material master does not remove the configuration (characteristics values) from the transaction data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For historical transaction data (closed documents etc.) that's not a a problem. But for the open documents we want to see only the new configuration (characteristics). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm currently investigation the possibilities of removing the 'old' configuration data from said transaction data. But if someone has some ideas on it or has actually done this before, i would love to hear about it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 May 2010 07:16:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/variant-configuration/m-p/6931834#M1485856</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-05-18T07:16:48Z</dc:date>
    </item>
    <item>
      <title>Re: Variant Configuration</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/variant-configuration/m-p/6931835#M1485857</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In the end no need for complex conversions or whatever in the system.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The client decided to do a full load (and conversion) into a new SAP system.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Nov 2010 10:37:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/variant-configuration/m-p/6931835#M1485857</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-11-05T10:37:21Z</dc:date>
    </item>
  </channel>
</rss>

