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
Install the SAP BW Reader transport files on the SAP machines that you want to connect to. If you don't install the latest version of the SAP BW Reader transport files, the following message appears on the Registration page when you configure the catalog source: The test connection for <Connection name> failed. Unable to fetch Function Module, please validate for transport installation
For more information, see Installing SAP BW Reader transport files in the SAP Connector module in the Data Integration Connectors help.
Import SAP transports
Import SAP transports to the SAP BW/4HANA source. You can choose the transport from the dedicated Informatica namespace or the custom namespace.
Transports are available in the SAP_Scanner_Binaries.zip file located in the Informatica Cloud Secure Agent installation directory. The ZIP file is available in the following location:
It is recommended that you import the latest version of the transports. If you use the transports from the version preceding the current version, you see the following message in the logs: SAP Transport version is on previous Version.!!Please import latest transport!!
Important: Metadata extraction from SAP BW/4HANA sources can fail if the transports are not valid or unavailable. For more information, see Knowledge Base article 000202750.
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
Note: Create the deploy_to_main\bin\rdtm-extra\tpl\sap directory if it does not already exist.
Configure the JAVA_LIBS property
Configure the JAVA_LIBS property in Administrator. Perform the following steps:
1Log in to Administrator.
2Click Runtime Environments to access the Runtime Environments page.
3From the menu to the left of the agent name, select Edit Secure Agent.
4From the Service list, select Data Integration Server.
5From the Type list, select Tomcat JRE.
6Enter the JAVA_LIBS value based on the operating system where the Secure Agent runs.
8Repeat steps on every machine where you installed the Secure Agent.
9Restart the Secure Agent.
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)
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.
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.