September 9–11, 2013 Anaheim, California

From Web Intelligence Prompt to Universe Filter A Best Practices Guide to BI Personalization Presented by: David Hudgins, Consultancy By Kingfisher Inc.

What topics will this session cover?  In this session, you will be exposed to the following items:  Web Intelligence (WebI) Prompts  Information Design Tool (IDT) Filters  IDT Parameters and Prompts  IDT @Variables  Business Intelligence (BI) Profiles  BI Personalization

2

What will I learn from this session?  When you leave this session today you will be able to:  Create reports the can conditionally display datasets based on any or all of the following:  How the user responds or failed of responds  Filters on an objects, folder or universe query  Visible and Hidden

 Create or transfer WebI prompts to IDT

3

Who this guy anyway  Presenter: David Hudgins  Over 10 years Business Objects hands-on experience  Started with Business Objects XI r2  Designed, implemented, and deployed over 100 SAP BI 3.x/4.x solutions globally

 ASUG Community Facilitator – Portals Communities  Sap Experts Business Intelligence Board of Advisor  Sap Certified Application Associate  Business Intelligence 4.x

 SAP Certified Instructor – BI 4.x curriculum  And yes I’m also one of ASUG’s poster people. 4

Prompts  What is a prompt?  A prompt is a question or condition that is triggered when a report is run or refreshed. The prompt runs before the data is pulled and limits what data is returned by passing prompt response into the report SQL query.  Prompts can be interactive or non-interactive based on the criteria or conditions of the prompt itself.  Prompts are the most common form of personalization used by Business Intelligence users. Please Select Sales Market(s): Date Range: Display Open Orders: Y/N User:

5

Why Use Prompts? “When I open this report I should only see my regions sales”  Prompts limit the results based on the user’s response, reducing overall refresh times “BUT, I may want to see other regions sales as well”  Prompts create reusable reports that can simulate ad hoc access to the data “Show me only Bob’s promotional sales from this week ”  Prompts provide a method for users to communicate with the report itself.

6

Creating Prompts in WebI  Starts with the Query Panel

7

Creating Prompts in WebI  Select the object you want to use as a prompt and add it to the Query Filters

8

Creating Prompts in WebI  Using the dropdown select the prompt option

9

Creating Prompts in WebI  Properties of a prompt

10

Prompt Best Practices There is no official rules or guidelines that defines “how” a prompt questions users, however here’s what most companies do. If a List of Values is available, start the prompt question with “SELECT…” If a List of Values is not available, start the prompt question with “ENTER…”

11

Prompt Options Prompts  Single or Multiple values  Use a List Of Values

 Free or Constrained  Use default values  Persistence vs. Non-Persistence  Persistence controls if the last value selected is store and displayed next time the report is run or refreshed  Non-Persistence purges the stored last value when the report is rerun

 Follow a predefined prompt order  Ask for Start Date First then Ask for End Date

 Optional or Required Prompts  Allows for flexibility and ease of use.

12

Running the Query

13

Results

14

Viewing the Query SELECT Calendar_year_lookup.Yr, Outlet_Lookup.State, Outlet_Lookup.City, Article_lookup.Category, Outlet_Lookup.Manager, sum(Article_lookup.Sale_price) FROM Calendar_year_lookup, Outlet_Lookup, Article_lookup, Shop_facts WHERE ( Outlet_Lookup.Shop_id=Shop_facts.Shop_id ) AND ( Article_lookup.Article_id=Shop_facts.Article_id ) AND ( Shop_facts.Week_id=Calendar_year_lookup.Week_id ) AND

Outlet_Lookup.Manager IN @prompt('Enter values for Name of manager:','A','Store details\Name of manager',Multi,Free,Persistent,,User:0) GROUP BY Calendar_year_lookup.Yr, Outlet_Lookup.State, Outlet_Lookup.City, Article_lookup.Category, Outlet_Lookup.Manager

15

Adding more than one prompt

16

Bringing it all into one prompt  Prompts can be combined if the prompt value matches  Optional Prompts must be used  OR Conditions  Prompt Text

17

Combining Properties

18

Single Prompt

19

Query String (

Outlet_Lookup.Manager IN @prompt('Filter:','A',,Multi,Free,Not_Persistent,,User:0,optional) OR Calendar_year_lookup.Yr IN @prompt('Filter:','A',,Multi,Free,Not_Persistent,,User:1,optional) )

20

Going Beyond WebI  IDT – Create a filter

21

Filters - Native

22

Query the new object

23

Parameters

24

Defining Parameters – IDT Prompts

25

Parameters & Prompts

26

Creating the Filter

27

Testing It

28

Personalize instances with prompted profiles

29

Live Demo (Time Permitting)  DEMO

30

Going BIG  Build multiprompted combined filters  Use profiling in CMC publications that populate prompts  Populate prompt values in instances based on predefined rules

31

Key Learnings     

32

Prompts are easy to make Personalize your reports by using prompts Build once and reuse Use Prompts in instances Ah-Hoc Like reporting

Thank you for participating. Please provide feedback on this session by completing a short survey via the event mobile application.

SESSION CODE: 0604 Learn more year-round at www.asug.com