Data types from SAP doesn't correspond anymore with the SAP SQL connector after Upgrade
Article Number: 000042225 | Last Modified: 2019/09/12
After an upgrade of the SAP Connector you can run into data type issues in Qlik View or Qlik Sense.
The reason is often related to new features that have been introduced in newer SAP Connector versions.
Since release 6.1 the SQL connector changed how some SAP data types are treated. For backward
compatibility, there are now several new Connection String Properties available.
When MixedMode is enabled, the NUMC and CHAR data types are sent as UNKNOWN instead
of ASCII, and it is up to Qlik to decide what their content is. A numeric string with a maximum
length of 14 characters will be interpreted as numeric in Qlik (the same behavior as in the legacy
-MixedMode (0 or false / 1 or true. Default/off = 0 or false.)
NulldateLegacy and Nulldate
When NulldateLegacy is enabled, the property Nulldate behaves as it did in the legacy
connector, returning an empty value when Nulldate is enabled and returning "0000-00-00"
when Nulldate is disabled.
When NulldateLegacy is disabled, null is returned when Nulldate is enabled and 0 (displays
as 1899-12-30) is returned when Nulldate is disabled.
When FLTPLegacy is enabled, FLTP (floating point) data is transferred to QlikViewas string values with scientific notation.
When FLTPLegacy is disabled (the default setting), floating point data is transferred in decimal format.
0/1 (default/off = 0 or false, on = 1 or true)
When TIMSLegacy is enabled, TIMS data is transferred to as DUAL.
When TIMSLegacy is disabled (the default setting), TIMS data is
A possible connection string can look like this:
CUSTOM CONNECT TO "Provider=QvSAPSqlConnector.exe;servertype=0;ASHOST=[ServerName];CLIENT=[Client];SYSNR=07;Timeout=3600;SNC_MODE=false;SNC_QOP=9;advancedProperties=false;ConvRoutine=false;
In general It is recommended to use the new data type handling introduced with the latest SAP Connector versions for new development