Hi
btree/bitmap index and scenarios
By default the index created for info cube in bitmap index.
When you make any dimension as high cordinolity, then system will create btree indexes to improves data retrieval.
Regards,
Venkatesh
Conditions - You want to get the top 10 customers, you can use condition to get the same. done during the execution, before displayign the data. last step in the report execution.
Filters - You can filter only particular plant, customer etc. will be done before query execution, kind of starting point for qery execution.
Btree / Bit map - in addition to Venkatesh said - Bit Map is read optimized and B Tree is write optimized.
Reconstruction - used in 3.x flow. if a request got deleted by request you can retriev it. Go to reconstruction tab and select the request and do reconstruction.
Repair - I guess you are asking repair full request, if it so, it is a way to pull the data from R3. with some selection that can be defined at the info package for example you found one purchase order with some incorrect data, what you do is delete selectively the purchase order from the system and do full repail request. You can define the same at info provider level.
Document update - you change a Purchase order from Me22n, the document will get update in the r/3 backend table EKKO EKPO etc. Statistical update is from the R/3 reporting table perspective, these are LIS tables.
