SAP BusinessObjects BI 4.0 Turns 3!

After the candles are blown out, here are some things to work on during the next year.

Happy Third Birthday, SAP BusinessObjects BI 4.0! You came into the world on September 16, 2011, after a lengthy gestation. We’ve made a lot of memories together, from your birth to taking your first steps. Potty training took a bit longer than expected, but we eventually got there with your BI 4.1 release. And I’ve mostly gotten over that time you pooped in the bathtub. As the parent of three children, I’m familiar with children moving from “baby” to “toddler” to “preschooler”. Software doesn’t mature in the same way as human children. But just like with humans, some things that were expected, manageable or even “cute” in earlier years become wearisome after three years. So I’d like to mention ten things that I hope you’ll work on before your fourth birthday.

10. Group Hierarchy tree control with “too many objects”

We’re thankful that after three years, the “too many objects” error is largely solved in the BI Launch Pad (see related article, Too Many Objects in Your BI Launch Pad). I realize that BI Launch Pad users outnumber Central Management Console users. But any administrator with a large BI installation knows how tedious it is to live without a decent tree control.

Top 10 annoyances of SAP BI4

9. User search feature in CMC

There are a lot of user attributes beyond just title and description. And I’d like to search any of them, thank you. Isn’t this just a few extra lines of code?

Top 10 annoyances of SAP BI4

8. Server search feature in CMC

Although most servers are appropriately named, sometimes they just aren’t. Please make it easier to find a server by type (Adaptive Processing Server, Crystal Reports Cache Server) regardless of what somebody else decided to name it.

Top 10 annoyances of SAP BI4

7. SAP BusinessObjects Design Studio server installation

If Design Studio is the future of SAP dashboards, then please take the time to integrate the required server features directly into the BI platform. The separate (and frequently changing) server components are a huge barrier to adoption (see related articles, Please Integrate the Integrated BI Platform and Over Designing BI Architecture for Design Studio).

Top 10 annoyances of SAP BI4

6. SAP BusinessObjects Explorer administration

We’ve suffered through poor SAP BusinessObjects Explorer administration since Explorer debuted as Polestar on the XI R2 platform. As you fold Explorer functionality into Lumira, please fold its administrative tasks into the Central Management Console (see related article, Family Planning).

Top 10 annoyances of SAP BI4

5. Web Intelligence panel preference

Thankfully you provide a script, setGroupPreferences (see SAP KB 1659566 or SAP KB 1816617), but even simpler would be the ability to set the default Web Intelligence report panel via the CMC. But even better would be retiring the Java report panel in favor of a single kick-a__ HTML 5 panel. Which leads us to number 4.
Top 10 annoyances of SAP BI4

4. Web Intelligence Java Report Panel

Who can forget WebiJavaGeddon (see related article, Never Let a Serious Crisis Go to Waste)?  I’ve logged hundreds of hours in the Web Intelligence Java Report Panel. But with security and performance concerns, it’s time to move on to a plug-in free future (see related article, Is it Time for Caffeine-Free Web Intelligence).

Top 10 annoyances of SAP BI4

3. Monitoring

Monitoring was a big marquee feature of the BI 4.0 launch. It’s a great first step, but it’s time to show us a more mature second generation of this important feature. Oh, and the Adobe Flash interface needs to go (see related article, Adobe Flash- Dying but not Dead Just Yet).

Top 10 annoyances of SAP BI4

2. Promotion Management/Lifecycle Management

Everyone thought the Import Wizard was evil. Until it went away. Like monitoring, this was a marquee feature of the BI 4.0 and rightly so. Also like monitoring, it re-appeared in BI 4.1 largely unchanged.

While we’re appreciative of the many stability improvements made post-BI 4.1, it’s time for you to show us the next generation of promotion management (see related article, Do I Feel Lucky? Musings on Promotion Management). We’d also be grateful if the user interface was more consistent with the rest of the CMC and eliminated the tiny bit of Adobe Flash that it contains (see related article, Adobe Flash- Dying but not Dead Just Yet).

Top 10 annoyances of SAP BI4

1. Platform Search

There are over 80 articles in the SAP knowledge base about platform search. Most of them highlight a design flaw or document a workaround, which isn’t terribly flattering. Given that platform search is often the first feature a new user will try, it’s time to put away the duct tape and introduce the next generation of platform search to the SAP BI platform.

Top 10 annoyances of SAP BI4

Make a wish, blow out the candles, and enjoy some well-deserved cake. But I hope you’ll take these things to heart over the next year.

What are your thoughts after three years of the SAP BI4 platform?

Adobe Flash- Dying but not Dead Just Yet

Declaring Adobe Flash “dead” sadly does not make it so.

At this year’s SAP SAPPHIRE conference Ty Miller, SAP VP of Solution Management, declared that “Flash is dead!”. He was referring, of course, to SAP’s dashboard roadmap and the transition from Adobe Flash-based Xcelsius/Dashboards to HTML5-based Design Studio (see related article, The Future of SAP Dashboards). While that high-profile transition is well underway, Adobe Flash is still lurking in other dark corners of the SAP BI platform.

Adobe Flash in the Central Management Console

Monitoring

The Monitoring dashboard introduced with the BI 4.0 Central Management Console is built with Adobe Flash. Two years ago, Mirko Langhorst posted the following on the SAP Idea Place:

We would like to totally get rid of Flash, the component in the CMC using Flash is the new Monitoring application. It would be great to change this HTML5, so the CMC would become Flash-free

Get Rid of Adobe Flash 01 500

Sadly, SAP buried this idea in the SAP Idea Graveyard, tagging it as “Not Planned by SAP”. Which is unfortunate, because the monitoring dashboard isn’t the only source of Adobe Flash frustration in the BI platform. Or just frustration in general (see related article, Less Flash, More Substance for SAP Business Intelligence Monitoring).

Get Rid of Adobe Flash 02 500

Visual Difference

The Visual Difference feature introduced with the BI 4.0 Central Management Console is built with Adobe Flash.

Adobe Flash in CMC Visual Difference

Promotion Management

Adobe Flash is used by the Override Settings in Promotion Management. And as an aside, all but the latest support packs of the BI platform use the much maligned Apache Derby for overrides (see SAP Mentor Greg Myers’ epic article, Derby Maybe).

Get Rid of Adobe Flash 03 500

Adobe Flash in the BI Launch Pad

Content Linking with BI Workspaces

Not content to limit use of Adobe Flash to the Central Management Console, SAP uses Adobe Flash in its implementation of BI Workspace content linking in the BI Launch Pad.

Get Rid of Adobe Flash 04 500

 

Crystal Reports for Enterprise Prompts

Crystal Reports for Enterprise uses Adobe Flash for scheduled prompts.

Crystal Reports for Enterprise Prompts with Adobe Flash

Crystal Reports 2013 does not use Adobe Flash.

Crystal Reports 2013 Prompts without Adobe Flash

Explorer

I haven’t mentioned SAP BusinessObjects Explorer, but SAP’s recent plans to fold it into SAP Lumira (and therefore SAP HANA) have effectively marooned it on an Adobe Flash island (see SAP executive Jayne Landry’s related article, Run Simple: Convergence of the SAP BusinessObjects BI Product Portfolio). It’s likely that any Explorer replacement will be built on HTML5, not Adobe Flash. But it’s unclear when SAP intends to deliver Explorer-like functionality by Lumira or any other tool in the BI platform.

Dashboards and Xcelsius

Of course, we can’t forget that SAP Dashboards require Adobe Flash at runtime.

Time to Retire Adobe Flash in SAP BI Platform

A decade ago, Adobe Flash had its place providing rich visuals for web applications. In today’s mobile and cloud-centric world, Adobe Flash is a relic. Instead of visual excitement, it generates support and security anxiety. For example, Apple last week took the drastic step of disabling all versions of Adobe Flash except the latest 14.0.0.145 (see related Apple bulletin). But this is two versions ahead of SAP, which has only recently added official support for version 12 in its latest patch levels of the BI platform.

The time is right for SAP to articulate a clear timeline for a plug-in free version of the SAP BI platform (see related article, Thoughts on BI 5.0). Until then, please show your support for Mirko Langhorst’s great idea.

Update (September 17, 2015): SAP has indicated that Promotion Management in BI 4.2 has been rewritten to no longer require Adobe Flash. However, SAP has not published a roadmap to address these other Adobe Flash dependencies.

Promotion Management gets a Promotion

SAP is listening to our concerns about promotion management on the BI platform.

It’s generally not a good idea to tweet when you’re angry. And I really try hard not to. But sometimes- in a moment of weakness- I’ve been known to say unkind things about SAP BusinessObjects BI 4.0 Promotion Management.

LCM Twitter Status 349637215804080131

Or try to laugh through my tears with some humor (see related article, Do I Feel Lucky? Musings on Promotion Management). If you’re not familiar with Promotion Management, I’ll try to describe it. Without using four letter words.

Promotion Management is a feature of the Central Management Console that, along with Version Management and Visual Difference, business intelligence administrators use to move content through a software development lifecycle (SDLC) from one environment to another. For example, from development to test to production. Promotion Management is usually one of the last things that you use in a BI4 migration project. All eyes are watching you. And it’s a really unpleasant feeling to be diagnosing why your job failed to promote properly in the 11th hour. Trust me, I know from experience.

Promotion Management was introduced in 2008 with SAP BusinessObjects Enterprise XI 3.1 as Lifecycle Manager or LCM (see related article, Business Objects Lifecycle Manager – first impressions) but many customers continued to rely on the Import Wizard for content promotion. In 2013, it’s easy to forget that back in 2005 the original Import Wizard wasn’t without its own flaws. Particularly for those classic BusinessObjects customers upgrading from BusinessObjects 5.1 or 6.x. But after listening to users gripe at each annual conference, the Import Wizard gradually improved. So much that early adopters of BI 4.0 are asking for the return of the Import Wizard, which is no longer part of the platform (see Please bring back the Import Wizard on the SAP Idea Place).

While nobody has gotten fired for using Promotion Management (at least to my knowledge), neither has anybody gotten a promotion by using it.

LCM Twitter Status 347412622875951105

Promotion Management can drive you to your knees in prayer

LCM Twitter Status 307545746121560064

Or more fervent demonstrations of religious expression

LCM Twitter Status 342731009143480321

Promotion Management can drive you to drink

LCM Twitter Status 274330101875888129

Or it can lead you to wonder what the Promotion Management development team has been drinking. Or smoking.
LCM Twitter Status 266918716623708160

This week, ASUG sponsored webcast What is New in BI 4.1 Promotion Management with Kai Chan of SAP. Promotion Management has officially been given a promotion in SAP BusinessObjects BI 4.1, which should go into general availability (GA) later this year. Beyond roadmaps and features, the most important thing that Kai said was that SAP was listening to customer concerns about lifecycle management and working to resolve them. SAP has even taken the bold step of reassigning development of Promotion Management to a new team in Vancouver, BC.

BI41 Promotion Management Roadmap
I’m grateful that SAP is taking these steps (see related article, Collaboration). As you can see from the roadmap above, it’s unlikely that all of our concerns will be addressed by the time of 4.1 GA. But like the SAP Lumira team, the Promotion Management team will be taking small steps with each minor release and not making us wait for a major one.

With Promotion Management working better than ever, perhaps I’ll earn a promotion, too.

How do you feel about SAP’s recent announcements about Promotion Management?

Do I Feel Lucky? Musings on Promotion Management

Do you feel lucky? Well, do ya, punk?

Nothing as exhilarating as having all eyes of the project team on you as you use Promotion Management (formerly known as Lifecycle Manager) to move SAP BusinessObjects universes and reports into production at the 11th hour.

Do you feel lucky?

I know what you’re thinking. “Did he create six Web Intelligence reports or only five?” Well, to tell you the truth, in all this excitement I kind of lost track myself. But being as this is Promotion Management, the lifecycle management tool for the most powerful business intelligence suite in the world, and would blow your promotion job clean off, you’ve got to ask yourself one question: Do I feel lucky?

Well, do ya, punk?

Today when I create and run a Promotion Management job, I get nervous, say a prayer, and hope I get lucky. I’m currently helping a customer apply a patch from BI 4.0 Support Pack 5 Patch 6 to Support Pack 6. Unfortunately, Promotion Management does not correctly calculate linked universe dependencies and the core universe does not get promoted to its proper destination (refer to SAP KB 1767657 for details). The issue was corrected in Support Pack 4 Patch 4; however, that patch- and many others- was forward fit to SP6 (refer to SAP BusinessObjects maintenance schedule and forward fit plan), not to SP5.

Let’s hope that SAP BusinessObjects Business Intelligence 4.1– which was released to customers (RTC) and into ramp-up this week- brings some improvements to the promotion management process when it goes into general availability (GA), expected in late Q3 2013.