If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

QE-DEF- Issues after changing Package

Started by charon, 14 May 2012 05:39:44 PM

Previous topic - Next topic

charon

HI Gurus,

its been a while, and i still have not mastered cognos fully ;)
Thats the situation...there are 3 reports running on 3 packages, once central package and two smaller ones, based on the central package but still have additional measures.

I am working on consolidating the packages, so all reports run on the central big one.
After changing the package for the reports, changing all paths and references, change the filter expressions and data items and fill in the missing data items 4 of 5 queries run well of the report, but the main query (with about 50 created calculations/ data items) throws me some errors i can not figure out on mnyself

Validatin the report -> QE-DEF-0459 cclException 'invalid forced movement of value to memberset, member, hierarchy, level for 1  (followed by an case when expression of an data item
also, RSV-VAL-0004 for all 50 data items.

Running the report -> UDA-SQL-0114 'the cursor for the operation sqlopenstatus is not activ

There is a data item which holds a parameter, filled in a promped with some static values/ descriptions. Its a way to let the user prompt against several dimension to sort a crosstab (data item "rows", you can choose for country, status and so on..works well with the old package)
Validatin this data item "rows" throws me -> QE-DEF-0260 'case when caption....'

Usualy, i write that any hints are not that important because i just want to learn cognos. Well..this time it IS urgent, i need to figure this out asap. I appreciate any hints, clues or idead..
Thank you all in advance, cheerz charon :P

tjohnson3050

Two things, the error for all 50 items should go away when you fix the first issue.  The main error message looks like your case statement is mixing values and hierarchy functions incorrectly.  Post the whole case statement and we can evaluate further.

charon

hi tjohnson,

its as uve described it...mixed up the concepts and also the errors vanished after i was able 2 focus on the data item which threw the error.
still, ty very much for searching for an solution for such an old post...appreciate it :=)
thx and cheerz :P

tjohnson3050

I was having trouble getting to sleep last night, I thought browsing through some old posts might help :)