<?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_REQUISITION_DELETE and BAPI_PR_CHANGE in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-requisition-delete-and-bapi-pr-change/m-p/10194809#M1824333</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;BAPI_REQUISITIONS* (4.0A+) are old BAPI relative to "outdated" non-Enjoy transaction, when BAPI_PR* (6.40+) are relative to new Enjoy transactions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reference :&amp;nbsp; &lt;A href="http://service.sap.com/sap/support/notes/499627" title="499627  - FAQ: BAPIs for purchase requisitions"&gt;&lt;SPAN class="title"&gt;499627 - FAQ: BAPIs for purchase requisitions&lt;/SPAN&gt;&lt;/A&gt;&lt;A href="http://service.sap.com/sap/support/notes/499627" title="499627  - FAQ: BAPIs for purchase requisitions"&gt; &lt;/A&gt; and &lt;A href="http://service.sap.com/sap/support/notes/1803189" title="1803189  - FAQ: End of Support of ME21, ME51, and BAPI_PO_CREATE etc."&gt;&lt;SPAN class="title"&gt;1803189 - FAQ: End of Support of ME21, ME51, and BAPI_PO_CREATE etc.&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Look also at OSS for notes relative to error ME 664 like &lt;A href="http://service.sap.com/sap/support/notes/1908567" title="1908567  - BAPI_PO_CREATE1/BAPI_PO_CHANGE : Information message &amp;quot;ME 664&amp;quot;"&gt;&lt;SPAN class="title"&gt;1908567 - BAPI_PO_CREATE1/BAPI_PO_CHANGE : Information message "ME 664"&lt;/SPAN&gt;&lt;/A&gt; or&amp;nbsp; &lt;A href="http://service.sap.com/sap/support/notes/1287690" title="1287690  - Ready for input status of purchase requisition dialog box"&gt;&lt;SPAN class="title"&gt;1287690 - Ready for input status of purchase requisition dialog box&lt;/SPAN&gt; &lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You should also been allowed to execute the change with ME52 and not with ME52N or with a warning/popup ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Raymond&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 19 Mar 2014 10:32:45 GMT</pubDate>
    <dc:creator>RaymondGiuseppi</dc:creator>
    <dc:date>2014-03-19T10:32:45Z</dc:date>
    <item>
      <title>BAPI_REQUISITION_DELETE and BAPI_PR_CHANGE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-requisition-delete-and-bapi-pr-change/m-p/10194807#M1824331</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to use BAPI_PR_CHANGE to close purchase requisition item when creating new PO with reference to PR, and here is my code snippet:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
&lt;P&gt;&lt;SPAN style="color: #c0c0c0;"&gt;* Create table for purchase requisition item's changing indicators&lt;/SPAN&gt;&lt;BR /&gt; APPEND INITIAL LINE TO lt_pritemsx ASSIGNING &amp;lt;fs_pritemx&amp;gt;.&lt;BR /&gt; &amp;lt;fs_pritemx&amp;gt;-preq_item = lv_pr_item_number.&lt;BR /&gt; &amp;lt;fs_pritemx&amp;gt;-closed = lc_x. " 'X' means we will change the CLOSED field&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="color: #c0c0c0;"&gt;* Create table for purchase requisition item's new values&lt;/SPAN&gt;&lt;BR /&gt; APPEND INITIAL LINE TO lt_pritems_new ASSIGNING &amp;lt;fs_pritem_new&amp;gt;.&lt;BR /&gt; MOVE-CORRESPONDING &amp;lt;fs_pritem&amp;gt; TO &amp;lt;fs_pritem_new&amp;gt;.&lt;BR /&gt; &amp;lt;fs_pritem_new&amp;gt;-closed = lc_x. " 'X' means the value of CLOSED field will be changed to 'X'&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="color: #c0c0c0;"&gt;* Set "PReq. Closed" flag&lt;/SPAN&gt;&lt;BR /&gt; CALL FUNCTION 'BAPI_PR_CHANGE'&lt;BR /&gt; EXPORTING&lt;BR /&gt; number = lv_pr_number&lt;BR /&gt; TABLES&lt;BR /&gt; return = lt_return&lt;BR /&gt; pritem = lt_pritems_new&lt;BR /&gt; pritemx = lt_pritemsx.&lt;/P&gt;
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;For most cases, BAPI_PR_CHANGE works well. But for some case, for example there is ‘Release stragety’ tab in some PR item, and I released it using ME54, then BAPI_PR_CHANGE will give me such message and 'PReq. Closed' flag is set failed.&lt;/P&gt;&lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/jiveimages/414019" width="450" /&gt;&lt;/P&gt;&lt;P&gt;But if I use BAPI_REQUISITION_DELETE for the same case, 'PReq. Closed' flag will be set successfully.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So could anyone tell me why BAPI_PR_CHANGE doesn't work here? And what's the difference between BAPI_REQUISITION_DELETE and BAPI_PR_CHANGE in deleting or closing purchase requisition?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Shelwin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Mar 2014 09:56:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-requisition-delete-and-bapi-pr-change/m-p/10194807#M1824331</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-03-19T09:56:43Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_REQUISITION_DELETE and BAPI_PR_CHANGE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-requisition-delete-and-bapi-pr-change/m-p/10194808#M1824332</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;You also need to set the PRITEMX-CLOSED flag for the item which you want to close.&lt;/P&gt;&lt;P&gt;This is required in BAPI_PR_CHANGE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know if it helped?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Zuber&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Mar 2014 10:04:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-requisition-delete-and-bapi-pr-change/m-p/10194808#M1824332</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-03-19T10:04:39Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_REQUISITION_DELETE and BAPI_PR_CHANGE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-requisition-delete-and-bapi-pr-change/m-p/10194809#M1824333</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;BAPI_REQUISITIONS* (4.0A+) are old BAPI relative to "outdated" non-Enjoy transaction, when BAPI_PR* (6.40+) are relative to new Enjoy transactions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reference :&amp;nbsp; &lt;A href="http://service.sap.com/sap/support/notes/499627" title="499627  - FAQ: BAPIs for purchase requisitions"&gt;&lt;SPAN class="title"&gt;499627 - FAQ: BAPIs for purchase requisitions&lt;/SPAN&gt;&lt;/A&gt;&lt;A href="http://service.sap.com/sap/support/notes/499627" title="499627  - FAQ: BAPIs for purchase requisitions"&gt; &lt;/A&gt; and &lt;A href="http://service.sap.com/sap/support/notes/1803189" title="1803189  - FAQ: End of Support of ME21, ME51, and BAPI_PO_CREATE etc."&gt;&lt;SPAN class="title"&gt;1803189 - FAQ: End of Support of ME21, ME51, and BAPI_PO_CREATE etc.&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Look also at OSS for notes relative to error ME 664 like &lt;A href="http://service.sap.com/sap/support/notes/1908567" title="1908567  - BAPI_PO_CREATE1/BAPI_PO_CHANGE : Information message &amp;quot;ME 664&amp;quot;"&gt;&lt;SPAN class="title"&gt;1908567 - BAPI_PO_CREATE1/BAPI_PO_CHANGE : Information message "ME 664"&lt;/SPAN&gt;&lt;/A&gt; or&amp;nbsp; &lt;A href="http://service.sap.com/sap/support/notes/1287690" title="1287690  - Ready for input status of purchase requisition dialog box"&gt;&lt;SPAN class="title"&gt;1287690 - Ready for input status of purchase requisition dialog box&lt;/SPAN&gt; &lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You should also been allowed to execute the change with ME52 and not with ME52N or with a warning/popup ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Raymond&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Mar 2014 10:32:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-requisition-delete-and-bapi-pr-change/m-p/10194809#M1824333</guid>
      <dc:creator>RaymondGiuseppi</dc:creator>
      <dc:date>2014-03-19T10:32:45Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_REQUISITION_DELETE and BAPI_PR_CHANGE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-requisition-delete-and-bapi-pr-change/m-p/10194810#M1824334</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Zuber,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have already set the PRITEMX-CLOSED flag for the item, please refer to my code snippet.&lt;/P&gt;&lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/jiveimages/414087" /&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/jiveimages/414081" width="450" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Shelwin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Mar 2014 10:36:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-requisition-delete-and-bapi-pr-change/m-p/10194810#M1824334</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-03-19T10:36:03Z</dc:date>
    </item>
  </channel>
</rss>

