<?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 COR6N - BAPI_PROCORDCONF_CREATE_TT in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/cor6n-bapi-procordconf-create-tt/m-p/10552218#M1857209</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 am having an issues on posting good movement documents via FM above.&lt;/P&gt;&lt;P&gt;Attached are my sample codes and would appreciate anyone can guide me through if there any missed out or wrong parameters entered.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By using attached codes, I've assumed it can posted with 1 material document with 2 line items (movement type 101, and 261). However, its currently on can posted with 2 different material documents for 101 and 261. Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 12 Aug 2014 07:13:01 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2014-08-12T07:13:01Z</dc:date>
    <item>
      <title>COR6N - BAPI_PROCORDCONF_CREATE_TT</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/cor6n-bapi-procordconf-create-tt/m-p/10552218#M1857209</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 am having an issues on posting good movement documents via FM above.&lt;/P&gt;&lt;P&gt;Attached are my sample codes and would appreciate anyone can guide me through if there any missed out or wrong parameters entered.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By using attached codes, I've assumed it can posted with 1 material document with 2 line items (movement type 101, and 261). However, its currently on can posted with 2 different material documents for 101 and 261. Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Aug 2014 07:13:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/cor6n-bapi-procordconf-create-tt/m-p/10552218#M1857209</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-08-12T07:13:01Z</dc:date>
    </item>
    <item>
      <title>Re: COR6N - BAPI_PROCORDCONF_CREATE_TT</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/cor6n-bapi-procordconf-create-tt/m-p/10552219#M1857210</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Anyone can advise on this? Could you provide some sample codes on how to using this FM and what are the mandatory parameters should use?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Aug 2014 01:59:31 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/cor6n-bapi-procordconf-create-tt/m-p/10552219#M1857210</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-08-13T01:59:31Z</dc:date>
    </item>
    <item>
      <title>Re: COR6N - BAPI_PROCORDCONF_CREATE_TT</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/cor6n-bapi-procordconf-create-tt/m-p/10552220#M1857211</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Blue Sky,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What's your issue when you are running this bapi and getting the error information from return internal table?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Yawa&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Aug 2014 03:11:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/cor6n-bapi-procordconf-create-tt/m-p/10552220#M1857211</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-08-13T03:11:14Z</dc:date>
    </item>
    <item>
      <title>Re: COR6N - BAPI_PROCORDCONF_CREATE_TT</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/cor6n-bapi-procordconf-create-tt/m-p/10552221#M1857212</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Yawa,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your reply.&lt;/P&gt;&lt;P&gt;There is no error returned from RETURN internal table. It managed to posted with 2 material documents. What I've expected is only single material document get posted.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Current Results:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Material document 1: Movement type 101 (with material 200001)&lt;/P&gt;&lt;P&gt;Material Document 2: Movement type 261 (with material 200002 and material 200003(This is not specify in coding but unsure why its get posted here).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Expected results&lt;/STRONG&gt;:&lt;/P&gt;&lt;P&gt;Single material document: Line Item 1: Movement type 101 (With material 200001)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Line Item 2: Movement type 261 (with material 200002)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Aug 2014 06:20:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/cor6n-bapi-procordconf-create-tt/m-p/10552221#M1857212</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-08-13T06:20:56Z</dc:date>
    </item>
  </channel>
</rss>

