SAP BO Web intelligence reports best practice check list

-
Below are best practice guidelines for development of webi reports:

• Variable names should start with “V_” or “Var_”.

• Avoid creation of variables/formulas (in tool bar) without naming them.

• Name the report tabs and queries with meaningful names and tab / query name should start with Capital letters. Example, Have DLY (daily), MTH (Monthly) and QTR (Quarterly) in end of report name to identify the report frequency easily. Example, “DWBI SALSE REPORT MTH”.

• Follow the same hierarchy for Condition (objects) as classes/objects. It helps user locate the conditions quicker and makes condition objects more meaningful as well.

• In query panel, pulling the Dimension objects followed by detail objects before selecting Measures help user locate the objects easily (it avoids scrolling down in search of any objects. This helps more in case of queries built with more than 25 objects).

• Purging the data before saving it to the repository saves a lot of space on servers; It also helps in retrieving/opening the documents faster unless the reports have the option, “Refresh on open”.

• While working on a large data avoid using the report view instead use “view structure” mode of display as it is going to eliminate some complexities in data rendering and simply it saves time.

• Having report Header (Company Logo and name of the report), Footer (Page Number, Name of the tab and any comments of the tab, etc.,) would provide more better look & feel of the report.

• Export / Save the report with result mode and don’t export / save the report in repository with structure mode.

• It is always good to have a handy report template in any BI tools. Template that is already formatted for page orientations, paper size, numbers, text fields, block layout, headers, footers, execution time stamp, page no and back ground logo or image will save lot of time of development. You just need to fetch the objects required for your specific requirement.

• Provide "Input control" filters on the report so that users can do multi way analysis after report is refreshed.

• ForEach and ForAll should only be used when really necessary. Use IN when possible instead

• Where operator can also take longer to process behind the scenes. Using  If… Then… Else may be better.

• Factorizing variables reduces overhead for calculation engine. For example:
v_Sales= [MeasureA] + [MeasureB]
v_SalesEst= [v_Sales] + [MeasureC]

• Use “Save for ALL Users” option to remove the document security from the WEBI files. It can used when we physically transfer the *.wid files from machine to machine, say for example QA to PROD.

Above points should be followed with Webi performance tuning guidelines given separately on this blog to get presentable and good performance reports.

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