SAP traces

<< Click to Display Table of Contents >>

Navigation:  Bizagi Studio > Bizagi Studio user interface explained > Advanced settings > Tracing configuration >

SAP traces

Overview

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

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

 

SAP traces

Whenever you are debugging a SAP BAPI invocation (in Development environments) or whenever you wish to retrieve further detail about a failed invocation, you may choose to turn on the SAP traces.

 

SAPTrace_all

 

 

note_pin

Keep in mind that Interfaces traces can be enabled anytime, but it is strongly recommended to enable them temporarily only when needed (and afterwards, to disable them).

Changes in this configuration will require a reset in your Bizagi Server's services.

 

Enabling these traces is useful to track down, after an error in the application, the exact point where said error has happened. There are 4 points where details are logged and you may diagnose if there is a problem with your SAP BAPI (target's invocation), or whenever 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

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

The following convention is followed:

BizagiSAPImport[timestamp].xml

Note that timestamp is set as yyyyMMddHHmm.

2

Import Transformed

Leaves a XML-structured log with the business information retrieved from Bizagi.

The following convention is followed:

BizagiSAPImportTransformed[timestamp].xml

Note that timestamp is set as yyyyMMddHHmm.

3

Export

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

The following convention is followed:

BizagiSAPExportTransformed[timestamp].xml

Note that timestamp is set as yyyyMMddHHmm.

4

Export Transformed

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

The following convention is followed:

BizagiSAPExportTransformed[timestamp].xml

Note that timestamp is set as yyyyMMddHHmm.