Enterprise Data Catalog Scanner Configuration Guide > Configuring Application Resources > SAP S/4HANA
  

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.
Technical Preview Notice: Effective in version 10.4.1, the SAP S/4HANA resource is available for technical preview. Technical preview functionality is supported but is unwarranted and is not production-ready. Informatica recommends that you use these features in non-production environments only. Informatica intends to include the preview functionality in an upcoming GA release for production use, but might choose not to in accordance with changing market or technical circumstances. For more information, contact Informatica Global Customer Support.

Objects Extracted

You can use the SAP S/4HANA resource to extract metadata from the following assets in an SAP S/4HANA data source:
Note: If the asset type does not include lineage, hierarchy, categories, and relationship information, you cannot view the following tabs in the Catalog:
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. 1. Install Scanner transports.
  2. 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.
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
SEU_COMPONENT
ZINFA_ERP
RFC_TYPE : FUGR, FUNC
S_RFC_ADM
Administration for RFC destination
ACTVT :03

Prerequisites

  1. 1. Disable the Catalog Service.
  2. 2. Download the sapjco3.jar file and copy the file to the following location: <Install_directory>/services/CatalogService/access/WEB-INF/lib.
  3. Note: The SAP Java Connector version supported is 3.0.19.
  4. 3. Download the libsapjco3.so file and copy the file to the following location: <Install_directory>/services/shared/bin.
  5. 4. Include the libsapjco3.so file in the SAPJCO.zip file and copy the SAPJCO.zip file to the following location: <Install_directory>/services/CatalogService/ScannerBinaries.
  6. 5. Enable the Catalog Service.

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.
Username
SAP S/4HANA system user name.
Password
SAP S/4HANA system password.
Language
The language for metadata import from the resource. The selected login language is used to extract the SAP descriptions.
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.
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:
  • - Low
  • - Medium
  • - High
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
JVM 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.