Business Intelligence with SAP Business Objects 4.3

Business Objects Designer Basic Rules:  Keep the number of objects to 700 - 800  Larger universes will require more memory to use - This means more Java runtime memory allocated for Web Intelligence users  Reduce complexity where possible   Focus your universe efforts  Test  how this universe will work   Implement this universe as one piece of an overall strategic solution  Minimize your maintenance Classes are  group logically related business terms (objects) together. Best practices for classes include: - Naming conventions - Descriptions - Layout - Nesting limits (classes within classes) Layout and Organization - Limit to 20 – 25 objects per class - This will reduce scrolling through long lists - Use subclasses and detail objects  Determine how objects will be listed:    Most commonly used is most popular or  Alternatives: ...

Best practices for using delegated measures  Use a delegated measure when report users manipulate the measures in reports. When they only need to refresh, view, and print their reports, the calculation may be simpler to perform in the report. So use a delegated measure: -          to replace multiple query aggregates. -         on calculations that could give inaccurate results when calculated in the report (such as complex averages). -         for measures requiring division. When you create a delegated measure, make sure that you enter text to identify as such to users. You can do so in the Edit Properties dialog box for the measure in the Description box of the Definition tab. This ensures that report designers can quickly recognize a delegated measure when they glide their mouse over it in a query. Case in wich delegated measures must not to be used. Do not use delegated measures when you apply...

Here you will find some tips in order to improve your Business Object Universe: 1. In Universe design Un-necessary Tables, Classes, Objects and joins are to be remove. 2. Use Shortcut joins for query retriving fast. 3. Integrity Check. 4. Use Index awareness 5. Disable List of values for Measures and unncessary dimension Objects. 6. Partitioning the fact table can boost your query performance. 7. Keep the number of key figures low to increase the performance Performance Tuning in WebI: 1. Un-necessary Objects remove from Query Panel. 2. Limit the no of Rows for report level analysis and usage. 3. Use Query filters and report filters. 4. Array fetch size will be use as max. 5. Limited use of complex queries and Prompts. 6. Decrease the Creation of variables See also Universe best practises