<?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_PRODORDCONF_CANCEL in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-prodordconf-cancel/m-p/6738965#M1458347</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG&gt;BAPI_PRODORDCONF_CANCEL.&lt;/STRONG&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are using the BAPI_PRODORDCONF_CANCEL to post 102 movement with reference to a 101. &lt;/P&gt;&lt;P&gt;If the referenced 101 is in previous period and that pervious posting period is open then the its using the 101 posting date instead current date. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Per our business requirement we need the current date on 102 movement. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help would be appreciated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 16 Mar 2010 22:01:39 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2010-03-16T22:01:39Z</dc:date>
    <item>
      <title>BAPI_PRODORDCONF_CANCEL</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-prodordconf-cancel/m-p/6738965#M1458347</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG&gt;BAPI_PRODORDCONF_CANCEL.&lt;/STRONG&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are using the BAPI_PRODORDCONF_CANCEL to post 102 movement with reference to a 101. &lt;/P&gt;&lt;P&gt;If the referenced 101 is in previous period and that pervious posting period is open then the its using the 101 posting date instead current date. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Per our business requirement we need the current date on 102 movement. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help would be appreciated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Mar 2010 22:01:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-prodordconf-cancel/m-p/6738965#M1458347</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-03-16T22:01:39Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_PRODORDCONF_CANCEL</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-prodordconf-cancel/m-p/6738966#M1458348</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 don't think that it is possible to force posting date. Here is a quote from SAP documentation for this BAPI&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PostgDate                                                         &lt;/P&gt;&lt;P&gt;The posting date for the cancellation can be entered in the       &lt;/P&gt;&lt;P&gt;PostgDate parameter. This posting date is only used though, if the&lt;/P&gt;&lt;P&gt;posting period of the original posting date has been locked in    &lt;/P&gt;&lt;P&gt;Controlling for further posting. This could be the case if the    &lt;/P&gt;&lt;P&gt;posting period is a long time ago and it has been settled.        &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can try to replicate fucntionality of this BAPI in your own function module where you will force your own posting date.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Mar 2010 23:07:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-prodordconf-cancel/m-p/6738966#M1458348</guid>
      <dc:creator>mvoros</dc:creator>
      <dc:date>2010-03-16T23:07:52Z</dc:date>
    </item>
  </channel>
</rss>

