BI7.0全英文开发指南：数据仓库工具详解

需积分: 14 155 浏览量更新于2024-08-02 收藏 6.19MB PDF 举报

"BI7.0综合教材（全英文）"是一本专门针对企业数据仓库（EDW）场景的开发指南，它涵盖了SAP NetWeaver 2004 SP7环境下的商业智能（BI）工具和技术。该教材详细介绍了如何利用这些工具来设计、构建和管理复杂的商业智能解决方案，以便于用户能够对企业的关键业务数据进行深入分析和可视化。书中涉及的主要内容包括但不限于： 1. **开发者指南**：这部分着重于向开发人员提供详细的开发流程和最佳实践，可能包括编程接口、数据模型设计、ETL（Extract, Transform, Load）过程以及数据仓库架构的搭建。 2. **SAP NetWeaver 2004 SP7**：作为基础平台，该部分解释了如何在SAP的企业应用环境中集成BI功能，如SAP BusinessObjects等组件，以及如何利用其功能来实现数据仓库的高效管理和性能优化。 3. **Enterprise Data Warehousing**：这部分深入探讨了数据仓库的设计原则、技术选型（如星型或雪花模式）、数据质量管理、数据安全和性能调优策略，以及如何确保数据一致性与可靠性。 4. **文档版本3.00 - March 2006**：表明这是教材的一个历史版本，反映了当时的BI技术和标准，可能包含对BI 7.0早期版本的对比和迁移指南。 5. **联系信息**：提供了SAP AG的地址和联系方式，对于寻求技术支持或获取最新更新的用户来说，这是一个重要的资源。 6. **版权和许可**：强调了所有内容的版权保护，并指出未经SAP AG明确许可，不得复制或传播任何部分。同时，提到了涉及的一些软件产品及其商标归属，例如Microsoft、IBM、Oracle等，这些都是BI7.0教材中可能引用的重要厂商技术。 BI7.0综合教材旨在帮助IT专业人员掌握最新的BI工具和方法，通过结合SAP NetWeaver 2004 SP7的特性，提升企业决策支持系统的效能。对于任何希望在数据分析和可视化领域深入学习或者进行项目实施的人来说，这是一本不可或缺的参考资源。随着时间和技术的发展，书中可能的部分内容可能已经过时，但其基本原理和框架仍然是理解现代BI系统的关键。

Core Development Tasks March 2006

Developing Business Logic

Enterprise Data Warehousing 11

How you model the folder for non-cumulatives in the BI system depends on your scenario.

For more information, see Non-Cumulatives [Page

392].

Developing Customer or Partner Content

You can develop your own BI Content and deliver it to your business areas. You can also

make limited modifications and changes to BI Content.

For more information about developing your own BI Content, see Customer and Partner

Content [Page 419].

Implementing Routines

BI allows you to implement routines for transferring data. In this way, you reproduce your own

business logic.

For more information, see Routines During the Transformation [Page

236].

In addition to the new transformation concept, you can still use the 3.x concept of transfer and

update rules.

For more information, see

● Start Routines in Transfer Rules [Page 262] and Creating Transfer Routines [Page 263]

● Update Routines and Start Routines [Page 297] and Creating Update Routines [Page

301]

Prerequisites

Developing Customer or Partner Content:

Before you can develop customer and partner content, you may need to apply for your own

namespace. This requires you to have an ABAP development license (ABAP/4 Development

Workbench License).

4.1.1 Recommendations for Modeling Layers

Modeling a Data Warehouse Layer:

● If you are extracting data from heterogeneous source systems, we recommend that you

model a data warehouse layer as an intermediate layer for consolidating the data. You

use DataStore objects for this purpose.

● If you want to store data in the BI system at document level, we recommend that you

use DataStore objects to build a data warehouse layer. The data that is stored there is

only slightly denormalized and is stored at a useful level of granularity.

● The granularity of the data in the data warehouse layer should correspond to the

granularity of the data as it was when obtained from the extractor.

● So that information relevant to operational reporting is retained, the data is not

aggregated in the data warehouse layer.

● The extractors for transaction and master data should be delta enabled.

● The data should contain the whole history.

Core Development Tasks March 2006

Developing Business Logic

Enterprise Data Warehousing 14

3. The data is updated to the architected data marts and saved there in an InfoCube in

aggregated form. The InfoCube provides reporting-optimized access to the data and

allows multidimensional reporting on aggregated data.

4.1.2.3 Modeling Without Persistent Data Storage

In this model, data is not stored persistently in the BI system but is read for reporting directly.

Simple Model with VirtualProvider

The data is read straight from the source system using a VirtualProvider.

Reporting Store

Any Source

Access to Information

Virtual-

Provider

Reporting using a VirtualProvider is a suitable alternative if:

● you need up-to-date availability of data from the source system

● you only want to access small datasets sporadically, and replicating the data into BI

would be too time-consuming in comparison

● only a few users execute queries simultaneously on the requested dataset.

As long as a suitable extractor is available, a query based on a VirtualProvider can replace

drill through to an SAP source system using the report-report interface. In both cases, you

obtain real-time data. However, a drill through uses an SAP query to present the data,

whereas a VirtualProvider uses a BEx query.

Restrictions:

● The source system must always be available.

● BI reporting based on VirtualProviders represents additional system load on the source

system. Performance is reduced further the more users are working with BI queries

based on VirtualProviders and the higher the level of aggregation for the queries.

● VirtualProviders do not support navigation attributes.

You can also use VirtualProviders with a prototyping process with the generic extractor. You

can also access non-SAP systems quickly and easily using DB Connect.

Since VirtualProviders do not require persistent data storage in the BI system, changes to the

structures (extract structure, transfer structure, transfer rules) in the whole staging process of

the prototype phase can be performed quickly.

剩余751页未读，继续阅读

xxh718500

粉丝: 0

BI7.0全英文开发指南：数据仓库工具详解

sap 官方BI7.0 教材

BI7.0权限设置

BI7.0教程：初学者如何加载BO特征数据

DB Connect Usage in SAP BI 7.0

SAP BI 7.0 Important T-Codes List

SAP BI 7.0 Demo and Overview of Features.ppt

SAP BI7.0初探：NetWeaver7.0与Business Intelligence概述

SAP BI 7.0关键事务代码大全

SAP BI 7.0中的DB Connect实施

BW7.0 教程

最新资源