Using DataBridgeAgent with SAP Connector for Purchase-to-Pay Discovery Accelerator

Important:

DataBridgeAgent is only needed if you are migrating from an on-premises stand-alone Process Mining version.

Only use DataBridgeAgent if you have a custom .mvp connector. Otherwise, use CData Sync, Theobald Xtract Universal for SAP, or files to upload data.

Note: DataBridgeAgent already includes the SAP Connector for Purchase-to-Pay Discovery Accelerator. You do not need to download and deploy the connector itself.

Introduction

Below is an overview of the parameters that need to be specified in the Datarun.json file for using DataBridgeAgent with SAP Connector for Purchase-to-Pay Discovery Accelerator.

Generic settings

Below is an overview of the generic settings.

Setting	Value
azureURL	"sas url" The SAS URL of the Azure blob storage to which the extracted data needs to be uploaded. Note: The azureURL is not used when loading data for use in Process Mining on-premises (Automation Suite). Make sure this field is left blank.
endOfUploadApiUrl	The API that is called to start data processing in Process Mining, once all data has been uploaded. Note: The endOfUploadApiUrl is not used when loading data for use in Process Mining on-premises (Automation Suite). Make sure this field is left blank.
connectorWorkspace	"SAP_Connector_for_Purchase-to-Pay_Discovery_Accelerator"
connectorModuleCode	"SAP_Connector_for_Purchase-to-Pay_Discovery_Accelerator"
Use credential store	true | false

Extracting data from an SAP source system

SAP Settings

Below is an overview of the parameters that can be used for SAP datasources.

Setting	Value
SAP Host	The hostname or IP address of the SAP application server. "yourserver.domain:1234"
SAP Systemnumber	The two-digit number between 00 and 99 that identifies the designated instance. "00"
SAP Username	Username of the account that is being used to log in to the SAP instance. "username"
SAP Password	Password of the account that is being used to log in to the SAP instance, or the password identifier from the credential store. (If the credential store is used, the Use credential store generic setting should be set to true.) "password" | "PasswordIdentifier"
SAP Client	The client that is being used. (000-999). "000"
Exchange rate type	The exchange rate type which is used for currency conversion (KURST). "M"
Language	The language that is being used for descriptions extracted from the data (E = English). "E"

Loading .csv files from SAP tables

If you want to use data loaded from .csv files always make sure that all the required input data is available.

Always make sure that:

• a separate .csv file is available for each table.
• the file names of the .csv files are the same as the names of the input tables of the connector.
• all the fields specified in the Fields used in Process Mining column of a table are present in the .csvfile.
• the fields in the .csv files have the same names as the field names specified in the Fields used in Process Mining column.

Optionally, you can set a CSV Suffix. By default the suffix is optional 2 digits and .csv/.CSV. For example, for the EBAN table, with the default suffix, the filename must be EBAN.csv or EBAN1.csv or EBAN.CSV. The other settings can be defined in the CSV parameters of the DataBridgeAgent.

CSV parameters

Below is an overview of the parameters that can be used for CSV datasources.

SAP Setting	Description
CSV Data path	Data path in the Server Data that points to the place where the .csv files are stored. For example P2P/ if all files can be found in the folder named P2P.
CSV Suffix	A regular expression containing the files extension of the file to read in. May contain a suffix up to 2 digits that are added to the name of the table.
CSV Delimeter	The delimiter character that is used to separate the fields.
CSV Quotation character	The quote character that is used to identify fields that are wrapped in quotes.
CSV Has header	Indicate whether the first line of the .CSV file is a header line.

Troubleshooting

Note: If the data upload with DataBridgeAgent fails, you can check the file EXTRACTORDIR\datarun.txt that contains the logs of the last data run.