Business object detect the solutions for business professionals which could be beneficial to gain data from the corporate database directly from the desktop.
SAP Business Objects is a business intelligence tool that provides the combination of analysis, reporting and querying intended to find instant answers to the business related questions and help management improve their decision-making process.
Business object can be considered as integrated analysis, reporting and query for the purpose of finding solution to some business professionals that can be helpful for them to retrieve data from the corporate databases in a direct manner from the desktop. This retrieved information can be presented and analyzed within a document that of business objects. Business objects can be helpful as an OLAP tool by the high level management as a major part of Decision Support Systems.
BusinessObjects Data Services provides a graphical interface that allows you to easily create jobs that extract data fromheterogeneous sources, transform that data to meet the business requirements of your organization, and load the data into a single location
I worked for a US based health-care distributor who delivers pharmaceuticals to various retails and institutional providers across North America. Depending upon the sales made, the company offers different kinds of rebates to its customers.
Broadly speaking, the aim of our project was to build a rebate calculation application for the company through which we can calculate rebates accurately and present real-time state of the system to the business so that losses incurred on inaccurate rebate calculation are minimized and decision making can be improved by viewing more realistic reports.
This was an agile project & I was involved in the development team of the scrum.
My tasks were bringing data into SAP HANA system from various sources and develop data models over this data. Then, over the calculation views created in SAP HANA, I used to build universes in IDT depicting different scenarios needed for reporting.
And finally, I used to build reports in SAP Business Objects utilizing these universes. These reports were the end product of our project. The top management used to consume these reports for better decision-making.
There are many advantages in making use of business objects and they are
- User friendliness
- Business terms that are familiar
- Graphical interface
- Deployment of documents on an enterprise basis by making use of WebI
- Dragging and dropping
- Powerful reports for a lesser amount of time.
There are various kinds of products related with business objects and they are
- User module
- Set Analyzer
- Info View
- Business Objects – Software Development – Kit
- Broadcast Agent
We have the following type of tools under SAP BO BI 4.0:
- Business User tools – Business user tools are the ones intended for a business user (example –HR manager or a financial manager of any organization) which help them to view and manage business reports to aid them in a decision-making process.
- Data manager tools – They are used to design a sematic layer between the designer tool and its source of data.
- Designer tools – It provides the facility to design a query based on your reporting requirement.
Designer is a module related with Business Objects IS used by the designers for creating and maintaining universes. Universes can be considered as semantic layer that can isolate the end users from the various issues that are technical and related with the structure of database. Universe designers has the possibility for distributing the universes to the end users after moving these as file through the system of files or can be done by exporting the files to the repository.
This can be achieved through BI launch pad.
BI launch pad is a SAP BO BI 4.0 business user tool used for broadcasting the reports. It provides an interface to the SAP BO business intelligence platform repository that enables us to navigate to view & manage our business intelligence documents. It is a web based application/portal from where we can access the reports and organize the reports as per our need.
There are especially two different kinds of modes associated with these platforms, they are
- Enterprise mode
- Workgroup mode
There are two different methods related with multidimensional analysis available inside BO and these methods are
The result of the query is the final report. A report is a business representation of the data.
There are various different kinds of users associated with business object, they are
- General supervisor
- Graphical Interface
- Supervisor Designer
- End User
- Versatile User
We would choose SAP BO Dashboards in this scenario.
There are various kinds of data providers available for the business objects and they are
- Stored procedures
- Queries over universe
- Free hand – SQL
- VBA procedures
- OLAP servers
- Personal data files
We can go with webi in this scenario.
This 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 good – bad result.
We would go with ‘SAP crystal reports for enterprise’ in this case as it gives very powerful formatting options.
Personal connection can be created only by a single user and it can’t be made used by others. The details regarding such a connection can be usually stored inside PDAC.LSI file.
There are three different kinds of connections available:
- Personal connection
- Shared connection
- Secured connection
Personal connection is the one which can be used by you only i.e. this connection is available to only the user who creates it. No other user has access to use this connection. We have a PDAC.LSI file where the connection details are kept in case of a personal connection.
Next, comes is the shared connection where all the users can access the connection. We have a shared server in this case and the connection details are kept in SDAC.LSI file.
The limitation of shared connection is that we can’t establish rights & permissions over the objects. Also, we cannot export the universe to a central repository in case we are using a shared connection.
The last type of connection available is secured connection which can be shared between the users and we can also set rights & permissions in CMS (central management server). in this case.
Additionally, we can export the universe to a central repository in case we are using a secured connection. Secure connections are saved in the repository.
This is a kind of connection that is usually made used by other user via a server which is shared one. The details regarding the connection can be stored within the SDAC>LSI file which can be found within the installation folder of the business objects.
In my project, we were using secured connection as we were working in a team and also the reports had to be shared between the cross-functional team.
We had to create BO reports over the IDT universe and publish these reports. When it comes to a live project, the secured connection is the best kind of connection to use because here we can limit the access to different users. Also, secured connection can be accessed from different servers.
The last and main reason of using secured connection is that since it is saved in a repository, so if your requirement is to publish the reports over repository, you will have to use 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 with this kind of connection can be set over documents as well as objects. Universes can be brought inside central repository only by making use of secured connection. The parameters regarding these connection care usually saved inside CMS.
A universe is a logical layer between backend and a front end of the reporting. It is a metadata layer which isolates the technical complexities of the source system from business user/report developer.
In the universe, the required attributes and measures are picked up from the backend and arranged in a way we want to use them further for reporting. In my project, we used to create IDT universe on top of calculation views developed in HANA. These IDT universes were further utilized to create BO reports.
The custom hierarchies can be used for defining the universe for facilitating drill down that is customised and can happen between objects from different or same classes considering the user requirements.
In IDT, the universes get created with “.unx” extension. It is stored in the form of a file.
The custom hierarchies can be created by following the path tools ->hierarchies in BO designer.
Context can be defined as the particular path of join between a specific group of joins or the tables for the purpose of a particular query. A particular object that can be found inside the column of a table, belonging to particular context is supposed to be compatible to all the various kinds of objects belonging to the same context. In the case of objects that are from the various kinds of context, different kinds of SQL can be generated, and the results can be merged inside micro cube. This is for making sure that there is no incorrect result associated with a loop or any other kind of issue related with join path.
Once universe is created, we publish the universe using a secured connection and then import the universe in BO to make a report on top of it.
Context can be created by making use of feature associated with context or by manual procedures. The context are usually created by making use of logical calculation or based on the business requirements. The detect context may not be much useful in this case and so it should be done by making use of manual procedure.
The reason for opting webi was its user-friendly interface, the better way of presentations, ad-hoc analysis and advanced reporting capabilities. These features are lacking in other reporting tools like crystal reports, BeX analyzer, and WAD.
Chasm trap is a condition that arises when the values inside the fact table get inflated at the time of measuring the values from two different fact tables by considering the dimensions inside dimension table.
Chasm trap should be solved by making use of two different methods.
- In the case of SQL parameters in universe, the option generates numerous queries for each and every measure that needs to be chosen. This helps in generating SQL statement for every measure and gives the correct results.
- Another approach is to include two joints in different contexts, where the problem will get solved by generating two synchronized queries.
We have two such methods in BO:
- Slice and Dice method
- Drill down method
Using SQL queries from the database level, Derived tables are created in the universe. The columns of the derived table will be the columns selected in the query. Derived table can be used in the complex calculations which are difficult to be achieved in the report levels. Using a dblink, tables can be accessed from a different schema, is another use of derived tables.
User objects is a universe of classes and objects which is created by the universe designer. Once the objects consisted in the universe does not matches your necessities, then the user can create his own objects called User objects.
The @prompt function asks the end user to enter any specific values. The Visual Basics for applications macro’s results will be recovered by using @Script function. An existing statements SELECT statement can be re-used by using @Select function. For a name or variable, the value assigned to it will be referenced using @Variable. An existing object’s where clause can be re-used by @Where functions.
There are three Domains in Business Objects and they are:
Using @Derived_table function, we can access one derived table from another. The syntax is as ,
@derived_table(the derived table name)
Slice works with the master or detail reports and it is used to rename, reset and delete the blocks.
We will go with business objects explorer in this case. It acts like a business objects search engine. We can search anything through a keyword search box in the explorer and all the information spaces appear in the result where that particular keyword exists.
Large blocks of data can be split into sections by using master/detail report. Repeating values can be avoided by using this and also the subtotals can be displayed.
The class can be defined as a collection of objects in a universe. Subclasses can be derived from classes and using these classes and the subclasses, we can create a hierarchy.
There are three approaches available for linking the universes and they are:
- The Kernal approach.
- The Master approach.
- The Component approach.
Data mining is the process through which you can extract the required details from the database, which can be made used for making conclusions.
Drill modes helps to analyze data from different angles and different state of details. The available Drill modes are;
- Drill up.
- Drill down.
- Drill by.
- Drill through.
when we have a same fact tables in different grains,we use aggregate_awarness function to define one object for measures in fact tables.the syntax is as,
A one to many join links to a table which respond with another one to many join links is called fan trap.
The query or the data source is called as the data provider.
Context is created when the dimension objects are present in one or both fact tables.
Only the users within the group can be accessed in this mode.
There are five different schemas supported by Business Objects designer and they are:
- star schema.
- Snowflake schema
- Multistar schema
- Normalized production schema.
- Data warehouse with aggregates.
Channel is a website with ‘push’ technology. It is to make the users know up-to-date information. Each and every Business Objects channel will be associated with a broadcast agent, who can have several channels.
User objects are not shared with other end users. It is stored in a specific user object definition file. So if any end-user tries to refresh or edit the query contains another user’s user object, it will be automatically cleaned and removed.
The main components it consists of are:
- The table browser.
- The structure pane.
- The universe pane.
To maintain the version documents according to the user profiles, we use report bursting.
Web intelligence is a solution that is specialized in supporting the decisions related with queries, reports and analysis.
Decision Support Systems.
To automatically extract structural information from database or from a flat file we use a script known as strategy.
It is a set of objects and classes.these objects and clss es will be intended for an application or a group of users.
Secured mode restricts the access of specific users over specific commands.
Using drill by we can move to other hierarchy and analyze the other data, which belongs to another hierarchy.
It is file which contains the data values associated with an object.
It is called as ‘BI workspaces’ in BO BI 4.0 platform.
There are many users who are comfortable in using only Microsoft office products. They need business reports in Microsoft office products like Microsoft excel and all. For those users, we have SAP BO Live office tool.
No, it is not necessary for a company to buy all the tools that come under SAP BO platform. SAP provides the customization packages under which the company can buy only the tools which are needed.
The different data source scan is SAP BW, OLAP, application database, customer database, Text file, XML file and Web service.
The universes which are designed in UDT are UNV universes whereas the universes which are designed in IDT are UNX universes. In UDT we don’t have multi-resource universes enabled whereas in IDT we have this option. IDT is enhanced and more organized as compared to UDT.
No, the tools like crystal report for Enterprises, Dashboards, BO explorer does not support UNV universe (designed by UDT). It supports only UNX universe (designed by IDT). Web Intelligence is the only tool which supports both the universes – UNV and UNX.