<?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 Variant condtions via BAPI in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/variant-condtions-via-bapi/m-p/1139478#M114119</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;has anyone experience with manual conditions in variant configuration via BAPI. Lets say with "BAPI_CUSTOMERQUOTATION_CHANGE" and its "condition_in" structure. &lt;/P&gt;&lt;P&gt;I've got no problem with changing this manual conditions via  the BAPI mentioned, but when I want to reset the price for a characteristic from manual to automatic I found no way to do it. I can change the price to the default but the field KHERK is still 'C' (manual). The problem is that when the default condition is assigned a new value via pricing maintenance the variant will not be recalculated because system thinks its manual.&lt;/P&gt;&lt;P&gt;I'm looking for possibilty to delete the manual variant condition so that the price is recalculated considering only the configurations default prices for this characteristic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope someone can help,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hans&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 02 Feb 2006 00:27:05 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-02-02T00:27:05Z</dc:date>
    <item>
      <title>Variant condtions via BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/variant-condtions-via-bapi/m-p/1139478#M114119</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;has anyone experience with manual conditions in variant configuration via BAPI. Lets say with "BAPI_CUSTOMERQUOTATION_CHANGE" and its "condition_in" structure. &lt;/P&gt;&lt;P&gt;I've got no problem with changing this manual conditions via  the BAPI mentioned, but when I want to reset the price for a characteristic from manual to automatic I found no way to do it. I can change the price to the default but the field KHERK is still 'C' (manual). The problem is that when the default condition is assigned a new value via pricing maintenance the variant will not be recalculated because system thinks its manual.&lt;/P&gt;&lt;P&gt;I'm looking for possibilty to delete the manual variant condition so that the price is recalculated considering only the configurations default prices for this characteristic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope someone can help,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hans&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Feb 2006 00:27:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/variant-condtions-via-bapi/m-p/1139478#M114119</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-02-02T00:27:05Z</dc:date>
    </item>
    <item>
      <title>Re: Variant condtions via BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/variant-condtions-via-bapi/m-p/1139479#M114120</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Hans,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have the same price issues in our variant config. if any charcterstics deleted or changed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have created a Custome program for calculating the price if any charctersitcs changed in a variant config.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At this moment I am away from my system and I will send you the details tomorrow.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Lanka&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Feb 2006 00:57:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/variant-condtions-via-bapi/m-p/1139479#M114120</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-02-02T00:57:28Z</dc:date>
    </item>
    <item>
      <title>Re: Variant condtions via BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/variant-condtions-via-bapi/m-p/1139480#M114121</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Lanka,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm tensley waiting for your solution. My major problem is that I didn't get back the automatic flag KHERK = 'A' via BAPI when the  variant condition is reset to default value.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope you can help me&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hans&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Feb 2006 23:01:33 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/variant-condtions-via-bapi/m-p/1139480#M114121</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-02-02T23:01:33Z</dc:date>
    </item>
    <item>
      <title>Re: Variant condtions via BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/variant-condtions-via-bapi/m-p/1139481#M114122</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Hans,&lt;/P&gt;&lt;P&gt;Earlier We had same issue in using BAPI. I think we have used a function module(using in SAP Standard PO/Requistion creation) + BDC (I think I have to check my code) . Today we have power outage and I am not able to check my code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will send you the code as soon as I am able to log in to my system.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Lanka&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Feb 2006 23:49:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/variant-condtions-via-bapi/m-p/1139481#M114122</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-02-02T23:49:04Z</dc:date>
    </item>
    <item>
      <title>Re: Variant condtions via BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/variant-condtions-via-bapi/m-p/1139482#M114123</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Hans,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have adopted the following statergy in our VC for price varuation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;a) We have maintained a Ztable(X) which will holds all the charctestics combination values for a machine/Equipment.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;       Example : IF Chancterstic is VOLTAGE&lt;/P&gt;&lt;P&gt;                      110V        $10&lt;/P&gt;&lt;P&gt;                      220V        $20&lt;/P&gt;&lt;P&gt;                      440V        $40&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At the time of Order Or Requition cration our program looks in to this price and accumulate al of the prices and populates against pricing condition(Variance price).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;b) There is Z program to update/change the prices in Ztable(X).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;c) If any of the Charcterstics changed in Order/Quotation.&lt;/P&gt;&lt;P&gt;   We have another Zprogram which checks the "price change date" in order/Quotation w.r.t to the price in Ztable against the charcterstic price and adjust the varuance price via BDC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have tried BAPI but we found lot of issues and then we hve adopted the above statergy.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this may help you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Lanka&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 03 Feb 2006 14:24:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/variant-condtions-via-bapi/m-p/1139482#M114123</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-02-03T14:24:25Z</dc:date>
    </item>
    <item>
      <title>Re: Variant condtions via BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/variant-condtions-via-bapi/m-p/1139483#M114124</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Lanka,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;this seems to me something like the last resort and not like a sophisticated approach to solve the real problem. I want to do the change online and not scheduling a job for that. I want to take the BAPIs because of the confguration and price changes are both made in an external configurator which has an XML-Interface to the R/3 system. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for your contribution to my problem but it´s not the solution I will favour.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hans&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Feb 2006 20:30:57 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/variant-condtions-via-bapi/m-p/1139483#M114124</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-02-07T20:30:57Z</dc:date>
    </item>
  </channel>
</rss>

