Customer-specific maintenance means that SAP provides solutions for known problems while the customer pays for the assessment of new issues and problem solving. At this point, JDK 1. For this reason, security patches are no longer delivered for JDK 1. SAP NetWeaver 7. The Java 7. The ABAP 7.
|Published (Last):||14 January 2011|
|PDF File Size:||2.59 Mb|
|ePub File Size:||17.2 Mb|
|Price:||Free* [*Free Regsitration Required]|
With BusinessObjects 3. This meant that a person modeling data in BusinessObjects had to pay attention to which BusinessObjects tool and BW interface they were using.
For example, an Xcelsius now known as Dashboard Design dashboard and a Web Intelligence report that use the same BW data set might display different performance characteristics because they use different interfaces.
Figure 1. The interface story as of BW 7. Third-party tools as well as version 3. BusinessObjects 4. Source: SAP Interfaces are important from a performance as well as a functionality perspective. Multidimensional expressions MDX is a language for writing analytic queries on multidimensional databases. MDX on BW is not fast but works well for queries that return small amounts of data.
However, MDX slows to a crawl or fails when the data set returned by a query grows large. This sort of larger dataset is exactly what BusinessObjects Universes and applications often require to support analytic calculations.
In reaction to these performance issues, SAP developed a SQL interface add-on component, which delivers a much higher performance on large data sets but suffers from functional drawbacks such as lack of support for BW hierarchies or noncumulative key figures.
That scenario works though not great, according to some for relational universes, which are table-based in nature and therefore not so concerned with the BW features missing from the SQL interface.
With BW 7. SQL-based access to BW data was included, so it no longer required an add-on. Further, BusinessObjects moved toward more consistent technical and user-facing interfaces to BW data. For BW-specific semantic concepts such as hierarchies and display attributes, the user interface took a more consistent approach across the BusinessObjects product line. The 4. This interface was developed solely by SAP and is not available to third parties.
These applications need to be able to transfer a lot of data from BW to the client, but they also need access to the OLAP functionality that BW provides, which includes hierarchies and noncumulative key figures. The BICS interface goes a long way toward meeting these requirements. Not all applications currently support all of these features, but the goal of a unified feature set is in sight.
As BusinessObjects moves on to these updated user and technical interfaces more exclusively, many of the struggles that data modelers faced with these applications under the 3. Figure 2. The current structure of BusinessObjects-BW integration. This illustrates the current types of connections available between BusinessObjects applications and BW on BusinessObjects 4.
This was incorrect. Integration challenges remain Still, there is a long way to go. Universes in the new BI 4. SAP indicates that this capability is on the roadmap for a future release , so it is an area to watch. Many customers believe that third-party BI tools currently outperform BusinessObjects in mobile and visualization capabilities. BW would be more attractive as an enterprise data warehouse if it supported an open, high-performance BI reporting interface.
This situation, which was workable but difficult in the BusinessObjects 3. This area will be one to watch in future updates as SAP continues delivering improvements. Dig Deeper on SAP business intelligence.
Search Results for "sap-bw-7-4-practical-guide"
Search Results for "sap-netweaver-bw-7-3-practical-guide"