6/24/2010

Advanced Data Analyzer Techniques

Dorene Lofgren Consultant, GSUSA July 11, 2010

What is Web Intelligence?

Business Objects Web Intelligence is an ad hoc reporting tool for business users that provides self-service access to data. Business users can interact with data without having to know the complexities of their database.

What are Universes?

A Universe is a watered-down version of a relational database. The Universe translates the complexities of the database into business-friendly terms for endusers and allows for correct SQL generation.
http://hubpages.com/hub/BusinessObjects_Universe:

A Universe is the interfacing layer between the client and the actual database. The Universe defines the relationships among the various tables in the database and contains the connection parameters to the database.
http://www.geekinterview.com

6/24/2010

Universes make life easier

But it can never be too easy

The data objects I need for my report are in two different universes!

But I dont want the 9 digit postal code

Yesterday it was a #DATASYNC error, today its a #MULTIVALUE error. Why am I getting all of these errors?

I need the data joined with an outer join not an inner join! Wheres the Find Unmatched feature?

Session Objective
This workshop is designed to empower users with the knowledge and skills to manipulate universe data to achieve desired results. Major takeaways include:
How to merge data across multiple data providers with success How to combine queries within a universe in different ways How to build powerful expressions.

6/24/2010

Instructional Methods
This isnt a presentation- its a hand-on workshop! Buddy up and start problem-solving!

Data Analyzer Warm Up!

Lets get everyone on the same page!

Terminology Review
How is a Universe organized?
Classes - Logical grouping of objects.

Objects - Named component that maps to data in the database. You use objects in a query to retrieve data for your reports.

6/24/2010

Universe Objects Defined

Object Dimension Example Definition Retrieves data that will provide the basis for analysis in a report.

Measure

Retrieves numeric data based on a calculation performed on data in the database. Refers to pieces of information that do not form the basis for a query but, nonetheless, are needed for the results of a query. A Detail is always attached to a dimension. Details come into play when you merge data providers, so stay tuned!

Detail

Girl Scouts Universes of Interest

Accounting Setup Whats in it? The Accounting Setup universe contains a list of your orgs GL accounts in Personify. It also shows the accounts associated with each product in your org. Query this Universe to See the revenue accounts for meeting products Review your Personify chart of accounts Access an account name (other universes typically include account numbers not names) All Order Entry Whats in it? All Order Entry contains a record for every order line in Personify, segmented by org. It includes information about the customers and products associated with each order as well. Query this Universe to generate a list of active members create a basic meeting roster retrieve a list of donors

Girl Scouts Universes of Interest

Committee Personify Technical Universe Whats in it? The Committee Universe is segmented by org. This universe tracks : every committee (e.g. award, troop, and service unit ) in your org the positions held by committee members customer information about each committee member Query this Universe to generate a troop or service unit roster see a list of customers who currently hold a position (e.g. 01s or 02s) retrieve a list of award recipients

Customers Whats in it? Tracks information on every customer in the database, regardless if theyve placed an order or not. This universe is not segmented by org. Query this Universe to access non-primary communication methods, aliases, special needs, non-member employers, position codes, credit statuses and purchasing group information.

6/24/2010

Girl Scouts Universes of Interest

Generic Product Setup Whats in it? Contains information about every product set up in your org, including rates and pricing, GL accounts, cancellation fees, and package components for eBiz. Query this Universe to Generate a list of meeting products with or without registrants. Marketing Universe Whats in it? The Marketing Universe is the only universe that currently holds Contact Tracking data. Query this Universe to generate a list of contact tracking records by topic or staff assigned. Meetings Whats in it? Meeting registrations and meeting products. Meeting product nformation exceeds what is available in All Order Entry. Only includes meetings that have customers registered to them. Query this Universe to produce a meeting roster with detailed product information

Girl Scouts Universes of Interest

Security Setup Whats in it? Contains user login information and user group information. Query this Universe to See the last time your users logged into Personify See the groups assigned to your users in Personify

System Setup Whats in it? Contains setup information for your org and products. You typically will not need to query this universe unless you cannot find a products attribute anywhere else. For example, this is the only universe that contains eCommerce controls for web products. Query this Universe to check setup information for your web products.

Warm Up Team Activity

Which Universe would you select to create
1. An adult member listing?
All Order Entry Committee

2. A troop roster for the current year? 3. A list of programs coming up in the next three months, including programs where no one is registered?
Generic Product Setup Security Setup Customer

4. A list of users with the last time they logged on? 5. A list of customers in the database that have an Alias?

6/24/2010

Lets Build One Together

A Troop Roster for 2010
Additional Requirements
Include a user prompt for troop name

Begin Date and End Date Filters

Inclusions
Test Case Annual Members (positions added from batch) Mid-year transfers (to troop/council) Annual mid-year positions added manually Lifetime members Begin Dates 10/01/09 End Dates 09/30/10

Exclusions
Test Case Annual Members (past or future) Mid-year transfers (from troop/council) Annual mid-year positions that were terminated Begin Dates 10/01/08 10/01/10 10/01/09 11/01/09 10/01/09 11/01/09 End Dates 09/30/09 09/30/11 12/15/09 06/01/10 12/15/09 06/01/10

11/30/09 06/15/10 11/30/09 06/15/10 11/30/00 10/01/09

09/30/10 09/30/10 09/30/10 09/30/90 09/30/10

[Begin Date] <= 9/30/10 And [End Date] >= 9/30/10

Result Objects and Query Filters

6/24/2010

Merged Queries
Introduction

What is a Merged Query?

A merged query draws related data from different data providers.
Data comes from Query 1 which is based on the All Order Entry universe

Data come from Query 2 which is based on the Customers universe

Why merge?
When the data you need comes from two different data providers, Web Intelligence does not know that it is related. You tell Web Intelligence that the data is related by merging the two data providers on the common dimension.

6/24/2010

Merged query example

Merged Objects

Query 1 - Members

Query 2 Customer Aliases

All Order Entry is needed to display active members. But Customer Aliases are not stored in the All Order Entry Universe

Common Dimension

Customer Aliases are stored in the Customers Universe

Examples of Merged Queries

1. Position Codes for Lifetime Members
All Order Entry Universe is needed to display customers that purchased a Life membership product Positions are stored in the Committee Universe. But You cannot tell from the Committee Universe that a customer is also a lifetime member

Examples of Merged Queries

2. Non-Primary Email Addresses for Members
Non-Primary contact records are in the Customers Universe. But You cannot tell from the Customers Universe that customer is also a member

All Order Entry Universe is needed to display customers that have an active membership product

6/24/2010

Examples of Merged Queries

3. Adult Member Training History
All Order Entry contains all the Data Objects you need for this report. But Data Objects must be contained in two separate queries because youre dealing with two separate data sets with different filters The first data set filters for all adult members The second data set filters for all training order lines and includes the customers who attended them.

Common Mistake
And condition cancels out everything! You are filtering for order lines that sell an Adult membership product and products classified as trainings. Each order line can sell either, however, not both!

Create 2 queries and merge the fields you need

Active Order Lines that sell products classified as Trainings

Better Solution:

Active Adult Members for 2010

6/24/2010

Examples of Merged Queries

4. Meeting Roster that shows the SU of each participant
The first data set filters for all active order lines that sell a specified meeting product. The second data set filters for each members current service unit

All Order Entry technically contains all the Data Objects you need for this report. But Data Objects must be contained in two separate queries because youre dealing with two separate data sets with different filters

Common Mistake
And condition cancels out everything! You are filtering for order lines that sell a specified meeting product and are linked to a Hierarchy Year. However, only membership order lines are linked to a hierarchy record!

Create 2 queries and merge the fields you need

Active Order Lines for a specified Meeting Product Name Active Members for 2010 with their 2010 membership hierarchy

Better Solution:

10

6/24/2010

Team Activity
To Merge or Not to Merge

Ex 1 A List of Members Associated with a List Demographic

To Merge or Not to Merge

No, you do not need to merge! List Demographics are associated with Ship-to Customers (e.g. members) in ALL Order Entry.

Ex. 2 Adult member award Listing by Service Unit

To Merge or Not to Merge

Yes, you need merge! Service Units are related to troop records, not awards. You first will need to generate an award listing, then a member listing by service unit. Then, connect the lists by Customer ID and merge whats missing!

11

6/24/2010

Ex 3 A Statistical Report that counts resident camp participants by year and race
To Merge or Not to Merge

No, you do not need to merge, although you can! Camp orders are found in ALL Order Entry. The Race is an attribute of the Ship-to Customer and can be found in All Order Entry also.

Ex 4 An Employer Listing for Adult Members

To Merge or Not to Merge

No, you do not need to merge! Adult member employers are found in the Ship-to Customer All Relationships folder of All Order Entry.

Ex. 5 Girl Guardian Employers

To Merge or Not to Merge

Yes, you need merge! You can get the guardian Customer IDs from All Order Entry, but not the employers of the guardians. Instead, you will need to merge guardian IDs with the Customers Universe to grab their employer info.

12

6/24/2010

How to Merge
A Step-by-Step Guide

Merged Query Demo #1

Member Roster with WinPCMS IDs

Merged Query Demo #2

Meeting Roster that shows each members troop and Service Unit

13

6/24/2010

Components of a Merged Query Query 1 and 2

Query 1- Main query Query 2- Detail Query

Contains the records you want to see in your final report, and includes the Merged Dimension

Contains the Merged Dimension and the fields you will merge into your final report

Components of a Merged Query Report 1 and 2

Report 1- Main report Report 2- Detail Report

Contains the output of Query 1. This report will be your final report that contains merged data.

Contains the output of Query 2. You can discard this report if youd like.

Components of a Merged Query Merged Dimension & Detail Objects

Merged Dimension Detail Objects

Common field in Query 1 and Query 2 you need to join in order to bridge data from Query 2 to Query 1. The object s name in both queries can be different as long as the data is the same.

Fields in Query 2 that you will bridge over to your final report.

14

6/24/2010

Components of a Merged Query Putting it all together

Merged Dimension

Detail Objects

Source Dimensions for Detail Objects

Creating a Merged Query Step-by-step (1)

Step 1: Build a new Webi based on the universe you need for Query 1

Creating a Merged Query Step-by-step (2-3)

Step 2: Construct Query 1. Add as many fields as possible that you want to show on the final report, including your merged dimension. Step 3: Right-click the Query 1 tab and choose Add Query to build Query 2. Select the Universe that represents the data source for Query 2.

15

6/24/2010

Creating a Merged Query Step-by-step (4-5)

Step 4: Click the Query 2 tab and construct Query 2. In this query include the merged dimension and all of the objects not available in Query 1 that you will merge in your final report. Step 5: Click Run Queries to generate the reports. At the New Query message, opt to Insert a table in a new report.

Creating a Merged Query Step-by-step (6-7)

Step 6: Click the tab for Report 1. You are ready to build your merged dimension. Click the Merged Dimension icon in the toolbar. Step 7: Under Query 1 and Query 2, select the fields you will use to join the queries. Typically these fields are IDs of some kind that are the same field in the underlying database. Then click Merge.

Creating a Merged Query Step-by-step (8)

Step 8: Create a name for the merged dimension and click OK. Back in the Merged Dimensions window, click OK as well.

16

6/24/2010

Creating a Merged Query Step-by-step (9-10)

Step 9: Now you are ready to build your Detail objects. Open the Variable Editor in the toolbar. Step 10: In the Variable Editor,
1. Double-click the first field you want to merge into Report 1 so that it displays in the Formula box. Give the field a name. (The name must be different than the original objects name.) Under Qualification, select Detail. Click the ellipsis next to Associated Dimension. Expand the merged dimension and select the original dimension from Query 1. This links the Detail object to Query 1. Click OK Click OK in the Variable Editor. Repeat the process for all the fields you want to merge into Report 1.
1 2 3 4

2.

3. 4.

5.

Creating a Merged Query Step-by-step (11)

Step 11: From Report 1, drag the detail objects you just created onto the report. Save your work. You have just created a merged query!

Team Activity
Plan your merges

17

6/24/2010

Activity #1: Adult Members and their Awards

Adult Members and their Awards Step 1: Choose your universes

1. What Universe do you query to retrieve adult members? (Becomes Query 1) __________________ 2. What Universe do you query to retrieve the awards customers have received? (Becomes Query 2) _____________________
Answer: Committee

Answer: All Order Entry

Adult Members and their Awards Step 2: Choose your Result Objects
1. What are the Result Objects in Query 1? (List them below)
Answer:

2.

What are the Result Objects in Query 2? (List them below)

Answer:

18

6/24/2010

Adult Members and their Awards Step 3: Choose your filters

1. What filters do you need for Query 1? (List them below)
Answer:

2.

What filters do you need for Query 2? (List them below)

Answer:

Adult Members and their Awards Step 4: Create the Merged Dimension
1. Which object from Query 1 will become the merged dimension? (Circle your answer) 2. Which object from Query 2 will become the merged dimension? (Circle your answer)

Adult Member Awards Step 5: Create your Detail Objects

1. Which objects from Query 2 will become Detail Objects? (Circle your answer below.)

19

6/24/2010

Adult Member Awards Step 5: Create your Detail Objects

For each Detail, identify its Name, Associated Dimension and Formula.
Begin Date Detail Name: _________________
Associated Dimension: Ship to Customer ID ________________________

=[Begin Date] Formula: _______________

Answer: Master Customer ID

Label Name Detail Name: _________________

Associated Dimension: Ship to Customer ID ________________________

Name] Formula:=[Label _______________

Merged Query Joins

Utilize the common dimension to select the records you want

Merged query joins

Data is merged on the common dimension in a left- or right-outer join, depending on which side of the merged dimension you insert in your final report. You can join data with an inner join also.

20

6/24/2010

Join Definitions
A left outer join selects all of the IDs from Query 1 and shows data from Query 2 if theres a match. A right outer join selects all of the IDs from Query 2 and shows data from Query 1 if theres a match. An inner join only selects IDs that exist in both queries.

Left Outer Join Example

Query 1 Current Adult Members Query 2 Customers with awards

Selecting the Ship-to Customer ID from Query 1 displays all members (i.e. Ship to Customers), whether they have awards or not.

Inner Join Example

Query 1 Current Members Query 2 Customers with awards

Only members with an awards show in the results. Selecting the Master Customer ID from Query 2 creates an inner join if the property Show rows with empty dimension values is set to No. (It is set to No by default)

21

6/24/2010

Right Outer Join Example

Query 1 Current Adult Members Query 2 Customers with awards

Selecting the Master Customer ID from Query 2 displays all customers with awards, regardless if they are members or not if the property Show rows with empty dimension values is set to Yes. (It is set to No by default)

How to change joins in a Webi

To create a Left Outer Join Drag merged dimension from Query 1 onto report

To create an Inner Join

Drag merged dimension from Query 2 onto report

Drag merged dimension from Query 2 onto report. Set Show rows with empty dimension values to Yes.

To create a Right Outer join

Team Activity
Select the records you want using Inner and Outer joins

22

6/24/2010

Activity #1a: Lifetime Member Positions Codes

Circle the dimension you would drag to show all lifetime members, regardless if they hold a position or not.

Query 1 contains lifetime members Query 2 contains customers with active positions

Activity #1b: Lifetime Member Position Codes

Circle the dimension you would drag to only show lifetime members with positions.

Query 1 contains lifetime members Query 2 contains customers with active positions

Activity #2a:
Non-Primary Email Addresses for Members
Circle the dimension you would drag to show all members, whether they have a non-primary email address or not.

Query 1 contains all current members Query 2 contains customers with a non-primary email address

23

6/24/2010

Activity #2b: Lifetime Member Position Codes

Circle the dimension you would drag to only show members that have a non-primary email address.

Query 1 contains all current members Query 2 contains customers with a non-primary email address

Which query becomes Query 1?

The importance of starting off the way you want to finish

FAQ: I know which queries I need. Which query should I make Query 1?
Contains your final record count in other words, the records that should display on the final report.

Query 1

Query 2

Includes information you want to see relating to the records in your final report, but not the actual filters that will produce your final record set.

This recommendation only applies if data needs to be related with an outer join (all records from one data provider show in the final report). If data ultimately needs to be related in an Inner join, it doesnt matter which query becomes Query 1.

24

6/24/2010

Team Activity #1
Award Listing by Service Unit The final report displays award recipients by their 2010 membership Service Unit (SU). If they do not have a 2010 SU (because they arent members), they should display a Null value in the SU column. Here are the two queries you will need. Which should become Query 1? (Circle your answer)
A list of all of the award recipients at the council with the award name and Begin Date A list of active members in 2010 with their current SU.

Team Activity #2
Girl Guardian Employers The final report displays a list of guardian customers for 2010 that are employees of the specified employer, in this example Conoco Phillips. Here are the two queries you will need. Which should become Query 1?
A lists all guardian 1 and guardian 2 customers related to girl members registered for the current membership year. A list of adult customers related to the specified employer.

It doesnt matter! The queries must be joined with an inner join.

Common Errors associated with Merged Queries

And how to avoid them!

25

6/24/2010

#DATATSYNC Errors
Cause Associated Dimension for the Detail Object is not linked to the Merged Dimension. Fix Link the Associated Dimension to the Merged Dimension from Query 1.

#MULTIVALUE Errors
Cause
A Detail object can have one value only for each value of its associated dimension. If the detail object contains multiple values for an associated dimension, Web Intelligence places the #MULTIVALUE error in the detail cell.

Fix
Select the table. Under Properties set the Avoid Duplicate Row Aggregation property to Yes

#MULTIVALUE Error Explained: Lifetime Member Position Codes

Merged dimension is unique in lifetime member query. Theres one membership product per customer. Merged dimension repeats in Position Code query. Each customer can hold more than one position.

26

6/24/2010

#MULTIVALUE Error Explained: Lifetime Member Position Codes

After merging data from position code query into Lifetime member query
Query 1 Query 2

#MULTIVALUE Error Explained: Lifetime Member Position Codes

After changing the Avoid Duplicate Row Aggregation property to Yes
Query 1

Checkpoint #1
What youve learned so far
Merging queries becomes necessary if the data you need comes from two different data providers. To merge two queries you need a common dimension in each query. The merged dimension tells BO how to match up data across queries. Dimensions merging to Query 1 must be made into Detail objects before they can be merged. You can change the way data is joined across queries by dragging either half of the merged dimension to your main query. Data Sync errors can be resolved by ensuring Detail objects are associated with the merged dimension Multi-value errors can be resolved by setting the Avoid Duplicate Row Aggregation property to Yes

27

6/24/2010

Combined Queries
Multiple queries on the same universe

About Combined Queries

You can combine queries in three relationships

Combined Queries

Intersection

Union

Minus

Union Queries
A union combination takes the all the data from both queries, eliminates duplicate rows, and builds a combined data set

Query 1

Union
Query 2

28

6/24/2010

Intersection Queries
An intersection combination returns the data common to both queries.

Query 1

Query2

Intersection Query Example: Returning Leaders

Query 1: Current Leaders

Query 2: Last Years Leaders

Minus Queries
A minus combination returns data from the first query that does not appear in the second query.

Query 1Query 2

29

6/24/2010

Minus Query Example: New Leaders

Query 1: Query 2 : Current Last Years Leaders Leaders

What data would this Minus Query Return?

Query 2: Query 1: Last Years Current Leaders Leaders

How to Build Combined Queries

A step-by-step guide

30

6/24/2010

Intersection Query Demos

Returning Leaders New Leaders

Combined Query Structure

The queries within a combined query must return the same number of objects of the same data type and the objects must be in the same order. Likely the result objects for each query within a combined query will be exactly the same.

To Build a Combined Query Step 1

1. Create Query 1, selecting your Result Objects and Filters. Run the query if youd like.

31

6/24/2010

To Build a Combined Query Steps 2-3

2. Back in the query, click the Combined Query icon in the toolbar.

3. The query transforms to a combined query, giving you access to two queries. The Combined Query type defaults to Union. Double-click Union to change it to a Minus or Intersection query.

To Build a Combined Query Step 4

4. So far youve completed Combined Query 1. You now need to add filters for Query 2. Click Combined Query 2 to access the query.

To Build a Combined Query Step 5

5. Select the filters necessary for Query 2. Then run the query.

32

6/24/2010

Combining more than 2 queries

What if you wanted to compare more than 2 queries in your combined query?
New Leaders (checking 3 years of data)

New Leaders (checking 3 years of Data)

Combined Query Precedence Round 1 Results

Query Combined Query 1 (2010 Leaders) Combined Query 2 (2009 Leaders) Minus Round 1 Results: (CQ1- CQ2) Results Carol, Sue, Tina, Wendy Barbara, Kim, Tina Carol, Sue, Wendy

33

6/24/2010

Combined Query Precedence Round 2 Results

Query Minus Round 1 Results: (CQ1-CQ2) Combined Query 3 (2008 Leaders) Minus Round 2 Results: (Round 1 Results CQ 3) Results Carol, Sue, Wendy Amanda, Barbara, Carol Sue, Wendy

Combined Query Precedence Round 3 Results

Query Results Minus Round 2 Results: Sue, Wendy (Minus Round 1 Query 3) Combined Query 4 (2007 Leaders) Minus Round 3 Results: Round 2 CQ 4) Amanda, Tina, Wendy Sue (Final results)

Summary of Combined Query Logic

Web Intelligence first finds the set of data that represents the union/intersection/minus between Combined Query n and Combined Query n+ 1. Web Intelligence then finds the union/intersection/minus between that data set and the data returned by Combined Query n + 2. Web Intelligence continues in this way through all the queries in the relationship.

Intersection, Minus or Union

Query 1 Query 2 Query 3

34

6/24/2010

Team Activity
Combined Queries

Activity #1 Answer the questions below

You would like to produce a list of girls who have been registered to your councils for the past 3 years (in 2010, 2009, and 2008).
1. 2. 3. What kind of combined query could you use to generate this Intersection result?_____________ 3 How many combined queries would you need? ________ What filters would each combined query have? Write your responses in the space below.
Query 1: 2010 Girl members Query 2: 2009 Girl Members Query 2: 2008 Girl Members Product Code = Girl_2010 Line Status Code = A Product Code = Girl_2009 Line Status Code = A Product Code = Girl_2009 Line Status Code = A

Activity #2 Answer the questions below

You would like to produce a list of lapsed girls who havent reregistered from last year.
1. 2. 3. What kind of combined query could you use to generate this Minus result?_____________ 2 How many combined queries would you need? ________ What filters would each combined query have? Write your responses in the space below.
Query 1: 2009 Girl members Query 2: 2010 Girl Members Product Code = Girl_2009 Line Status Code = A Product Code = Girl_2010 Line Status Code = A

35

6/24/2010

Super Combined Query on Steroids (for super advanced users)

Lapsed girls ( Going back 2 years)
2008 Girl Members

Minus
2010 Girl Members

2009 Girl Members

Minus
2010 Girl Members

Combines results of both minus queries, selecting Distinct Records to avoid duplicates from both record sets

Checkpoint #2
What youve learned so far Combined queries allow you to answer questions that are otherwise difficult or impossible to frame in a single Web Intelligence query:
A minus combination returns data from the first query that does not appear in the second query. An intersection combination returns the data common to both queries. A union combination takes the all the data from both queries, eliminates duplicate rows, and builds a combined data set

The individual queries in a combined query must have the same structure. You can include more than 2 queries in a combined query

Formulas
Display results based on a formula you create

36

6/24/2010

Variable Editor
The Variable Editor enables you to build your own dimensions based on other dimensions, formulas and operators

Takes the first 5 characters of each zip code

To learn how to use Functions

Click on the function name

Description provides info about the required syntax

Provides a detailed definition of the function

To Build a Formula
1. From the Report, click the Variable Editor In the Variable Editor, give your expression a Name. Then build your formula, using the Functions, Operators and Data objects required. Click the green checkmark to validate your formula. Click Ok to return to the report. Then drag the expression from the Data tab onto your report.

2.

3.

37

6/24/2010

Formula Demo
Create a Service Unit Roster from the Committee Universe that includes Trooplevel and SU-level positions grouped under each Service Unit.

Why do we need a formula?

The Problem: Only Troop-level positions show a Service Unit Name in the Committee Hierarchy folder. SU-level positions show a blank. We need to show the service units of both positions in one column in the report.
Service Unit-level position (Service Unit is the Label Name)

Troop-level position (Service Unit is the hierarchy)

What formula do we need?

The Solution: Create a formula based on this condition:
If the position is held on a Troop, show the Service Unit Name from the Committee Hierarchy folder, else Show the Label Name of the committee itself.

38

6/24/2010

Checkpoint #3
What youve learned so far To can build your own expressions in your reports based on formulas. Formulas can consist of report objects, functions and operators. The If function can help you display the results you want in a column based on a condition.

Data Analyzer Resources

Data Dictionaries on CES Support eLearning on CES Support Web Intelligence User Guide
http://www.csdw.status.dhhs.state.nc.us/usergui des/WebIntelligenceUserGuide.pdf

Web Intelligence XI and XI Release 2

http://www.doa.louisiana.gov/ois/Adhoc/Busines s%20Objects/Webi%20XI%20R2_calculation_chan ges.pdf

Q&A
Thank you for attending!

39