Skip to Content

Transfer IDoc data from one system to another


The main aim of this document is to explain how to transfer IDoc data from one system to another for testing purposes.


We need to perform end to end test for an outbound IDoc scenario in System-A (ECC) using the IDoc data present in System-B (ECC).


  • Create a test directory in System-B (ECC) FTP server. Ex: /sapinst/IDOCflatfiles


  • Note the IDoc number in System-B (ECC)


  • Execute the T-Code WE19 in System-B (ECC) and enter the IDoc Number and press F8.


  • Click on inbound file.


  • Enter the directory along with the filename (/sapinst/IDOCflatfiles/FileName) which you created earlier in System-B (ECC) FTP Server. Make sure that Start IDoc inbound processing of file immediately is unchecked and hit enter or execute.


  • Now you can find a file (IDoc Flat File) created in the directory that was created. In addition to the file, an Inbound IDoc will be created (can be viewed in WE02). But, this IDoc will not be defined for processing as Start IDoc inbound processing of file immediately is unchecked.


  • Transfer this file to your desktop.


  • Create a test directory in the System-A (ECC) FTP server. Ex: /sapinst/IDOCflatfiles_Target


  • Transfer the file from your desktop to the directory that was just created in the System-A (ECC) FTP server.


  • Login to the System-A (ECC) and execute WE19 T-Code. Select File as template radio button. Enter the directory along with the file name and execute.


  • Now the IDoc data is transferred from System-B to System-A for testing. Control record values have to be verified before testing.


You must be Logged on to comment or reply to a post.
  • Hi Aditya,

    Thanks for sharing this.

    However, I would suggest caution when using WE19 in a production system as it is considered a Test Tool. Most organisations have authorisations in place to disallow usage of WE19 in their production system.

    Can you confirm when you execute WE19 with “Inbound File” option, would it create a new IDoc in the system? If yes, this might raise potential audit issues.

    If the source system is not a production system, it should be okay to use this method.


    Eng Swee

    • Hello Eng Swee,

      Inboud File option will create an IDoc flat file. As I mentioned if we create a test directory and mention it before clicking Inbound File, IDoc flat file will be create in that directory. And we shall upload this IDoc flat file into the system we need.


      Aditya Vempati.

      • Hi,

        Thanks for your reply. What I would like to know is will it create ALSO (in addition to the flat file in the directory) a new IDoc in the Production system, i.e. with a new IDoc number with same content which can be seen in WE02?


        Eng Swee

        • Hi Eng Swee,

          Yes, it would create an IDoc along with the Flat file. But, as an Inbound IDoc. And as we are not checking Start IDoc inbound processing of file immediately, it will not be defined for processing.


          Aditya Vempati.

          • Hi Aditya

            Ok, thanks for confirmation. My concern is not so much the technicality of this approach, but because it is creating additional objects in the production system, there is audit risk involved (even though it is not defined for processing.)

            Of course, this will depend on the compliance model which differs from organisation to organisation. If your organisation does not consider it an audit risk for additional test objects being created in production, then that’s fine.

            All I am saying is that this approach is perfectly fine to be used in a non-production system, but it needs to be weighed against the organisation’s compliance model when using it in production system.


            Eng Swee

  • Hi Adtiya,


    Thank you for this blog, very helpful.

    Is it possible to copy multiple idocs using this method? I have a need to copy 100 idocs from one system to another. When I tried to do this, It appears to be only create a file with a single doc.