6 Replies Latest reply: Apr 8, 2011 3:08 AM by s j RSS

    SAP Connector APO

    Sravan Puppala

      HI Guys,

      I am connecting with the following connector from Qlikview to SAP-APO

      error loading image

      I did not see anything like this before. I get the connect string etc like this

      CUSTOMCONNECT TO "Provider=QvSAPConnector;ASHOST=10.232.57.54;SYSNR=00;CLIENT=100;KeepCasing=1;NullDate=1;XUserId=GAXBQYRNJbaMXUVMXTTA;XPassword=QRMVRUZNJDdADYEGBC;";

      I try to load only one table t000 which has only 4 data records.

      In SAP side with the transaction /n/qtqvc/sql when I try I see only 4 records

      when I try in Qlikview, it goes on and on and on and never comes to end. I see now more than 500,000 and it is still goin on. Not only this table but any table i am loading is never ending :-(

      Any Idea what Is the problem. I never saw something like this.

      Thanks

      Sravan

       

        • SAP Connector APO
          Rakesh Mehta

          Hi Sravan,

          I had the same problem with BW where version was 3.5 or something. Working with QlikView support, they gave me a parameter to put in the connection string - something I remember like: LeafNotSupported=1. But this was BW Cube and you are concerned with APO table, so I am sure this will not help you.

          What is your APO's BASIS release? You may want to upgrade to 5.5 and see hot it goes.

          I would go ahead and open a ticket to QlikView for this problem anyway in parallel.

          Hope this helps.

          Rakesh

            • SAP Connector APO
              Sravan Puppala

              Hi Rakesh,

              Thanks for the answer.

              My APO's Basis Release is 701. I have the transports of SAP Connector 5.3 in the APO System.

              Normal 0 21 false false false DE X-NONE X-NONE

              1) QT2K900238 (Data extraction)

              2) QT2K900101 (User profile)

              and I have the SAP connector 5.4 in the Qlikview Server, I downloaded and checked whether 5.5 works but it does not work even for Test connection.


              Due you mean to install the transports of 5.5 in SAP?

              I will open a ticket with Qliktech on this Regard.

              Regards

              Sravan

              PS: I have Qlikview Desktop clients 9.0.7646.9 and 9.0.7502.8 On the Servers.

               

                • SAP Connector APO
                  s j

                  Are you sure that you are using same qlikview connector client version for which you transported in SAP R/3 ?.

                   

                    • SAP Connector APO
                      Sravan Puppala

                      Yes the Problem is the compatibility of SAP Connector and the Transports. I switched the SAP Connector to 5.3 and it works. My problem is that the SAP Systems(Other than APO) work with SAP connector5.4 and not with SAP 5.3

                      For a common connector 5.5 I need to change the transports in SAP (APO) and in other SAP Systems. Otherwise I cannot maintain one common connector in the Server.

                       

                      Regards

                      Sravan

                    • SAP Connector APO
                      Rakesh Mehta

                      Yes, I suggested to upgrade connector to 5.5, not sure it will fix the problem or not.

                      I am sure you have done all the "obvious" troubleshooting, so I guess your best bet to go to QV support and save your time and frustrations.

                      Rakesh

                        • SAP Connector APO
                          s j

                          I suggest the same and request to go with QVC 5.5 SR3

                          Bugs corrected in version - 5.5 SR3


                          SQL Connector:
                          • New parameter for Connectionstring; RemoveAllBlanks=0/1 default=0. If used gives possibility
                          to get "old" behavior where fields in SAP containing only Blank characters got trimmed. The
                          default behavior leaves one Blank character to be able to distinguish from Null fields.
                          OLAP Connector:
                          • Queries with only Characteristics and no Key figures gave no result in BW systems without
                          EHP1.