on 08-01-2006 7:06 AM
Hi all,
I want to know about calculated request id in the roll-up.What is the purpose of this option and where exatly we use this option.
Thank you,
RD
Hi,
You can select this indicator if you want to calculate a request ID. During the runtime it is determined whether and to which calculated request ID the data of the request is rolled up in the aggregate
With calculated request IDs you can
either specify the number of requests that are not rolled up in the aggregate,
or specify that only requests older than XXX days are rolled up in the aggregate.
To make the entries for a calculation select Calculated Request ID.
Hope this helps you....
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi ,
Thank you very much now i under stood.I have checked how it will works.
Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Thank you very much now i under stood.I have checked how it will works.
Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Re: what is calculated request id in roll-up?
Posted: Aug 1, 2006 2:39 AM Reply E-mail this post
Hi AVR,
Thank you for giving the reply.But i need more clear.As you said from my point of view if there are 4 request are not roll-up to the aggregare.Then how we calculate on these 4 requests and it will effect in the aggregate.Please give me one example.
Thank you
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
If you have 4 requests, and if you enter the number days for which the requests should be rolled up, after each load a check is made to see wheteher since the load there is a request older than the days specified. The requests are only then aggregated or compressed if they are older.
In Second option, if you enter how many requests should always be kept not aggregated or compressed in the InfoCube, the last requests in the InfoCube are therefore not aggregated or compressed.
After every load a check is made to see whether more than 4 requests are not aggregated or commpressed in the InfoCube. Surplus requests are then aggregated or compressed.
Hope this helps you....
User | Count |
---|---|
91 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.