<?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 and IDOC relationship in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-and-idoc-relationship/m-p/3995717#M954604</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Gaurav&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you explain me what an ALE interface means for  BAPI?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 11 Jun 2008 18:45:33 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-06-11T18:45:33Z</dc:date>
    <item>
      <title>BAPI and IDOC relationship</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-and-idoc-relationship/m-p/3995712#M954599</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am trying to use LSMW to create sales order using the BAPI method CREATEFROMDAT2. While trying to save I keep getting the error message maintain the default values for IDOC inbound processing. What does IDOC processing have anything to do with BAPI's. Are BAPI's and IDOC's related?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Jun 2008 18:09:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-and-idoc-relationship/m-p/3995712#M954599</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-11T18:09:18Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI and IDOC relationship</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-and-idoc-relationship/m-p/3995713#M954600</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi check this example for that here the relation is given clearly..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Step-by-Step Guide for using BAPI in LSMW&lt;/P&gt;&lt;P&gt;Note! The screen prints in this article are from ECC 5.0. They may differ slightly in other versions. &lt;/P&gt;&lt;P&gt;Introduction:&lt;/P&gt;&lt;P&gt;This document details the usage of BAPI in LSMW. We have used the example of migration of the purchase order data into SAP. &lt;/P&gt;&lt;P&gt;Pre-requisites:&lt;/P&gt;&lt;P&gt;It is assumed that the reader of this article has the minimum knowledge required on the Business Object, BAPI, Message Types and IDoc Types. &lt;/P&gt;&lt;P&gt;Step-by-Step Procedure:&lt;/P&gt;&lt;P&gt;Details of the BAPI used in this scenario:&lt;/P&gt;&lt;P&gt;Business Object: BUS2012&lt;/P&gt;&lt;P&gt;Method: CreateFromData &lt;/P&gt;&lt;P&gt;Details of Message Type and Basic IDoc Type:&lt;/P&gt;&lt;P&gt;Message Type: PORDCR&lt;/P&gt;&lt;P&gt;Basic IDoc Type: PORDCR02 &lt;/P&gt;&lt;P&gt;Let&amp;#146;s have a look at the BAPI first, before proceeding to the LSMW:&lt;/P&gt;&lt;P&gt;1. Go to Transaction BAPI &lt;/P&gt;&lt;P&gt;2. Click on Search Button &lt;/P&gt;&lt;P&gt;3. Enter the value &amp;#147;BUS2012&amp;#148; and select &amp;#147;Obj.type(Technical Object Name&amp;#148; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4. Press ENTER &lt;/P&gt;&lt;P&gt;5. Following screen appears: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;6. On the left side of the screen, Expand the &amp;#147;PurchaseOrder&amp;#148;. &lt;/P&gt;&lt;P&gt;7. Select &amp;#147;PurchaseOrder&amp;#148; and double-click on the same for details. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Building LSMW using BAPI: &lt;/P&gt;&lt;P&gt;1. Go to Transaction LSMW.&lt;/P&gt;&lt;P&gt;2. Enter the Project, Subproject and Object information and click on CREATE.&lt;/P&gt;&lt;P&gt;3. Enter the descriptions for Project, Subproject and Object.&lt;/P&gt;&lt;P&gt;4. Now select Settings à IDoc Inbound Processing&lt;/P&gt;&lt;P&gt;5. &amp;#147;IDoc Inbound Processing&amp;#148; screen appears. Enter the required details as shown below:&lt;/P&gt;&lt;P&gt;6. Click on &amp;#147;Activate IDoc Inbound Processing&amp;#148;.&lt;/P&gt;&lt;P&gt;7. Click on &amp;#147;Yes&amp;#148; when prompted for &amp;#147;Activate IDoc Inbound?&amp;#148;&lt;/P&gt;&lt;P&gt;8. Hit on &amp;#147;Back&amp;#148; to return to the main screen.&lt;/P&gt;&lt;P&gt;9. Click on Continue (F8). Following Screen appears:&lt;/P&gt;&lt;P&gt;10. Select the Step 1 &amp;#147;Maintain Object Attributes&amp;#148; and select &amp;#147;Execute&amp;#148;.&lt;/P&gt;&lt;P&gt;11. Select the radio button &amp;#147;Business Object Method&amp;#148; and enter the following details:&lt;/P&gt;&lt;P&gt;Business Object: BUS2012&lt;/P&gt;&lt;P&gt;Method: CreateFromData&lt;/P&gt;&lt;P&gt;Hit ENTER&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;12. Save and click on BACK button. Following information message is displayed.&lt;/P&gt;&lt;P&gt;13. Now select step 2 &amp;#147;Maintain Source Structures&amp;#148; and click &amp;#147;Execute&amp;#148;.&lt;/P&gt;&lt;P&gt;14. In this step, we need to maintain the source structure. In our example, lets consider the example of a file with 2 structures Head and Item data as shown below: &lt;/P&gt;&lt;P&gt;Click on Create and name the source structure as HEADERDATA. Now select HEADERDATA and click on &amp;#147;Create&amp;#148; again to create the child structure. Following popup appears:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Select &amp;#147;Lower Level&amp;#148; and click on Continue. Enter the Item data structure name. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Click Save and hit BACK button to go to the main screen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;15. Select step 3 &amp;#147;Maintain Source Fields&amp;#148; and hit execute.&lt;/P&gt;&lt;P&gt;16. Enter the fields as shown below:&lt;/P&gt;&lt;P&gt;17. Click SAVE and return to main screen.&lt;/P&gt;&lt;P&gt;18. Select step 4 &amp;#147;Maintain Structure Relations&amp;#148; and click Execute.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Select E1PORDCR and click on CREATE RelationShip. Following screen appears:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Select HEADERDATA and hit ENTER&lt;/P&gt;&lt;P&gt;Similarly do the same for the structure E1BPEKKOA, E1BPEKPOC and E1BPPEKET. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Click Save and return to main screen.&lt;/P&gt;&lt;P&gt;19. Select the step &amp;#147;Maintain Field Mapping and Conversion Rules&amp;#148; and click on execute. Maintain the Field Mapping as seen below:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;20. Select step 7 &amp;#147;Maintain Source Files&amp;#148; and provide the link for the test file created. (Create a test file with the same structure as defined earlier).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Save and return to main screen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;21. Select the step &amp;#147;Assign Files&amp;#148; and click on Execute.&lt;/P&gt;&lt;P&gt;Assign the file provided to the source structure. Here the same file is provided for both the structures.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Save and return to the main screen.&lt;/P&gt;&lt;P&gt;22. Select the step &amp;#147;Read Data&amp;#148; and click on Execute.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Click on Execute.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Return to the main screen.&lt;/P&gt;&lt;P&gt;23. Select the step &amp;#147;Display read data&amp;#148; and click on execute.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Click on the structure name to get the field level values.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;24. Return to main screen and now select &amp;#147;Convert Data&amp;#148;.&lt;/P&gt;&lt;P&gt;25. Return to the main screen and select &amp;#147;Display Converted data&amp;#148;.&lt;/P&gt;&lt;P&gt;26. Return to main screen and select &amp;#147;Start IDoc generation&amp;#148;.&lt;/P&gt;&lt;P&gt;27. Now select the step &amp;#147;Start IDoc Processing&amp;#148; on the main screen.&lt;/P&gt;&lt;P&gt;28. Return to main screen and click on &amp;#147;Create IDoc overview&amp;#148;. Here the data record and status records of the IDoc could be viewed&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is given in screen shot.&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.saptechnical.com" target="test_blank"&gt;http://www.saptechnical.com&lt;/A&gt;&lt;/P&gt;&lt;P&gt;see this&lt;/P&gt;&lt;P&gt;&lt;A href="http://esnips.com/doc/ef04c89f-f3a2-473c-beee-6db5bb3dbb0e/LSMW-with-BAPI.ppt" target="test_blank"&gt;http://esnips.com/doc/ef04c89f-f3a2-473c-beee-6db5bb3dbb0e/LSMW-with-BAPI.ppt&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;venkat&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Jun 2008 18:19:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-and-idoc-relationship/m-p/3995713#M954600</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-11T18:19:17Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI and IDOC relationship</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-and-idoc-relationship/m-p/3995714#M954601</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am more interested in understanding the relationship between BAPI and IDOC&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Jun 2008 18:24:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-and-idoc-relationship/m-p/3995714#M954601</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-11T18:24:23Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI and IDOC relationship</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-and-idoc-relationship/m-p/3995715#M954602</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI Megan,&lt;/P&gt;&lt;P&gt;   Yes, there is a relation ship between the idocs and corresponding BAPIs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The IDOC Inbound processing function modules internally call the BAPIs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example: &lt;/P&gt;&lt;P&gt;BAPI_FIXEDASSET_CREATE is called in IDOC_INPUT_FIXEDASSET_CREATE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDOC_INPUT_BANK_CREATE calls the BAPI BAPI_BANK_CREATE&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ravi Kanth Talagana&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ravi Kanth Talagana&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Jun 2008 18:35:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-and-idoc-relationship/m-p/3995715#M954602</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-11T18:35:01Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI and IDOC relationship</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-and-idoc-relationship/m-p/3995716#M954603</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You used BAPI BAPI_SALESORDER_CREATEFROMDAT2.&lt;/P&gt;&lt;P&gt;It is associated with ALE message type SALESORDER_CREATEFROMDAT2.&lt;/P&gt;&lt;P&gt;It means there is an ALE interface for this BAPI hence the message.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;G@urav.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Jun 2008 18:39:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-and-idoc-relationship/m-p/3995716#M954603</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-11T18:39:09Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI and IDOC relationship</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-and-idoc-relationship/m-p/3995717#M954604</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Gaurav&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you explain me what an ALE interface means for  BAPI?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Jun 2008 18:45:33 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-and-idoc-relationship/m-p/3995717#M954604</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-11T18:45:33Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI and IDOC relationship</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-and-idoc-relationship/m-p/3995718#M954605</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;check this&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/18/22b812773211d396b20004ac96334b/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/18/22b812773211d396b20004ac96334b/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;G@urav.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Jun 2008 18:50:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-and-idoc-relationship/m-p/3995718#M954605</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-11T18:50:23Z</dc:date>
    </item>
  </channel>
</rss>

