Skip to Content

XI: Mapping Tool Exports

This weblog will help you understand the “Tools” menu in the data-flow editor which will allow you to export/import your graphical message maps as MappingTool Export files (.mte). This .mte file is an accurate representation of the graphical message map and it is also editable. But i don’t recommend editing it unless you are extremely conversant and sure about what you are doing with the .mte files. Place your mouse cursor on the Data Flow Editor area and press Ctrl+Shift and right-click the mouse button to view the “Tools” menu. You can keep the map in Edit or display mode to export it as a .mte file (mapping tool export file).
You will be prompted to enter the name for the .mte file. I recommend you to use the same name as your message/graphical map name. image
When importing the .mte files make sure you have your graphical map in edit mode and your source & target messages are selected. The “Import” menu item will be enabled only during edit mode.

image The following screenshots show how the mapping tool export files looks like: image

Besides the transformation information, other information like User-defined functions, test cases, position co-ordinates of the graphical bricks etc are stored in this .mte files.

You must be Logged on to comment or reply to a post.
    • Thanks Michal !

      Some of these menu items don’t work or at least i have not got them to work 🙂 I have updated my blog accordingly.
      But you can be absolutely sure that Export/Import works fine and I have been using it for quite a while now.


        • Mapping tool export files are XML based files that contain the complete definition of your graphical mapping.

          Mapping template is just a part of your graphical map which by itself is a graphical map. So you can export/import Mapping templates as mapping tool export files (.mte) as well.

          E.g. real-life usage of a .mte file: Assume you have completed message map using an external definition (XSD) as source structure  and target is an IDoc. Now you find that in your external definition you want change the name of an XML tag.
          If you do a import of the updated XSD, you will lose the mapping for the tags which were dependent on the updated tag.

          Solution: Export the .mte file before you import the updated XSD. Open the .mte file using any text/xml editor and find/replace the old xml tag with the new xml tag. Now import the updated XSD. Delete the old map. create a new one selecting the source and target structure and simply import the updated .mte file.

    • Hi Michal,

      Sorry for the late reply.Been busy.
      I was never able to get the export test case to work 🙂 I generally use the saved ones that come with the exported .mte file.


  • Hi folks,

    In case you didn’t know, the functionality you’re discussing, is not supported by SAP and is hidden for good reasons. Firstly, it has never ever been tested, and secondly, a user is not supposed to tinker with metadata of Message-Mapping, which could be changed in any SP without notice.
    I see Sridhar is pretty sure that Export/Import works, but I am not. And by the way, I’m a developer of the tool. If you have use-cases, which are not covered by current functionality, I suggest that you better send a development request, rather than playing with that hidden functionality.


    • Hi Alexey,

      Very Glad to hear from the developer himself 🙂

      I wanted to add the statement “use at your own risk” since SAP has not documented this feature. But its far better that people hear about it from the horse’s mouth 🙂

      >>I see Sridhar is pretty sure that Export/Import works, but I am not.
      Atleast it has worked fine for me till date 🙂
      But i will be careful in future.