<?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_REUIREMENTS_CHANGE for usage probability in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-reuirements-change-for-usage-probability/m-p/2277148#M495402</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;use bapi_transaction_commit after your BAPI call.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;just check FM docu,&lt;/P&gt;&lt;P&gt;from here i can see one thing...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;you need delete old ones and cretae neew ones ,&lt;/P&gt;&lt;P&gt;new data to be passed to REQUIREMENTS_SCHEDULE_IN&lt;/P&gt;&lt;P&gt;Existing Schedule Lines/&amp;gt;&lt;/P&gt;&lt;P&gt;Existing schedule lines are deleted, and the system creates the schedule lines transferred in parameter REQUIREMENTS_SCHEDULE_IN again.&lt;/P&gt;&lt;P&gt;When parameter DELETE_OLD has initial value, the existing schedule lines are not changed if the transferred schedule lines with the same requirements date do not overwrite them.&lt;/P&gt;&lt;P&gt;Existing schedule lines must be deleted for the following items (DELETE_OLD = X'):&lt;/P&gt;&lt;P&gt;Items for which automatic splitting is carried out&lt;/P&gt;&lt;P&gt;Items for which configuration supporting points are created&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try to add BAPI_TRANSACTION_COMMIT or COMMIT WORK statement at the end of BAPI_REQUIREMENTS_CHANGE.&lt;/P&gt;&lt;P&gt;Perhaps it may help but you may not needed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this will help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;VAsanth&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 24 May 2007 09:49:40 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-05-24T09:49:40Z</dc:date>
    <item>
      <title>BAPI_REUIREMENTS_CHANGE for usage probability</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-reuirements-change-for-usage-probability/m-p/2277147#M495401</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Transaction MD62 (planned independent requirement change - schedule line) - I need to Maintain Usage Probability functionality for the characteristics. I am trying to use BAPI_REUIREMENTS_CHANGE, but it is not updating the usage probabilities. If anyone has worked on this BAPI then please suggest me how to maintain usage probabilities. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jigisha&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 May 2007 09:46:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-reuirements-change-for-usage-probability/m-p/2277147#M495401</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-24T09:46:52Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_REUIREMENTS_CHANGE for usage probability</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-reuirements-change-for-usage-probability/m-p/2277148#M495402</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;use bapi_transaction_commit after your BAPI call.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;just check FM docu,&lt;/P&gt;&lt;P&gt;from here i can see one thing...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;you need delete old ones and cretae neew ones ,&lt;/P&gt;&lt;P&gt;new data to be passed to REQUIREMENTS_SCHEDULE_IN&lt;/P&gt;&lt;P&gt;Existing Schedule Lines/&amp;gt;&lt;/P&gt;&lt;P&gt;Existing schedule lines are deleted, and the system creates the schedule lines transferred in parameter REQUIREMENTS_SCHEDULE_IN again.&lt;/P&gt;&lt;P&gt;When parameter DELETE_OLD has initial value, the existing schedule lines are not changed if the transferred schedule lines with the same requirements date do not overwrite them.&lt;/P&gt;&lt;P&gt;Existing schedule lines must be deleted for the following items (DELETE_OLD = X'):&lt;/P&gt;&lt;P&gt;Items for which automatic splitting is carried out&lt;/P&gt;&lt;P&gt;Items for which configuration supporting points are created&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try to add BAPI_TRANSACTION_COMMIT or COMMIT WORK statement at the end of BAPI_REQUIREMENTS_CHANGE.&lt;/P&gt;&lt;P&gt;Perhaps it may help but you may not needed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this will help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;VAsanth&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 May 2007 09:49:40 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-reuirements-change-for-usage-probability/m-p/2277148#M495402</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-24T09:49:40Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_REUIREMENTS_CHANGE for usage probability</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-reuirements-change-for-usage-probability/m-p/2277149#M495403</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 u send ur snip of ur code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Naveen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 May 2007 09:55:40 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-reuirements-change-for-usage-probability/m-p/2277149#M495403</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-24T09:55:40Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_REUIREMENTS_CHANGE for usage probability</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-reuirements-change-for-usage-probability/m-p/2277150#M495404</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Vasant,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have selected the delete_old as 'X' and have also done a transaction commit but still the updates to the usuage probability are not happening.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jigisha&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 May 2007 10:12:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-reuirements-change-for-usage-probability/m-p/2277150#M495404</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-24T10:12:48Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_REUIREMENTS_CHANGE for usage probability</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-reuirements-change-for-usage-probability/m-p/2277151#M495405</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Naveen,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here it is:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA:  i_bapisshdin TYPE TABLE OF bapisshdin,&lt;/P&gt;&lt;P&gt;       i_bapischarr TYPE TABLE OF bapischarr,&lt;/P&gt;&lt;P&gt;       i_bapireturn1 TYPE TABLE OF bapireturn1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA:   wa_bapisshdin TYPE bapisshdin,&lt;/P&gt;&lt;P&gt;        wa_bapischarr TYPE bapischarr,&lt;/P&gt;&lt;P&gt;        wa_bapireturn1 TYPE bapireturn1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;wa_bapisshdin-date_type = '3'.&lt;/P&gt;&lt;P&gt;wa_bapisshdin-req_date = '05/01/2007'.&lt;/P&gt;&lt;P&gt;wa_bapisshdin-req_qty = '100.000'.&lt;/P&gt;&lt;P&gt;wa_bapisshdin-unit = 'EA'.&lt;/P&gt;&lt;P&gt;APPEND wa_bapisshdin TO i_bapisshdin.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;wa_bapischarr-requ_date = '05/01/2007'.&lt;/P&gt;&lt;P&gt;wa_bapischarr-int_char = 'UNIT_SIZE'.&lt;/P&gt;&lt;P&gt;wa_bapischarr-char_value = '016'.&lt;/P&gt;&lt;P&gt;wa_bapischarr-ch_qty = '25'.&lt;/P&gt;&lt;P&gt;APPEND wa_bapischarr TO i_bapischarr.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CALL FUNCTION 'BAPI_REQUIREMENTS_CHANGE'&lt;/P&gt;&lt;P&gt;  EXPORTING&lt;/P&gt;&lt;P&gt;    material                 = '38AKS'&lt;/P&gt;&lt;P&gt;    plant                    = '2000'&lt;/P&gt;&lt;P&gt;    requirementstype         = ' '&lt;/P&gt;&lt;P&gt;    version                  = '00'&lt;/P&gt;&lt;P&gt;    reqmtsplannumber         = ' '&lt;/P&gt;&lt;P&gt;    vers_activ               = ' '&lt;/P&gt;&lt;P&gt;    do_commit                = 'X'&lt;/P&gt;&lt;P&gt;    update_mode              = 'X'&lt;/P&gt;&lt;P&gt;    delete_old               = 'X'&lt;/P&gt;&lt;P&gt;    no_withdr                = ' '&lt;/P&gt;&lt;P&gt;  TABLES&lt;/P&gt;&lt;P&gt;    requirements_schedule_in = i_bapisshdin&lt;/P&gt;&lt;P&gt;    requirements_char_in     = i_bapischarr&lt;/P&gt;&lt;P&gt;    return                   = i_bapireturn1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'&lt;/P&gt;&lt;P&gt;  EXPORTING&lt;/P&gt;&lt;P&gt;    wait = 'X'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jigisha&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 May 2007 10:16:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-reuirements-change-for-usage-probability/m-p/2277151#M495405</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-24T10:16:37Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_REUIREMENTS_CHANGE for usage probability</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-reuirements-change-for-usage-probability/m-p/2277152#M495406</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have tried using same BAPI, It is returning a message &lt;/P&gt;&lt;P&gt;"No authorization for changing in plant ".&lt;/P&gt;&lt;P&gt;so i think in my  dev server i dont have authorisation to change the plant and its showing that message. &lt;/P&gt;&lt;P&gt;wats the BAPI is returning in ur case?&lt;/P&gt;&lt;P&gt;Revert back .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Naveen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 May 2007 10:45:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-reuirements-change-for-usage-probability/m-p/2277152#M495406</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-24T10:45:16Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_REUIREMENTS_CHANGE for usage probability</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-reuirements-change-for-usage-probability/m-p/2277153#M495407</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Naveen,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The BAPI is deleting the schedule line instead of updating the usage probability.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jigisha&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 May 2007 10:54:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-reuirements-change-for-usage-probability/m-p/2277153#M495407</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-24T10:54:05Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_REUIREMENTS_CHANGE for usage probability</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-reuirements-change-for-usage-probability/m-p/2277154#M495408</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jigisha , &lt;/P&gt;&lt;P&gt; When parameter DELETE_OLD has initial value, the existing schedule lines are not changed if the transferred schedule lines with the same requirements date do not overwrite them.&lt;/P&gt;&lt;P&gt;so try using  delete_old = '  ' .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As DELETE_OLD = X,   will delete that record.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Iam not sure wheteher it will work or not, coz i dont have authorisation to change PLANT in my server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Naveen&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: &lt;/P&gt;&lt;P&gt;        Naveen Deva&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 May 2007 11:46:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-reuirements-change-for-usage-probability/m-p/2277154#M495408</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-24T11:46:54Z</dc:date>
    </item>
  </channel>
</rss>

