Qlik SAP Exctractor connector - Different output on QlikView and QlikSense

[WalterSchmidt]

Hello,

I want to move my SAP connectors from QlikView to Sense.

The last things are the SAP extractor connector and SAP SQL connector.

The SQL connector in Sense can be configured to a legacy mode and the result should be exactly like the export  from View - there should be no problem.

But the SAP extractor connector outputs from View and Sense are different.
I'm running version 7.0.2 on every system  (I tried 7.0.3 on Sense too - no difference).

The differences are:
1. View exports empty text fields as 1 space - Sense fills the whole field with spaces

2. In Sense some columns containing numbers are exported as text now (before in View - if there are only numbers in the column the export was numeric)

3. in View: negative Values with spaces between sign and value - in Sense without spaces (that should be no problem)

4. That's the biggest problem - different values on both systems
Is this a language problem (both extractions running with EXTRLANGUAGE D )?

Are there undocumented parameters available (for Sense extractor connector) to get the View-result?

================================================================================

Extraction Log Sense:

12 Mar 2020 13:23:28,283 [1] - INFO - Configuring connector
12 Mar 2020 13:23:28,458 [1] - INFO - Connector: QvSAPExtractorConnector.exe Component version: 7.0.3.0 [Qlik SAP Connector Package v7.0.3]
12 Mar 2020 13:23:28,463 [1] - INFO - Debug:False LogLevel:INFO PID:3172 ParentProcess:(Name:Engine.exe MajorVersion:12 MinorVersion:388 FileVersion:12.388.2)
12 Mar 2020 13:23:28,518 [1] - INFO - Running server
12 Mar 2020 13:23:28,685 [1] - INFO - Handling QVX_CONNECT.
12 Mar 2020 13:23:28,801 [1] - INFO - Handling QVX_EXECUTE.
12 Mar 2020 13:23:28,816 [1] - INFO - ExtractorQueryParserService.Parse() - Parsing query:
EXTRACTOR 2LIS_11_VAITM
TFRMETHOD T

UPDMODE R

EXTRLANGUAGE D
LOGSYS QVEXTRACT2
12 Mar 2020 13:23:28,817 [1] - INFO - Verifying license
12 Mar 2020 13:23:29,065 [1] - INFO - Retrieved reply from service:'4!#|4!#|SUCCESS : connected to SAP system!#|7.0.2!#|'
12 Mar 2020 13:23:31,130 [4] - INFO - Starting to receive rows
12 Mar 2020 13:23:59,387 [4] - INFO - Found SapDataComplete in msg from SrvService: 6!#|SAPDATACOMPLETE!#|2LIS_11_VAITM!#|1060!#|11784!#|0!#|ENDOFSTRING!#| - parsed row count = [11784]
12 Mar 2020 13:23:59,391 [4] - INFO - Total rows received: 11784
12 Mar 2020 13:23:59,398 [4] - INFO - Retrieved reply from service:'4!#|4!#|SUCCESS!#|7.0.2!#|'
12 Mar 2020 13:23:59,400 [1] - INFO - Handling QVX_GET_EXECUTE_ERROR.
12 Mar 2020 13:23:59,636 [1] - INFO - Handling QVX_DISCONNECT.
12 Mar 2020 13:23:59,636 [1] - INFO - Handling QVX_TERMINATE.
12 Mar 2020 13:23:59,637 [1] - INFO - Terminating connector client with exitCode:0

================================================================================

Extraction Log View:

2020-03-12 13:44:01 Connector: C:\Program Files\Common Files\QlikTech\Custom Data\QvSAPConnector\QvSAPEXTRConnector.dll - Component version: 7.0.2, Release version: 7.0.2
2020-03-12 13:44:01 Using Server Host: localhost , Port: xxxx
2020-03-12 13:44:01 Socket timeout parameter (s): 900
2020-03-12 13:44:01 Socket created OK
2020-03-12 13:44:01 DNS: getaddrinfo
2020-03-12 13:44:02 Connected to SAP (ASHOST): xx.xxx.xxx.xx
2020-03-12 13:44:02 Making new SAP Request
2020-03-12 13:44:02 EXTRACTOR = 2LIS_11_VAITM
2020-03-12 13:44:02 TFRMETHOD = T
2020-03-12 13:44:02 UPDMODE = R
2020-03-12 13:44:02 EXTRLANGUAGE = D
2020-03-12 13:44:02 LOGSYS = QVEXTRACT2
2020-03-12 13:44:02 EXTRACTOR 2LIS_11_VAITM#TFRMETHOD T#UPDMODE R#EXTRLANGUAGE D#LOGSYS QVEXTRACT2#
2020-03-12 13:44:02 Connection properties: ASHOST=[xx.xxx.xxx.xx], SYSNR=[xx], CLIENT=[xxx], SRVHOST=[localhost], SRVPORT=[xxxx], USERIP=[xxx.xxx.x.xx]
2020-03-12 13:44:02 TimeoutSAP : 14400
2020-03-12 13:44:02 TimeoutInit : 900
2020-03-12 13:44:02 TimeoutActivity: 7200
2020-03-12 13:44:02 TimeoutData : 3600
2020-03-12 13:44:02 TCPBufSize : 1024
2020-03-12 13:44:02 Received Meta Data, No of Fields: 134
2020-03-12 13:44:02 Information from server: INFOMSG : Started job (INITRNR): REQU_QVEXTRACT2_20200312134402
2020-03-12 13:44:32 Information from server: INFOMSG : No data available. Data selection ended. Id: 4
2020-03-12 13:44:32 JOB STATUS: FINISHED, Total Rows: 0, Name: 2LIS_11_VAITM
2020-03-12 13:44:32 Disconnected
2020-03-12 13:44:32 Unloading the Connector.
2020-03-12 13:44:32 Closing the Socket
END AT:
2020-03-12 13:44:34
Total run time: 00h 00m 33s

[Tomas_Sommergyll]

Hi,

There are no undocumented connection string/script parameters available for the Qlik SAP Extractor Connector. 

For (4.): it is strange that your viewer software shows formatted value of -5.000 as -5000. Have you tried to look at the results in apps for both QlikView and Qlik Sense? I tried to reproduce the issue on our internal systems but the result shows the correct values. 

It would be interesting to see the output from the SrvService log (file name like: SrvService_20200313_xxxxxx.txt) using the special "dataLimit_y" level in the settings.config:

folder: "C:\ProgramData\QlikTech\Custom Data\QvSAPConnector"

Add the following line to the bottom under section "[logLevels_NetworkServer]" and save the file:

level=dataLimit_20

Note: This log level parameter will log the data as received from the SAP system. The number "20" is the amount of rows to log per packet, please experiment to get the correct data, e.g. "-5.000".
If the table is small, simply put "level=data" instead.
(Remember to remove the added line in settings.config when finished testing, as the log file will grow quickly)

Best regards,

Tomas

[WalterSchmidt]

Thanks for the answer.

I did an upload with two files (first from View, second from Sense) into one table.
You can see the difference between the columns KWMENG and num(KWMENG).
KWMENG seems to show the correct values - but converting to a number shows the difference.

At the end the sum should be 0 - but now 50050.

I will try the extended log tomorrow.
Do I have to restart any services after editing the config-file?

Thanks for your help.

[Tomas_Sommergyll]

It will be sufficient to save the settings.config after making the changes. The service will pick it up immediately and adjust the log output to the SrvService_xxxx.txt  

Thanks,

Tomas