Skip to Content

1.       Universe

1.    Quick Checks

·         Check If Universe version and release date has been updated properly in Universe definition.

·         Check the aggregate navigation properties for a newly added object/filter.

·         Check whether new tables/views joins are added in proper context.

2.    New View added to Universe.

2.1. Aggregate Views for Fact tables.

2.1.1.    Refresh the universe structure.

2.1.2.    Parse the Universe and check if there are any syntax or join errors.

2.1.3.    Cross verify the joins to check if all the tables have been joined.

2.1.4.    Check if cardinality has been set properly.

2.1.5.    Check if you need to apply any stubbing or self join.

2.1.6.    Check if all the joins have been included in relevant context.

2.1.7.    Verify all the join conditions by running few queries which use that join (e.g. To check join   condition between Sales Fact table and Customer table run a sample query which uses   same join condition which has been mentioned in universe and check if data is coming properly)

2.2. Dimension Views

2.2.1.    Refresh the universe structure.

2.2.2.    Parse the Universe and check if there are any syntax or join errors.

2.2.3.    Check if cardinality has been set properly.

2.2.4.    Check if you need to apply any stubbing or self join.

2.2.5.    Verify the join condition by running few queries which use that join (e.g. To check join condition between Sales Fact table and Customer table run a sample query which uses same join condition which has been mentioned in universe and check if data is coming properly)

2.3. Modifying Existing View.

2.3.1.    Refresh the universe structure.

2.3.2.    Parse the Universe and check if there are any syntax or join errors.

2.3.3.    Cross verify the joins with others views to check if all the tables have been joined (if adding     Week level aggregate view the verify it with month level views because most of the joins    will be same).

2.3.4.    Check if cardinality has been set properly.

2.3.5.    Check if you need to apply any stubbing or self join.

2.3.6.    Check if the new column displays in the table under designer.

2.4. New Object in Universe

2.4.1.    Parsing

2.4.1.1.Check the Object SQL if proper table is selected.

2.4.1.2.If this object exists at multiple level, check if the tables in @Agg_aware function are      arranged properly(i.e. in descending order).

2.4.1.3.Parse the Object.

2.4.1.4.Check if Object type is selected correctly (Measure/detail/dimension).

2.4.1.5.Check if LOV option is selected and “Export with Universe” option is unchecked.

2.4.1.6.If object is measure then,SQL should be preceded with proper aggregation function (i.e. Sum/Avg/Min/Max).

2.4.1.7.Under Properties tab select the appropriate aggregation from the drop down.

2.4.2.    Formatting

2.4.2.1.Right Click on Object and select “Object Format”

2.4.2.2.Check if correct format has been applied there i.e. If it’s a measure which contains number       of days then it’s format should be such that it does not show decimals.

2.4.2.3.Check for Other format options.

2.4.3.    Description

2.4.3.1.Check if Object description has been mentioned correctly.

2.4.4.    Incompatibility

2.4.4.1.As per the granularity of the object there should be a proper incompatibility with respect to various tables.

2.4.4.2.Click on Tools>Aggregate Navigation.

2.4.4.3.Select the table’s which are not compatible with newly added object and mark them incompatible with the object.

2.4.5.    Test Object in report.

2.4.5.1.Create a User ID with minimum rights.

2.4.5.2.Log on to Business Objects QA using that user ID and Pwd.

2.4.5.3.Drag newly created objects in data provider and run the report.

2.4.5.4.Report should run successfully.

3.    Modifying/Renaming existing Object in Universe

3.1.  Follow each step of 2.4 New Object in Universe i.e. from a to e.

3.2.  Login to business objects using the ID created in step 3.

3.2.1.    Open the report which already contains this object (pre modified version).

3.2.2.    Open the data provider and check if the original object has been automatically replaced       with modified object. Run the report.

3.2.3.    Report should run successfully with original object automatically getting replaced with         modified object.

4.    New Filter in Universe

4.1. Parsing

4.1.1.    Check the Filter SQL, if proper table is selected.

4.1.2.    Parse the Filter.

4.2. Description

4.2.1.    Check if Filter description has been mentioned correctly.

4.3. Incompatibility

4.3.1.    As per the granularity of the Filter there should be a proper incompatibility with respect to   various tables.

4.3.2.    Click on Tools>Aggregate Navigation.

4.3.3.    Select the table’s which are not compatible with newly added Filter and mark them incompatible with the Filter.

4.4. Test Object in report.

4.4.1.    Create a User ID with minimum rights.

4.4.2.    Log on to Business Objects QA using that user ID and Pwd.

4.4.3.    Drag newly created Filter in data provider with some objects and run the report.

4.4.4.    Report should run successfully.

4.5. Data Match

4.5.1.    Login to Business Objects using ID created in previous step.

4.5.2.    Create a report using this newly created filter.

4.5.3.    Save data in Excel.

4.5.4.    Write a manual query who’s where clause is equivalent to above filter.

4.5.5.    Fetch the same columns in query which report has fetched.

4.5.6.    Run this query on Aquadata.

4.5.7.    Compare its output with report output.

4.5.8.    Data should match.

5.    Modifying/Renaming existing Filter in Universe

5.1.  Follow each step of 4. New Filter in Universe i.e. from 1 to 5.

5.2.  Login to business objects using the ID created in step 5.

5.2.1.    Open the report which already contains this Filter (pre modified version).

5.2.2.    Open the data provider and check if the original object has been automatically replaced       with modified Filter. Run the report.

5.2.3.    Report should run successfully with original Filter automatically getting replaced with           modified Filter.

6.    Object/Filter’s access is restricted.

6.1. Hide Object/Filter.

6.1.1.    Login to business objects.

6.1.2.    Click on New Report and select the Universe.

6.1.3.    In the data provider search for the Object/Filter which has been set as hidden.

6.1.4.    Object/Filter should not be available.

6.2. Restrict Access to an Object.

6.2.1.    Login to business objects using ID created in step 3-e.

6.2.2.    Click on New Report and select the Universe.

6.2.3.    In the data provider search for the Object which has been restricted.

6.2.4.    Object should not be available.

6.2.5.    Login again to Business Objects using admin ID.

6.2.6.    Repeat step ii and iii.

6.2.7.    Object should be available to use.

7.    Incompatibility Checks

8.    Testing Canned Reports

8.1. New View has been added to Universe and View is not yet migrated to Prod.

8.1.1.    Create a User ID in QA and Prod CMC with rights mapped to a business user.

8.1.2.    Open designer, Login to Prod.

8.1.3.    Click on “Manage Access Restrictions”.

8.1.4.    Apply a restriction called “QA Connection” to this newly created ID.Once its done all reports     refreshed by this user will use QA database instead of Prod.

8.2. New View has been added to Universe and this View is already present in Prod

8.2.1.    Create a User ID in QA and Prod CMC with rights mapped to a business user.

8.2.2.    Open designer, Login to QA.

8.2.3.    Click on File>Parameters.

8.2.4.    Change the Universe connection such that it points to Prod database.

8.3.  Copy all the canned report’s which needs to be tested in a folder.

8.4.  Login to Business Objects Prod using Administrator login and retrieve this report : 10 Technology   Folder>Report Execution Runtime.rep

8.5.  Refresh this report and you will get a prompt. Give the folder path of Canned Reports and select    all the Radio buttons as “No”. Click on Ok.

8.6.  This will open all the reports under that folder and will save it for “All Users”.

8.7.  Create two copies of this folder and name one as “QA” and other as “Prod”.

8.7.1.    QA

8.7.1.1.Log in to business objects QA using ID created in step 1 and open the report> Report Execution Runtime.rep

8.7.1.2.Refresh this report. Under File Location give the path of QA folder which was created in above step.

8.7.1.3.Mark “Save Data Provider SQL” as “No” and all other options as “Yes”.

8.7.1.4.Click on OK.

8.7.2.    Prod

8.7.2.1.Log in to business objects Prod using ID created in step 1 and open the report> Report Execution Runtime.rep

8.7.2.2.Refresh this report. Under File Location give the path of Prod folder which contains canned reports.

8.7.2.3.Mark “Save Data Provider SQL” as “No” and all other options as “Yes”.

8.7.2.4.Click on OK.

8.8.  Once QA and Prod version of reports are refreshed, Compare .rpt files of each report using Windiff/Beyond Compare and check if there is any difference in data. You can ignore the decimal point differences.

9.    Testing Object combinations and Joins

9.1.  Create a sample report by using all possible measures and dimensions in data provider.

9.2.  In report tab only pull measure totals. Refresh this report against Prod Universe and QA Universe   and then cross check if financials are matching.

9.3.  This report will also test most of the universe joins.

10. Universe Overloads

10.1.  Open the Universe in Designer.

10.2.  Click on “Manage Access Restrictions”.

10.3.  Check if there are any universe overloads.

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

Leave a Reply