Commentary

Mary Hayes Weier
 

SAP Hopes To See TomorrowNow Become YesterdayThen

So the other shoe drops. Four months after admitting one of its subsidiaries downloaded Oracle documents it didn't have legal rights to, SAP is doing everything it can to yank out and destroy that thorn in it's paw known as TomorrowNow.

So the other shoe drops. Four months after admitting one of its subsidiaries downloaded Oracle documents it didn't have legal rights to, SAP is doing everything it can to yank out and destroy that thorn in it's paw known as TomorrowNow.I'm not surprised, since back in April, just a month after Oracle filed its lawsuit against SAP claiming "corporate theft on a grand scale," SAP CEO Henning Kagermann acknowledged concerns about TomorrowNow's innocence in the matter. "We have policies in place to ensure obligations as management," Kagermann had said during an interview at the Sapphire user conference, adding that SAP was doing its own investigation. "Nevertheless, having policies is one thing, having them enforced is another thing," he said. "We have to have a complete picture."

SAP's version of a complete picture came in July, when it filed a response to Oracle's lawsuit. SAP said personnel from TomorrowNow -- a company it acquired that provides services for Oracle's JD Edwards and PeopleSoft products -- had indeed downloaded thousands of documents from Oracle's Web site on the behalf of its customers. As buyers of Oracle products, TomorrowNow customers had rights to some of those support documents, SAP said, while admitting that TomorrowNow also had downloaded some documents related to applications not licensed by those customers, for reasons unclear. But it claimed those documents stayed in TomorrowNow's separate systems and no one from SAP got access to them.


More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

That's a different picture from Oracle's allegation that SAP employees pretended to be Oracle customers to log on to its Web site and copy proprietary technical and customer-support data so it could provide lower-cost services to those customers, with the eventual goal of luring them over to competing SAP products.

It will be interesting to see what comes out in the trial -- if the suit makes it to court before it's settled -- but I was intrigued by a news release SAP issued yesterday that is the most blatant effort at corporate hand-washing I've ever seen. We've booted TomorrowNow CEO Andrew Nelson and several top managers, it said, and, by the way, is anyone out there interested in buying the company? (Actually, the release said Nelson and his colleagues had "chosen to resign" and SAP was considering "several options" for TomorrowNow's future, including a "possible sale." But it's my blog entry and I reserve the right to read between the lines.)

SAP's press release, while not an admission of its own guilt in any way, appears to me an ongoing admission that something stank over at TomorrowNow. It's also a continuation of the claim that SAP knew nothing of what was going on, and wants to show the world it's working hard to clean up the mess. But if you believe Oracle's version of events, this would be SAP's attempt to create a scapegoat out of a subsidiary that fronted its alleged scheme to commit "corporate theft on a grand scale."

The truth still lies out there somewhere. In the meantime, based on the swiftness with which SAP is trying to distance itself from TomorrowNow, there's a good chance the subsidiary will be YesterdayThen by the time this thing goes to court.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links