SAP S/4HANA
SAP Business Suite 4 SAP HANA (SAP S/4HANA) is an ERP business suite that can be used to perform transactions and analyze business data in real time.
Objects Extracted
You can use the SAP S/4HANA resource to extract metadata from the following assets in an SAP S/4HANA data source:
- •Application Components
- •Packages
- •Classes
- •Data Elements
- •Data Sources
- •Domains
- •Function modules
- •Programs
- •RFC Connections
- •Tables
- •Fields
- •Transaction Codes
- •Views such as database views, CDS views, append views, and external views
Note: If the asset type does not include lineage, hierarchy, categories, and relationship information, you cannot view the following tabs in the Catalog:
- •Lineage and Impact
- •Relationship
- •Contains
You can also view the detailed lineage between the function module and data source assets in the Catalog.
Permissions to Configure the Resource
To configure SAP S/4HANA, perform the following tasks:
- 1. Install Scanner transports.
- 2. Configure a user-authorization profile.
- Installing Scanner Transports
- To extract metadata from SAP S/4HANA, you must import the Scanner transports that Enterprise Data Catalog uses to extract metadata from SAP S/4HANA. The transports are located in the SAP_Scanner_Binaries.zip file that is downloaded from the Informatica installer location.
Note: To extract profiling data from SAP S/4HANA, you must import the Scanner transports located in the following folder where you downloaded PowerCenter: <download location>\saptrans\mySAP.
- Configuring User-Authorization Profiles
- To access metadata from SAP S/4HANA, the SAP S/4HANA administrator needs to create the following user authorization profiles:
Authorization Object | Description | Field Values |
|---|
S_RFC | Authorization check for RFC access | ACTVT: 16 (Execute) RFC_NAME: DDIF_FIELDINFO_GET RFCPING RFC_GET_FUNCTION_INTERFACE RFC_METADATA_GET SEU_COMPONENT ZINFA_ERP RFC_TYPE: FUGR, FUNC |
Prerequisites
- 1. Use Informatica Administrator to create an Event Details Record (EDR) connection for SAP.
For more information about creating connections, see "Connections" in the Informatica Administrator for Enterprise Data Catalog guide.
Note: Ensure that in the Enterprise Application section, you choose the "SAP" connection type and provide the SAP S/4HANA details with Staging and FTP connection details.
- 2. Disable Catalog Service.
- 3. Download the sapjco3.jar file and copy the file to the following locations:
- - Install_directory/services/CatalogService/access/WEB-INF/lib
- - Install_directory/services/shared/jars/thirdpatry
Note: The SAP Java Connector version supported is 3.1.4.
- 4. Download the libsapjco3.so file and copy the file to the following locations:
- - Install_directory/services/shared/bin
- - Install_directory/server/bin
- 5. Create a SAPJCO.zip file, and then add the following files to the first level directory of the .zip file:
- - libsapjco3.so
- - sapjco3.jar
- 6. Copy the .zip file to the following location: Install_directory/services/CatalogService/ScannerBinaries
- 7. Enable the Catalog Service.
Note: If you use the SAP S/4HANA resource to extract profiling data, you must restart the Informatica domain.
Prerequisites to use Secure Network Communications (SNC) connection
- 1. Stop the Informatica Service.
- 2. Create a sec directory in the following location:
<Informatica installation directory>/server/bin/
- 3. Download the libsapcrypto.so file, and copy the file to the <Informatica installation directory>/server/bin/sec location.
- 4. To process profiling data with SNC connection, add the following environment variables:
Environment Variable | Description |
|---|
SNC_LIB | Path of the libsapcrypto.so file including the file name. For example, export SNC_LIB=/home/mdsqe/Informatica/10.5.2/server/bin/sec/libsapcrypto.so |
SECUDIR | Location of PSE and libsapcrypto.so files. For example, export SECUDIR=/home/mdsqe/Informatica/10.5.2/server/bin/sec |
- 5. If you want to process profiling data, include the following SNC parameters as additional parameters, when you configure the SAP EDR connection:
jco.client.snc_mode=<value>; jco.client.snc_partnername=<Name of the Partner>; jco.client.x509cert=<certificate content without space>
Note: You can include up to 1024 characters as additional parameters. Use a semicolon and space to separate the parameters.
For example, you can include the SNC parameters in the following format:
jco.client.snc_mode=1;jco.client.snc_partnername=p:CN=IN0; jco.client.x509cert=MIICqzCCAZMCCAogIgIVBhdBMA0GCSqGSIb3DQEBCwUAMBgxFjAUBgNVBAMTDWludnI3NmRzZzE1OTIwHhcNMjIwMjE1MDYxNzQxWhcNMzgwMTAxMDAwMDAxWjAYMRYwFAYDVQQDEw1pbnZyNzZkc2cxNTkyMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAl2fc9beLR9Q5zBJwh9clQwTHRgg6biqsRge0NBjBVpAeJlCcZ1X0gOcZeoY5rRUxjxSPH1zIozFvo6s87H4nBvQVHAKn4oW19EkPrQYpRuBSD3Bs2sNUnbqbFlPhvaXq+GMJKmmgT6eYrWLQwteXFRGuO+H+d08EivMDBRxDL17lDYkTWytVfMbdkJrFR/R3WLTcDnaGAIfu5zjKfCYYcD4RW3+1Z3SAJs4Bl+4YcFrz709ZVwyRbQqOyfapVNDJTe0tqbp85/s92Ie49A+GF/6EVfkzC03mSVyiu9ZXWSq5NoiDuHC1AsCfiH+bPRzDESdvZI0V/baopcIj0alB1wIDAQABMA0GC
- 6. Download the sapjco3.jar file and copy the file to the following locations:
- - <Install_directory>/services/CatalogService/access/WEB-INF/lib
- - <Install_directory>/services/shared/jars/thirdpatry
Note: The SAP Java Connector version supported is 3.1.4.
- 7. Download the libsapjco3.so file and copy the file to the following locations:
- - <Install_directory>/services/shared/bin
- - <Install_directory>/server/bin
- 8. Configure the SNC connection type with X.509 certificate. For more information about the steps to configure SNC connection type, see the SAP documentation.
- 9. Include the following files in the SAPJCO.zip file:
- - cred_v2
- - libsapcrypto.so
- - sapjco3.jar
- - libsapjco3.so
- - X.509 certificate
- 10. Copy the SAPJCO.zip file to the following location: <Install_directory>/services/CatalogService/ScannerBinaries
- 11. Restart the Informatica Service.
- 12. In a multi-node cluster, verify that you perform the following tasks:
- - Copy the Personal Security Environment (PSE) file into the same path on all the cluster nodes.
- - Configure read permission on the SAP S/4HANA data source for the user account that you use to access the data source.
Basic Information
The General tab includes the following basic information about the resource:
Information | Description |
|---|
Name | The name of the resource. |
Description | The description of the resource. |
Resource type | The type of the resource. |
Execute On | You can choose to execute on the default catalog server or offline. |
Resource Connection Properties
The General tab includes the following properties:
Property | Description |
|---|
SAP Server Type | The type of SAP server installation: - - SAP Central Instance
- - SAP Load Balancer (Message Server)
|
Server Host | Host name or IP address of the system that hosts the SAP S/4HANA. |
Login Group | Login group is a group of servers that belong to an SAP system. Login groups distribute user logins to individual instances or groups of SAP instances or application servers. Login groups are maintained in the transaction SAP Logon Groups (SMLG). The option appears when you select SAP Load Balancer (Message Server) as the SAP Server Type. |
Message Server Port | Default port of the Message server. The option appears when you select SAP Load Balancer (Message Server) as the SAP Server Type. |
System Number | System number of the SAP S/4HANA. The option appears when you select SAP Central Instance as the SAP Server Type. |
SAP SID | The SAP System Identifier of the SAP instance. |
Client | The SAP S/4HANA client to access data from the SAP S/4HANA. |
Language | The language for metadata import from the resource. The selected login language is used to extract the SAP descriptions. |
Connection Type | The type of SAP server connection: - - Basic
- - Secure Network Communications (SNC). You can use the connection type to extract metadata from the SAP S/4HANA data source.
|
Username | SAP S/4HANA system user name. |
Password | SAP S/4HANA system password. |
Enable Streaming for Data Access | |
SNC Partner Name | The SNC name of the communication partner. |
X.509 Certificate File Name | The file name of the X.509 certificate as the log in ticket. |
SNC My Name | The SNC name of the user sending the Remote Function Call (RFC) from Enterprise Data Catalog. |
SNC QoP | Specifies the level of protection to use for the connection. Following are the available protection levels: - - 1. Authentication only
- - 2. Integrity protection
- - 3. Privacy protection
- - 8. Use the value from the snc/data_protection/use location on the application server
- - 9. Use the value from the snc/data_protection/max location on the application server
The default protection level is 3. |
Auto Assign Connections | Indicates whether the connections must be assigned automatically. |
The following table describes the properties that you can configure in the Source Metadata section of the Metadata Load Settings tab:
Property | Description |
|---|
Enable Source Metadata | Enables metadata extraction |
Repository Objects | Filter to extract metadata based on the SAP S/4HANA application components, and packages. The resource performs a full metadata scan if you do not select an SAP S/4HANA application component or package. |
Asset Types | Select the asset types that you want to load into the catalog. Use the options to refine the Repository Objects. |
Enable Reference Resource | Extracts metadata about assets that are not included in the selected component or package, but referred to in the selected component or package. |
Retain Unresolved Reference Assets | Retains unresolved reference assets in the catalog after you assign connections. Retaining unresolved reference assets help you to view the complete lineage. The unresolved assets include assets that are not present in the primary resource. |
Memory | The memory value required to run a scanner job. Specify one of the following memory values: Note: For more information about the memory values, see the Tuning Enterprise Data Catalog Performance article on How To-Library Articles tab in the Informatica Doc Portal |
Custom Options | JVM parameters that you can set to configure scanner container. Use the following arguments to configure the parameters: - - -Dscannerloglevel=<DEBUG/INFO/ERROR>. Changes the log level of scanner to values, such as DEBUG, INFO, or ERROR. Default value is INFO.
- - -Dscanner.container.core=<No. of core>. Increases the core for the scanner container. The value must be a number.
- - -Dscanner.yarn.app.environment=<key=value>. Key pair value that you need to set in the Yarn environment. Use a comma to separate the multiple key value pairs.
- - -Dscanner.pmem.enabled.container.memory.jvm.memory.ratio=<1.0/2.0>. Increases the scanner container memory when pmem is enabled. Default value is 1.
Note: Contact the Informatica Global Customer Support before you change the default JVM parameters. |
Track Data Source Changes | View metadata source change notifications in Enterprise Data Catalog. |
You can use the SAP S/4HANA resource to extract the following profiling information for a Table asset during staging:
- •Domain Discovery
- •Column Profiling
- •Relationship Discovery
Note: Effective in version 10.5.0.1, the SAP S/4 HANA resource does not support extraction of profiling information from columns of type string and string with variable or fixed length.