<?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 Missing Position Conditions after ERP-Update while Using bapi_salesorder_createfromdat2 in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/missing-position-conditions-after-erp-update-while-using-bapi-salesorder/m-p/9000329#M1697896</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We habe Problems with Using the BAPI bapi_salesorder_createfromdat2 after Updating our Kernel last week.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;System A (with Kernel Update) --&amp;gt; no manuel Conditions will be save in the salesorder&lt;/P&gt;&lt;P&gt;System B (without Kernel Update) --&amp;gt; saves the Conditions we are given to the BAPI.&lt;/P&gt;&lt;P&gt;The Call of that BAPI is in both System completely the same. we havent changes the calling while that ERP-Update.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;SPAU was made and all modification were assumed. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've checked the internal Table for Conditions from FM SD_SALES_DOCU_MAINTAIN who is called in bapi_salesorder_createfromdat2 and they look like that:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #1f497d; font-family: &amp;amp;quot;Calibri&amp;amp;quot;,&amp;amp;quot;sans-serif&amp;amp;quot;; font-size: 11pt; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-ansi-language: DE; mso-fareast-language: DE; mso-bidi-language: AR-SA;"&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/jiveimages/136855" height="246" width="1038" /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; the FM SD_SALES_DOCU_MAINTAIN have been changed after that ERP-Update from last User SAP. So something changed! But what??&lt;BR /&gt;&amp;nbsp;&amp;nbsp; If i insert the conditions with VA02 in that created salesorder manually, everything works fine. So the condition-finding seems to be fine.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #1f497d; font-family: &amp;amp;quot;Calibri&amp;amp;quot;,&amp;amp;quot;sans-serif&amp;amp;quot;; font-size: 11pt; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-ansi-language: DE; mso-fareast-language: DE; mso-bidi-language: AR-SA;"&gt;&lt;BR /&gt;What have been changed in BAPI bapi_salesorder_createfromdat2? &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #1f497d; font-family: &amp;amp;quot;Calibri&amp;amp;quot;,&amp;amp;quot;sans-serif&amp;amp;quot;; font-size: 11pt; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-ansi-language: DE; mso-fareast-language: DE; mso-bidi-language: AR-SA;"&gt;What is the Problem? If you need any more informations, like the calling from that BADI, just let me know and i will post it ! &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #1f497d; font-family: &amp;amp;quot;Calibri&amp;amp;quot;,&amp;amp;quot;sans-serif&amp;amp;quot;; font-size: 11pt; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-ansi-language: DE; mso-fareast-language: DE; mso-bidi-language: AR-SA;"&gt;thanks a lot &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #1f497d; font-family: &amp;amp;quot;Calibri&amp;amp;quot;,&amp;amp;quot;sans-serif&amp;amp;quot;; font-size: 11pt; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-ansi-language: DE; mso-fareast-language: DE; mso-bidi-language: AR-SA;"&gt;&lt;BR /&gt;&amp;nbsp; &lt;BR /&gt;&amp;nbsp; &lt;BR /&gt;&amp;nbsp; &lt;BR /&gt;&amp;nbsp; &lt;BR /&gt;&amp;nbsp; &lt;BR /&gt;&amp;nbsp; &lt;BR /&gt;&amp;nbsp; &lt;BR /&gt;&amp;nbsp; &lt;BR /&gt;&amp;nbsp; &lt;BR /&gt;&amp;nbsp; &lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 12 Sep 2012 07:37:24 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2012-09-12T07:37:24Z</dc:date>
    <item>
      <title>Missing Position Conditions after ERP-Update while Using bapi_salesorder_createfromdat2</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/missing-position-conditions-after-erp-update-while-using-bapi-salesorder/m-p/9000329#M1697896</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We habe Problems with Using the BAPI bapi_salesorder_createfromdat2 after Updating our Kernel last week.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;System A (with Kernel Update) --&amp;gt; no manuel Conditions will be save in the salesorder&lt;/P&gt;&lt;P&gt;System B (without Kernel Update) --&amp;gt; saves the Conditions we are given to the BAPI.&lt;/P&gt;&lt;P&gt;The Call of that BAPI is in both System completely the same. we havent changes the calling while that ERP-Update.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;SPAU was made and all modification were assumed. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've checked the internal Table for Conditions from FM SD_SALES_DOCU_MAINTAIN who is called in bapi_salesorder_createfromdat2 and they look like that:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #1f497d; font-family: &amp;amp;quot;Calibri&amp;amp;quot;,&amp;amp;quot;sans-serif&amp;amp;quot;; font-size: 11pt; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-ansi-language: DE; mso-fareast-language: DE; mso-bidi-language: AR-SA;"&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/jiveimages/136855" height="246" width="1038" /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; the FM SD_SALES_DOCU_MAINTAIN have been changed after that ERP-Update from last User SAP. So something changed! But what??&lt;BR /&gt;&amp;nbsp;&amp;nbsp; If i insert the conditions with VA02 in that created salesorder manually, everything works fine. So the condition-finding seems to be fine.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #1f497d; font-family: &amp;amp;quot;Calibri&amp;amp;quot;,&amp;amp;quot;sans-serif&amp;amp;quot;; font-size: 11pt; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-ansi-language: DE; mso-fareast-language: DE; mso-bidi-language: AR-SA;"&gt;&lt;BR /&gt;What have been changed in BAPI bapi_salesorder_createfromdat2? &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #1f497d; font-family: &amp;amp;quot;Calibri&amp;amp;quot;,&amp;amp;quot;sans-serif&amp;amp;quot;; font-size: 11pt; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-ansi-language: DE; mso-fareast-language: DE; mso-bidi-language: AR-SA;"&gt;What is the Problem? If you need any more informations, like the calling from that BADI, just let me know and i will post it ! &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #1f497d; font-family: &amp;amp;quot;Calibri&amp;amp;quot;,&amp;amp;quot;sans-serif&amp;amp;quot;; font-size: 11pt; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-ansi-language: DE; mso-fareast-language: DE; mso-bidi-language: AR-SA;"&gt;thanks a lot &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #1f497d; font-family: &amp;amp;quot;Calibri&amp;amp;quot;,&amp;amp;quot;sans-serif&amp;amp;quot;; font-size: 11pt; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-ansi-language: DE; mso-fareast-language: DE; mso-bidi-language: AR-SA;"&gt;&lt;BR /&gt;&amp;nbsp; &lt;BR /&gt;&amp;nbsp; &lt;BR /&gt;&amp;nbsp; &lt;BR /&gt;&amp;nbsp; &lt;BR /&gt;&amp;nbsp; &lt;BR /&gt;&amp;nbsp; &lt;BR /&gt;&amp;nbsp; &lt;BR /&gt;&amp;nbsp; &lt;BR /&gt;&amp;nbsp; &lt;BR /&gt;&amp;nbsp; &lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Sep 2012 07:37:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/missing-position-conditions-after-erp-update-while-using-bapi-salesorder/m-p/9000329#M1697896</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2012-09-12T07:37:24Z</dc:date>
    </item>
    <item>
      <title>Re: Missing Position Conditions after ERP-Update while Using bapi_salesorder_createfromdat2</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/missing-position-conditions-after-erp-update-while-using-bapi-salesorder/m-p/9000330#M1697897</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I resolved the issue on my own *happy*.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Problem was, that we delivery the structure "logic_switch" which contains the field PRICING(pricing type). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;after our erp-update (&lt;SPAN class="urTxtH2"&gt;SP 20 for SAP_APPL 6.00 and &lt;SPAN class="urTxtH2"&gt;SP 21 for SAP_APPL 6.00) the BAPI "bapi_salesorder_createfromdat2" seems to handle the structure logic_switch in a different way.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="urTxtH2"&gt;&lt;SPAN class="urTxtH2"&gt;now we call the bapi without that structure logic_switch and the manuel conditions are saved in the created salesorder.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="urTxtH2"&gt;&lt;SPAN class="urTxtH2"&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="urTxtH2"&gt;&lt;SPAN class="urTxtH2"&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Sep 2012 15:01:59 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/missing-position-conditions-after-erp-update-while-using-bapi-salesorder/m-p/9000330#M1697897</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2012-09-12T15:01:59Z</dc:date>
    </item>
  </channel>
</rss>

