Meta Integration® Model Bridge (MIMB)
"Metadata Integration" Solution

MIMB Bridge Documentation

MIMB Import Bridge from SAP Business Suite 4 HANA (S/4HANA), ECC, R/3 ERP

Bridge Specifications

Vendor SAP
Tool Name Business Suite 4 HANA (S/4HANA), ECC, R/3 ERP
Tool Version 6.0
Tool Web Site
Supported Methodology [Business Application] Data Store (Physical Data Model, Logical Data Model) via JCO API

Import tool: SAP Business Suite 4 HANA (S/4HANA), ECC, R/3 ERP 6.0 (
Import interface: [Business Application] Data Store (Physical Data Model, Logical Data Model) via JCO API from SAP Business Suite 4 HANA (S/4HANA), ECC, R/3 ERP
Import bridge: 'SapR3' 11.0.0

This bridge imports metadata from the SAP ECC ABAP dictionary.

The bridge relies on the SAP Java Connector (JCo) api libraries to connect and retrieve metadata. Therefore, the JCo libraries must be available on the machine executing this bridge.

The api communicates with the SAP server over the local network, and the following server ports may be used:
* Dispatcher port: 32NN used by SAP GUI for Windows and Java
* Gateway port: 33NN used for CPIC and RFC communications
* SNC secured Gateway port: 48NN used for CPIC and RFC encrypted communications
(where NN is your SAP Instance number from 00 to 99).
Make sure that your firewall settings allow communications on these ports.

Before using the bridge, you must configure the SAP ECC server by deploying an ABAP RFC function module.
You need an ABAP developer account to create the RFC FunctionModule on the SAP server.
This module responds to queries from the bridge, to retrieve the necessary metadata.
Supplemental documentation is available explaining how to deploy the RFC function module on the server at:

Retrieving metadata from the SAP server may take a few hours depending on the volume of metadata, workload of the SAP server, and speed of network between the SAP server and the local machine.
Using the bridge 'Miscellaneous' parameter it is possible to store the downloaded metadata as text files in a local directory.
Using the bridge 'Offline metadata directory' parameter it is possible to read the metadata from previously downloaded text files, to speed up bridge execution, avoiding the delay of downloading from the server again.


Q: How do I provide metadata to the support team to reproduce an issue?
A: Configure the bridge 'Miscellaneous' parameter to save SAP metadata as text files into a local directory.
Compress the resulting files in a ZIP archive and send to the support team.

Bridge Parameters

Parameter Name Description Type Values Default Scope
Application server Enter here the name or IP address of the SAP Application Server Host to connect to. STRING     Mandatory
Router string Enter here the SAP router string to use for a system protected by a firewall. STRING      
System number Enter here the SAP system number (instance ID of the ABAP instance). This is a two digit integer between 00 and 99. NUMERIC     Mandatory
Client Enter here the SAP system client id. The client is identified with three digit numeric number from 000 to 999. NUMERIC     Mandatory
User name Enter here your logon user name, it must be a valid user name on the SAP system. STRING     Mandatory
Password Enter here your logon user password. PASSWORD     Mandatory
Default Language Specify the language you would like to use. ENUMERATED
Chinese (Simplified)
Chinese (Traditional)
JCo library path The bridge reads metadata from SAP using the Java Connector (JCo) 3.0 api.
Specify in this parameter the directory path where the JCo libraries are located.
This directory should contain for example on Microsoft Windows:
- sapjco3.jar
- sapjco3.dll

Different versions of the JCo libraries are available from SAP, for various operating systems and processor architectures. Make sure that you are using the correct JCo distribution for your environment.
For example, if you use a 32bits Java JVM on a 32 bits Windows platform, you should use the 32bits JCo libraries for Intel x86 processor.

For download, licensing and other information, please refer to
DIRECTORY     Mandatory
Offline metadata directory In order to facilitate testing and reproducing SAP metadata environment, when that environment is not installed locally, this parameter allows importing metadata from files previously downloaded from the SAP server. Specify in this parameter the directory path where the downloaded files are located. No connection to the SAP server is needed in this case, the usual connection parameters are ignored. DIRECTORY      
Content Allows to reduce import scope to a set of objects smaller than the whole server content. REPOSITORY_SUBSET      
Miscellaneous Specify miscellaneous options identified with a -letter and value.

For example, -backup "F:\Work\SAP\output\" -m 4G -j -Dname=value -Xms1G

-v set environment variable(s) (e.g. -v var1=value -v var2="value with spaces").
-jre {path to java executable} to specify a custom Java Runtime Environment. It could be an absolute path to javaw.exe on Windows or a link/script path on Linux.
for example: -jre "c:\Program Files\Java\jre1.8.0_211\bin\javaw.exe"
-m the maximum Java memory size whole number (e.g. -m 4G or -m 2500M ).
-j the last option that is followed by Java command line options (e.g. -j -Dname=value -Xms1G).
-jco.file specify path to file with additional connection details( for example SNC connection details). The bridge appends parameters specified in the bridge configuration to the file before passing it to JCo.
-backup full path of an empty directory to save the metadata input files for further troubleshooting, or use for the Offline metadata directory parameter.


Bridge Mapping

Meta Integration Repository (MIR)
(based on the OMG CWM standard)
"SAP Business Suite 4 HANA (S/4HANA), ECC, R/3 ERP"
SAP ERP Central Component (SAP ERP Central Component)
Mapping Comments
Attribute Primary Key Field, Message, Table Field  
Description Short Description  
Name Name  
Optional Optional  
Position Position  
Class Table, IDoctype  
Description Description, Short Description  
Name Name  
DataAttribute Data Field  
Name Name  
DataSet Structure  
Name Name  
DatabaseSchema Schema  
Description Description  
Name Name  
NativeId Native Id  
NativeType Native Type  
DerivedType Data Element, Domain  
Description Short Description  
Length Length  
LowerBound Lower Limit  
Name Name  
NativeDataType Data Type  
Scale Decimal Places  
UpperBound Upper Limit  
DesignPackage Program, Subject Area, Transaction, Application Component, Function Group, Class, Package  
Description Description, Short Description  
Name Name  
NativeId Id  
PhysicalName Software Component  
ForeignKey Foreign Key  
Name Name  
Index Index  
Description Short Text  
Name Name  
Unique Unique  
IndexMember Index Member  
Name Name  
SQLViewAttribute View Field  
Description Short Description  
Name Name  
Position Position  
SQLViewEntity View  
Description Short Description  
Name Name  
ViewStatement View Statement  
StoreModel ECC Instance  
Name Name  
StoreType Store Type  
SystemType System Type  
StoredProcedure Function Module  
Description Description  
Name Name  
TypeValue Domain Value  
Description Short Description  
Name Name  
Position Position  
Value Value  

Last updated on Tue, 23 Jun 2020 18:16:25

Copyright © Meta Integration Technology, Inc. 1997-2020 All Rights Reserved.

Meta Integration® is a registered trademark of Meta Integration Technology, Inc.
All other trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.