1 Reply Latest reply on Apr 18, 2011 2:15 PM by WPaffhausen

    Error 7123 on successful drill through

    852598
      Good morning,

      I've noticed a strange error message on drill through. I work with HFM/FDM 11.1.1.3 and after foreign name update I'm able to drill through correctly.
      The issue is on error log that displays :

      ERROR:
      Code............................................. 7123
      Description...................................... SELECT vDataFact.PartitionKey, PartName, CatName, CatTarget, PeriodKey, PeriodDesc, DataView, AccountX, EntityX, ICPX, UD1X, UD2X, UD3X, UD4X, UD5X, UD6X, UD7X, UD8X, UD9X, UD10X, UD11X, UD12X, UD13X, UD14X, UD15X, UD16X, UD17X, UD18X, UD19X, UD20X, SUM(Case ChangeSign WHEN 0 THEN (Amount) WHEN 1 THEN (Amount * -1) Else (Amount) END) AS Amt From vDataFact Where (((CatTarget) = N'CONS') And ((PeriodTargetM) = N'December') And ((YearTarget) = N'2010') And ((CalcAcctType) > 0) And ((AccountX) = N'1B107A01') And ((EntityX) = N'P002') And ((ICPX IS NULL) or (ICPX = N'') or (upper(ICPX) = N'[ICP NONE]')) And ((upper(UD1X)) = N'CHI') And ((upper(UD2X)) = N'CO') And ((UD3X IS NULL) or (UD3X = N'') or (upper(UD3X) = N'[NONE]')) And ((UD4X IS NULL) or (UD4X = N'') or (upper(UD4X) = N'[NONE]')) And ((UD5X IS NULL) or (UD5X = N'') or (upper(UD5X) = N'[NONE]')) And ((UD6X IS NULL) or (UD6X = N'') or (upper(UD6X) = N'[NONE]')) And ((UD7X IS NULL) or (UD7X = N'') or (upper(UD7X) = N'[NONE]')) And ((UD8X IS NULL) or (UD8X = N'') or (upper(UD8X) = N'[NONE]')) And ((UD9X IS NULL) or (UD9X = N'') or (upper(UD9X) = N'[NONE]')) And ((UD10X IS NULL) or (UD10X = N'') or (upper(UD10X) = N'[NONE]')) And ((UD11X IS NULL) or (UD11X = N'') or (upper(UD11X) = N'[NONE]')) And ((UD12X IS NULL) or (UD12X = N'') or (upper(UD12X) = N'[NONE]')) And ((UD13X IS NULL) or (UD13X = N'') or (upper(UD13X) = N'[NONE]')) And ((UD14X IS NULL) or (UD14X = N'') or (upper(UD14X) = N'[NONE]')) And ((UD15X IS NULL) or (UD15X = N'') or (upper(UD15X) = N'[NONE]')) And ((UD16X IS NULL) or (UD16X = N'') or (upper(UD16X) = N'[NONE]')) And ((UD17X IS NULL) or (UD17X = N'') or (upper(UD17X) = N'[NONE]')) And ((UD18X IS NULL) or (UD18X = N'') or (upper(UD18X) = N'[NONE]')) And ((UD19X IS NULL) or (UD19X = N'') or (upper(UD19X) = N'[NONE]')) And ((UD20X IS NULL) or (UD20X = N'') or (upper(UD20X) = N'[NONE]')) ) GROUP BY vDataFact.PartitionKey, PartName, CatName, CatTarget, PeriodKey, PeriodDesc, Dataview, AccountX, EntityX, ICPX, UD1X, UD2X, UD3X, UD4X, UD5X, UD6X, UD7X, UD8X, UD9X, UD10X, UD11X, UD12X, UD13X, UD14X, UD15X, UD16X, UD17X, UD18X, UD19X, UD20X ORDER BY PartName
      Procedure........................................ JapaneseTesting

      IDENTIFICATION:
      User............................................. xxxx
      Computer Name.................................... xxxx
      App Name......................................... xxxx
      Client App....................................... WebClient

      CONNECTION:
      Provider......................................... SQLOLEDB
      Data Server...................................... xxxxx
      Database Name.................................... xxxxx
      Trusted Connect.................................. False
      Connect Status.. Connection Open

      GLOBALS:
      Location......................................... Sample
      Location ID...................................... 748
      Location Seg..................................... 2
      Category......................................... WLCat
      Category ID...................................... 12
      Period........................................... Dec - 2010
      Period ID........................................ 12/31/2010
      POV Local........................................ False
      Language......................................... 1033
      User Level....................................... 1
      All Partitions................................... True
      Is Auditor....................................... False


      even if my app works perfectly.
      My question: is this an application bug or some warning about potential wrong configuration?

      Thank you
      Francesco