Prepare and Share SAP Visual Intelligence Visualizations

SAP Visual Intelligence development interface is easy to navigate and is split between two major modes of Prepare and Share. The client installed tool once opened allows us to create New Documents or open existing Visualizations and or Datasets, the two components making up a .SVID file. Typically these files can be saved in SAP Visual Intelligence Documents folder under Users Documents folder.

Creation of a Visualization involves three steps, one is to connect to a data source and scope and acquire a dataset; two is to prepare the dataset for final cosmetics and data manipulation as part of any cleansing or business representation of Dimensions or Attributes and Measures from raw data, if required; and third is to choose and chart type and built the chart. Once the chart display is the desired result, save and share it.

Why Ad Hoc Reporting Won’t Work (part 5): If I Give Them Ad Hoc Access to Data, They’ll Keep Asking For More

Back in March I posted “Five Reasons Why Ad Hoc Reporting Won’t Work In Some Organizations“. In that post, I listed some of the major concerns that I hear from potential clients when the subject of ad hoc reporting is broached. We’ve already addressed “Our people aren’t smart enough to create their own reports”, “We need to massage the data first”, “I don’t want people poking around in data they shouldn’t have access to”, and “I already pay people in IT to create reports”.

As a conclusion to this series, let’s look at out final topic: If I give them ad hoc access to data, they’ll keep asking for more.

Why Ad Hoc Reporting Won’t Work (part 4): I Pay People in IT to Create Reports

One of the other reasons I hear is that managers don’t want to train end-users to create reports, since they have folks in IT that already tasked with that. Some report authoring will always need to be handled by IT, due to it’s complexity, lack of data availability, etc… But I argue that the lion’s share of the development can be handled within each department instead, freeing IT developers to take on other projects critical to the organization.

Why Ad Hoc Reporting Won’t Work (part 3): I don’t want people poking around in data they shouldn’t have access to

Data security is typically a really a big deal for organizations, and it SHOULD be. Thankfully, SAP BusinessObjects offers a number of ways to provide security around functionality, content and data. With some careful planning and a well-designed SAP BusinessObjects implementation, you can rest assured knowing that users will have access to only the information that they are supposed to see.

Why Ad Hoc Reporting Won’t Work (part 1): Our People Aren’t Smart Enough

I recently posted an article titled “Five Reasons Why Ad Hoc Reporting Won’t Work In Some Organizations”. In that article, I listed some of the major concerns that I hear from potential clients when the subject of ad hoc reporting is broached. As promised, I will be addressing each of those concerns and showing how they can be overcome. Today, we begin with the first one: “Our people aren’t smart enough to create their own reports”

Five Reasons Why Ad Hoc Reporting Won’t Work in Some Organizations

Over the past ten years, I’ve been a part of literally hundreds of SAP BusinessObjects client demos. I’m always struck, however, when we reach the ad hoc portion of the demo and begin talking about WebIntelligence. While the end-users in the room get excited about having the ability to create their own reports and analysis without waiting on the IT department, we usually get a lot of push-back from the managers and executives in the room.