BW:Difference between BW 3.5 and BI 7.0
来源:互联网 发布:homer仿真软件 编辑:程序博客网 时间:2024/06/07 06:54
1. In Infosets now you can include Infocubes as well.
2. The Remodeling transaction helps you add new key figure and characteristics and handles historical data as well without much hassle. This is only for info cube.
3. The BI accelerator (for now only for infocubes) helps in reducing query run time by almost a factor of 10 - 100. This BI accl is a separate box and would cost more. Vendors for these would be HP or IBM.
4. The monitoring has been improved with a new portal based cockpit. Which means you would need to have an EP guy in ur project for implementing the portal ! :)
5. Search functionality has improved!! You can search any object. Not like 3.5
6. Transformations are in and routines are passed! Yes, you can always revert to the old transactions too.
7. The Data Warehousing Workbench replaces the Administrator Workbench.
8. Functional enhancements have been made for the DataStore object: New type of DataStore object Enhanced settings for performance optimization of DataStore objects.
9. The transformation replaces the transfer and update rules.
10. New authorization objects have been added.
11. Remodeling of InfoProviders supports you in Information Lifecycle Management.
12. The Data Source: There is a new object concept for the Data Source. Options for direct access to data have been enhanced. From BI, remote activation of Data Sources is possible in SAP source systems.
13. There are functional changes to the Persistent Staging Area (PSA).
14. BI supports real-time data acquisition.
15. SAP BW is now known formally as BI (part of NetWeaver 2004s). It implements the Enterprise Data Warehousing (EDW). The new features/ Major differences include:
a) Renamed ODS as DataStore.
b) Inclusion of Write-optmized DataStore which does not have any change log and the requests do need any activation
c) Unification of Transfer and Update rules
d) Introduction of "end routine" and "Expert Routine"
e) Push of XML data into BI system (into PSA) without Service API or Delta Queue
f) Intoduction of BI accelerator that significantly improves the performance.
g) Load through PSA has become a must. I am not too sure about this. It looks like we would not have the option to bypass the PSA Yes,
16. Load through PSA has become a mandatory. You can't skip this, and also there is no IDoc transfer method in BI 7.0. DTP (Data Transfer Process) replaced the Transfer and Update rules. Also in the Transformation now we can do "Start Routine, Expert Routine and End Routine" during data load.
New features in BI 7 compared to earlier versions:
i. New data flow capabilities such as Data Transfer Process (DTP), Real time data Acquisition (RDA).
ii. Enhanced and Graphical transformation capabilities such as Drag and Relate options.
iii. One level of Transformation. This replaces the Transfer Rules and Update Rules
iv. Performance optimization includes new BI Accelerator feature.
v. User management (includes new concept for analysis authorizations) for more flexible BI end user authorizations.
- Difference between BW 3.5 and BI 7.0
- BW:Difference between BW 3.5 and BI 7.0
- BW and BI
- BW
- BW
- BW
- BW
- BW:Transaction Codes in BI
- Communicate BW and ECC
- SAP BW 与BI的区别
- 更多关于SAP/BW BI的笔记
- BW:Interrupt Process & Decision Between Multiple Alternatives
- The difference between (()) and ().
- difference between "<" and "<<"
- BW:浅谈BW Authorization
- BW:小结:BW系统升级
- BW:BW与第三方BI接口设计与实现:APD、Open Hub、RFM
- BW--SAP BI的一些常用TCODE列表
- ~~
- Backus–Naur Form(巴科斯范式)
- 一个关于无边框拉大小的问题
- Java SE 6中 XML 数字签名的标准 Java 接口
- 了解C++默默编写并调用那些函数
- BW:Difference between BW 3.5 and BI 7.0
- 建立安全的AXIS服务(上)
- 为多态基类声明virtual析构函数
- SQL+C#打包问题
- 架构师备考准备
- 认识 p-unit : 一款开源的性能测试工具
- 这里的很不错啊
- 若不想使用编译器自动生成的函数,就应该明确拒绝
- 集成电路上面标的各种术语,留作翻译用