6 Replies Latest reply: Sep 9, 2014 10:45 AM by Mats Olin RSS

    QLIKVIEW SAP BW CUSTOM READ FAILURE

    Bradley Coyne

      Hi.

       

      i am attempting to read out of SAP BW with Qlikview but am getting the following Error.

       

      Custom read failed

      Select PseudoMDX D (

       

      Any one else experienced this?

       

      i have opened MDX access to query up via Query Designer but still not working.

       

      Best

      Brad

        • Re: QLIKVIEW SAP BW CUSTOM READ FAILURE
          Yaniv Feldman

          Did you try to check you connector user authorizations?

          Please attached the SAP connector log, it may give some clues

            • Re: QLIKVIEW SAP BW CUSTOM READ FAILURE
              Bradley Coyne
              2014-09-03 20:07:13ProgressConnected to SAP with C:\Program Files\Common Files\QlikTech\Custom Data\QvSAPConnector\QvSAPOLAPConnector.dll 5.7 SR1, 10958
              2014-09-03 20:07:13ProgressLog: 1
              2014-09-03 20:07:13ProgressLogpath:
              2014-09-03 20:07:13ProgressLogFile: QvSAPOLAPConnector
              2014-09-03 20:07:13ProgressConnected
              2014-09-03 20:07:13ProgressCreation of function OCS_GET_SYSTEM_INFO returned after 00:00:00
              2014-09-03 20:07:13ProgressSystemVersion is 701. Support pack level is 0008
              2014-09-03 20:07:14ProgressStatement is: SELECT PSEUDOMDX D ( DIMENSIONS ( [0MATERIAL] (), [0CALWEEK] ()), MEASURES ( [0MEASURES0000000000000000].[ZSTOCK0000000000000000000]), FROM ($ZFRE_C01))
              2014-09-03 20:07:14ProgressGlobalOptions: m_TryWithoutSlicing - Yes
              2014-09-03 20:07:14ProgressGlobalOptions: m_OptimizeByReducingOnCharacteristic - No
              2014-09-03 20:07:14ProgressCreation of function BAPI_MDPROVIDER_GET_DIMENSIONS returned after 00:00:00
              2014-09-03 20:07:14ProgressBAPI_MDPROVIDER_GET_DIMENSIONS returned after 00:00:00
              2014-09-03 20:07:14ProgressCreation of function BAPI_MDPROVIDER_GET_DIMENSIONS returned after 00:00:00
              2014-09-03 20:07:14ProgressBAPI_MDPROVIDER_GET_DIMENSIONS returned after 00:00:00
              2014-09-03 20:07:15ProgressCreation of function BAPI_CUBE_GETDETAIL returned after 00:00:01
              2014-09-03 20:07:15ProgressBAPI_CUBE_GETDETAIL returned after 00:00:00
              2014-09-03 20:07:15ProgressBAPI_CUBE_GETDETAIL returned 20 rows in DIMENSIONINFOOBJECTS
              2014-09-03 20:07:16ProgressCreation of function BAPI_CUBE_GETLIST returned after 00:00:01
              2014-09-03 20:07:16ProgressBAPI_CUBE_GETLIST returned 29 rows in INFOCUBELIST
              2014-09-03 20:07:16TraceCube Type is: B
              2014-09-03 20:07:16ProgressCreation of function BAPI_MDPROVIDER_GET_LEVELS returned after 00:00:00
              2014-09-03 20:07:16ProgressCreation of function BAPI_MDPROVIDER_GET_LEVELS returned after 00:00:00
              2014-09-03 20:07:16ProgressCreation of function SRTT_GET_TABLE_SIZE_RFC returned after 00:00:00
              2014-09-03 20:07:17ProgressCreation of function BAPI_MDPROVIDER_GET_MEASURES returned after 00:00:01
              2014-09-03 20:07:17ProgressBAPI_MDPROVIDER_GET_MEASURES returned after 00:00:00
              2014-09-03 20:07:17TraceCharacteristic: [0MATERIAL], Dimension: ZFRE_C012
              2014-09-03 20:07:17TraceTime Characteristic: [0CALWEEK], Dimension: ZFRE_C01T, Key for seperate load: [0CALWEEK]
              2014-09-03 20:07:17ProgressCreation of function RSR_MDX_CREATE_OBJECT returned after 00:00:00
              2014-09-03 20:07:17TraceChecking syntax for: SELECT NON EMPTY {DISTINCT (DESCENDANTS ([0MATERIAL].[All],[0MATERIAL].[LEVEL00],AFTER))} ON AXIS(0) FROM [$ZFRE_C01]
              2014-09-03 20:07:17ProgressCreation of function BAPI_MDDATASET_CHECK_SYNTAX returned after 00:00:00
              2014-09-03 20:07:47Error.[LEVEL00],AFTER))} ON AXIS(0) FROM [$ZFRE_C01]

              resulted in the ErrorMessage:

              Error occurred when starting the parser: timeout during allocate / CPIC-CALL: 'ThSAPCMRCV'

              2014-09-03 20:07:47ProgressSELECT NON EMPTY {DISTINCT (DESCENDANTS ([0MATERIAL].[All],[0MATERIAL].[LEVEL00],AFTER))} ON AXIS(0) FROM [$ZFRE_C01]
              2014-09-03 20:07:47ProgressCreation of function RSR_MDX_GET_AXIS_DATA returned after 00:00:00
              2014-09-03 20:07:47ProgressRSR_MDX_GET_AXIS_DATA returned after 00:00:00
              2014-09-03 20:07:47ProgressRSR_MDX_GET_AXIS_DATA returned 0 rows in MNDTRY_PRPTYS
              2014-09-03 20:07:47ProgressRSR_MDX_GET_AXIS_DATA returned 0 rows in OPTION_PRPTYS_KEYS
              2014-09-03 20:07:47ProgressRSR_MDX_GET_AXIS_DATA returned 0 rows in OPTION_PRPTYS_VALS
              2014-09-03 20:07:47ProgressCreation of function RSR_MDX_CREATE_OBJECT returned after 00:00:00
              2014-09-03 20:07:47TraceChecking syntax for: SELECT NON EMPTY {DISTINCT (DESCENDANTS ([0CALWEEK].[All],[0CALWEEK].[LEVEL00],AFTER))} ON AXIS(0) FROM [$ZFRE_C01]
              2014-09-03 20:07:47ProgressCreation of function BAPI_MDDATASET_CHECK_SYNTAX returned after 00:00:00
              2014-09-03 20:08:12Error.[LEVEL00],AFTER))} ON AXIS(0) FROM [$ZFRE_C01]

              resulted in the ErrorMessage:

              Error occurred when starting the parser: timeout during allocate / CPIC-CALL: 'ThSAPCMRCV'

              2014-09-03 20:08:12ProgressSELECT NON EMPTY {DISTINCT (DESCENDANTS ([0CALWEEK].[All],[0CALWEEK].[LEVEL00],AFTER))} ON AXIS(0) FROM [$ZFRE_C01]
              2014-09-03 20:08:12ProgressCreation of function RSR_MDX_GET_AXIS_DATA returned after 00:00:00
              2014-09-03 20:08:12ProgressRSR_MDX_GET_AXIS_DATA returned after 00:00:00
              2014-09-03 20:08:12ProgressRSR_MDX_GET_AXIS_DATA returned 0 rows in MNDTRY_PRPTYS
              2014-09-03 20:08:12ProgressRSR_MDX_GET_AXIS_DATA returned 0 rows in OPTION_PRPTYS_KEYS
              2014-09-03 20:08:12ProgressRSR_MDX_GET_AXIS_DATA returned 0 rows in OPTION_PRPTYS_VALS
              2014-09-03 20:08:12ProgressCreation of function RSR_MDX_CREATE_OBJECT returned after 00:00:00
              2014-09-03 20:08:12TraceChecking syntax for: SELECT NON EMPTY SUBSET (

              Crossjoin(

                {Distinct(Descendants([0MATERIAL].[All],[0MATERIAL].[LEVEL00],AFTER))},

                {Distinct(Descendants([0CALWEEK].[All],[0CALWEEK].[LEVEL00],AFTER))}), 0, 1333333) ON AXIS(0),

              {[0MEASURES0000000000000000].[ZSTOCK0000000000000000000]} ON AXIS(1)

              FROM [$ZFRE_C01]

               

               

              2014-09-03 20:08:12ProgressCreation of function BAPI_MDDATASET_CHECK_SYNTAX returned after 00:00:00
              2014-09-03 20:08:37Error(1)

              FROM [$ZFRE_C01]

               

               

              resulted in the ErrorMessage:

              Error occurred when starting the parser: timeout during allocate / CPIC-CALL: 'ThSAPCMRCV'

              2014-09-03 20:18:37ProgressDisconnected
            • Re: QLIKVIEW SAP BW CUSTOM READ FAILURE
              Bradley Coyne

              thank you for your responses.

               

              the issue is now solved. There is a setting in SAP BW Trans sm59. there you can check your MDX parser settings. Unicode or Non Unicode. make the appropriate parameter setting change and all went well.

               

              Best

              Brad

              • Re: QLIKVIEW SAP BW CUSTOM READ FAILURE
                Mats Olin

                The OLAP Connector was originally designed to extract data from Queries on InfoCubes, it seems like you are accessing the cube/MP directly ('$ZFRE_C01'). In the selection screen for the OLAP Connector, first select InfoProvider (in your case ZFRE_C01) and then the appropriate query.

                 

                Also, removing the D in 'PseudoMDX  D (' triggers the auto-optimizer in QV which works fine for queries on infocubes but not for queries on other type of InfoProviders (the number of returned rows and the data in them can be wrong).

                 

                / Mats