SAP Watch

November 20, 2008  10:06 AM

The future of SAP jobs

JackDanahy Jack Danahy Profile: JackDanahy

SAP, long the gold standard of IT employment, is feeling the global economic crisis. SAP’s growth has slowed, the company is taking cost-cutting measures and there are many frustrated SAP job seekers out in the marketplace.

On the assumption that the global economy will not recover for at least 18 months, what should SAPers — whether currently employed, or seeking a job — do? Here are some ideas culled from SearchSAP experts over the past several months:

  1. Build your functional skills. In the future, low-level technical activities such as configuration will be increasingly automated, and there will be greater demand for people who understand both SAP application logic and business processes. Look into getting the BPX certification to learn more about business processes from SAP’s perspective.
  2. Build your industry credentials. Getting a one-week tech certification isn’t the same as passing something like the APP test offered by the Institute for Supply Management (ISM). A techie who possesses industry credentials will tend to be more employable, all else being equal.
  3. Build your academic credentials. How about getting a one- or two-year MBA? For non-U.S. residents, there are plenty of credible one-year MBA programs in Europe and India, and you can always apply for a scholarship.
  4. Keep building your SAP intelligence. SAP technology is constantly shifting, and you need to keep up with current trends even if you take time off to build another aspect of your professional portfolio.

These tips can help you position yourself for an SAP job, or a better SAP job, after the downturn ends.

Demir Barlas, Site Editor

November 14, 2008  3:23 PM

Is it a buyer’s market for vendors?

JackDanahy Jack Danahy Profile: JackDanahy

Not everyone will be hunkering down in this economic downturn – the big vendors, including SAP, will be spending money.

The high cost of winning new customers will drive acquisitions – because many vendors are spending more than $1 for every $1 they’re bringing in, according to AMR Chief Research Officer Bruce Richardson.

“They’ve come to realize, it’s too expensive. They have to do acquisitions to offset organic growth,” Richardson said during his keynote at the AMR Research’s Business Technology Conference being held in Boston this week. “Even in a down economy, I think we’ll continue to see acquisitions.”

So who’s up for grabs? Richardson broke up the software field into two categories, the predators and the prey. The prey, “the shrinking software middle class,” as Richardson refers to them, are best of breed software companies that bring in between a $100 million and $500 million in revenue.

They are: Ariba, JDA, Manhattan, RedPrairie, Chordiant, RightNow, SuccessFactors, Taleo, Deltek, Epicor, Lawson and QAD .

Typically between a third and a half of their revenue comes from maintenance and Richardson thinks we could see a lot of those companies acquired in the next two years.

Larry Ellison’s certainly showing no fear when it comes to continuing the company’s acquisition spree in this economy- Oracle having just made its 10th acquisition of the year.

And with SAP’s blockbuster announcement this week that it will engage in more organic growth – tapping former Oracle exec John Wookey to lead the development of on-demand software for large companies -will SAP offset that with acquisitions of on-premise vendors and the maintenance revenue streams they carry?

Courtney Bjorlin, News Editor 

November 7, 2008  11:52 AM

No Business“Buy”Design, no problem?

JackDanahy Jack Danahy Profile: JackDanahy

SaaS ERP — with its irresistible pay-as-you-go model and less-costly deployment — is well positioned for the current economy, most analysts agree.

 So is SAP missing out on big chances to sell Business ByDesign?

In a week when there’s been no shortage of digs on SAP’s debuted, then-delayed SaaS ERP, and attempts to sway SAP customers to other vendors, it’s tempting to think so. NetSuite is trying to lure SAP customers to its own SaaS ERP offering with discounts and freebies. CEO Marc Benioff took aim at SAP during’s annual Dreamforce conference, saying that SAP — along with Microsoft and Oracle — were too late to the game.

Analysts say that NetSuite’s 50% off offer to SAP customers is less likely to appeal to the R/3 customers it’s targeted at, than to enterprise-size SAP customers who were thinking of deploying SaaS ERP in a smaller division or subsidiary. Those are potential, new SMB customer wins SAP could be missing out on.  

But there’s also another view emerging.

The Wall Street Journal, in its Business Technology blog, took aim this week at the claim that online software is recession proof, citing NetSuite’s slightly lowered guidance for the remainder of the year, as well Benioff’s answer on how the economy had affected — that these were difficult and unusual times, but was in a position of strength.

And evidence is starting to emerge that IT budgets are, at best, uncertain. A recent story on our sister-site, centered on a Forrester Research survey on how IT is riding out the recession, revealed the approach to IT spending right now is somewhat unclear.

While the report said that “more than half of the IT executives said they are not cutting budgets and do not have plans to make cuts for 2009,” it also added that “the number of CIOs responding thus far is roughly a third of what Forrester normally sees at this point in a survey…suggesting deep uncertainty about what is going to happen.”

Will SaaS vendors just ride out the recession better than on-premise vendors, or will they really get a significant boost?

And is SAP missing out on a bunch of chances to sell its SaaS ERP, or, is it no big deal? Is the economy actually good, or at least neutral, for Business ByDesign?

Courtney Bjorlin, News Editor

November 5, 2008  5:11 PM

What SAP is doing right

JackDanahy Jack Danahy Profile: JackDanahy site expert Axel Angeli recently leveled some criticism against SAP’s leadership and technical direction. This week he offers some support of SAP’s policies.

There are areas in which SAP is making positive progress, mainly in the embedding of communities and in collaboration with customers and vendors. SAP has learned a lesson from the enthusiastic engagement of Global Communication and the community experts. SDN is doing great and discussing product strategies in SDN would give better insight than listening to internal plans for the future.

A new member in the family is the SAP EcoHub. The idea is great. It creates a marketplace where SAP third party-vendors and SAP customers can meet in a single place. The questions that remain are: Why is a marketplace not simply called a marketplace, and why did EcoHub come into being shortly after some former SAP employees started a similar project under the name

The business counterpart to SDN, the Business Process Expert community (BPX), is getting more and more popular. A BPXer is a knowledge engineer, an advisor who should be able to explain the technology to business and explain the real business needs to the technical staff. Here is where paths cross: Listening to the true BPX community would give SAP an idea of where they need to invest, rather than investing in something later pushed into a market that hasn’t asked for it.

SAP has established standards for certified Business Process Experts. The idea here is to deliver a canonical set of knowledge and methods as the common ground for everyone working as ERP consultants. There are plans for training and certification in order to make BPX more popular and to quickly get a critical mass of qualified BPXers all over the world.

SAP is a good company and SAP has great products. SAP customers enjoy working with the ABAP stack; not for nostalgic reasons but because it is reliable, stable, still elaborate by design and superior to everything else that competes with it. SAP ERP is also the best choice for SMBs, if it is installed and if all service is rendered by an experienced SAP partner who specializes in the SMB customer’s industry sector. SAP ERP is still the best, and only Microsoft Dynamics AX will come close.

There is still potential for SAP, but management has to understand that listening to customers and freely giving out information early — even if details change later — is better than hatching strategies in an ivory tower. SAP leaders, wake up: Listen to your community and treat customer complaints as sacred!

In part one of this blog, published earlier this week, Axel Angeli discussed why he isn’t fond of SAP CEO Leo Apotheker, SAP’s service fee increases or elements of NetWeaver. In part two, Axel criticized some of SAP’s technology decisions.

November 3, 2008  10:31 AM

How can SAP get back on track?

JackDanahy Jack Danahy Profile: JackDanahy site expert Axel Angeli isn’t one to pull his punches when it comes to SAP and he makes no exception in discussing SAP’s technological direction in this guest blog.

Has SAP lost its mojo?

In the good old days, SAP was an extremely successful technology company and the darling of many analysts. This was in the last millennium, before SAP lost its belief in its own strengths and virtues.

In 1998 SAP undertook its last breath-taking act of innovation when it introduced the BAPI framework. BAPIs had been designed to transform SAP’s transaction-based system into a component-based service suite where any functionality would be programmatically accessible. Back then, SAP was already an SOA-aware software package! But this successful path was needlessly abandoned in the years to come. The old SAP crew that defined the company’s technological success — in terms of ABAP, RFC and Batch Input — was mugged by the dogma of Java.

Even though it was implemented in the mindset of assembler programming, Java is a language that decorates itself with the feathers of object-oriented programming. It is unstable, unreadable, incomplete and completely redundant, since it did not introduce a single new feature that the world had been waiting for.

How should SAP escape the Java trap? Go back to its old merits. Make a clear and non-negotiable decision in favor of ABAP. This would also mean polishing up ABAP with a more modern syntax. The new ABAP 7.2 kernel has already taken some first steps in this regard. Technically the rudders are in the right direction. What is missing is the clear commitment of the SAP board.

In terms of SOA, there is another problematic area that requires immediate action: Process Infrastructure (PI). SAP doesn’t have the power to make technology changes from the inside and needs to shore up PI by buying a standing technology as an enhancement package for the existing stack. IBM bought Mercator Datastage TX, Progress took IONA, Oracle snagged BEA and Software AG showed mercy to suffering webMethods. The number of possible candidates for purchase is limited. If looking for quality products with an inherent Event-Driven ESB architecture, there are mainly Fiorano, ActiveBPEL or the not-for-sale SAP partner Seeburger. 

In part one of this blog, published last week, Axel Angeli discussed why he isn’t fond of SAP CEO Leo Apotheker, SAP’s service fee increases or elements of NetWeaver. In the next part of this blog, Axel will explain what SAP is, in his opinion, doing right.

October 30, 2008  3:00 PM

Which way to Web 2.0?

JackDanahy Jack Danahy Profile: JackDanahy

My colleague Shayna Garlick, who writes for, blogged on something this week that is timely for SAP customers as well –whether Web 2.0 for the enterprise will take a hit in this economy.

The post’s premise was that as established vendors and start-ups compete for Web 2.0 deals with companies, prices will fall, but so will vendors’ profits and, consequently, innovation.

It’s one reason why SAP’s investment in sort-of start-up LinkedIn is particularly interesting — as it could prove to be the best of both worlds for customers and the vendor alike.

Last week, it was revealed that the venture capital arm of SAP, SAP Ventures, poured some money into the young, social/business-networking site. LinkedIn provides an online community for professionals to pass their “business cards” around, recommend colleagues and even search for new employees among its members. And this week, LinkedIn added new applications for activities like blogging.

While investments made by SAP Ventures are somewhat independent of SAP AG, (if you’re interested in some of its other investments, here’s a list) LinkedIn said it decided to work with SAP as a “strategic investment.” They’ve been hearing for a long-time from members who run SAP software — including many CIOS — who want to leverage the online community to help people do their jobs more efficiently, a LinkedIn spokeswoman said.

“The idea that we could work with SAP was intriguing to us,” said Ellen Levy, LinkedIn’s Vice President of Corporate Development & Strategy, declining to give any clues as to what the two might work on, or when customers might see it.

SAP had this to say about the deal.

“LinkedIn is one of the leading Internet companies in the world that targets business users,” SAP spokesman Saswato Das said. “When Web 2.0 technologies are smartly applied to the enterprise, they can produce significant efficiencies for small, medium and large companies, and we believe in LinkedIn’s pioneering approach.”

SAP has poured money into its own Web 2.0 initiatives.  But while vendors like Oracle, with its WebCenter Suite, and IBM, which announced in the fall it’s opening a social software research center in Massachusetts, are working to improve their own initiatives, SAP’s LinkedIn partnership signals an approach to Web 2.0 of leveraging and improving ideas from start-ups that are already working.

What’s the best way for vendors to optimize Web 2.0 for the enterprise, while still making money off it?

Courtney Bjorlin, News Editor

October 29, 2008  12:07 PM

SAP: What went wrong? Blame marketing, NetWeaver

JackDanahy Jack Danahy Profile: JackDanahy site expert Axel Angeli isn’t one to pull his punches when it comes to SAP and he makes no exception in discussing SAP’s recent earnings in this guest blog.

SAP has seen better times. The company’s quarterly revenues have declined and SAP is tightening its belt accordingly. What’s really to blame for the tension in Walldorf?

Deputy CEO Leo Apotheker blames the financial crisis. This is an attempt to avoid mentioning the turmoil ignited by the raising of annual SAP service fees from 17% to 22%. Customers haven’t shown the least bit of understanding for this decision. As a consequence, many customers have put their SAP purchases on hold. For example, the German SAP User Group (DSAG) decided in a common action to withhold any SAP purchases until next year.

The new enterprise support is a marketing disaster. The way it was communicated left the impression that SAP makes decisions behind the backs of its customers. Since Apotheker is the SAP marketing guru, he has turned into a burden for all of SAP. There is no one he can blame for this unfortunate move, and I have no idea how Apotheker will be able to escape from this trap. I myself am a techie and therefore feel indifferent towards Leo Apotheker; he is simply not my kin. But the analysts, also, do not seem to like him very much, which makes it difficult for him to explain his position. If this mishap would have been linked to Henning Kagermann, he might have escaped with a simple “Sorry, we meant it differently!” But the contract of the congenial, bright-minded professor is ending soon and he seems to be partially retired, like many of the old SAP crew. 

The explanation given by SAP for the steep increase in support fees is the same old story: Due to the increasing complexity of the full NetWeaver stack, the costs invested by SAP into support rose heavily and now need to be recouped. Customers see it differently. The higher costs stem only from the new dimension of components that SAP introduced in the past decade, against customer wishes.

High support costs and a high frequency of support requests are signs of low quality or a depreciation of support-friendly design. And the same products that have been under fire for years have caused the problems. These are the products that require the Java stack, with the biggest culprits being Enterprise Portal (EP) and Process Integration (PI). PI is awkward to use, costly to install and operate, difficult to examine for causes of malfunctions and no longer based on state-of-the-art Enterprise Service Bus technology. There is no time to pimp up PI into a full featured, modern Event-Driven-Architecture process engine.

In part two of this blog, Axel Angeli discusses ways for SAP to get back on track.

October 24, 2008  10:09 AM

SAP and Oracle vs. third-party support?

JackDanahy Jack Danahy Profile: JackDanahy

Forrester Research’s recent SAP support fee report has made quite a splash over these last couple of weeks – with its challenge to customers to push for more value from Enterprise Support.

But it also raised something that’s getting little press – a suggestion that bolder measures might need to be taken to contain maintenance and support costs in the long-run.

Third-party support provider TomorrowNow’s operation officially comes to a close at the end of next week, and the court is starting to push Oracle and SAP toward a settlement in the TomorrowNow case.

It’s all a stark reminder to customers that their options are limited when it comes to maintenance and support. Oracle customers have a few alternatives, but the vendor has a cigarette-like warning label on its website cautioning its customers about using them. And while Rimini Street is getting ready to deliver third-party support to SAP R/3 customers in January, the options for SAP customers are limited.

Plus, Forrester says it has started to see SAP become more aggressive about discounting when competing against Oracle — a practice SAP has not historically embraced. At face value, this may seem like good news for new customers. But it also may spell trouble as parity between these two giants grows – along with the distance between them and smaller apps vendors.”

“To keep the market competitive, government regulators may ultimately have to force a third-party maintenance option via antitrust legislation,” the report reads.

Some argue that enterprise software, because of its very nature and purpose, needs to stay on an upgrade track.

But it seems more and more customers want a choice. In contrast to the picture the economy is painting for much of the rest of IT, Rimini Street announced this week it had a record quarter. And netCustomer CEO Punita Pandey said in an interview earlier this summer that they were exploring providing support for SAP customers.

Is Forrester’s suggestion the way to ensure customers have a choice?

Courtney Bjorlin, News Editor

October 22, 2008  10:16 AM

SAP EarlyWatch: Diagnosing SAP problems before they hurt you

JackDanahy Jack Danahy Profile: JackDanahy

SAP service has been a hot-button issue ever since SAP resolved to raise its maintenance fees earlier this year. As long as everyone’s talking about SAP service, this is a good time to familiarize yourself with what kinds of service and support SAP offers. This week, we’ll take a closer look at one of those services, SAP EarlyWatch.

SAP EarlyWatch is exactly what it sounds like — a diagnostic and reporting service designed to catch potential problems in your SAP system before they negatively impact your organization. EarlyWatch covers problems that can occur in:

  • SAP applications and programming. For example, EarlyWatch can find ABAP dumps that can cause a program to shut down.
  • Operating systems. EarlyWatch can detect and diagnose various performance issues.

When you run EarlyWatch, SAP will monitor your system, run a full slate of reports and send you an itemized action list explaining your existing and potential system problems, prioritized by urgency. EarlyWatch can be set up to run proactively, so that your system is monitored on an ongoing basis; it can also be requested whenever you need it. If your SAP environment has plenty of moving parts, it can be a good idea to have EarlyWatch running constantly, as the frequently daily changes that take place in your IT stack can have a deleterious impact on SAP applications and SAP-supporting infrastructure.

EarlyWatch can be run from within SAP Solution Manager. Here are step-by-step instructions from SAP on how to do so. The actual front end for EarlyWatch is SAP OSS, also known as SAPnet-R/3.

Knowing how to run, and act upon, EarlyWatch should be standard knowledge for an SAP Basis administrator. For the business, utilizing EarlyWatch is a way of preventing SAP downtime, which can be extremely costly and disruptive to operations.

Demir Barlas, Site Editor

October 21, 2008  11:19 AM

Helpful SAP Basis books

JackDanahy Jack Danahy Profile: JackDanahy

SAP Basis is one of the most important functions in the SAP ecosystem, as it touches so many components of SAP, such as system administration, security, user interface (UI) and development. Interestingly, though, there aren’t that many books pertaining directly to SAP Basis. That’s why we thought it was a good idea to bring together this following list of six books that cover Basis from different angles. We hope the list is helpful both to working SAP Basis administrators who want to get better at their jobs and to Basis consultants.

SAP FI/CO Questions and Answers: FI/CO remains a bread-and-butter SAP module, and this book offers a Basis overview grounded in the context of FI/CO. Don’t be fooled by the title; this book touches on Basis, ABAP, and a bunch of other modules, such as MM, SD and PP, so it can be of use to a lot of different job functions.

SAP Security Interview Questions, Answers, and Explanations: Security is a foundational concept within Basis, and this book prepares you for the security- and audit-related questions that can come up in an interview.

SAP Basis Certification Questions: Basis certification can add some market value to working Basis administrators, or help consultants break into the field. Whatever your role, it’ll help to be acquainted with the nuts and bolts of Basis certification.

SAP Security: SAP Security Essentials: What’s more essential than securing an SAP system? This book covers the fundamentals you need in order to put an SAP system in lockdown.

SAP R/3 Transaction Codes: Finding transaction codes can be a headache for SAP Basis administrators. This book lists them so you don’t have to hunt them down.

ABAP Objects: One of the interesting features of this book, here translated into English for the first time, is that it comes with two CD-ROMs containing a test version of SAP Basis for 2000/NT.

As always, be sure to read user reviews and book excerpts before deciding which book, if any, is right for your needs.

Demir Barlas, Site Editor

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to: