<?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: IDOC_INPUT_ORDERS problems in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-input-orders-problems/m-p/1206301#M132340</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Kiran,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Based on your post I am not exactly sure what your problem is.  But I can explain how this BDC processing works.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDOC_INPUT_ORDERS creates a BDC to load VA01 with the data from the IDOC.  In customer function 001, you can transfer data from the IDOC fields to the program variables.  If you transfer data to standard sap fields in the structures provided, the function module should automatically create the correct BDC Logic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the fields you are trying to add to VA01 are not standard SAP fields, then you need to change the BDC internal table in customer function 002.  However you need to take special care when doing this.  Since this is a BDC, you need to ensure that the additional BDC logic that you are added is inserted into the table correctly as to not cause issues when the call transaction is made.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If this doesn't answer your question, please provide more specifics with what you are trying to accomplish.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Chris&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 07 Mar 2006 16:06:10 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-03-07T16:06:10Z</dc:date>
    <item>
      <title>IDOC_INPUT_ORDERS problems</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-input-orders-problems/m-p/1206300#M132339</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Friends,&lt;/P&gt;&lt;P&gt;Ive got some problems when posting the idocs of type orders05. I could find a oss note relevant to this.. But i dont know how to do this practically. can somebody help me with this....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Solution:&lt;/P&gt;&lt;P&gt;The standard modules IDOC_INPUT_ORDERS, IDOC_INPUT_ORDCHG,                     &lt;/P&gt;&lt;P&gt;IDOC_INPUT_REQOTE provide customer functions which allow you to read           &lt;/P&gt;&lt;P&gt;additional fields from the Idoc and copy them into screens. For this           &lt;/P&gt;&lt;P&gt;purpose you must call within these functions the standard routines for  copying the fields into tables and, if necessary, for formatting the       &lt;/P&gt;&lt;P&gt;fields and transferring them into the screens.                             &lt;/P&gt;&lt;P&gt;You must carry out correctly the process of the background controlled      &lt;/P&gt;&lt;P&gt;screen sequence, the error-free field transfer and the proper enclosure    &lt;/P&gt;&lt;P&gt;of the documents, in particular if you call screens that are ignored in    &lt;/P&gt;&lt;P&gt;the standard case. SAP is not liable for resulting problems.               &lt;/P&gt;&lt;P&gt;                       &lt;/P&gt;&lt;P&gt;    o  Use Customer function '001' for reading the Idoc fields.            &lt;/P&gt;&lt;P&gt;                                                               o  The filling of the screen fields should be carried out in customer  function 002&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Kiran.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Mar 2006 15:58:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-input-orders-problems/m-p/1206300#M132339</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-03-07T15:58:49Z</dc:date>
    </item>
    <item>
      <title>Re: IDOC_INPUT_ORDERS problems</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-input-orders-problems/m-p/1206301#M132340</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Kiran,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Based on your post I am not exactly sure what your problem is.  But I can explain how this BDC processing works.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDOC_INPUT_ORDERS creates a BDC to load VA01 with the data from the IDOC.  In customer function 001, you can transfer data from the IDOC fields to the program variables.  If you transfer data to standard sap fields in the structures provided, the function module should automatically create the correct BDC Logic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the fields you are trying to add to VA01 are not standard SAP fields, then you need to change the BDC internal table in customer function 002.  However you need to take special care when doing this.  Since this is a BDC, you need to ensure that the additional BDC logic that you are added is inserted into the table correctly as to not cause issues when the call transaction is made.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If this doesn't answer your question, please provide more specifics with what you are trying to accomplish.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Chris&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Mar 2006 16:06:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-input-orders-problems/m-p/1206301#M132340</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-03-07T16:06:10Z</dc:date>
    </item>
    <item>
      <title>Re: IDOC_INPUT_ORDERS problems</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-input-orders-problems/m-p/1206302#M132341</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Chris,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Im developing an interface to upload purchase orders/sales orders from mercury system to sap and every field is a sap standard field. i populated the segments respectively and executed the inbound fm zXXXX. its creating an idoc with 51 status and the error message im getting is Function module not allowed:IDOC_INPUT_ORDERS. i dont know how to deal with this.. if i am not clear plz do let me know&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Mar 2006 16:15:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-input-orders-problems/m-p/1206302#M132341</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-03-07T16:15:55Z</dc:date>
    </item>
    <item>
      <title>Re: IDOC_INPUT_ORDERS problems</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-input-orders-problems/m-p/1206303#M132342</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Kiran,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since I am not familiar with what you have done so far here are some possible problems:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.  Are you using standard message type ORDERS or did you create a new message type?&lt;/P&gt;&lt;P&gt;2.  Have you verified that the inbound settings in transaction WE57 are correct for function module, basic type and message type?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Other than that I am no sure how to proceed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Chris&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Mar 2006 17:58:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-input-orders-problems/m-p/1206303#M132342</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-03-07T17:58:14Z</dc:date>
    </item>
  </channel>
</rss>

