SAP BusinessObjects 4.1 has been in the wild now for nearly a year and there has never been a better time to upgrade. After some rough beginnings with the 4.0 release, BusinessObjects 4.1 provides a stable and reliable platform. There are lots of reasons to upgrade! New Functionality There’s a litany of new tools available with […]
The Information Design Tool or IDT is the new universe authoring tool for SAP BusinessObjects BI 4. This tool allows you to create the new UNX format universes that are required by some of the new BusinessObjects tools. However, if you want to do this using your Windows Active Directory login, there’s an extra step […]
During our presentation at the annual ASUG SAP BusinessObjects User Conference, we had some questions from the session attendees that asked about administration of the multi-source universes. To elaborate on the answers that were given at the conference, here is a quick overview of the tool that can help your companies SAP BusinessObjects Administrators maintain and monitor their multi-source universes.
As a company we are always trying to further our experiences, give back to the user community and solidify our place in the marketplace as experts throughout the SAP BusinessObjects suite. Having presented at user conferences in the past, we are always looking to continue that trend and submit abstracts for as may as we can. This year at the 2013 ASUG SAP BusinessObjects User Conference in Anaheim, Ryan Muldowney and I will be presenting a session on the best practices of when and where to combine multiple data sources.
The Information Design Tool is the brand new metadata modeling application used for creating universes in SAP BusinessObjects 4.0. The universe layer has been completely reworked for the 4.0 release and the Information Design Tool (IDT) is the front-end for those changes. The new model takes the traditional universe and breaks it down into three components: the Connection, the Data Foundation, and the Business Layer. These components all existed in some form in previous versions, but now they each get their own editor and a host of new features and options. Let’s review these in a bit more detail.
As an SAP BusinessObjects Channel Partner, we have been given the privilege and opportunity to engage in a pre-release version of the SAP BusinessObjects Enterprise 4.0 product stack for evaluation purposes. This is a very exciting time for us here at Altek Solutions as our Center of Excellence has already installed the software and is in the process of analyzing and evaluating the new features that 4.0 has to offer. Be sure to come back often to view any news that we put out regarding the 4.0 release, but to start here are a few things that stick out from what we have found thus far!
I recently published the post 5 Reasons Why You Should Use an SAP BusinessObjects Universe to highlight some of the core benefits you’ll see when implementing the semantic layer for you organization. The post was derived from speaking with organizations new to the Business Objects world about the benefits of leveraging the semantic layer. Throughout those talks, I also get to hear a lot of misconceptions about SAP BusinessObjects Universes. Sometimes they are born out of a simple lack of understanding of the SAP BusinessObjects architecture, while other times they are propagated by competing business intelligence vendors. (Shocking, I know.)
In meeting with organizations who are new to SAP BusinessObjects or who are legacy Crystal Reports users, we are often asked the question “Why should I use a Business Objects Universe?”. To organizations who have worked with universes for a period of time, the advantages and value proposition are clear. But for organizations who are new to universes, it can often be a challenge to quantify the value of the semantic layer.
In this post I hope to outline a few of the reasons why we recommend implementing universes, even if you’re not using an SAP BusinessObjects tool that specifically requires them.
Finally after three projects and three months later, we are back to finish up our Aggregate Awareness series. In part 1 of our blog, we discussed the definition of aggregates and how to create summary tables. Today we are going to finish the process by showing how to implement these items into a SAP BusinessObjects Universe.
One of the other reasons I hear is that managers don’t want to train end-users to create reports, since they have folks in IT that already tasked with that. Some report authoring will always need to be handled by IT, due to it’s complexity, lack of data availability, etc… But I argue that the lion’s share of the development can be handled within each department instead, freeing IT developers to take on other projects critical to the organization.