Bridge Specifications
| Vendor | SAP |
| Tool Name | Business Warehouse 4 HANA (BW/4HANA) (via JCO API) |
| Tool Version | 7.0 to 7.5 |
| Tool Web Site | https://www.sap.com/products/business-warehouse.html |
| Supported Methodology | [Business Intelligence] Multi-Model, BI Design (OLAP Source) via Java API |
Import tool: SAP Business Warehouse 4 HANA (BW/4HANA) (via JCO API) 7.0 to 7.5 (https://www.sap.com/products/business-warehouse.html)
Import interface: [Business Intelligence] Multi-Model, BI Design (OLAP Source) via Java API from SAP Business Warehouse 4 HANA (BW/4HANA) (via JCO API)
Import bridge: 'SapBw' 10.0.0
This bridge imports SAP NetWeaver Business Warehouse (BW) metadata.
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 BW 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.
SUPPORT
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 |
|
DE | ||||||||||||||||||||||
| 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 https://support.sap.com/en/product/connectors/jco.html |
DIRECTORY | Mandatory | |||||||||||||||||||||||
| Mapping configuration file | Some Transformations in BW are represented with ABAP code. It is necessary to document these transformations in a mapping configuration file. Specify here the path to the configuration file in the following format: <Functions> <Function id="[TransformationId]" objType="TRFN"> <Target id="RESULT_FIELDS-[dstFieldName]" description="RESULT_FIELDS-[dstFieldName] = SOURCE_FIELDS-[srcFieldName] * [externalObjectId]-[externalField]."> <Source id="SOURCE_FIELDS-[srcFieldName]"/> <Source id="[externalObjectId]-[externalField]"/> </Target> </Function> </Functions> |
FILE | *.xml | |||||||||||||||||||||||
| Naming convention | Specify the naming rule you want to use. SAP BW metadata objects have a technical name, and optionally a description, and the description may vary depending on the user language. SAP BW tools offer various naming conventions to customize how names are displayed. This parameter allows one to reproduce such conventions, the possible choices are: - [TechnicalName] Description - Description [TechnicalName] - Description_TechnicalName - [TechnicalName] The default value is [TechnicalName] Description |
ENUMERATED |
|
KTX | ||||||||||||||||||||||
| Incremental import | Specifies whether to import only the changes made in the source or to re-import everything (as specified in other parameters). True - import only the changes made in the source. False - import everything (as specified in other parameters). An internal cache is maintained for each metadata source, which contains previously imported models. If this is the first import or if the internal cache has been deleted or corrupted, the bridge will behave as if this parameter is set to 'False'. |
BOOLEAN |
|
True | ||||||||||||||||||||||
| 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 | ||||||||||||||||||||||||
| 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). |
STRING |
Bridge Mapping
| Meta Integration Repository (MIR) Metamodel (based on the OMG CWM standard) |
"SAP Business Warehouse 4 HANA (BW/4HANA) (via JCO API)" Metamodel SapBW |
Mapping Comments |
| Attribute | DataSource Field | |
| Name | Name | |
| Position | Position | |
| BaseType | Datatype | BaseTypes are inferred from datatypes found in BW |
| DataType | Datatype | See datatype conversion arrays |
| Name | Based on the datatype | |
| Scale | Datatype | extracted from the datatype |
| UpperBound | Validation_Rule_Max_Value | |
| Class | DataSource | DataSources with multiple segments are not well supported yet (only one segment is assumed) |
| CppClassType | Set to ENTITY | |
| CppPersistent | Set to True | |
| Name | Technical Name | |
| ClassifierMap | Used to connect objects together, and represent data lineage | |
| Condition | Query Filter, Characteristic restriction | represents data filtering in Queries |
| Name | Name | computed from Technical Name and Description |
| NativeId | UID | |
| PhysicalName | Technical Name | |
| Connection | TransferRules, UpdateRules, Transformations | BW objects which move or transfer data from one object to another are imported as Data Mappings |
| MatchingRule | Long Description | |
| Name | Name | computed from Technical Name and Description |
| DatabaseSchema | DataSource | A Schema is created for each DataSource |
| Name | Name | computed from Technical Name and Description |
| DerivedType | Datatype | |
| DataType | Datatype | See datatype conversion arrays |
| Length | Length | |
| Name | Derived from BW datatype name | |
| Scale | Decimal Places | |
| Dimension | InfoSource, InfoObject, InfoProvider, Query, QueryView, Reports | Represents the internal structure of main objects in BW |
| Comment | Short Description | |
| Description | Long Description | |
| Name | Name | computed from Technical Name and Description |
| PhysicalName | Technical Name | |
| UserDefined | set to True | |
| DimensionAttribute | Characteristic InfoObject | |
| Comment | Short Description | |
| Description | Long Description | |
| Name | Name | computed from Technical Name and Description |
| PhysicalName | Technical Name | |
| DirectoryStructureModel | BW system | Represents the BW system |
| Name | System ID | |
| FeatureMap | Used to connect objects together, and represent data lineage | |
| Folder | InfoArea, Application | also used to group objects together |
| Author | Owner | |
| Description | Long Description | |
| LastModificationTime | Last changed timestamp | |
| Modifier | Last changed by | |
| Name | Name | computed from Technical Name and Description |
| Measure | KeyFigure InfoObject | |
| Comment | Short Description | |
| DefaultAggregation | Aggregation | |
| Description | Long Description | |
| Name | Name | computed from Technical Name and Description |
| PhysicalName | Technical Name | |
| OlapSchema | InfoSource, InfoObject, InfoProvider, Query, QueryView, Reports | an OlapSchema is created for each main BW object, to contain its structural details |
| Name | Name | computed from Technical Name and Description |
| PropertyElementTypeScope | BW specific properties | Used to record some BW specific properties, such as SourceSystem connection parameters |
| Scope | property scope | |
| PropertyType | BW specific properties | Used to record some BW specific properties, such as SourceSystem connection parameters |
| DataType | Type | |
| Name | Name | |
| PropertyValue | BW specific properties | Used to record some BW specific properties, such as SourceSystem connection parameters |
| Value | Value | value set on an object |
| StoreContent | InfoSource, InfoObject, InfoProvider, Query, QueryView, Reports | Main BW objects are imported as individual models |
| Author | Owner | |
| Description | Long Description | |
| LastModificationTime | Last changed timestamp | |
| Modifier | Last changed by | |
| Name | Name | computed from Technical Name and Description |
| StoreModel | DataSource, InfoSource, InfoProvider, Query, QueryView, Reports | Main BW objects are imported as individual models |
| Author | Owner | |
| Comment | Short Description | |
| Description | Long Description | |
| ModificationTime | Last changed timestamp | |
| Modifier | Last changed by | |
| Name | Name | computed from Technical Name and Description |
| PhysicalName | Technical Name | |
| Semantics | Code |