webiworx.

com
Web Intelligence XI 3.1 Training Course
Creating the Custom SQL Objects Class

Trademarks InfoView, Web Intelligence, Web Intelligence Rich Client, Central Management Console, Desktop Intelligence and Business Objects Designer are trademarks of SAP AG, Dietmar-Hopp-Allee 16, 69190 Walldorf, Germany. Screenshots and graphics reproduced in this book (of SAP BusinessObjects products) are subject to copyright of SAP AG, Dietmar-Hopp-Allee 16, 69190 Walldorf, Germany. Microsoft Access and Microsoft Windows are trademarks of Microsoft Corporation. Oracle Database is trademark of Oracle. All other products mentioned are registered or unregistered trademarks of their respective companies.

Limits of Liability and Disclaimer of Warranty The Author of this document has used best endeavours in testing the instructions and examples used. The Author makes no warranty of any kind, expressed or implied, with regards to the instructions, examples, sample data and documentation. The Author shall not be liable in any event for incidental or consequential damages in connection with, or arising out of the use of instructions, examples and sample data contained in this document.

The contents of this document provide instructions on how to create the class of objects called 'Custom SQL Objects' in both 'eFashion' and 'eFashion Oracle XI3.1' universes. This class of objects is required for the session on 'Advanced Measures'.

Alphanumeric Dimension objects.

Numeric Dimension objects.

Date Dimension objects.

Numeric Measure objects.

There is only a slight difference between Oracle and Microsoft Access in the definition of objects. Any specific differences will be described where relevant. Please Note - 'eFashion Oracle XI3.1' universe should already contain the 'Custom SQL Objects' class if downloaded from www.webiworx.com. 1. Create the 'Custom SQL Objects' class and its sub-classes as shown below. This can be performed in both universes in the same way, i.e. no specific requirements for Oracle or Access.

2. Create the first object in the 'Custom SQL Characters' sub-class as shown below. There is no difference in the definition of the object for Oracle or Access.

3. This object is not mapped to a column in any table. We need to map it to a table, therefore click on the 'Tables' button and select 'OUTLET_LOOKUP' in Oracle or 'Outlet Lookup' in Access.

4. Click 'OK' after assigning the table to the object. 5. Click on 'Parse' to ensure the object definition is correct. 6. Correct any errors. Ensuring you parse the object and then click 'OK' to create the object 'Custom SQL Char 01'.

7. The definition of 'Custom SQL Char 02' and 'Custom SQL Char 03' is the same as 'Custom SQL Char 01'. Therefore create these objects in the same way. Ensuring you assign 'OUTLET_LOOKUP' in Oracle or 'Outlet Lookup' in Access to the objects.

8. The remaining objects can be created in the same way using the definitions described below:

8.1. Objects in 'Custom SQL Numbers' class have the following 'Select' definition (no difference for Oracle or Access):

Remember to assign the object to 'OUTLET_LOOKUP' in Oracle or 'Outlet Lookup' in Access.

8.2. Objects in 'Custom SQL Dates' class have the following 'Select' definition (there is a difference between Oracle and Access): ORACLE

Remember to assign the object to 'OUTLET_LOOKUP' in Oracle.

ACCESS

Remember to assign the object to 'Outlet Lookup' in Access.

8.3. Objects in 'Custom SQL Measures' class have the following 'Select' definition (no difference for Oracle or Access):

Remember to assign the object to 'OUTLET_LOOKUP' in Oracle or 'Outlet Lookup' in Access. 9. Run an Integrity Check on the universe: Results for 'eFashion Oracle XI3.1' universe should show:

Results for 'eFashion' universe should show:

10. Export universe into your CMS using File Export.