Skip to Content

Some times when the Master data are to be uploaded from a legacy system or from any other non connected, non SAP systems LSMW will come to the rescue. LSMW can be expanded as Legacy System Migration Workbench. This is to migrate the business entities into the CRM system. This tool actually contains following methods in which we can import data to CRM system:

  • Standard Batch / Direct Input
  • Batch Input Recording    
  • BAPI
  • IDOC.

Out of these methods we will have a look into the steps of the importing business partners using Idoc method.

Step 1: Create project using transaction LSMW


Step 2: Select Maintain Attributes Radio Button:


Step 3: Maintain Attributes

Select Idoc Radio button and give “Message Type and Basic Type”.


Click on Save.

Step 4: Activate Inbound processing.

The following screenshots explain the activation of Idoc Inbound processing.


Click “Idoc inbound processings” under settings.


Here maintain “Port” and “Partner type” and Partner number here and Press Activate Idoc Inbound processing.

Step 5: Maintain Source attributes


Click on “Maintain source structures” radio button. Click on Source attributes and then click on create.


Step 6: Maintain source fields



Step 7: Maintain structure relations



Click on structure relation and click on relationship as shown above to maintain relationship.

Step 8: Maintain field mapping


And press F8.


Extras ==> Auto field mapping. Press Enter until you get a popup message field mapping completed.

Step 9: Specify files



Click on the Legacy data while taking file from presentation server and click create.

Step 10: Assign files



Step 11: Read data



Step 12: Display Read data


Step 13: Convert Data



Step 14: Start Idoc generation


We will get popup like this:


Click Ok.

Step 15: Create Idoc overview


After this step, idocs will be created which can be viewed in transaction WE05. I hope this might help who try to import the Business objects using Idoc method of LSMW. For illustration purposes i have combined partners and orders in few places. This is a guideline for LSMW Idoc input method.

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Former Member

    Hi Jothivenkatesh

    Very good posting.

    Also I was wondering if you could create a similarly detailed blog about ALE/IDoc mechnism? Especially I’m interested in delta load. Is there similar mechnism for ALE/IDoc to send data in a delta way like CRM middleware?

    1. Jothivenkatesh M Post author

      Thanks. I will try and publish one in that front. CRM middleware always get involved atleast in terms of XIF Idoc processing. But if the Idoc is originating from CRM system middleware will take part in it.



  2. Former Member


    Decent post!

    Can you please also let me know the basic difference between XIF and crm middleware?

    eg. you can send data from ecc to crm both with crm middleware and XIF. With crm middleware, ecc will use QRFC to call crm_bapi_save in crm and send the bapimtcs structures. But i’m not familar with XIF. With XIF, how the ecc will send the data with idoc? and how crm will take and handle the data?

    1. Jothivenkatesh M Post author


      Thanks. When the Bdoc got generated, in the scheduler, middleware decides whether there is a XIF site connected to the CRM system. If connected, then the data which is created in Bdoc, will be transferred on to the XIF related modules to get it carried to the connected system. Connected systems can be another CRM system itself or any other external systems.

      I am not sure of the fact where XIF is used to connect with ECC, because ECC will always be a R/3 site.



      1. Former Member

        Just one question. In the beginning of your blog “Some times when the Master data are to be uploaded from a legacy system…”, could you please let me know, what exactly ‘legacy system’ means? Can a CRM system be a legacy system? Or, is it that a legacy system has to be an ECC system?   

        1. Former Member

          Hi Juan,

          Legacy system in this context means old system, an example, imagine your company has another CRM like Siebel and now they want to replace Siebel with SAP CRM, the legacy system will be Siebel.




Leave a Reply