Developer Forum

Hi all,

I have created a Microsoft .NET windows application (in C#) which reads
and displays data directly from SAP BW using the SAP BW OleDb provider.
The application simply connects to the SAP BW system and executes
against it a very simple MDX query :

SELECT
[0CALMONTH2].[LEVEL01].Members ON COLUMNS,
[ZCOUNTRY].[LEVEL01].Members ON ROWS
FROM [$ZMYCUBE]
WHERE [Measures].[ZSALES]

The application returns expected results when the MDX query is executed
against a SAP BW 3.1. But, if the MDX query is executed against a SAP
BW 3.5 containing the very same cube, there is a row shift on the
dimension column (the first column). Here is the detailed illustration
of this unexpected behavior:

Here is the expected results, which is correctly obtained in my .NET
application using the SAP BW OleDb provider connecting to a SAP BW 3.1
system :

Jan Fev Mar
----------------------------
DE 60 80 85
FR 120 100 120
UK 140 110 110

And here is the obtained results in my .NET application using the same
SAP BW OleDb provider, connecting to a SAP BW 3.5 system :

Jan Fev Mar
----------------------------
FR 60 80 85
UK 120 100 120
140 110 110

The "DE" country has disappeared and other countries have been shifted
1 row up ! But note that measures values for columns "Jan", "Fev" and
"Mar", didn't move.

- I made this test using many different versions of the SAP BW OleDb
provider for Olap, and I encountered the same problem with all of them.
- Plus that, I tested the MDX query using the MDXTEST tool on both 3.1
and 3.5 versions of SAP BW and both systems returned correct and
expected results.
- I also could reproduce the bug on different SAP BW 3.5 systems.

I think SAP BW 3.5 doesn't return the same structure of data results,
thus making the SAP BW OleDb provider interpreting incorrectly. Did
anyone had this problem and is there a patch which could fix it? Thanks
in advance.

Best regards.

Julien,

this can be a bug in the ODBO driver of SAP. This is not at all unusual.
Post your problem to the OSS. Another Patchlevel might solve your issue.

Kind regards,

Joerg
hotmail

"Julien Cheyssial" < XXXX@XXXXX.COM > schrieb im Newsbeitrag

I fixed the problem by applying OSS Note 828949