Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
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
Did you try to check you connector user authorizations?
Please attached the SAP connector log, it may give some clues
2014-09-03 20:07:13 | Progress | Connected to SAP with C:\Program Files\Common Files\QlikTech\Custom Data\QvSAPConnector\QvSAPOLAPConnector.dll 5.7 SR1, 10958 |
2014-09-03 20:07:13 | Progress | Log: 1 |
2014-09-03 20:07:13 | Progress | Logpath: |
2014-09-03 20:07:13 | Progress | LogFile: QvSAPOLAPConnector |
2014-09-03 20:07:13 | Progress | Connected |
2014-09-03 20:07:13 | Progress | Creation of function OCS_GET_SYSTEM_INFO returned after 00:00:00 |
2014-09-03 20:07:13 | Progress | SystemVersion is 701. Support pack level is 0008 |
2014-09-03 20:07:14 | Progress | Statement is: SELECT PSEUDOMDX D ( DIMENSIONS ( [0MATERIAL] (), [0CALWEEK] ()), MEASURES ( [0MEASURES0000000000000000].[ZSTOCK0000000000000000000]), FROM ($ZFRE_C01)) |
2014-09-03 20:07:14 | Progress | GlobalOptions: m_TryWithoutSlicing - Yes |
2014-09-03 20:07:14 | Progress | GlobalOptions: m_OptimizeByReducingOnCharacteristic - No |
2014-09-03 20:07:14 | Progress | Creation of function BAPI_MDPROVIDER_GET_DIMENSIONS returned after 00:00:00 |
2014-09-03 20:07:14 | Progress | BAPI_MDPROVIDER_GET_DIMENSIONS returned after 00:00:00 |
2014-09-03 20:07:14 | Progress | Creation of function BAPI_MDPROVIDER_GET_DIMENSIONS returned after 00:00:00 |
2014-09-03 20:07:14 | Progress | BAPI_MDPROVIDER_GET_DIMENSIONS returned after 00:00:00 |
2014-09-03 20:07:15 | Progress | Creation of function BAPI_CUBE_GETDETAIL returned after 00:00:01 |
2014-09-03 20:07:15 | Progress | BAPI_CUBE_GETDETAIL returned after 00:00:00 |
2014-09-03 20:07:15 | Progress | BAPI_CUBE_GETDETAIL returned 20 rows in DIMENSIONINFOOBJECTS |
2014-09-03 20:07:16 | Progress | Creation of function BAPI_CUBE_GETLIST returned after 00:00:01 |
2014-09-03 20:07:16 | Progress | BAPI_CUBE_GETLIST returned 29 rows in INFOCUBELIST |
2014-09-03 20:07:16 | Trace | Cube Type is: B |
2014-09-03 20:07:16 | Progress | Creation of function BAPI_MDPROVIDER_GET_LEVELS returned after 00:00:00 |
2014-09-03 20:07:16 | Progress | Creation of function BAPI_MDPROVIDER_GET_LEVELS returned after 00:00:00 |
2014-09-03 20:07:16 | Progress | Creation of function SRTT_GET_TABLE_SIZE_RFC returned after 00:00:00 |
2014-09-03 20:07:17 | Progress | Creation of function BAPI_MDPROVIDER_GET_MEASURES returned after 00:00:01 |
2014-09-03 20:07:17 | Progress | BAPI_MDPROVIDER_GET_MEASURES returned after 00:00:00 |
2014-09-03 20:07:17 | Trace | Characteristic: [0MATERIAL], Dimension: ZFRE_C012 |
2014-09-03 20:07:17 | Trace | Time Characteristic: [0CALWEEK], Dimension: ZFRE_C01T, Key for seperate load: [0CALWEEK] |
2014-09-03 20:07:17 | Progress | Creation of function RSR_MDX_CREATE_OBJECT returned after 00:00:00 |
2014-09-03 20:07:17 | Trace | Checking syntax for: SELECT NON EMPTY {DISTINCT (DESCENDANTS ([0MATERIAL].[All],[0MATERIAL].[LEVEL00],AFTER))} ON AXIS(0) FROM [$ZFRE_C01] |
2014-09-03 20:07:17 | Progress | Creation of function BAPI_MDDATASET_CHECK_SYNTAX returned after 00:00:00 |
2014-09-03 20:07:47 | Error | .[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:47 | Progress | SELECT NON EMPTY {DISTINCT (DESCENDANTS ([0MATERIAL].[All],[0MATERIAL].[LEVEL00],AFTER))} ON AXIS(0) FROM [$ZFRE_C01] |
2014-09-03 20:07:47 | Progress | Creation of function RSR_MDX_GET_AXIS_DATA returned after 00:00:00 |
2014-09-03 20:07:47 | Progress | RSR_MDX_GET_AXIS_DATA returned after 00:00:00 |
2014-09-03 20:07:47 | Progress | RSR_MDX_GET_AXIS_DATA returned 0 rows in MNDTRY_PRPTYS |
2014-09-03 20:07:47 | Progress | RSR_MDX_GET_AXIS_DATA returned 0 rows in OPTION_PRPTYS_KEYS |
2014-09-03 20:07:47 | Progress | RSR_MDX_GET_AXIS_DATA returned 0 rows in OPTION_PRPTYS_VALS |
2014-09-03 20:07:47 | Progress | Creation of function RSR_MDX_CREATE_OBJECT returned after 00:00:00 |
2014-09-03 20:07:47 | Trace | Checking syntax for: SELECT NON EMPTY {DISTINCT (DESCENDANTS ([0CALWEEK].[All],[0CALWEEK].[LEVEL00],AFTER))} ON AXIS(0) FROM [$ZFRE_C01] |
2014-09-03 20:07:47 | Progress | Creation of function BAPI_MDDATASET_CHECK_SYNTAX returned after 00:00:00 |
2014-09-03 20:08:12 | Error | .[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:12 | Progress | SELECT NON EMPTY {DISTINCT (DESCENDANTS ([0CALWEEK].[All],[0CALWEEK].[LEVEL00],AFTER))} ON AXIS(0) FROM [$ZFRE_C01] |
2014-09-03 20:08:12 | Progress | Creation of function RSR_MDX_GET_AXIS_DATA returned after 00:00:00 |
2014-09-03 20:08:12 | Progress | RSR_MDX_GET_AXIS_DATA returned after 00:00:00 |
2014-09-03 20:08:12 | Progress | RSR_MDX_GET_AXIS_DATA returned 0 rows in MNDTRY_PRPTYS |
2014-09-03 20:08:12 | Progress | RSR_MDX_GET_AXIS_DATA returned 0 rows in OPTION_PRPTYS_KEYS |
2014-09-03 20:08:12 | Progress | RSR_MDX_GET_AXIS_DATA returned 0 rows in OPTION_PRPTYS_VALS |
2014-09-03 20:08:12 | Progress | Creation of function RSR_MDX_CREATE_OBJECT returned after 00:00:00 |
2014-09-03 20:08:12 | Trace | Checking 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:12 | Progress | Creation of function BAPI_MDDATASET_CHECK_SYNTAX returned after 00:00:00 |
2014-09-03 20:08:37 | Error | (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:37 | Progress | Disconnected |
Hi
I see that you're trying to extract data directly from an infocube (ZFRE_C01) - it may cause problems in cases of high volumes of data.
Did you try to extract data from a query that returns a limited number of records?
Thanks
Yaniv
Yes i have even attempted that unfortunately its does not work either.
Från: Yaniv Feldman
Skickat: den 5 september 2014 15:59
Till: Bradley Ryan Coyne
Ämne: Re: - QLIKVIEW SAP BW CUSTOM READ FAILURE
Qlik Community<http://community.qlik.com/>
QLIKVIEW SAP BW CUSTOM READ FAILURE
reply from Yaniv Feldman<http://community.qlik.com/people/yanivf?et=watches.email.thread> in QlikView Connector for SAP - View the full discussion<http://community.qlik.com/message/603010?et=watches.email.thread#603010>
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
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