<?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: BAPI_PRICES_CONDITIONS in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-prices-conditions/m-p/3055150#M723463</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;exactly....that BAPI is internally released and can cause inconsistency as you &lt;/P&gt;&lt;P&gt;faced. Hence this BAPI cannot take care of even creating conditions incase it is used for populating condition tables which wouldnt have anykeys otherthan material customer and dates. Incase of rebate conditions yoou can go ahead and use this as agreement number or something similar will also be a part of key.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For creating pricing conditions you can use RV_CONDITION_COPY.Which creates conditions exactly as in VK11( checking overlaping dates and arranging). &lt;/P&gt;&lt;P&gt;However to delete older connditions you are left with no choice otherthan to manually set kona-loevm field to 'X'.&lt;/P&gt;&lt;P&gt;Reward if usefull&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Rendeep&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 05 Dec 2007 11:02:38 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-12-05T11:02:38Z</dc:date>
    <item>
      <title>BAPI_PRICES_CONDITIONS</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-prices-conditions/m-p/3055147#M723460</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi guys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm trying to use BAPI_PRICES_CONDITIONS to create and/or update price conditions and scales info records, but I'm having some difficulties...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyone have a sample code to do this? or valuable tips on this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;most of the related posts are a bit contradictory... &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;&lt;P&gt;Nuno&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Nov 2007 16:13:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-prices-conditions/m-p/3055147#M723460</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-11-20T16:13:17Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_PRICES_CONDITIONS</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-prices-conditions/m-p/3055148#M723461</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check the below link :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapnet.ru/viewtopic.php?p=765&amp;amp;sid=88b6f60f85501678fc93cd16e187ad61" target="test_blank"&gt;http://www.sapnet.ru/viewtopic.php?p=765&amp;amp;sid=88b6f60f85501678fc93cd16e187ad61&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Seshu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Nov 2007 16:28:33 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-prices-conditions/m-p/3055148#M723461</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-11-20T16:28:33Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_PRICES_CONDITIONS</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-prices-conditions/m-p/3055149#M723462</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;does this BAPI manage overlapping validity dates? I find its behavior a bit strange.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and if you update a info record with a new validity period with scales, it updates other periods with same scale values... bizarre!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;any tips?!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Nov 2007 16:56:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-prices-conditions/m-p/3055149#M723462</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-11-30T16:56:03Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_PRICES_CONDITIONS</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-prices-conditions/m-p/3055150#M723463</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;exactly....that BAPI is internally released and can cause inconsistency as you &lt;/P&gt;&lt;P&gt;faced. Hence this BAPI cannot take care of even creating conditions incase it is used for populating condition tables which wouldnt have anykeys otherthan material customer and dates. Incase of rebate conditions yoou can go ahead and use this as agreement number or something similar will also be a part of key.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For creating pricing conditions you can use RV_CONDITION_COPY.Which creates conditions exactly as in VK11( checking overlaping dates and arranging). &lt;/P&gt;&lt;P&gt;However to delete older connditions you are left with no choice otherthan to manually set kona-loevm field to 'X'.&lt;/P&gt;&lt;P&gt;Reward if usefull&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Rendeep&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Dec 2007 11:02:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-prices-conditions/m-p/3055150#M723463</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-05T11:02:38Z</dc:date>
    </item>
  </channel>
</rss>

