SAP Business Objects ( BOBJ)

Category: SAP
Summary: 
Business Objects Business Intelligence (BI) platform provides flexible systems management for an enterprise SAP BI standard that allows administrators to confidently deploy and standardize their BI implementations on a proven, scalable, and adaptive service-oriented architecture.

SAP Business Objects (BO) 4.x suite is here with Seven major Enhancements.

  1. BO Universe (semantic layer) can now be sourced from multiple databases, overcoming a major obstacle of previous versions.
  2. Universe can now access MOLAP (cubes from Microsoft Analysis Services, Essbase etc.)
  3. Data sources directly via MDX without having to “flatten them out” first. In prior versions, Universe could only access SQL sources.
  4. There’s now a more common look and feel to individual BI products, including Crystal, Webi, Explorer, and Analysis (former BEx). This is another step in the right direction to unify SAP BI products, but it’s still not a complete solution. It will be a while before all SAP BI products are fully and seamlessly integrated, as well as other BI tools/platforms that grew more organically.
  5. All SAP BI tools, including Xcelsius (Dashboards in 4.x), that did not have access to BO Universe now do.
  6. There’s now a tighter integration with BW via direct exposure of BW metadata (BEx queries and Info Providers) to all BO tools.
  7. Improved BI/BW performance. This is the one I can’t validate until I talk with some customers. But SAP claims that, starting with 4.x, BW will have a unique set of proprietary SAP APIs that are 4+ times faster than APIs that are available to the other BI tools. I am assuming that what this means is that from now on, BW access by Business Objects will be faster than by any other BI tool.
  8. Last but not least, 4.x is the first version highly optimized for the HANA in-memory appliance. Previous versions and other BI tools will also work with HANA; that should not be the primary factor in your decision whether to upgrade to 4.x or not, but it’s indeed another variable in the mix. What does “optimized” mean in this case? Remember, all of your BI applications (with the exception of in-memory specific BI apps) were written and optimized for accessing disk-based RDBMS. Chunks of code that were written specifically for that purpose can now be removed, and that code can be optimized for direct memory data access. That’s indeed what SAP claims they did in version 4.x.

Course Duration : 45-50 hrs

Mode of Training: Live Instructor-led hands on Training

Start Date:  Saturday, 13 May 2017
Enrolment start date:  Friday, 01 July 2016
Cost: 850(USD)
Topics: 14