topic Problem in SAP report Data extraction through 5.50 connector in QlikView

Problem in SAP report Data extraction through 5.50 connector

Tue, 29 Mar 2011 09:16:20 GMT

Hi,

We are trying to extract SAP reprort data through Qlikview. In this purpose we are connecting to the SAP program: "sdorde01" with variant: "sdrkfl" in the Qlikview desginer. We are able to connect to the report. By default the field delimeter is '!'. But, we are facing problem while segregating columns through field delimeter. From the fifth field onwards Qlikview is unable to segregate almost 19 columns as per the delimeter and it is showing all the 19 columns as a single one. Hence attaching the file, containing the screenshot of the same problem.

In another z-report, we found that Qlikview was able to fetch only few columns out of the many columns as displayed in that report.

We will appreciate if any of you can guide us to resolve these two issues.

Thanks & regards

Supriyo Roy Kanungoe

Problem in SAP report Data extraction through 5.50 connector

Miguel_Angel_Baeyens — Tue, 29 Mar 2011 09:24:17 GMT

Hello,

Are you skipping titles and lines Rows by category, and using Header rows so you get the field names?

If you cannot, you can use

...SubField(Field, '!', 1) AS Blank,SubField(Field, '!', 2) AS Field1,SubField(Field, '!', 3) AS Field2...

to get the fiels loaded separately over the code that the Connector generates.

Hope that helps.

Problem in SAP report Data extraction through 5.50 connector

Tue, 29 Mar 2011 09:39:43 GMT

Hi,

Thank you for the reply. Your solution is working, but it is tedious.

So, instead we are skipping all the unwanted rows and only considering the Header row and Data rows by categorization. By doing so system is able to delemit first 4 columns as per the default field delimeter '!', but 5th column onwards default field delimeter fails to delemit.

Supriyo

Problem in SAP report Data extraction through 5.50 connector

Miguel_Angel_Baeyens — Tue, 29 Mar 2011 09:42:35 GMT

Hello Supriyo,

That may be because of some lines with different categories at the bottom of the report (if it's done by pages, at the end of the page or something).

If the delimiter is not working check with the SAP experts what may be going wrong.

Regards.

Problem in SAP report Data extraction through 5.50 connector

skoppe — Tue, 24 Jan 2012 10:10:20 GMT

Hi Supriyo,

I'm facing exactly the same problem, have you found a solution already?

Regards.

Re: Problem in SAP report Data extraction through 5.50 connector

Tue, 14 Feb 2012 12:58:38 GMT

The correction on this is a bit tedious.

Initially my workaround was to split the fields manually in my script using the delimiters. Something like:

SubField([Concatenated_Fields],'!',1)AS [Field_1],

SubField([Concatenated_Fields],'!',2)AS [Field_2]

This method worked perfectly for me on some reports but when testing the results, on larger reports, I found some rows with data shifted into the wrong column. These rows contained the delimiter [!] in the data and in the very column that started the concatenation.

The preferred method that worked across the board for my solution:

After you “Get” the report in the report builder and you have completed defining which rows are to be ‘Skipped’ and which are ‘Headers’, you need to count the number of fields that exist between the last delimiter and the point where the next should be. Insert that number (in the example below from 153 to 194) into the ‘Field delimiter after position box’ -> Click Add. A new separator appears in the sample view and the script is updated. Repeat until all your columns have been included...

The script that is created before looks something like:

Load [Field0_],[Field1_],[Field11_Concatenated]

Select SAPREPORT (REPORT (MYREPORT), VARIANT (QV_VARIANT),ROWS_PER_RECORD (1), FIELD_DELIMITER_POSITIONS (0, 11, 16, 27, 40, 48, 56, 65,96, 113, 142, 153), SKIP (T (1)),HEADER (P (0, "!Header !")));

Note FIELD_START_POSITIONS in the new script:

Load [Field0_],[Field1_],[Field11_],[Field12_],[Field13_],....

Select SAPREPORT (REPORT (MYREPORT), VARIANT (QV_VARIANT), ROWS_PER_RECORD (1),FIELD_DELIMITER_POSITIONS (0, 11, 16, 27, 40, 48, 56, 65, 96, 113, 142, 153), FIELD_START_POSITIONS (194, 195, 204, 205),SKIP (T (1)), HEADER (P (0, "!Header !")));

Finally, You need to remove the delimiter from these in your script:

PurgeChar([Field12_ThisField],’!’) as [Field12_ThisField]

Hope it helps.

Re: Problem in SAP report Data extraction through 5.50 connector

Tue, 26 Feb 2013 22:06:00 GMT

I see that his is an old post, but for anyone who still needs a suggestion --- I had the same problem until I realized that when you are omitting the rows that you don't want, you have to hit the Apply button for each type of row. That is, if you don't want rows with the type 1, select that row, click the box that says to omit all rows of that type, then press Apply. Then go to the next type, select it, and press Apply. Don't wait until you have selected all of the rows to omit.

You can tell if this is working when you see the lines disappear in the lower window as you hit the Apply button.

Once it figured this out, all of the columns came out the way they should, and QlikView recognized the delimiter.

Re: Problem in SAP report Data extraction through 5.50 connector

julian_rodriguez — Wed, 04 Sep 2013 20:39:27 GMT

Hello, I'm facing a similar problem:

When the widht of the columns is different from one day to the another, the sentence FIELD_START_POSITIONS is not useful, because the script can't find the field.

How can I determine the column's width dinamically?

Thanks

Re: Problem in SAP report Data extraction through 5.50 connector

Fri, 11 Oct 2013 16:48:17 GMT

Julian,

I am facing the same problem as you were. Did you find any solution to this? I will appreciate if you can please share. Thanks!

Best regards,

Sid