Sap bo technology and sapbo Technology

Sap bo technology and sapbo Technology

1. connection path problems:

-Loop

In relational database mode, a common join path that returns too few rows is called a loop. A loop is a group of joins. It defines closed joins of a group of tables in the pattern, for example:

Solution: Create an alias table (a copy of the base table ).

-Chasmtrap)

The fault trap is a common problem in the relational database model. The connection path returns more data than expected, A fault trap is a join path between three tables when two "many-to-one" joins in one table,

The context in the converged connection path is not properly separated, for example:

Solution: create a context for each fact table. This method applies to all situations.

-Fantrap)

Slice traps are common issues behind the fault traps in relational database models. Their impact is the same as that of returning more data than expected, when the "one-to-multiple" join link links tables connected by another "One-to-multiple" in turn,

A sector trap is a join path between three tables, such:

Solution: Create an alias table (a copy of the base table), create a new join between the alias table and the base table, and finally build the context.

 

2. What are the concepts, implementation methods, and advantages and disadvantages of derived tables and alias tables?

The derived table is similar to the database view, and the alias table is renamed in the Universe of the database physical table;

The derived table can flexibly process complicated data logic, but it is inefficient;

The alias table is set based on business needs and is generally used to solve the loop problem in Universe.

 

3. Key Points of Universe design and precautions?

Design Points:

A. Analysis and Planning of business problems Universe Solutions

B. Design Model

C. Construct Universe

D. Distribute Universe to users

E. Dimension objects are placed separately by Dimension

F. Place measurement objects by topic

G. The prompt corresponds to the dimension and topic.

Note: context, loop, fault trap, slice trap, base, and BO development specifications.

 

4. How to quickly analyze, locate, and solve BO report problems (TEST ):

 

5. Report performance optimization policies:

A. logical operations move to the backend, that is, the report layer moves to the Universe layer and the Universe layer moves back.

B. Add query conditions on the report to reduce the data volume returned for analysis.

C. Create a Materialized View

D. Avoid creating complex Universe. A Universe contains many fact tables and can be split as appropriate.

E. set multiple data requests for Parallel Data Query

F. Database optimization (Table Indexing and association conditions)

 

6. custom development:

The goal is to make it easy for customers to use. objects such as measurement, latitude, and filtering conditions should be made public and merged as much as possible, and named as easy-to-understand names, so that users can drag and drop combinations by themselves.

 

7. Variable creation:

Both Universe and WEBI reports can create variables, but Universe variables can be used in all reports of the Universe, while the variables of the WEBI report can only be used by the report itself.

 

8. Merge query, alarm, and dimension of WEBI reports:

Merge query is the Union operation in SQL. Each query must maintain the consistency of the number and type of query objects. Alarms are used for data warning. When the data meets certain conditions, specific content can be displayed as needed. Merge dimensions merge the same dimensions in multiple queries into one latitude. When a merge dimension is used in a report, the report searches for the latitude data of the corresponding Query based on the metric. However, if the report is complex, the merged dimension function may be disabled.

 

9. Under what conditions should I use multiple queries?

A. Different query themes

B. Low query efficiency

 

10. There is no problem when the SQL statement automatically generated by the report is obtained from the database, but the report result is incorrect because:

There is a problem with the database connection of Universe.

 

11. Context understanding:

A context is a set of joined sets, that is, the association relationship between a group of database tables. It provides a valid query path for the WEBI report so that the report can generate correct SQL statements.

 

12. Test: first, the BO consultant should perform the unit test on his own. The BO consultant must first ensure that the variables and logic made by BO are correct. Generally, data problems are mostly BW problems. Second, BO consultant and BW

The consultant performs integration testing together. Finally, the customer will be asked to perform the test after there are no problems in both aspects.

 

13. For the BO project with BW as the data source, the consultant focuses on the development report. Universe is automatically generated, so it does not need to spend too much work; before development, you must specify the report format and the type of BO report tool used with the customer.

The surrounding system (non-SAP system) is a data source BO project, focusing on the Universe design, first designing a correct and reasonable Universe, and then designing a report.

What is the difference between BW and BO in SAP?

Very different ~ BW is the data part (equivalent to Data Modeling and storage). BO is used to display the data front-end in BW (that is, the report part. BO has multiple report implementation tools)
1. sap bw refers to SAP Business Warehouse, that is, sap dw (Data Warehouse) referred to in SAP 7.0. Now everyone is called DW. If you are a BI engineer, you must know DW and BO.
2. sap bo is twists and turns. BO is a company called Business Object. At the same time, this company has a product called Business Object, which aims to provide dynamic reports and other commercial solutions, after being acquired by SAP, you can search for SAP to buy BO in Baidu to see the specific information.
3. At present, SAP has decided to integrate BO into the BOE framework. They only want to retain the basic BI report tools (BEx, the previous WAD does not support subsequent technical development. The BOE framework is the focus of SAP implementation. It contains multiple Report development tools, such as Business Object Dashboard, Crystal Report, and Web Intelligence.
SAP is currently moving towards their BPC (financial budget, consolidated reports), mobile business intelligence solutions (such as smartphones, Ipad, and other terminals), and BOE.
At present, there are a variety of Ipad front-end BI report tools on the market, I believe that the last two years are quite popular (thanks to the popularity of ipad)

What is the relationship between the BW module and BO in the sap erp system?

The question is incorrect.
BW is not a module in the sap erp system. ERP is ERP, BW is BW, And the relationship is parallel.
BW extracts data from the system for processing and sorting, and then forms a report. The company's management can understand the company's business situation based on the report content, so as to develop business strategies.
BO and BW are in the same relationship. They are also report tools. It is a product of business objects and subsequently acquired by SAP. Through the acquisition, SAP not only obtains the BO technology but also the BO customer base.
The reports made by BO are better in terms of functions and pictures than those made by BW. Therefore, most projects now use BW for data extraction and analysis, and use BO for data report presentation.