Business objects tutorial pdf

 

    SAP BusinessObjects is the main application coming under SAP Business Intelligence (BI).Here is an introductory tutorial with PDF training materials about SAP. PUBLIC. SAP BusinessObjects Business Intelligence Suite .. Exporting HTML Code, URLs, and Images to Excel Spreadsheets and PDF Files. Web Intelligence, the business intelligence reporting tool, is a part of SAP BusinessObjects in this tutorial, please notify us at [email protected]

    Author:DANTE ROLING
    Language:English, Spanish, French
    Country:Bahrain
    Genre:Politics & Laws
    Pages:363
    Published (Last):30.04.2016
    ISBN:322-4-28617-338-7
    Distribution:Free* [*Registration Required]
    Uploaded by: PORTER

    52565 downloads 165219 Views 15.50MB PDF Size Report


    Business Objects Tutorial Pdf

    Public folders and categories are created by the Business Objects team, and can be viewed by Reports can be exported as CSV, Excel, PDF, or Text files. The Mobile Compatibility panel. Sharing and annotating dashboards from the SAP BusinessObjects .. We also provide you with a PDF file that has color images of the available at trovotinuldes.tk Intelligence. Rich Client. Business Objects . Saving to Other File Formats ( Excel, PDF, CSV, and Text). .. Select SAP Business Objects Web Intelligence.

    Personal data files Define the drill mode. Drill is a kind of analysis mode associated with business objects and helps in breaking down data as well as in viewing data from all the possible angles and the levels of detail for discovering the factor that has caused a good or a bad result. What is a personal connection? The details regarding such a connection can be usually stored inside PDAC. LSI file. What is Shared connection? This is a kind of connection that is usually used by another user via a server which is a shared one. What is a secured connection? Secured connection is a kind of connection that can be helpful in overcoming the various limitations associated with the former connections. The rights related to this kind of connection can be set over documents as well as objects. Universes can be brought inside the central repository only by making use of the secured connection. The parameters regarding these connection care usually saved inside CMS. Define custom hierarchies?

    Even exclusively operational reporting will have a thought behind it. In many cases it is directly related to a business initiative that is very specific, while in other cases it may be a desire to really change the organization and its business processes.

    Recognize that customer resources will usually have done their research, but may misrepresent certain product features or misunderstand concepts that are very familiar to experienced consultants, so always clarify what they mean with what they say. Formulate the strategy and seek approval from the customer. Where possible, try to get download-in for a Business Intelligence Competency Center BICC to make sure there is a group that functions as a guardian of the BI solutions and applications post-implementation.

    The BICC members should not only drive best practices and system governance, but also ensure that the actual implementation aligns with the BI strategy. The BICC over time should help refine the strategy and drive it to ever further sophistication.

    We have all seen this process go astray with all of the other system-specific activities around the go-live and the post-golive processes including critical issues with performance, business user additional needs, or just running out of budget or time but please look to drive this effort so that the BW system and the BI concepts can continue to proactively impact the corporation. We have to keep in mind the critical position of information within our corporations.

    It is very important that you educate the business user or your customer on using the right tool for the right job, as the wrong choice is more likely to lead to implementations that fall short of the initial success criteria. You will have to manage not only which tool is more appropriate, but also the expectations with the customer, and what current product capabilities need to be considered when guiding the tool choice.

    Even if the right choice is made, diverging expectations or lack of support for certain features may still lead to problematic implementations. It is also clear, and this is the normal process with all new products, that a number of product changes have been, or are in the process of being enhanced, so all of these elements need to be taken into account when deciding on the right tool for the job at hand.

    Choosing the Right Tool for the Right Job Now we can look at the different tools within this set to see what works where, so that we can identify and recommend the appropriate tool for the job. With the current components available, we have a bit of a mix in toolsets—most with a significant background with BusinessObjects and one aligned with the SAP BI reporting component and this group of reporting components will be the best business practice approach until the development of SAP BusinessObjects Pioneer product is available.

    These reporting options are. As mentioned in the last section, SAP takes a use case—driven approach to determine which products are best to use for each business requirement, and then recommends that other consultants and businesses take a similar approach. When looking at the existing BW footprint at SAP customers, the following are the general guidelines for what constitutes the right tool for the right job:. As part of the requirements gathering in project preparation, it is strongly recommended to apply use cases to each of the requirements.

    That is, by not only capturing what the business needs are and how we plan to address them as part of the project , but also including how reports and dashboards are delivered and consumed, we discover how end users will use the information that is provided to them. With this process in place it will help us further understand the nature of the requirements and functionality each business user needs. This will also help us determine which tool to use, as well as help us with our design approach.

    By not only considering the needs and requirements of the business user, we can also identify the reporting toolset that will satisfy their needs. As you can see, the process is twofold. First, identify the actual functional requirements, and then identify the reporting component that will satisfy those requirements.

    The following sections include both a basic background of the product use and the guidelines for mapping required enduser capabilities to the BI platform, starting with an overall baseline approach, as depicted in the illustration.

    Again, the positioning of these components will really help you to conceptualize the BusinessObjects product. The preceding diagram shows the functionality across the top and the business user groups down the left side. Some of these tools overlap user groups, such as BusinessObjects Explorer and Xcelsius, but overall you can see what situation fits what tool.

    This should help you to identify the configuration approach and the implementation process. In a normal business use case, we would look at the process rather than the actual system component, and then work toward the appropriate tool that fits the situation.

    For now, we are going to look at the specific components of the BOBJ reporting toolset and include the use case information within each of these discussions.

    As we all look to migrate from our current reporting format to the newer format we always try to compare the newer items with the previous items and in this case I will also offer some comments to this effect in the areas that are really trade-offs such as the Crystal Reports versus Report Designer area but overall we will try to just outline the overall functionality.

    Also, in this case attempting to match reporting component to reporting component would be inconsistent with the approach that the business should take in terms of identifying the correct reporting functionality. Each should be viewed on their own value and functionality to the business. Now you can see that getting into too much detail would take us into another completely different avenue and the chapter would end up being twice the size. So the discussion will be high level and brushing over the functionality.

    As we always say, the devil is in the details, so using this section as an initial very general discussion of each component and then using other more detailed documentation to understand all of the complexities is a prudent approach. This section highlights the features of the WebI reporting tool and also gets into some of the configuration details.

    Now, remember, having a new reporting component will not mean that we are going to reinvent the wheel but using another toolset—BOBJ— rather than the SAP BI, we will be able to offer all of the same functionality plus some additional bells and whistles. Just that they will possibly use different terminology and access them in a different manner. In general, the Web Intelligence component has two main connectivity options for BW:.

    If you look at a best business practice for the WebI, you will see that the suggested approach is via the use of OLAP universes with BW, as this will be the most widely implemented solution within the existing SAP customer base. The preferred approach is to use the BEx query in this case, the query is created as a definition using the BEx Query Designer and will probably never really be run for any business users as a report ; this approach is preferred for several reasons, one of which is the ability to use calculated key figures CKFs and restricted key figures RKFs that are created in the query definition.

    Since these are not found in the Infocube, the direct access method would not have access to these formulas. After the linkage between the two systems is complete, you need to understand what the mapping process is for the different objects within the BEx query. The Rows area of this query includes several characteristics, and the Columns area includes several key figures. On the left side, the actual cube structure is shown with the cube dimensions and different characteristics.

    The symbol for dimensions has three triangles and the symbol for characteristics has one triangle. If we focus on one portion of this query, we see the characteristics, dimensions, and variables for the customer dimension, shown in the following illustration. In the next illustration, you can see what happens to these objects when translated or mapped into the OLAP universe.

    In addition, each characteristic in the query results in a class with dimension and detail objects. In terms of the display attributes of a BEx query definition, we see that they are detail objects within the OLAP universe. If we look at this in more detail, we see that display attributes are InfoObjects that are logically assigned or subordinated to a characteristic. In SAP reporting tools, the display attributes can only be used in combination with the actual characteristic, which means the attribute Phone Number can only be shown in the SAP reporting tool in combination with the characteristic Customer.

    In addition, characteristics can be defined as navigational attributes in the BW cube, which then makes these attributes available for navigational purposes in the reporting tools; navigational attributes are treated identically to a characteristic. This can get a bit confusing to both the developers and also for the OLAP universe so the universes differentiate between the two and the functionality of the display versus navigational attributes goes with these objects over to the OLAP universe.

    The row structure includes a characteristic Customer with four display attributes: In addition, the BW query contains three navigational attributes in the rows: When we build an OLAP universe on top of this BW query, it results in the elements shown in the following illustration. The cube dimension from BW results in a class in the OLAP universe for example, dimension Customer, not to be confused with the characteristic Customer.

    As mentioned, each characteristic in the query results in a class with dimension and detail objects. Also notice that each navigational attribute in the query results in a class with dimension and details objects navigational attribute Postal Code resulting in a class Postal Code with dimensions L00 Postal Code and L01 Postal Code. The next illustration shows the display attributes from characteristic Customer and how these display attributes are treated in an OLAP universe.

    Each display attribute for the characteristic results in a detail object for the corresponding dimension objects in the universe. In terms of the key figures used in a BW query, we can have up to three different sets of information:.

    The illustration here shows the result of two key figures in the OLAP universe. Each key figure is represented with a measure object in a class Key Figures. In the case where the key figure is configured in BW with a unit, an additional dimension object will be added representing the unit information.

    Once this process of creating an OLAP universe is complete, we can step into the Web Intelligence Rich Client and create the report by dragging and dropping the information into the appropriate columns and rows. The following illustration shows the initial screen for the Web Intelligence Rich Client. Once you start working in this environment, you will find that a number of functions and tasks are similar to those in the BEx Query Designer in terms of formatting and display options.

    Components of SAP businessobjects (BOBJ) for reporting - SAP BI

    All of the components are found in similar navigational processes as the BEx Query Designer—either in the right-click context menu or in the top toolbar, where you click and choose what you need to work on. Once you have created the report, you will have developed an ad hoc analysis component that you will be able to navigate and slice and dice on to generate multiple different views of the data, with the option to save each of the views for later analysis. This is the primary ad hoc reporting and analysis product for casual business users in the BOBJ components.

    Web Intelligence is a complementary tool to leverage outputs, for the casual and business user, that might have been derived from a deeper analysis achieved in BEx Analyzer. If we look at the overall reporting strategy and identify the areas and requirements that the WebI can fulfill, we have a fairly well-defined list. First, this component allows the business user to have a combination of ad hoc reporting and analysis primarily directed to the casual user.

    Third, this reporting tool also allows multiple sources of data, both SAP and non-SAP, to be integrated into the same reporting display.

    Fourth, all the functionality available in the BEx Web Analyzer is available in the WebI component, such as the ability to schedule and publish reports to a distribution list of users, and the ability to modify a report on-the-fly on the Web, save it, and then review or refer back to it in the future.

    Fifth, Web Intelligence also has all the user-friendly navigation capabilities that the BEx Web Analyzer has in terms of drag-anddrop navigation, context menu functionality, and the ability to switch information into a better format for the analyst.

    All of these components look at the actual information in the report, but in addition to these functions, Web Intelligence also has the ability to allow the business user to change the format of the report on the fly, adjust charts and table format, add conditions and exceptions, and adjust the positioning of all of these objects within the report.

    The illustration extends the information into the development of a chart to display the data. As you can see, the ability to develop and use dimensional charts is available in the WebI component. There are many other examples for the Web Intelligence reporting tool for BOBJ including variables, alerts, conditions, filters, and other parameters but these are just a few to offer some basic samples.

    Xcelsius Xcelsius is the component with all the bells and whistles for dashboarding in the BOBJ environment. This toolset really takes the whole dashboarding process to another level. It has all the functionality that is required for a dynamic dashboard and it is very easy to use and understand.

    Now, that being said, it still requires that we configure the underlying source of data correctly so that the different indicators available can read the appropriate information.

    Xcelsius is a visualization tool for creating interactive visual models based on highly aggregated data sets. It uses a point-and-click design time environment that can easily be used by business users.

    No programming skills are necessary for creating Xcelsius visualizations, but knowledge about dashboarding is still a requirement. The following illustration shows the initial workbench for the Xcelsius product. As you can see, the object—Bar Chart—has been dragged and dropped into the worksheet.

    Notice to the right side of the screen you can see that very similar questions are being asked for the development and configuration of this chart type as were asked for the WAD.

    So, what comes around goes around and as I mentioned nothing that you learn from the development of the chart types in the WAD will go to waste. The information such as subtitles, titles, categories, and so forth are the same and should be treated the same.

    The different categories of charts and types are found on the left side of the screen. One advantage that Xcelsius has over the WAD is that it offers additional types of objects, some of which are shown on the left side of the preceding illustration. You can see that the ease with which you can use a Selector or a Tachometer, and its dynamic and robust displays separate the Xcelsius from WAD functionality.

    This component is very user friendly and is positioned to be used by the business users as well as the power users to develop the dashboards on the fly. As you can see, there is plenty to review and discuss when it comes to the configuration using Xcelsius, but for this general introduction, we are going to look at some of the possible results that you can achieve with Xcelsius.

    All the features that are available in the other components are also available via Xcelsius, such as live data connectivity to KPIs, the ability to leverage the Excel modeling component as shown in the preceding illustration, the worksheet can be an Excel worksheet , and, once you develop the dashboard, the ability to embed a dashboard into any Microsoft Office application, including PowerPoint presentations.

    You can display the developed dashboard via a portal, whether a BI portal or a corporate portal, and integrate SAP and non-SAP data into one dashboard. The integration of the SAP and non-SAP data still requires IT department assistance in most cases, but the integration of the data is much easier to work with and complete.

    When you are in the process of deploying Xcelsius for the enterprise, other considerations need to be taken into account in addition to all the guidance for OLAP universes and Web Intelligence.

    With Xcelsius, you need to use specific best practices to ensure they do not overload the Flash engine component that allows the Xcelsius to function with dynamic displays and interactive activities , thus jeopardizing a fast response time for the live dashboards. End users of dashboard applications typically have little patience for poorly performing dashboards, so it is critical that you bear in mind the following best practices:. This is where you really see the difference between the WAD and Xcelsius.

    The following illustration shows a finished dashboard generated by Xcelsius functionality. All in all, this is a very direct, easy-to-read set of KPIs being displayed as a dashboard. In Xcelsius the functionality is standard for this component. You can see in the following illustration, the projected sales growth has been adjusted to The following illustration demonstrates how the use of all the additional functionality available in Xcelsius can start to get us into trouble.

    As you can see, within this dashboard, we have the ability to show the forecast using the chart type radar. As we all look to migrate from our current reporting format to the newer format we always try to compare the newer items with the previous items and in this case I will also offer some comments to this effect in the areas that are really trade-offs such as the Crystal Reports versus Report Designer area but overall we will try to just outline the overall functionality.

    Also, in this case attempting to match reporting component to reporting component would be inconsistent with the approach that the business should take in terms of identifying the correct reporting functionality. Each should be viewed on their own value and functionality to the business.

    Now you can see that getting into too much detail would take us into another completely different avenue and the chapter would end up being twice the size. So the discussion will be high level and brushing over the functionality. As we always say, the devil is in the details, so using this section as an initial very general discussion of each component and then using other more detailed documentation to understand all of the complexities is a prudent approach.

    This section highlights the features of the WebI reporting tool and also gets into some of the configuration details. Now, remember, having a new reporting component will not mean that we are going to reinvent the wheel but using another toolset—BOBJ— rather than the SAP BI, we will be able to offer all of the same functionality plus some additional bells and whistles. Just that they will possibly use different terminology and access them in a different manner.

    The preferred approach is to use the BEx query in this case, the query is created as a definition using the BEx Query Designer and will probably never really be run for any business users as a report ; this approach is preferred for several reasons, one of which is the ability to use calculated key figures CKFs and restricted key figures RKFs that are created in the query definition.

    Since these are not found in the Infocube, the direct access method would not have access to these formulas. After the linkage between the two systems is complete, you need to understand what the mapping process is for the different objects within the BEx query.

    The Rows area of this query includes several characteristics, and the Columns area includes several key figures. On the left side, the actual cube structure is shown with the cube dimensions and different characteristics. The symbol for dimensions has three triangles and the symbol for characteristics has one triangle. If we focus on one portion of this query, we see the characteristics, dimensions, and variables for the customer dimension, shown in the following illustration. In the next illustration, you can see what happens to these objects when translated or mapped into the OLAP universe.

    In addition, each characteristic in the query results in a class with dimension and detail objects. In terms of the display attributes of a BEx query definition, we see that they are detail objects within the OLAP universe. If we look at this in more detail, we see that display attributes are InfoObjects that are logically assigned or subordinated to a characteristic.

    In SAP reporting tools, the display attributes can only be used in combination with the actual characteristic, which means the attribute Phone Number can only be shown in the SAP reporting tool in combination with the characteristic Customer.

    In addition, characteristics can be defined as navigational attributes in the BW cube, which then makes these attributes available for navigational purposes in the reporting tools; navigational attributes are treated identically to a characteristic. This can get a bit confusing to both the developers and also for the OLAP universe so the universes differentiate between the two and the functionality of the display versus navigational attributes goes with these objects over to the OLAP universe.

    When we build an OLAP universe on top of this BW query, it results in the elements shown in the following illustration. The cube dimension from BW results in a class in the OLAP universe for example, dimension Customer, not to be confused with the characteristic Customer.

    As mentioned, each characteristic in the query results in a class with dimension and detail objects. Also notice that each navigational attribute in the query results in a class with dimension and details objects navigational attribute Postal Code resulting in a class Postal Code with dimensions L00 Postal Code and L01 Postal Code.

    The next illustration shows the display attributes from characteristic Customer and how these display attributes are treated in an OLAP universe. Each display attribute for the characteristic results in a detail object for the corresponding dimension objects in the universe.

    In terms of the key figures used in a BW query, we can have up to three different sets of information: Numeric value of the key figure Unit or currency information Formatted value, representing the user-specific formatting The illustration here shows the result of two key figures in the OLAP universe.

    business objects web intelligence tutorial pdf

    Each key figure is represented with a measure object in a class Key Figures. In the case where the key figure is configured in BW with a unit, an additional dimension object will be added representing the unit information. Once this process of creating an OLAP universe is complete, we can step into the Web Intelligence Rich Client and create the report by dragging and dropping the information into the appropriate columns and rows. The following illustration shows the initial screen for the Web Intelligence Rich Client.

    Once you start working in this environment, you will find that a number of functions and tasks are similar to those in the BEx Query Designer in terms of formatting and display options.

    All of the components are found in similar navigational processes as the BEx Query Designer—either in the right-click context menu or in the top toolbar, where you click and choose what you need to work on. This is the primary ad hoc reporting and analysis product for casual business users in the BOBJ components. Web Intelligence is a complementary tool to leverage outputs, for the casual and business user, that might have been derived from a deeper analysis achieved in BEx Analyzer. If we look at the overall reporting strategy and identify the areas and requirements that the WebI can fulfill, we have a fairly well-defined list.

    First, this component allows the business user to have a combination of ad hoc reporting and analysis primarily directed to the casual user. Third, this reporting tool also allows multiple sources of data, both SAP and non-SAP, to be integrated into the same reporting display. Fourth, all the functionality available in the BEx Web Analyzer is available in the WebI component, such as the ability to schedule and publish reports to a distribution list of users, and the ability to modify a report on-the-fly on the Web, save it, and then review or refer back to it in the future.

    Fifth, Web Intelligence also has all the user-friendly navigation capabilities that the BEx Web Analyzer has in terms of drag-anddrop navigation, context menu functionality, and the ability to switch information into a better format for the analyst.

    All of these components look at the actual information in the report, but in addition to these functions, Web Intelligence also has the ability to allow the business user to change the format of the report on the fly, adjust charts and table format, add conditions and exceptions, and adjust the positioning of all of these objects within the report. The illustration extends the information into the development of a chart to display the data.

    As you can see, the ability to develop and use dimensional charts is available in the WebI component. There are many other examples for the Web Intelligence reporting tool for BOBJ including variables, alerts, conditions, filters, and other parameters but these are just a few to offer some basic samples.

    Xcelsius Xcelsius is the component with all the bells and whistles for dashboarding in the BOBJ environment. This toolset really takes the whole dashboarding process to another level. It has all the functionality that is required for a dynamic dashboard and it is very easy to use and understand.

    Now, that being said, it still requires that we configure the underlying source of data correctly so that the different indicators available can read the appropriate information. Xcelsius is a visualization tool for creating interactive visual models based on highly aggregated data sets.

    Components of SAP businessobjects (BOBJ) for reporting - SAP BI

    It uses a point-and-click design time environment that can easily be used by business users. No programming skills are necessary for creating Xcelsius visualizations, but knowledge about dashboarding is still a requirement. The following illustration shows the initial workbench for the Xcelsius product.

    As you can see, the object—Bar Chart—has been dragged and dropped into the worksheet. Notice to the right side of the screen you can see that very similar questions are being asked for the development and configuration of this chart type as were asked for the WAD.

    So, what comes around goes around and as I mentioned nothing that you learn from the development of the chart types in the WAD will go to waste. The information such as subtitles, titles, categories, and so forth are the same and should be treated the same. The different categories of charts and types are found on the left side of the screen.

    One advantage that Xcelsius has over the WAD is that it offers additional types of objects, some of which are shown on the left side of the preceding illustration. You can see that the ease with which you can use a Selector or a Tachometer, and its dynamic and robust displays separate the Xcelsius from WAD functionality. This component is very user friendly and is positioned to be used by the business users as well as the power users to develop the dashboards on the fly.

    As you can see, there is plenty to review and discuss when it comes to the configuration using Xcelsius, but for this general introduction, we are going to look at some of the possible results that you can achieve with Xcelsius.

    All the features that are available in the other components are also available via Xcelsius, such as live data connectivity to KPIs, the ability to leverage the Excel modeling component as shown in the preceding illustration, the worksheet can be an Excel worksheet , and, once you develop the dashboard, the ability to embed a dashboard into any Microsoft Office application, including PowerPoint presentations.

    You can display the developed dashboard via a portal, whether a BI portal or a corporate portal, and integrate SAP and non-SAP data into one dashboard. The integration of the SAP and non-SAP data still requires IT department assistance in most cases, but the integration of the data is much easier to work with and complete.

    When you are in the process of deploying Xcelsius for the enterprise, other considerations need to be taken into account in addition to all the guidance for OLAP universes and Web Intelligence. With Xcelsius, you need to use specific best practices to ensure they do not overload the Flash engine component that allows the Xcelsius to function with dynamic displays and interactive activities , thus jeopardizing a fast response time for the live dashboards.

    End users of dashboard applications typically have little patience for poorly performing dashboards, so it is critical that you bear in mind the following best practices: Make sure that you pull in only the data that you absolutely need and must display in the dashboard.

    Xcelsius dashboards run within the Flash engine inside the browser, which is not designed for aggregating data, performing large mathematical calculations, or processing large data sets that require a large amount of memory. The guideline for data volume is to try to keep your data set ideally to rows, 5, rows maximum.

    To guarantee fast response times, you may need to create highly specific BEx queries to base the universes on, and keep the universes small; or at the very least, keep the number of key figures low to increase query performance. Be smart in how queries are initiated. If the dashboard has multiple tabs, try to pull in data for subsequent tabs only when those tabs are accessed.

    Running all the queries on initial load can delay the moment the dashboard first displays, which may be longer than an end user is willing to wait.

    Splitting the queries up between tabs can make the dashboard far more responsive. Push aggregation down to BW. This is a proven and industry-standard strategy to keep the data sets small and make queries run fast. Expectations around the response of dashboards are very different from refreshing operational reports.

    Where a live query is not feasible, LiveOffice is a good option. However, the LiveOffice documents should also be optimized to ensure good dashboard performance.

    A number of product issues have been enhanced, so the latest Fix Packs provide all the resolutions for issues identified earlier. This is where you really see the difference between the WAD and Xcelsius.

    The following illustration shows a finished dashboard generated by Xcelsius functionality. This dashboard uses all the different concepts and rules described in the previous chapters: The title of the dashboard is very straightforward—Annual Sales by Region vs Top Competitors. We can review the current actuals, then navigate to or execute a what-if analysis directly from the present screen.

    Very direct chart types enhancements are used. The dynamic component of this is that we can really see the difference in the coloring and highlighting that are available in this dashboard. The chart at the bottom right has a very interesting approach to showing the current actual sales versus the forecast sales.

    The same information is displayed using two different chart types in the same chart. It actually works in this case and shows a dramatic difference between the actual data and the forecasted data. This uses the concept that we talked about to draw the business users, attention to the critical KPI first before viewing the remaining information. All in all, this is a very direct, easy-to-read set of KPIs being displayed as a dashboard.

    In Xcelsius the functionality is standard for this component. You can see in the following illustration, the projected sales growth has been adjusted to The following illustration demonstrates how the use of all the additional functionality available in Xcelsius can start to get us into trouble.

    As you can see, within this dashboard, we have the ability to show the forecast using the chart type radar. Can you figure the forecasted sales information within 20 seconds?

    It is possible but not as easy as in the previous dashboard. Even in this case, the ability for the chart type to shift with the changes using the what-if process is unique. The following illustration shows the result of moving the slider from The following illustration shows another example of what Xcelsius can do. The dashboard has three KPI screens and, instead of scroll bars, buttons are available at the top of the screen to support quick switching from one screen to another.

    As for the actual dashboard, you can see that each quarter is displayed individually, but the rightmost button enables the business user to see all four quarters in one screen.

    Clicking the Growth button at the top displays information for all four quarters for revenue growth. This changes depending on what bar you click, and that information will show up on the left. Even though this dashboard has only one KPI, it demonstrates the ability to make a very basic dashboard useful and dramatic.

    Each of the other two buttons also shows a basic chart type—one displays a pie chart and the other displays a line chart, as shown in the following two illustrations, respectively. The final example, shown next, is a very different type of dashboard, a complete what-if calculator.

    Similar articles


    Copyright © 2019 trovotinuldes.tk.