Query building question

You may also want to look at using structures to handle common (even the basic) key figure and calc kf usages so that they just need to grab the structure and all their KF's and CKF's are dropped in place and ready to go.

I also try with new cubes and such try and create a set of standard variables against most of the characteristics available to have as much "<i>ready to go</i>" for the developers to build queries against.

I always have the first query built something which contains just about everything in a query (<b>a "ktichen sink" query if you will</b>). - This is never published to the end users, but is available to developers and admins as a catch all query they can use to verify data, check out different bits of infromation as needed.

- Stephen

There is no way to do what you propose (although it would be nice).

However, what we generally do is provide a "master" query for each InfoProvider that already has most or all of the fields of interest defined with appropriate filters, variables, etc.

All the user then has to do is to modify that query to suit his/her needs and do a Save As...

Hope this helps...

Bob

Hi Allan,

It is not possible because each query is based on a set of charcteristics and key figures.They are not standard set.They differ from cube to cube.So, there is no standard set.But you can use RRI to jump from a query to a query(BEX or SAP) or any sap transaction,i am pretty sure that it is not a solution for your quetion.

Ravi.