During our presentation at the annual ASUG SAP BusinessObjects User Conference, we had some questions from the session attendees that asked about administration of the multi-source universes. To elaborate on the answers that were given at the conference, here is a quick overview of the tool that can help your companies SAP BusinessObjects Administrators maintain and monitor their multi-source universes.
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.
SAP Visual Intelligence is a new product from SAP AG introduced earlier this year as a standalone installed application which produces crisp, detailed visualizations using charts. The specific goal is to provide business owners and business-centric users the ability to create and deliver visualizations, enabling them to present their business information quickly.
Visual Intelligence users can by-pass traditional IT using full client reporting tools like SAP BusinessObjects, Web Intelligence or SAP Crystal Reports and reduce the time of the development cycle.
I recently published the post 5 Reasons Why You Should Use an SAP BusinessObjects Universe to highlight some of the core benefits you’ll see when implementing the semantic layer for you organization. The post was derived from speaking with organizations new to the Business Objects world about the benefits of leveraging the semantic layer. Throughout those talks, I also get to hear a lot of misconceptions about SAP BusinessObjects Universes. Sometimes they are born out of a simple lack of understanding of the SAP BusinessObjects architecture, while other times they are propagated by competing business intelligence vendors. (Shocking, I know.)
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. As promised, I will be addressing each of those concerns and showing how they can be overcome. We’ve already addressed “Our people aren’t smart enough to create their own reports.” Now let’s turn our attention to data, and look at “We need to massage the data first.”
Integrating data is a constantly evolving strategy, especially as Business Intelligence becomes a more critical application. In order to ensure success, trustworthy data must be built and, to do this, tools need to be used to bring together disparate data and address data quality.
The evolution of Enterprise Information Management (EIM) has brought us to several strategies. Now, there is consolidation, federation, or a combination of the two. Business Objects offers solutions in the form of two products: Data Integrator and Data Federator.