White spaces / ASCII 160 from SAP BW Extraction

Tue, 05 Apr 2016 12:15:15 GMT

Hello together,

since we have installed the new SAP connector 6.1.1 / 6.1.2 we have the problem that white spaces and/or parts of the content are removed while extracting.

Key1: "D003201229"

Key2: "D003201229 "

Key3: "D003201229 "

That means if we try to extract /BI0/TMATERIAL using the SAP SQL Connector some keys are existing multiple times. That is a big problem because if we connect these lines they will also double or multiply the factdata. Is there any way dealing with this issue?

Currently the script looks like this:

// CONNECTION-STRING has been removed

[/BI0/SMATERIAL]:

SELECT MATERIAL

FROM /BI0/SMATERIAL

WHERE MATERIAL like 'D003201229%';

This has the following result (3 means the frequency):

D003201229 3

I know its not the best approach fixing error coming from the source system on QV side but we need a workaround to deal with this as soon as possible.

Any ideas?

Best

Simon

Re: White spaces / ASCII 160 from SAP BW Extraction

Gysbert_Wassenaar — Fri, 15 Apr 2016 11:53:03 GMT

You can try using the Verbatim system variable:

SET Verbatim = 1;

That prevents the default stripping out blank characters. To be honest I have no idea if this has any effect i.c.w. the SAP connector.

topic Re: White spaces / ASCII 160 from SAP BW Extraction in QlikView

White spaces / ASCII 160 from SAP BW Extraction

Re: White spaces / ASCII 160 from SAP BW Extraction