<?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_SALESORDER_CHANGE lock in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change-lock/m-p/6013086#M1346441</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sorry for the last post, some code is missing. Here again the code:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
    wa_schedule_lines-itm_number = wa_tussen-orderpositie.
    wa_schedule_lines-sched_line = '0001' .
    wa_schedule_lines-req_dlv_bl = '15'.

    append wa_schedule_lines to gi_schedule_lines.

    wa_schedule_linesx-itm_number = wa_tussen-orderpositie.
    wa_schedule_linesx-sched_line = '0001'.
    wa_schedule_linesx-updateflag = 'U'.
    wa_schedule_linesx-req_dlv_bl = 'X'.

    append wa_schedule_linesx to gi_schedule_linesx.

      call function 'BAPI_SALESORDER_CHANGE'
        exporting
          salesdocument    = wa_tussen-order
          order_header_inx = wa_order_header_inx
        tables
          return           = gi_return
          schedule_lines   = gi_schedule_lines
          schedule_linesx  = gi_schedule_linesx.

      if   gv_recordfout = 'X'.
        move   wa_return-message to wa_tussen-omschrijving.
        append wa_tussen to gi_fout.
        continue.
      endif.

      call function 'BAPI_TRANSACTION_COMMIT'
        exporting
          wait   = 'X'
        importing
          return = wa_return.
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 20 Aug 2009 09:25:00 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-08-20T09:25:00Z</dc:date>
    <item>
      <title>BAPI_SALESORDER_CHANGE lock</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change-lock/m-p/6013082#M1346437</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 have the following problem. In my code I'm trying to delete a delivery and after that change the schedule line of the salesorder. I'm using the following function/bapi:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WS_DELIVERY_UPDATE (to delete the delivery)&lt;/P&gt;&lt;P&gt;BAPI_SALESORDER_CHANGE (to update the scheduleline lifsp (delivery block))&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But the bapi returns errors saying Field LIFSP can't be changed, because there is nog input possible VBEPKOM etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can someone help me with this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thnx in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pieter&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Aug 2009 08:12:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change-lock/m-p/6013082#M1346437</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-08-20T08:12:10Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_SALESORDER_CHANGE lock</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change-lock/m-p/6013083#M1346438</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Pieter,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The error you are getting is related to the conditions tab in the BAPI SALES ORDER CHANGE . But this is not a mandatory tab.&lt;/P&gt;&lt;P&gt;if you want to change delivery , you only need to update orders and delivery tab &lt;/P&gt;&lt;P&gt;and in the orderx and deliveryx tab u need to update the indicators for whatever fields you want to update.&lt;/P&gt;&lt;P&gt;if you have all the above parameters correct, pls paste your code and maybe i can help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;tc&lt;/P&gt;&lt;P&gt;sajimon chandran&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Aug 2009 08:30:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change-lock/m-p/6013083#M1346438</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-08-20T08:30:26Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_SALESORDER_CHANGE lock</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change-lock/m-p/6013084#M1346439</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;I think that you should use BAPI_TRANSACTION_COMMIT or COMMIT WORK statement after calling the BAPI.&lt;/P&gt;&lt;P&gt;Hope , it works fine for you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sarita Singh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Aug 2009 08:34:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change-lock/m-p/6013084#M1346439</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-08-20T08:34:27Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_SALESORDER_CHANGE lock</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change-lock/m-p/6013085#M1346440</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sajimon,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the quick reply. I'm just confused with you reply because in the BAPI SALESORDER CHANGE there is no deliveryx to fill. What I have done is the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
call function 'BAPI_SALESORDER_CHANGE'
     exporting
      salesdocument    = wa_tussen-order
      order_header_inx = wa_order_header_inx
      tables
      return           = gi_return
         schedule_lines   = gi_schedule_lines
        schedule_linesx  = gi_schedule_linesx.
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Aug 2009 09:12:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change-lock/m-p/6013085#M1346440</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-08-20T09:12:19Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_SALESORDER_CHANGE lock</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change-lock/m-p/6013086#M1346441</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sorry for the last post, some code is missing. Here again the code:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
    wa_schedule_lines-itm_number = wa_tussen-orderpositie.
    wa_schedule_lines-sched_line = '0001' .
    wa_schedule_lines-req_dlv_bl = '15'.

    append wa_schedule_lines to gi_schedule_lines.

    wa_schedule_linesx-itm_number = wa_tussen-orderpositie.
    wa_schedule_linesx-sched_line = '0001'.
    wa_schedule_linesx-updateflag = 'U'.
    wa_schedule_linesx-req_dlv_bl = 'X'.

    append wa_schedule_linesx to gi_schedule_linesx.

      call function 'BAPI_SALESORDER_CHANGE'
        exporting
          salesdocument    = wa_tussen-order
          order_header_inx = wa_order_header_inx
        tables
          return           = gi_return
          schedule_lines   = gi_schedule_lines
          schedule_linesx  = gi_schedule_linesx.

      if   gv_recordfout = 'X'.
        move   wa_return-message to wa_tussen-omschrijving.
        append wa_tussen to gi_fout.
        continue.
      endif.

      call function 'BAPI_TRANSACTION_COMMIT'
        exporting
          wait   = 'X'
        importing
          return = wa_return.
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Aug 2009 09:25:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change-lock/m-p/6013086#M1346441</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-08-20T09:25:00Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_SALESORDER_CHANGE lock</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change-lock/m-p/6013087#M1346442</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Can you post the error message number and id?&lt;/P&gt;&lt;P&gt;Is it possible to change the field value online via VA02 transaction?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Incase it is not then there might be some functional reason for the same which you need to understand with your functional consultant.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ankur Parab&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Ankur Parab on Aug 20, 2009 3:04 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Aug 2009 09:34:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change-lock/m-p/6013087#M1346442</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-08-20T09:34:26Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_SALESORDER_CHANGE lock</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change-lock/m-p/6013088#M1346443</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;See here the records of the return table:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;           TYPE           ID                   NUMBER     MESSAGE    &lt;/P&gt;&lt;P&gt;                I              |V1                |739                              |Veld 'LIFSP' niet wijzigbaar, omdat geen &lt;/P&gt;&lt;P&gt;                E             |V4                |219                              |Verkoopdocument 0006479955 is niet gewijz&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message tekst is in dutch. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pieter&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Aug 2009 10:56:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change-lock/m-p/6013088#M1346443</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-08-20T10:56:34Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_SALESORDER_CHANGE lock</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change-lock/m-p/6013089#M1346444</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Can the field changed online via VA02?&lt;/P&gt;&lt;P&gt;Did you check the same?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ankur Parab&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Aug 2009 10:59:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change-lock/m-p/6013089#M1346444</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-08-20T10:59:29Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_SALESORDER_CHANGE lock</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change-lock/m-p/6013090#M1346445</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;Yep I can change the field in VA02. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pieter&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Aug 2009 11:03:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change-lock/m-p/6013090#M1346445</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-08-20T11:03:36Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_SALESORDER_CHANGE lock</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change-lock/m-p/6013091#M1346446</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Is the UPDATEFLAG passed in the structure ORDER_HEADER_INX?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ankur Parab&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Aug 2009 11:10:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change-lock/m-p/6013091#M1346446</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-08-20T11:10:20Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_SALESORDER_CHANGE lock</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change-lock/m-p/6013092#M1346447</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ankur,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pieter&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Aug 2009 11:13:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change-lock/m-p/6013092#M1346447</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-08-20T11:13:27Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_SALESORDER_CHANGE lock</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change-lock/m-p/6013093#M1346448</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Try passing the item details also to the BAPI.&lt;/P&gt;&lt;P&gt;ORDER_ITEM_IN and  ORDER_ITEM_INX &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ankur Parab&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Ankur Parab on Aug 20, 2009 4:51 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Aug 2009 11:20:59 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change-lock/m-p/6013093#M1346448</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-08-20T11:20:59Z</dc:date>
    </item>
  </channel>
</rss>

