Catalog Source Configuration > SAP ERP

SAP ERP

SAP Enterprise Resource Planning (ERP) is a platform that incorporates the key business functions of an organization. Use this catalog source to extract metadata from SAP ERP Central Component (ECC) or SAP S/4HANA source systems.

Objects extracted

The SAP ERP catalog source extracts metadata from the following assets in SAP S/4HANA and SAP ECC source systems:

•Packages

Includes subpackages and assets in subpackages.

•Classes in active state
•Data Elements in active state
•Data Sources built on tables, views and function modules
•Domains in active state
•RFC function modules and function modules used in a data source
•Executable programs in active state
•RFC Connections in active state
•Tables in active state such as transparent tables, cluster tables, and pool tables
•Fields
•Transaction codes in active state
•Views such as database views, CDS views, append views, and external views

Prerequisites

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

Create a connection in the Administrator: Use the SAP BAPI connector to configure a connection to SAP ERP in Informatica Intelligent Cloud Services Administrator. For information about configuring a connection in Administrator, see Connections in the Cloud Common Services help.

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. Copy the files to <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 permissions

To extract metadata, you need account access and permissions on the SAP S/4HANA and SAP ECC source systems.

Configure user-authorization profiles: To access metadata from SAP ERP, the SAP ERP administrator creates the following user authorization profiles:
Permissions to run data profiles: You do not need additional permissions to run data 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 RFC_TYPE: FUGR, FUNC If you imported scanner transports from the custom namespace, use the following value: ZINFA_ERP If you imported scanner transports from the Informatica namespace, use the following value: /INFASCAN/ERP_META 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/

Connection properties

After you configure a connection to SAP BAPI 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 basic SAP Bapi 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 Bapi
Runtime Environment	The execution platform that runs tasks. The runtime environment is either a Secure Agent or a Serverless runtime environment.
Username	The user name with the appropriate user authorization to connect to the SAP account.
Password	The password to connect to the SAP account.
Host Name	The host name or IP address of the SAP server to which you want to connect.
Client	The client number of the SAP 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.
System Number	The system number of the SAP server. Get the required system number from the SAP system to which you want to connect.

The following table describes the advanced SAP Bapi connection properties:

Property	Description
SAP Additional Parameters	Additional SAP properties that the Secure Agent uses to connect to the SAP system as an RFC client. See the following examples where you can use this field to configure additional parameters for the connection: - To create a load balancing connection, define the additional arguments listed in the following sample: GROUP=interfaces MSHOST=<Message server hostname> R3NAME=<System ID or name of SAP system> SAP infers the connection type based on the parameters that you specify. For example, if you define the GROUP, MSHOST, and R3NAME parameters, SAP infers the connection type as a load balancing connection. The GROUP parameter defines the group name of the SAP application server. The MSHOST parameter defines the host name of the SAP message server. The R3NAME parameter defines the system ID or name of the SAP system. - To commit data to the SAP system with each BAPI/RFC call, define the DOCOMMIT=true parameter. - To create a connection with the Secure Network Communication (SNC) protocol, define the required additional parameters. f you specify a property both in the dedicated connection field and in the SAP Additional Parameters field, the value specified in the SAP Additional Parameters field takes precedence. For more information about SAP parameters, see the SAP documentation.
Jco Trace	Select this checkbox to enable tracing for the BAPI call. Even if you define the Trace parameter in the SAP Additional Parameters field, select the Jco Trace check box to generate the trace file.

Property

Description

SAP Additional Parameters

Additional SAP properties that the Secure Agent uses to connect to the SAP system as an RFC client.

See the following examples where you can use this field to configure additional parameters for the connection:

- To create a load balancing connection, define the additional arguments listed in the following sample:

GROUP=interfaces
MSHOST=<Message server hostname>
R3NAME=<System ID or name of SAP system>

SAP infers the connection type based on the parameters that you specify. For example, if you define the GROUP, MSHOST, and R3NAME parameters, SAP infers the connection type as a load balancing connection. The GROUP parameter defines the group name of the SAP application server. The MSHOST parameter defines the host name of the SAP message server. The R3NAME parameter defines the system ID or name of the SAP system.

- To commit data to the SAP system with each BAPI/RFC call, define the DOCOMMIT=true parameter.
- To create a connection with the Secure Network Communication (SNC) protocol, define the required additional parameters.

f you specify a property both in the dedicated connection field and in the SAP Additional Parameters field, the value specified in the SAP Additional Parameters field takes precedence.

For more information about SAP parameters, see the SAP documentation.

Jco Trace

Select this checkbox to enable tracing for the BAPI call.

Even if you define the Trace parameter in the SAP Additional Parameters field, select the Jco Trace check box to generate the trace file.

After you configure a connection to SAP Table in Informatica Intelligent Cloud Services Administrator, you can view the source connection name for that connection on the Data Profiling and Quality tab of the Configuration page in Metadata Command Center.

The following table describes the basic SAP Table 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 Table Connector
Runtime Environment	Required. The name of the runtime environment where you want to run the tasks.
Username	The user name with the appropriate user authorization to connect to the SAP account.
Password	The password to connect to the SAP account.
Client	The client number of the SAP application 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 SAP Table connection properties:

Property	Description
Saprfc.ini Path	Required. Local directory to the sapnwrfc.ini file. To write to SAP tables, use the following directory: <Informatica Secure Agent installation directory>/apps/Data_Integration_Server/ext/deploy_to_main/bin/rdtm
Destination	DEST entry that you specified in the sapnwrfc.ini file for the SAP application server. Use all uppercase letters for the destination. This property is required if you create the connection to write to SAP tables. If you enter the DEST entry in this field, do not enter the host name or IP address, and system number of the SAP application server in the Application Server and System Number fields.
Port Range	HTTP port range. The SAP Table connection uses the specified port numbers to connect to SAP tables 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.
Test Streaming	Tests the connection. When selected, tests the connection using both RFC and HTTP protocol. When not selected, tests connection using RFC protocol.
Https Connection	When selected, connects to SAP through HTTPS protocol. To successfully connect to SAP through HTTPS, verify that an administrator has configured the machines that host the Secure Agent and the SAP system.
Keystore Location	Absolute path and file name of the keystore file to connect to SAP. Specify both the path and file name in the following format: <Directory>/<Keystore file name>.jks
Keystore Password	The destination password to access the keystore file.
Private Key Password	The export password to access the .P12 file.

Configuration parameters for metadata extraction

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

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.

Data profiling for SAP ERP objects

Prerequisites

Configure data profiling to run profiles on metadata extracted from SAP S/4HANA and SAP ECC source systems. You can run data profiles on the following SAP ERP objects:

•Table
•View

Note: You can run data profiles on database views and CDS views.

After running the catalog source job, you can view the profiling statistics in Data Governance and Catalog. The data profiling task runs profiles on the following data types for SAP ERP objects:

•ACCP
•CHAR
•CLNT
•CUKY
•CURR
•DATS
•DEC
•D16D
•D16R
•D34D
•D34R
•FLTP
•INT2
•INT4
•LANG
•LCHR
•LRAW
•NUMC
•QUAN
•SSTRING
•STRING
•STRU
•TIMS
•UNIT
•RAW
•RAWSTRING

For information about rules and guidelines for SSTRING, STRING, and RAWSTRING data types, see SAP Connector in the Data Integration-Free and PayGo help.

Sampling type: You can run data profiling on all rows in the metadata extracted from SAP S/4HANA and SAP ECC source systems.

Data classification for SAP ERP objects

Configure data classification for SAP ERP catalog sources to classify and organize data in your organization.

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 ERP 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 ERP 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.