Catalog Source Configuration > SAP BW/4HANA

SAP BW/4HANA

SAP BW/4HANA is an enterprise data warehouse platform that captures, stores, and consolidates enterprise data.

Objects extracted

The SAP BW/4HANA catalog source extracts metadata from the following assets in an SAP BW/4HANA source system:

•Info Area
•Data Source
•Info Objects
•Source System
•Info Source
•Characteristics
•Key Figures
•Navigational Attributes
•Transformation
•Transformation Rule
•Query
•Query Element or Field
•Advanced DSO
•Composite Provider
•DTP
•Open ODS View
•Aggregation Level
•Open Hub Destination
•InfoObject as InfoProvider

Prerequisites

To extract metadata from SAP BW/4HANA source systems, complete the following prerequisite tasks:

Create a connection in Administrator: Use the SAP BW connector to connect to the SAP BW/4HANA source system. For information about configuring a connection in Administrator, see Connections in the Cloud Common Services help.

Install the SAP BW Reader transport files

Import SAP transports

Download the SAP JCo libraries: Download the latest version of the 64-bit SAP JCo libraries from the SAP Service Marketplace based on the operating system on which the Secure Agent runs and copy the files to the following location: <Informatica Secure Agent installation directory>\apps\Data_Integration_Server\ext\deploy_to_main\bin\rdtm-extra\tpl\sap

Secure Agent System	SAP File Name
Windows	sapjco3.jar sapjco3.dll
Linux	sapjco3.jar libsapjco3.so

Configure the JAVA_LIBS property: Configure the JAVA_LIBS property in Administrator. Perform the following steps:

Configure permissions

Before you configure an SAP BW/4HANA catalog source in Metadata Command Center, configure the following permissions:

Configure user-authorization profiles: The SAP Business Warehouse administrator creates the following product and development user authorization profiles:

Authorization Object	Description:
S_RFC	Authorization check for RFC access. This class uses the Cross Application Authorization Objects with the following field values: ACTVT: 16 (Execute) RFC_NAME: DDIF_FIELDINFO_GET RFCPING RFC_GET_FUNCTION_INTERFACE RFC_METADATA_GET RFC_TYPE : FUGR, FUNC If you imported scanner transports from the custom namespace, use the following value: ZINFA_BW4H_FG If you imported scanner transports from the Informatica namespace, use the following value: /INFASCAN/BW4H_FG If you enabled UCON (Unified Connectivity), perform one of the following tasks: - Disable UCON. Set the ucon/rfc/active profiling parameter value to 0. - If you can't disable UCON, whitelist the Informatica RFC function modules that start with: ZINFA or /INFASCAN/
S_RS_COMP	Business explorer components. This class uses the Business Warehouse with the following field values: ACTVT : 03,16 RSINFOAREA: * (Full Authorization) RSINFOCUBE: * (Full Authorization) RSZCOMPID: * (Full Authorization) RSZCOMPTP: Full Authorization
S_RS_COMP1	Business explorer components: Enhancements to the owner. This class uses the Business Warehouse with the following field values: ACTVT : 03,16 RSZCOMPID: * (Full Authorization) RSZOWNER: * (Full Authorization) RSZCOMPTP: * (Full Authorization)

Connection properties

After you configure a connection to SAP BW/4HANA in Informatica Intelligent Cloud Services Administrator, you can view the connection properties for that connection on the Registration page in Metadata Command Center.

The following table describes the SAP BW/4HANA connection properties:

Property	Description
Connection Name	Name of the connection. Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -, Maximum length is 255 characters.
Description	Description of the connection. Maximum length is 4000 characters.
Type	SAP BW Connector
Runtime Environment	The name of the runtime environment where you want to run tasks. Select a Secure Agent.
Username	The user name with the appropriate user authorization to connect to the SAP BW account.
Password	The password to connect to the SAP BW account.
Connection type	Required. Type of connection that you want to create. Select one of the following values: - Application. Create an application connection when you want to connect to a specific SAP BW server. - Load balancing. Create a load balancing connection when you want to use SAP load balancing. Default is Application.

The following table describes the basic connection properties for an application connection:

Property	Description
Host name	The host name or IP address of the SAP BW server to which you want to connect.
System number	The system number of the SAP BW server. Get the required system number from the SAP system to which you want to connect.
Client	The client number of the SAP BW server. Get the required client number from the SAP system to which you want to connect.
Language	Language code that corresponds to the SAP language. Get the required language code from the SAP system to which you want to connect.

The following table describes the advanced connection properties for an application connection:

Property	Description
Trace	Determines whether to track the JCo calls that the SAP system makes. Enter one of the values between 0 and 8. By default, SAP doesn't store information about the JCo calls in a trace file. Default is 0. For more information about trace level values, see Setting up an SAP Java Connector (SAP JCo) and Related Traces. You can access the trace files from the following directories: - Design time information: <Informatica Secure Agent installation directory>\apps\Data_Integration_Server\<Latest version>\ICS\main\tomcat - Run-time information: <Informatica Secure Agent installation directory>\apps\Data_Integration_Server\<Latest version>\ICS\main\bin\rdtm
Additional parameters	Additional JCo connection parameters that you can use when you read SAP BW data. You can enter multiple JCo connection parameters, separated by a semicolon, in the following format: <parameter name1>=<value1>;<parameter name2>=<value2>;<parameter name3>=<value3>.... For example, if you want to create an SAP SNC connection, enter the following additional parameters: SNC_MODE=1;SNC_QOP=3;SNC_MYNAME=p:CN=<Common name>, OU=<Organizational unit>, O=<Organization>, C=<Country>;SNC_PARTNERNAME=p:CN=<Common name>, OU=<Organizational unit>, O=<Organization>, C=<Country>;SNC_LIB=C:\SNC_11\sapcrypto.dll;TRACE=1
Port Range	HTTP port range. The SAP BW connection uses the specified port numbers to connect to SAP BW using the HTTP protocol. Default range is 10000-65535. Enter a range in the default range, for example, 10000-20000. When a range is outside the default range, the connection uses the default range.
Use HTTPS	Select this option to enable https streaming.
Keystore location	The path and file name of the keystore file to connect to SAP. Enter both the path and file name in the following format: <Directory>/<Keystore file name>.jks
Keystore password	The password to access the keystore file.
Private Key password	The export password to access the .P12 file.
SAP Additional Parameters	Additional SAP properties that the Secure Agent uses to connect to the SAP system as an RFC client. Specify the required RFC-specific parameters and connection information that enable the Secure Agent to connect to SAP. For example, you can specify the SNC connection parameters as additional arguments listed in the following sample: MSHOST= <Message server hostname> GROUP=PUBLIC R3NAME=SLT SNC_MODE=1 SNC_QOP=3 SNC_MYNAME=p:CN=<Common name>, OU=<Organizational unit>, O=<Organization>, C=<Country> This is the SNC name of the Secure Agent machine. SNC_PARTNERNAME=p:CN=<Common name>, OU=<Organizational unit>, OU=SAP Web AS, O=<Organization>, C=<Country>. This is the SNC name of the SAP system. SNC_LIB =<Secure Agent installation directory>/apps/Data_Integration_Server/ext/deploy_to_main/bin/<libsapcrypto.so for Linux/sapcrypto.dll for Windows> X509CERT=<X509 certificate> For more information about SNC parameters, see How to configure the SAP Secure Network Communication protocol Informatica How-To Library article. For more information about RFC-specific parameters, see the SAP documentation. Note: If you specify a parameter in both the SAP Additional Parameters and Additional parameters fields, the value specified in the SAP Additional Parameters field takes precedence.

The following table describes the basic connection properties for a load balancing connection:

Property	Description
Host name	The host name or IP address of the SAP BW server to which you want to connect.
System number	The system number of the SAP BW server. Get the required system number from the SAP system to which you want to connect.
Client	The client number of the SAP BW server. Get the required client number from the SAP system to which you want to connect.
Language	Language code that corresponds to the SAP language. Get the required language code from the SAP system to which you want to connect.

The following table describes the advanced connection properties for a load balancing connection:

Property	Description
Message host name	Required. The host name of the SAP message server to which you want to connect when you use a load balancing connection.
R3 name/SysID	Required. The system ID of the SAP message server to which you want to connect when you use a load balancing connection.
Group	Required. The name of the SAP logon group through which you want to connect when you use a load balancing connection.
Trace	Determines whether to track the JCo calls that the SAP system makes. Enter one of the values between 0 and 8. By default, SAP doesn't store information about the JCo calls in a trace file. Default is 0. For more information about trace level values, see Setting up an SAP Java Connector (SAP JCo) and Related Traces. You can access the trace files from the following directories: - Design time information: <Informatica Secure Agent installation directory>\apps\Data_Integration_Server\<Latest version>\ICS\main\tomcat - Run-time information: <Informatica Secure Agent installation directory>\apps\Data_Integration_Server\<Latest version>\ICS\main\bin\rdtm
Additional parameters	Additional JCo connection parameters that you can use when you read SAP BW data. You can enter multiple JCo connection parameters, separated by a semicolon, in the following format: <parameter name1>=<value1>;<parameter name2>=<value2>;<parameter name3>=<value3>.... For example, if you want to create an SAP SNC connection, enter the following additional parameters: SNC_MODE=1;SNC_QOP=3;SNC_MYNAME=p:CN=<Common name>, OU=<Organizational unit>, O=<Organization>, C=<Country>;SNC_PARTNERNAME=p:CN=<Common name>, OU=<Organizational unit>, O=<Organization>, C=<Country>;SNC_LIB=C:\SNC_11\sapcrypto.dll;TRACE=1
Port Range	HTTP port range. The SAP BW connection uses the specified port numbers to connect to SAP BW using the HTTP protocol. Default range is 10000-65535. Enter a range in the default range, for example, 10000-20000. When a range is outside the default range, the connection uses the default range.
Use HTTPS	Select this option to enable https streaming.
Keystore location	The path and file name of the keystore file to connect to SAP. Enter both the path and file name in the following format: <Directory>/<Keystore file name>.jks
Keystore password	The password to access the keystore file.
Private Key password	The export password to access the .P12 file.
SAP Additional Parameters	Additional SAP properties that the Secure Agent uses to connect to the SAP system as an RFC client. Specify the required RFC-specific parameters and connection information that enable the Secure Agent to connect to SAP. For example, you can specify the SNC connection parameters as additional arguments listed in the following sample: MSHOST= <Message server hostname> GROUP=PUBLIC R3NAME=SLT SNC_MODE=1 SNC_QOP=3 SNC_MYNAME=p:CN=<Common name>, OU=<Organizational unit>, O=<Organization>, C=<Country> This is the SNC name of the Secure Agent machine. SNC_PARTNERNAME=p:CN=<Common name>, OU=<Organizational unit>, OU=SAP Web AS, O=<Organization>, C=<Country>. This is the SNC name of the SAP system. SNC_LIB =<Secure Agent installation directory>/apps/Data_Integration_Server/ext/deploy_to_main/bin/<libsapcrypto.so for Linux/sapcrypto.dll for Windows> X509CERT=<X509 certificate> For more information about SNC parameters, see How to configure the SAP Secure Network Communication protocol Informatica How-To Library article. For more information about RFC-specific parameters, see the SAP documentation. Note: If you specify a parameter in both the SAP Additional Parameters and Additional parameters fields, the value specified in the SAP Additional Parameters field takes precedence.

Note: The SAP BW catalog source in Metadata Command Center supports only Secure Network Communication (SNC) with X.509 certificate. You can also use SNC with username and password.

Configuration parameters for metadata extraction

Specify additional configuration parameters from the Configuration Parameters area in the Metadata Extraction tab of the Configuration page.

Source Extraction. Filters the metadata that you extract from an SAP BW/4HANA source system.

You can choose one of the following values:

•Full. Extracts the full metadata from the source.
•Based on Query Execution Date. Extracts metadata based on the query execution date that you specify for the Scan date parameter in the YYYYMMDD format. The corresponding dependent metadata objects are also extracted.
•Based on Object Modified Date. Extracts metadata that is modified or created after the date that you specify for the Scan date parameter in the YYYYMMDD format. Perform at least one full extraction before extracting metadata based on object modified date.

Namespace. Specifies the namespace from which you imported the scanner transport. Select the dedicated Informatica namespace or the custom namespace based on the scanner transport that you imported.

Referenced source systems

When you run the catalog source job, if the catalog source references another source system, a reference catalog source and connection get created that point to the reference source system. To view the complete lineage for your catalog source, you can perform connection assignment from the reference catalog source connection to the objects in the reference source system. A reference source system might be a database, such as SAP HANA Database. You must first create and run an endpoint catalog source that connects to the reference source system.

Note: You can view the lineage with reference objects without performing a connection assignment. After connection assignment, you can view the actual objects.

You can assign the following source systems as endpoint catalog sources:

Source system	Endpoint
SAP HANA Database	Database
SAP ERP	SapSchema

You can perform a connection assignment from the following assets and catalog sources to SAP BW/4HANA:

•From Calculation View assets of SAP HANA Database to Composite Provider assets of SAP BW/4HANA
•From Table assets of SAP HANA Database to DataSource assets of SAP BW/4HANA
•From View assets of SAP HANA Database to DataSource assets of SAP BW/4HANA
•From CDS View assets of SAP ERP to DataSource assets of SAP BW/4HANA
•From DataSource assets of SAP ERP to DataSource assets of SAP BW/4HANA

Data classification for SAP BW/4HANA objects

Configure data classification for SAP BW/4HANA catalog sources to classify and organize data in your organization. You can view the data classification results in Data Governance and Catalog.

You can choose one of the following options:

•Data Classification Rules. Choose from predefined or custom data classifications.
•Generated Data Classifications. CLAIRE automatically generates data classifications for the data elements.

Note: SAP BW/4HANA source systems can contain ambiguous data with technical field names. To ensure that CLAIRE generates accurate data classifications, it uses the extracted Business Name attribute to generate data classifications.

You can view the data classification results in Data Governance and Catalog.

For more information about data classifications, see Data classification in the Administration help.

Glossary association

Enable glossary association and configure settings for the catalog source to automatically associate or recommend glossary terms as business names for data elements in technical assets.

The following table describes the settings:

Property	Description
Enable auto-acceptance	When enabled, this option automatically associates glossary terms with data elements based on the threshold limit that you specify. The automatically accepted glossary terms appear as business names of data elements in Data Governance and Catalog.
Confidence Score Threshold for Auto-Acceptance	Specify a percentage from 80 to 100 inclusive to set a threshold limit. If a glossary term matches a data asset within the threshold specified, Metadata Command Center automatically assigns the matching glossary term to the data element. The name and description of the glossary term with the highest confidence score appears as the name and description of the data element asset in Data Governance and Catalog.
Enable below-threshold recommendations	If you enable auto-acceptance, you can select this option to receive glossary association recommendations below the auto-acceptance threshold.
Confidence score threshold for recommendations	If you enable auto-acceptance, specify a percentage between 80% and the selected confidence score threshold for auto-acceptance. If you disable auto-acceptance, specify a percentage between 80% and 100%.
Assign business names and descriptions	Choose to automatically assign business names and descriptions to technical assets.
Keep existing business names and descriptions	Applicable if you choose to assign business names and descriptions. Choose to retain existing assignments and only assign business names and descriptions to assets that don't have assignments, or allow overwrite of existing assignments. By default, existing assignments are retained.
Ignore Keywords	Choose to ignore specific parts of data elements when making recommendations. You can enter multiple unique prefix and suffix keywords. Keyword values are case insensitive.
Glossary Association Scope	Choose specific top-level business glossary assets to associate with technical assets. Selecting a top-level asset selects its child assets as well.

Note: SAP BW/4HANA source systems can contain ambiguous data with technical field names. To generate accurate glossary associations, CLAIRE uses the extracted Business Name attribute for such technical field names.

For more information about the glossary association settings, see the Administrator help.