|Tool Name||Business Suite 4 HANA (S/4HANA), ECC, R/3 ERP (via ABAP program)|
|Tool Web Site||https://www.sap.com/products/erp.html|
|Supported Methodology||[Business Application] Data Store (Physical Data Model, Logical Data Model) via ABAP generated text File|
Import tool: SAP Business Suite 4 HANA (S/4HANA), ECC, R/3 ERP (via ABAP program) 6.0 (https://www.sap.com/products/erp.html)
Import interface: [Business Application] Data Store (Physical Data Model, Logical Data Model) via ABAP generated text File from SAP Business Suite 4 HANA (S/4HANA), ECC, R/3 ERP (via ABAP program)
Import bridge: 'SapR3' 10.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.
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.
Please contact support for details.
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.
|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||
|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:
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 https://support.sap.com/en/product/connectors/jco.html
|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, -f "F:\Work\SAP\output\" -m 4G -j -Dname=value -Xms1G
-f specify path to store metadata locally (for subsequent use with Offline metadata directory parameter).
-v set environment variable(s) (e.g. -v var1=value -v var2="value with spaces").
-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).
Mapping information is not available