SAP BOXI 31 Tutorial to Create Basic Universe

SAP BOXI 3.1 Tutorial to Create Basic Universe Applies to: SAP Business Object XI 3.1. For more information, visit the Business Objects homepage. Summary This tutorial is to help the beginners to create a basic universe in SAP BusinessObjects 3.1. Author: Seema Mane Company: Cognizant Technology Solutions Created on: 19 July 2011 Author Bio Seema Mane has been in the IT industry for over six years. She has extensive experience in the datawarehousing field. As part of her assignments, she works as a developer, team lead, on site cocoordinator, Coe in BI Technologies. SAP COMMUNITY NETWORK © 2011 SAP AG SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com 1 ....................................................com 2 . 5 Learning Objectives ...................sap.................................................. 15 SAP COMMUNITY NETWORK © 2011 SAP AG SDN ........................sap.....................1 Tutorial to Create Basic Universe Table of Contents Introduction .....................................................................................................................................uac..............................................sap......... 9 Learning Objectives ..... 3 Building the Universe Structure ...................................com | UAC ................. 12 Learning Objectives ............................................................................................................. 12 Related Content .......boc..............................sap.................................................... 5 Creating Dimension Objects ........................................................................................................................................................................................................bpx.............................SAP BOXI 3........................................................com | BA .................................................................................................com | BPX ........................... 3 Learning Objectives ...................................................................................................................................................................................................... 14 Disclaimer and Liability Notice .......................................................................................................................... 3 Create a New Universe and Define its Connection to the Database ..sdn................ 9 Creating Measure Objects ............................................................ 4. Create a New Universe and Define its Connection to the Database Learning Objectives Upon completion of this activity you will be able to create a new universe and define its connection to the database. 5.boc. Log into the Enterprise server.com | UAC .com | BPX .1 Tutorial to Create Basic Universe Introduction This tutorial is to help the beginners to create a basic universe in SAP BusinessObjects 3. Save the new universe in a file called Motors2004.mdb is the access DB: Motor Cars Database for Showrooms.sap. 2. Create a DSN called MotorsDSN.mdb.SAP BOXI 3.unv.sdn.bpx.sap.uac.com | BA . Models sold. 3. Start a Designer session. Connection = Motors2004. Rental and Sales Business used for this tutorial you can used any DB. Motors2004. SAP COMMUNITY NETWORK © 2011 SAP AG SDN . 7.com 3 .sap.sap. Create a new universe and define the following parameters: Name = Motors2004 Description = this universe provides information on the Prestige 6. Tip: Use the New Connection Wizard to create the Motors2004 connection against the Motors2004. Here are the steps: 1.1. Description = this universe provides information on the personnel of Prestige Cars. SAP COMMUNITY NETWORK © 2011 SAP AG SDN . Create another new universe and define the following parameters: a.1 Tutorial to Create Basic Universe 8.unv. c.boc.sap.sap.com 4 .com | BA . Save the second universe in a file called Staff.sap.com | BPX .uac.sdn.com | UAC . Connection: Motors2004 9.sap. Name = Staff2004 b.SAP BOXI 3.bpx. 2.com | UAC .boc. SAP COMMUNITY NETWORK © 2011 SAP AG SDN .sap. Order the tables so that they are laid out in the same way as the illustration below.uac.com | BPX .  COUNTRY  REGION  CLIENT  SALE  SALE_MODEL  COLOUR  MODEL  MAKER  STYLE  SALES_PRICE_RANGE  SHOWROOM  FINANCE_PERIOD.sap.sap.bpx.com | BA .  Insert joins between tables in the Motors2004 universe and set cardinalities.1 Tutorial to Create Basic Universe Building the Universe Structure Learning Objectives Upon completion of this activity you will be able to:  Insert tables into the Motors2004 universe. Insert the tables listed below into the Motors2004 universe.com 5 .sap.sdn.SAP BOXI 3. Here are the steps: 1. 1 Tutorial to Create Basic Universe 3.com | BA .com | UAC .sap.MODEL_PRICE BETWEEN b.boc.COUNTRY_ID to REGION.uac.PRICE_RANGE_MAX SAP COMMUNITY NETWORK © 2011 SAP AG SDN .COUNTRY_ID 5.SAP BOXI 3. Insert the following equi-join using the Edit Join dialog box. a.sap.sap. 4.PRICE_RANGE_MIN AND c.REGION_ID to CLIENT. SALE_PRICE_RANGE. REGION. MODEL. Insert the following theta join: a. COUNTRY.sdn.com 6 .sap. Save the changes to the universe. Insert the following equi-join using the drag and drop technique: a.REGION_ID 6.com | BPX .bpx. SALE_PRICE_RANGE. 13. Manually set the cardinality for the following join: a.sap. a.uac.SAP BOXI 3. a. 12.COUNTRY_ID to REGION. Tip: The remaining joins required involve inserting equi and theta joins only. Remedy the divergences found in the integrity check of the Motors2004 universe using manual techniques. Check integrity for: a.1 Tutorial to Create Basic Universe 7. Check that the universe structure includes all of the joins in the table below: SAP COMMUNITY NETWORK © 2011 SAP AG SDN . Check integrity to ensure no divergences in the Motors2004 universe remain.sap.SALE_TYPE='S' 8.sdn. COUNTRY.REGION_ID to CLIENT. Detect the cardinality for the following join.sap.com | UAC .COUNTRY_ID 10.bpx.com | BPX .boc. REGION. SALE.com | BA . Universe structure and joins 11.REGION_ID 9.com 7 . Insert the following self-restricting join.sap. uac.sap.com 8 .1 Tutorial to Create Basic Universe 14.com | BPX .sap.SAP BOXI 3.sap. SAP COMMUNITY NETWORK © 2011 SAP AG SDN .sdn.sap.com | BA .com | UAC . Save the changes to the universe.bpx.boc. CLIENT_FIRSTNAME d. Check the integrity of the objects. Type = Character b. ' + CLIENT. 5.bpx.CLIENT_LASTNAME + '. Forename c. SELECT = CLIENT.SAP BOXI 3. Description = Unique Client ID Number c. 2.sap. SAP COMMUNITY NETWORK © 2011 SAP AG SDN . No Associated LOV 6. However. Here are the steps: 1. Some of the properties for each object have been specified for you.sdn.com | BA . Type = Number b.sap. qualification. 8.boc. Car b.1 Tutorial to Create Basic Universe Creating Dimension Objects Learning Objectives Upon completion of this activity you will be able to create and test classes and objects. Sale Prices (subclass of Car) 3. Description = Surname. Create the following class: Client. Create a Client ID detail object automatically with the settings: a. Create a Client Name dimension object manually with the settings: a. Create objects for each of the classes as identified in the tables below. No Associated LOV 7.com | UAC .CLIENT_ID d.sap. Automatically create the following class from its table in the structure: Region 4.sap. Create the Showroom class.uac. and whether or not a LOV should be associated with each object. Create the following class and subclass: a.com 9 . Remove the following class: Region. 9. you will have to determine the data type. SELECT = CLIENT.com | BPX . uac.sap.com | UAC .sap.1 Tutorial to Create Basic Universe SAP COMMUNITY NETWORK © 2011 SAP AG SDN .com 10 .boc.com | BA .sdn.sap.bpx.sap.SAP BOXI 3.com | BPX . sap. Save the universe again and export to the Enterprise server. Build a query in the Java Report Panel using the objects created and test the results. a. and make any alterations required.sdn. 15. In InfoView. 14. 11.com | UAC .sap.bpx.sap.sap. Check the integrity of the objects. SALE. Note: Test the validity of the joins also. Save the universe. create a new Web Intelligence document and select the Motors2004 universe that has been exported.com | BA .boc.SALE_ID Unique Invoice ID Number SELECT Statement Object Description 13. Create Area Code (CLIENT.uac. c. Make sure you have defined each object using the appropriate object type.CLIENT_AREA_CODE) object under the client Class. Create Sales Class. Create Financial Class. Object Name Class SubClass Sales Sales Details Invoice ID Number 12.1 Tutorial to Create Basic Universe 10. b. SAP COMMUNITY NETWORK © 2011 SAP AG SDN .SAP BOXI 3.com 11 .com | BPX . The SQL code for the Select properties of each object has been specified. Run the query. Edit the query by adding the Country dimension object. USA). Create another query using the Showroom and Sales Revenue objects. Note the value returned.1 Tutorial to Create Basic Universe Creating Measure Objects Learning Objectives Upon completion of this activity you will be able to create and test measure objects. Description = Total Sale Invoice Revenue c. Check the SQL and note the GROUP BY clause. Does it aggregate to Country level correctly? a. create the following measure objects in the Sales Figures subclass and test them. Run the query. Select = SUM (SALE_MODEL. 5.com | BA .sap.com | UAC . Here are the steps: 1. c.sap.uac.SAP BOXI 3. Edit the query by adding the Region dimension object.SALE_SALE_DISCOUNT) / 100)) d. Create a new Web Intelligence document and select the universe just exported. No Associated LOV 3. Edit projection to the block from the microcube by removing the Country column from the block. Build a query containing only the Sales Revenue object. Apply a break to the Country column and reapply the sum calculation to the Sales Revenue column of the projected block. Create a Sales Revenue measure object with the settings: a. Sales Figures 2. SAP COMMUNITY NETWORK © 2011 SAP AG SDN . Does the Country group sum match the value of the noted block row from the previous query (e. Create the following subclass in the Sales class.bpx. determine the appropriate projection function aggregate. d. Does the sum match the value of the previous query? Note the value of the Sales Revenue in a row of the block (for example. a. Change the projection to the block from the microcube by removing the Region column from the block. b.SALE_QTY * MODEL. It should contain the SQL for the Country object.sdn.boc. Does it aggregate to the total Sales Revenue level correctly? b. USA)? 4. Check the SQL and note the GROUP BY clause.sap. Type = Number b. Test the Sales Revenue object as follows: a. Save the universe. Export the universe and log in to InfoView. Apply a SUM calculation to the Sales Revenue column of the projected block.sap. Function = SUM e. then another using Maker and Sales Revenue.MODEL_PRICE * ((100 SALE. In Designer.com | BPX . However.com 12 . It should now contain the SQL for the Country and Region objects.g. Note the total values remain the same. Create a query to return Country. Town. (Resolution: Click the Tables button in the Edit Properties Definition tab for both the Cost of Car Sales and Number of Cars Sold objects. Query 3: Country.com | BA . and Number of Cars Sold. Compare the results. Note: Two of the above objects will produce inconsistent results that are sometimes incorrect. Create an additional measure object as shown below: a.com | BPX .com | UAC . Query 1: Country. create a query with Showroom and Cost of Car Sales.sap.) 7. Save and export the universe. Lowest Priced Value based on Manufacturers recommended retail price. Web Intelligence has summed the average. Select the Sale table to force a join to that table as well. Place them in the appropriate existing class or subclass and then test them in Web Intelligence. Test the finished objects by building three queries in Web Intelligence: b. Set the Select Projection function to AVERAGE. this should become apparent. To test. Sales Revenue. Just identify what the problem is and why it is occurring.bpx. b.boc. Town. Insert a sum on the Sales Revenue and Number of Cars Sold columns 4. Do not attempt to remedy the issue. 8. which are not accurate results. Create a second query to return Country and the Average Revenue per Cars Sold. 2.uac. and then create a query with Maker and Cost of Car Sales. The reason for this is the same in both instances. Save the universe and export it to the Enterprise server.SAP BOXI 3. Average Revenue per Car Sold d.com 13 . 3. When testing the objects. Recreate the query and the results are correct or create a variable in the report.sap. SAP COMMUNITY NETWORK © 2011 SAP AG SDN . Create the measure objects listed below. Create a variable to show the average. Number of Clients. 5. Average Revenue per Car Sold Which Country and Town spends the most on cars on average? What happens to the average if Town is sliced away from Query 3? What conclusion can be drawn from this? Create another document to demonstrate this. Highest Priced Value based on Manufacturers recommended retail price.sap. 9. a. Resolution: Modify the Average Revenue object so that the projected aggregate on the Edit Object Properties tab is set to none. 1.sdn. Average Revenue per Car Sold c. Query 2: Town.sap.1 Tutorial to Create Basic Universe 6. sap. SAP COMMUNITY NETWORK © 2011 SAP AG SDN .bpx.com | BA .uac.sdn.com | UAC .boc.sap. visit the Business Objects homepage.sap.com | BPX .1 Tutorial to Create Basic Universe Related Content For more information.com 14 .SAP BOXI 3.sap. com 15 .com | BA .SAP BOXI 3. and anyone using these methods does so at his/her own risk.sap. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample.boc.com | BPX .sdn.sap. Changes made based on this information are not supported and can be overwritten during an upgrade.sap. including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. code or methods suggested in this document.1 Tutorial to Create Basic Universe Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP.uac. You agree that you will not hold. SAP will not be held liable for any damages caused by using or misusing the information. or seek to hold. SAP COMMUNITY NETWORK © 2011 SAP AG SDN . SAP responsible or liable with respect to the content of this document.com | UAC .sap.bpx.