1. Difference between Hierarchy and Hierarchy node.

2. Selection variables are used for restriction.

3. Hierarchy Variables source a part of hierarchy- yes
4. Data Source can have multiple initializations – yes
5. Mail receipts can be used in the process chain- true
6. BWA fetches queries from the DB index
7. Changes to DTP settings are allowed only if we have full load
8. Key figures can be hidden in reports – yes
9. Queries can be created on
Multiprovider
Virtual provider
DSO
Cube
All the above
10. Key fields in DSO are 16

11. Using DB utility you can

Activate and adjust DB statistics
Display…
Both

12. Filters on display attributes cannot be possible – True

13. Type D is Date format

14. Which cannot be activated without identification of info object involved –
Info source
Multiprovider
Info object

15. Description of the query is not changeable- False

16. Additional DSO indexes can be created- true
17. Primary structure of start routine consists of- source structure
18. Multiprovider navigation attributes are not defines automatically based on available
target navigational attribute. False
19. Info package is first step of full load process of DS- false
20. Transaction code for global class - /se24
21. Request can be deleted from infocube compressed – No
22. Recovery of ds 3x is possible from 7.o only if with export option is choosen.
 23. Which is not exception aggregation
Summation
Min
Max
Variants
Median

24. SID table for ZCost is /BIC/SZCost

25. Warning messages can be suppressed on queries- yes
26. Info set uses primary technical names of characteristics- true
27. Internal table types- 3 standard, sorted and hashed
28. Int8 is not a valid data type –no
29. DSO can have aggregation property – yes
30. Quantity is units and amount is currency
31. Loading data from dso to info cube is delta then it gets data from change log file
32. Bi statistics are to improve loading an query performance
33. In cube, dimension ids are used in fact table for dimension defined as line item
dimension- no
34. We can add indexes only to cube
35. Full repair request is possible for DSO not for cube.

after employing a DTP for loading an object, changes to DTP settings are allowed only if the prev load is__full
In general, the best practice to develop queries on multiprovider
in a scenario of data flow consisting of data loaded from a DSO to Infocube. Delta records loaded to the
infocube are from the following DSO table-
automatic generation of time dependent master data tables are known as time dependent hierarchies
A DTP can be used in multiple process chains – yes
Full Repair request is associated with which of the following object – dso
Business ware house accelerator creates indexes on which of the following objects – DB index
Datasources can have multiple init initialization infopackages – yes
Multiprovider can consists of data sources –no
what are the two fact tables available in an infocube – E and F
key fig aggregation functionality is handled in the system –yes
Deleted DSO request reconstruction is __possible
additional customer made indexes can be defined for Multi Providers – true
which of the following key figure data type has unit attached to it- quantity and amount