instruktsiya.info Business Business Objects Tutorial Pdf

BUSINESS OBJECTS TUTORIAL PDF

Wednesday, April 17, 2019


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:BARRIE RODRIQUEZ
Language:English, Spanish, German
Country:Iraq
Genre:Science & Research
Pages:142
Published (Last):14.01.2016
ISBN:238-9-24217-708-4
ePub File Size:22.72 MB
PDF File Size:15.16 MB
Distribution:Free* [*Regsitration Required]
Downloads:41501
Uploaded by: BLYTHE

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 instruktsiya.info Intelligence. Rich Client. Business Objects . Saving to Other File Formats ( Excel, PDF, CSV, and Text). .. Select SAP Business Objects Web Intelligence.

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.

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.

SAP BusinessObjects Tutorial – PDF Training Materials

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.

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.

SAP BI Related Tutorials

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: 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.

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

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 Loop is a Drawback in reporting.

Because of Loop, reports will display the data in Time Slash. Finding the possible loops in Universe structure panel is called as Detecting Loops.

Detect Loop is the option used in Universe to find possible Loops. To resolve the Loops we can use 4 techniques in Business Objects. Delete Unnecessary Joins: In Industries most of the reports are created using Transaction based master data. By deleting J3, if business requirements can be satisfied then delete J3 join. Second Solution: Create Alias Table: As the memory is already created in BO Repository Data retrieval, is possible.

This is divided in to 3 areas as: Security Domain Area: Universe Domain Area: Document Domain Area: Document Domain Area is the area where created documents are saved to be accessed by client environment with corresponding Authentications. A class is the presenting Object in Universe to present Business Information to the reporting Environment.

A class is assigned with one or more Tables information to be presented to the Reporting layer. A class represents Schema in Universe. A class is a collection of Objects. Ob jects represent a table column for reporting.

Simply, reporting columns in Business Objects are called as Objects. Dimension Object: It is the default property applied for every database column added inside the class. This property can be assigned with all data types of source database to display source business data as it is. Detail Objects: Using this property we need to select a parent Dimension Object. While reporting detail object is also added with parent dimension object automatically. Measure Objects: This property is appled only for Numeric Columns added with corresponding Aggregated functions to display summary information in the reporting.

Hierarchy is collection of Dimension objects arrangement to support Drill Down and Drill Up functionalities. In hierarchies we can find two options as. All objects added under the class panel are displayed as Default Hierarchies.

Based on these default hierarchies we can create required Custom hierarchies to support RRI Concepts. Report to Report Interactions. Using this option, the. Posted by Unknown at Email This BlogThis! Sunday, March 17, Business Objects: Basic Question and Answers. Business Intelligence is a technology used for preparing the reports for multidimensional analyses. The following are the responsibility assigned to administrator. Installations and configurations in a distributed environment.

Creating the BO Enterprise Repository. Performing back up and recovery of Metadata. Tuning the servers. Deployment of reports. Once the Interface has designed it should be regressively tested before giving to the end user population. To design the interface and architect having good knowledge on database under standing the report requirements.

Design the Reports according to the report requirement templates. Testing the each report with following types of tests. Unit Testing. System Testing. Performance Testing. When install the XI R2 following products get installed: Business View Manager. Business Objects enterprise. Net administration launch pad. Business objects Enterprise.

About Anson

Net Info view. Designer desktop intelligence. Central management console. Universe builder. Designer is a Business Objects IS module used by universe designers to create and maintain universes. Universes are the semantic layer that isolates end users from the technical issues of the database structure. Universe designers can distribute universes to end-users by moving them as files through the file system, or by exporting them to the repository.

Universe provides a semantic layer between you and the database. It consists of classes and objects named in business terms. It is basically a mapping of table and the columns in the database to classes and objects respectively in the query panel.

Alternatively, It is logical mapping of data in business terms. In the Business Objects User module, universes enable end users to build queries from which they can generate and perform analysis. Universes isolate end users from the complexities of the database structure as well as the intricacies of SQL syntax. Universe will be created using designer.

Using this classic universe we can create web intelligence reports, desktop intelligence reports, crystal repots. Universe Parameters. Import Tables. Import Joins. Define hierarchies.

A universe parameter defines the name of the universe and connection to the target database. The first step in creating a universe is to specify its parameters.

These parameters include the definition of a universe, which is comprised of: You enter universe parameters from the Universe Parameters dialog box. This dialog box also lets you set up database options, external strategies, graphic options, and print settings.

With the Check Integrity command, you can test the structure of your active universe. This means testing to determine whether its components are accurate and up-to-date. Check Integrity serves the following purposes: It detects any inconsistencies in the objects, joins, conditions, and cardinalities of your universe. It detects whether there are any loops in the joins. It determines whether changes were made to the database to which the universe is connected.

Using check Integrity, u can check the universe. If the data provided is from two different data providers then we can link those two universes, such type of universe is called Linked Universe. A multi dimensional analyses is a technique to modify the data so that the data can be view from different prospective and at the different levels of details. The following are the features of multidimensional analyses: Drill Down For more details. Drill Across Like from year to different cities.

SAP BusinessObjects Data Services Tutorial

You can view Business Objects documents in the following formats: Enhanced Document Format. Business Objects Format. There are 2 types: Enterprise Mode, Workgroup Mode. Designer lets you save universes in either enterprise or workgroup mode.

Enterprise mode means that you are working in an environment with a repository. Workgroup mode means that you are working without a repository. The mode in which you save your universe determines whether other designers are able to access them. By default, a universe is saved in the mode in which you are already working. For example, if you launched a session in enterprise mode, any universe you save is automatically in that mode. If we want to make a universe accessible to another designer working without a repository, then click the Save as Workgroup check box in the Save as universe dialog box.

Designer provides three types of connections: A universe can be accessed by multiple users and can send multiple queries to the database. A Join is a relationship that explains how the data in one table relates to data in another table. The following are the types of Joins: Inner Joins.

Left outer Joins. Right outer Joins. Full outer Joins. Theta Join. Short cut Join. A join is a relational operation that causes two or more tables with a common domain to be combined into a single table.

The purpose of joins is to restrict the result set of a query run against multiple tables. A Theta join links tables based on a relationship other than equality between two columns. A macro is a series of commands and functions that are stored in a Visual Basic for Applications module and can be run whenever you need to perform the task. If you perform a task repeatedly, you can automate the task with a macro.

You create macros using the Visual Basic Editor. Loop is a situation that occurs when more than one path exists from one table to another. Loops result in ambiguity in the design of a universe. Designer enables you to identify loops in one of two ways: You can run the Check Integrity function, which indicates the existence of any loops.

You can select the Detect Loops command from the Tools menu. If there are loops, the Loop Detection viewer appears; it indicates the joins causing a loop. An alias is a logical pointer to an alternate table name. The purpose of an alias is to resolve loops in the paths of joins. In some cases, more than one alias may be necessary for a given table. As you create aliases, Designer may prompt you to create other aliases.

This occurs when the new aliases result in the need for additional aliases; in other words, creating such aliases entails the propagation of other aliases.

In such a situation, two options are available to you: Designer displays an alias in the Structure pane as a table. It links an aliased table to existing tables, re-arranging joins, as necessary. You can resolve loops in two ways: The first step in resolving loops is to detect the cardinalities of the tables.

Yes, you can use contexts and aliases in the same universe. In fact, in many cases you should use them together. One to Many. One to One. Many to Many. All you probably need to do is install and uninstall add-ins that are sent to you. Designer provides four types of functions: Number, Character, Date and Functions. Functions beginning with the character are BusinessObject functions that render the definition of objects dynamic and database-independent.

In the Query Panel, this type of object causes a message to appear that prompts the end user to enter a specific value. The qualification of an object reveals how it can be used in multidimensional analysis.Select the active case series filter before selecting data mart fields for your report. The relationship between object in the hierarchy is one — to — many. This property can be assigned with all data types of source database to display source business data as it is.

Universe Domain — Consists of 24 database tables used to store universes. In general, the name of a class reflects a business concept that conveys the category or type of objects. Table Formatting Options for Data in Reports Format Description Default The default format is the format of the report item before any formatting is applied.

If I were to look at just one item for comparison—the ability to use changes that have been made to the underlying query that supports the formatted report—I would immediately give the nod to Crystal Reports.

IDALIA from Kansas
Please check my other posts. I enjoy lancashire wrestling. I do love exploring ePub and PDF books youthfully.