SAP BO Interview question: What are the difficulties you face while developing report?

-
If you know all the features of webi and universe, you may think that you generally don't feel any difficulty as you know all the features. But this question is not about features but real reporting issues that arise with reports.

This is a interview question panel ask to understand your overall experience. If you have written particular years of experience, your answer to this question should give overall idea to them about the complexity of the work you have done.

Below are top two issues people generally get while working on report
1) Report is taking too much time to run
The report which you have developed on Universe may sometime take more time than expected. You need to explain here the performance tunning techniques you apply to solve the performance issues of report on webi , universe and database level.
2) Traps in the Universe
You may be get inflated results due to traps i.e. fan trap or chasm trap. This can be avoided if you have done proper universe designing to resolve these traps. Explain various trap resolving techniques with examples.

You can add more points based on your experience. Always give a simple and good example of any topic you explain. Good examples make good impression about clarity of your concepts.
Be example ready:
Prepare for examples of each topic before you attend interview. This will give you confidence in front of panel. You will not need to take time to think about examples on the fly which many times leads to messed up answers.

Happy learning!

Comments

Post a Comment

Popular posts from this blog

SAP BO Universe Performance tunning guidelines

-
Below are Universe performance tuning guidelines : These guidelines need to followed with Webi performance tuning guidelines given separately on this blog to get good performance reports. • Always use aggregate functions i.e.  Sum, max, min etc with measure objects. • Set the proper query limits at the universe, especially “Limit size of result set to” & “Limit execution time to”. Setting the right parameters will result in a good universe by performance wise • Create aggregated tables for reports taking too much time to execute due to huge data set in underline tables. • List of values: Create LOV’s on small lookup/master tables instead of actual fact table. Avoid LOV on measure and date objects. Remove LOV from non required objects i.e. keep LOV on objects which are going to be used in filters. • Use conditional objects/filters on Universe level to filter out non required data from universe level instead of reports • Push complex calculation of object...
Read more

Oracle to SAP HANA Date Conversions

-
Are you migrating your reports and dashboards from Oracle to SAP HANA?  Below are some ready to use date conversion SQL formulas which would save your significant amount of time. Please note that I have considered Financial year from 1-April to 31 March for year calculations. Also, number of days Calculations are considered till previous day. 1)   Current Financial year start e.g. 1-Apr-2017  ADD_MONTHS(ADD_DAYS(CURRENT_DATE, DAYOFYEAR(CURRENT_DATE) * -1 + 1), 3) 2)  Previous Financial Year start  ADD_YEARS(ADD_MONTHS(ADD_DAYS(CURRENT_DATE, DAYOFYEAR(CURRENT_DATE) * -1 + 1), 3), -1)  3) First date of current Month   ADD_DAYS(LAST_DAY(ADD_MONTHS(CURRENT_DATE, -1)), 1)   4)First date of current Month Previous year   Add_months(ADD_DAYS(LAST_DAY(ADD_MONTHS(CURRENT_DATE, -1)), 1), -12) 5)Number of days till date This Financial year  DAYS_BETWEEN(ADD_MONTHS(ADD_DAYS(CURRENT_DATE, DAYOFYEA...
Read more

SAP BO Universe Best Practice check list

-
Below are best practice guidelines for Universe development • Universe Name & Universe Description should be defined with proper Business Name and description in the Universe properties. • Class name should be started in INIT cap. • Objects name should be started in INIT cap. • Object should be placed in alphabetical order in the class. • Measure Objects in any class should be placed after the dimensions/detail objects. • Always define every object with meaningful description so that it helps user easily understand the purpose of it which avoids going through heavy documentation. • Measure objects should be created with aggregate functions like sum, max, min etc. This will ensure that only required aggregated data is returned to reports instead of whole set of raw data. • Create the context with proper business logic names. It will help you to find out what context is used in a particular report. • Always place any derived tables or isolated tables down ...
Read more