<?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 BAPI_SALESORDER_CHANGE in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change/m-p/6356297#M1399691</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi I have a requirement to update the price condistions for sales orders using the Update step 'G'. However I just discovered this step appears in a different position for different order types, so going down a BDC route is going to be difficult. So I was wondering if I can use the above BAPI but unsrue how to populate the segments.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All I want to do is drill into the each line item, and from the conditions tab, choose the update button and selct Price type 'G'. So can someone tell me how I go about populating the structure BAPICOND to achieve this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN __default_attr="red" __jive_macro_name="color"&gt;Moderator message - Moved to the correct forum&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Rob Burbank on Dec 15, 2009 9:12 AM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 14 Dec 2009 16:18:45 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-12-14T16:18:45Z</dc:date>
    <item>
      <title>BAPI_SALESORDER_CHANGE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change/m-p/6356297#M1399691</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi I have a requirement to update the price condistions for sales orders using the Update step 'G'. However I just discovered this step appears in a different position for different order types, so going down a BDC route is going to be difficult. So I was wondering if I can use the above BAPI but unsrue how to populate the segments.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All I want to do is drill into the each line item, and from the conditions tab, choose the update button and selct Price type 'G'. So can someone tell me how I go about populating the structure BAPICOND to achieve this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN __default_attr="red" __jive_macro_name="color"&gt;Moderator message - Moved to the correct forum&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Rob Burbank on Dec 15, 2009 9:12 AM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Dec 2009 16:18:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change/m-p/6356297#M1399691</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-12-14T16:18:45Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_SALESORDER_CHANGE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change/m-p/6356298#M1399692</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;Declare work area as &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA wa_cond type bapicond,&lt;/P&gt;&lt;P&gt;           wa_condx type bapicondx.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pass the required value as mentioned below as per the requirement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;      wa_cond-itm_number = wa_konv-kposn.&lt;/P&gt;&lt;P&gt;      wa_cond-cond_type = wa_konv-kschl.&lt;/P&gt;&lt;P&gt;      wa_cond-cond_value = wa_konv-kbetr / 10.&lt;/P&gt;&lt;P&gt;      wa_cond-stat_con = 'X'.&lt;/P&gt;&lt;P&gt;      wa_cond-CONBASEVAL = wa_konv-kawrt.&lt;/P&gt;&lt;P&gt;        wa_cond-COND_NO = wa_konv-knumh.&lt;/P&gt;&lt;P&gt;      APPEND wa_cond TO i_cond.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;      wa_condx-itm_number = wa_konv-kposn.&lt;/P&gt;&lt;P&gt;      wa_condx-cond_type = wa_konv-kschl.&lt;/P&gt;&lt;P&gt;      wa_condx-updateflag = c_x.&lt;/P&gt;&lt;P&gt;      wa_condx-cond_value = c_x.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;      APPEND wa_condx TO i_condx.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Call the fm BAPI_SALESORDER_CHANGE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;U can get the log in BAPIRET structure&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Bysani.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Dec 2009 12:10:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change/m-p/6356298#M1399692</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-12-16T12:10:10Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_SALESORDER_CHANGE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change/m-p/6356299#M1399693</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI thanks for this.  I am getting issues with the below import parameters that are mandatory.  The error is: Field header_inx-updateflag is not an input field - yet I am not populating this parameter...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;        ORDER_HEADER_IN             = ls_order&lt;/P&gt;&lt;P&gt;        order_header_inx            = ls_orderx&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Dec 2009 10:45:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change/m-p/6356299#M1399693</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-12-17T10:45:04Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_SALESORDER_CHANGE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change/m-p/6356300#M1399694</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Okay I now have it working to an extent but I am getting the below messages related to the condition I am trying to change - I am basically trying to simulate the pressing of the update button - so is this not possible via the BAPI&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;205   |Condition MWST cannot be processed manually                        &lt;/P&gt;&lt;P&gt;219   |Sales document 0004208540 was not changed&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Dec 2009 11:03:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change/m-p/6356300#M1399694</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-12-17T11:03:46Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_SALESORDER_CHANGE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change/m-p/6356301#M1399695</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It sounds like you are performing the same task as myself getting ready for the UK vat rate change.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am performing the same process of updating on 'G' to update the taxes to the revised 17.5 % rate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am using BAPI_SALESORDER_CHANGE, and it does appear to be working okay.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are you setting the LOGIC_SWITCH parameters on the call to the BAPI.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;logic_switch-pricing = 'G' allows the update mode to be set.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Dec 2009 11:35:57 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change/m-p/6356301#M1399695</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-12-17T11:35:57Z</dc:date>
    </item>
  </channel>
</rss>

