Qlik Community

QlikView Scripting

Discussion Board for collaboration on QlikView Scripting.

Announcements

Breathe easy -- you now have more time to plan your next steps with Qlik!
QlikView 11.2 Extended Support is now valid through December 31, 2020. Click here for more information.

Not applicable

OLAP Connector to Qlikview- No Cubes seen

Hello Guys,

After connecting with the OLAP connector, I can open this window but I dont see any Infocubes here. I allotted all the Authorisations as in the Document. Any suggestions

error loading image

Tags (2)
1 Solution

Accepted Solutions
suniljain
Honored Contributor

OLAP Connector to Qlikview- No Cubes seen

Dear Sravan,

Pls Check SAP Connection where it is successful or not.

Regards

Sunil

6 Replies
suniljain
Honored Contributor

OLAP Connector to Qlikview- No Cubes seen

Dear Sravan,

Pls Check SAP Connection where it is successful or not.

Regards

Sunil

Not applicable

OLAP Connector to Qlikview- No Cubes seen

I got it correct and now I have the Problem that the script is not running. After switch on the Log it shows the following. Any Ideas??


2010-08-25 15:09:10 Progress Connected to SAP with C:\Program Files\Common Files\QlikTech\Custom Data\QvSAPConnector\QvSAPOLAPConnector.DLL 5, 3, 7758 IR
2010-08-25 15:09:10 Progress Statement is: SELECT PSEUDOMDX ( DIMENSIONS ( [9AACTNAME] (), [9ALOCFROM] (), [9ALOCNO] (), [9ALOCTO] (), [9AMATNR] (), [9APPMNAME] (), [9ARNAME] (), [9ATRNAME] (), [9ATTYPE] (), [9AVERSION] (), [0CALMONTH] (), [0CALWEEK] (), [0UNIT] ()), MEASURES ( [0MEASURES0000000000000000].[9ADMDDI000000000000000000], [0MEASURES0000000000000000].[9APSHIP000000000000000000]), FROM ($Y01_SA_01))
2010-08-25 15:09:10 Progress Disconnected
2010-08-25 15:09:10 Progress Connected
2010-08-25 15:09:47 Error SELECT NON EMPTY {Distinct(Descendants([9AACTNAME].ALLMEMBERS,1,LEAVES))}
ON AXIS(0),
{[0MEASURES0000000000000000].[9ADMDDI000000000000000000],[0MEASURES0000000000000000].[9APSHIP000000000000000000]} ON AXIS(1)
FROM [$Y01_SA_01]
resulted in the ErrorMessage:
Fehler beim Start des Parser: timeout during allocate / CPIC-CALL: 'ThSAPCMRCV'
2010-08-25 15:10:15 Progress Disconnected


Not applicable

OLAP Connector to Qlikview- No Cubes seen

Anyone has seen this type of Error??

suniljain
Honored Contributor

OLAP Connector to Qlikview- No Cubes seen

There is error in Select Query and Because of that SAP connector is unable to give specific outcome in decided time.

Pls Try on Cube which have single table . Whether it is working or not.

disqr_rm
Valued Contributor III

OLAP Connector to Qlikview- No Cubes seen

Hi Sravan,

How many records are you expecting out of this query?

It seems you are getting timeout error. This should be generating a system dump in BW. Check ST22 and see if that system dump information can point you to any direction.

By the way which BW version are you on?

Rakesh

Not applicable

OLAP Connector to Qlikview- No Cubes seen

Hi folks,

the thread is old,

but look at the following link: (it's german :-))

The problem is in SAP BW. Follow SAP note 1032461

cheers

Martin

http://forum.cubeware.de/forenuebersicht/forum/beitraege/cubeware_cockpit_v6pro_free_limited/sap_bw_...

This ist the instruction copied:

Fehlermeldung:

"Error in SAPBW_Iterator:Smiley Surprisedpen: Fehler beim Start des Parser:timeout during allocate /CPIC-CALL:´ThSAPCMRCV´"

Hintergrund:

Das Cubeware Cockpit nutzt für den Zugriff auf SAP BW die Schnittstelle OLAP BAPI. Die Anfragen, welche das Cockpit an SAP BW stellt laufen über den MDX-Prozessor von SAP BW, welcher dem OLAP Prozesser vorgeschaltet ist. Der MDX-Prozessor ist eine 32-Bit Non-Unicode Komponente auf dem BW Applikationsserver, welche die RFC-Bibliothek librfc32 ebenfalls als Non-Unicode und 32-Bit Version benötigt. Tritt der oben beschriebene Fehler bei Ihnen auf, so fehlt diese Bibliothek auf Ihrem BW Server.

Lösung:

Die Behebung des Fehlers muss SAP BW seitig durch das Einspielen der RFC-Bibliothek librfc32 vorgenommen werden. Die genau Vorgehensweise wird über denSAP Note 1032461 beschrieben.