Diagnosing SAP errors

<< Click to Display Table of Contents >>

Navigation:  Automation Server > Automation Server configuration and administration guide > System maintenance and monitoring > Environment settings and administration > Management Console > Diagnosing errors in integrated systems >

Diagnosing SAP errors

Overview

When configuring SAP's BAPI invocations in Bizagi, you can rely on several features for error control and diagnostics.

One of these features is the use of Traces when you detect there is an issue with the SAP BAPI invocation, and you want to retrieve further detail.

 

SAP traces

When you are debugging a SAP BAPI invocation (in Development environments) or want to retrieve further details about a failed invocation, you can turn on the SAP traces.

 

SAPTrace_all_patch

 

note_pin

You can enable Interfaces traces at any time, but we strongly recommend that you enable them only when they are needed and afterward disable them.

Changes in this configuration require a reset in your Work portal services.

 

Enabling these traces helps you track down, after an error in the application, the exact point where the error has happened. There are four points where details are logged and you can diagnose if there is a problem with your SAP BAPI (target's invocation), or when transformations were being applied to the information.

 

Types of traces

The following traces are logged in chronological order.

 

Chronological order

Trace type

Description

1

Import

Writes aa XML-structured log with information of how the mapping is done for the Import parameters (involving transformation functions).

The following naming convention is followed:

BizagiSAPImport[timestamp].xml

The timestamp is set as yyyyMMddHHmm.

2

Import Transformed

Writes an XML-structured log with the business information retrieved from Bizagi.

The following convention is followed:

BizagiSAPImportTransformed[timestamp].xml

The timestamp is set as yyyyMMddHHmm.

3

Export

Writes an XML-structured log with information of how the mapping is done for the Export parameters (involving transformation functions).

The following naming convention is followed:

BizagiSAPExportTransformed[timestamp].xml

The timestamp is set as yyyyMMddHHmm.

4

Export Transformed

Writes a XML-structured log with the business information incoming from the SAP BAPIs export.

The following naming convention is followed:

BizagiSAPExportTransformed[timestamp].xml

The timestamp is set as yyyyMMddHHmm.