Skip to main content

SAP TO WIND DOWN OPERATIONS OF TOMORROWNOW

NEWTOWN SQUARE, Pa. - July 21, 2008 - — Today, SAP (NYSE: SAP) announced that it has chosen to wind down operations of TomorrowNow, a subsidiary it purchased in February 2005 that has provided third-party support for Oracle and other applications.

SAP is working directly with TomorrowNow’s more than 225 current customers to help them return to support from Oracle for those customers on PeopleSoft, JDEdwards or Siebel applications or to smoothly transition to new support options.

“Our goal is to assist our customers in transitioning to a new support provider, including Oracle, without a disruption to their support during the wind-down process,” said Mark White, executive chairman, TomorrowNow.

SAP intends to conclude the wind-down process prior to October 31, 2008.

For more information, please visit http://www.tnlawsuit.com.

Any statements contained in this document that are not historical facts are forward-looking statements as defined in the U.S. Private Securities Litigation Reform Act of 1995. Words such as “anticipate,” “believe,” “estimate,” “expect,” “forecast,” “intend,” “may,” “plan,” “project,” “predict,” “should” and “will” and similar expressions as they relate to SAP are intended to identify such forward-looking statements. SAP undertakes no obligation to publicly update or revise any forward-looking statements. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. The factors that could affect SAP's future financial results are discussed more fully in SAP's filings with the U.S. Securities and Exchange Commission ("SEC"), including SAP's most recent Annual Report on Form 20-F filed with the SEC. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates.

Copyright © 2008 SAP AG. All rights reserved. 
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serve informational purposes only. National product specifications may vary.

For more information, press only:
Christoph Liedtke, +49 6227 7-50383, christoph.liedtke@sap.com, CET
Andy Kendzie, +1 (202) 312-3919, andy.kendzie@sap.com, EDT 
Saswato Das, + 1 (212) 653 9571, saswato.das@sap.com, EDT
Lindsey Held, +1 (650) 320-3524, Lindsey.held@sap.com, PDT

Comments

Popular posts from this blog

A new experience on www.innova9.io!

After almost a year, a new and redesigned web site for Innova9. With this new website, we'll be able to communicate better, educate better, and we launch a new initiative for integrations: We'are now Dell Boomi's Partner and we can build seamless integrations for on-prem, Cloud and hybrid business scenarios using JD Edwards' Orchestrator and the versatility of Dell Boomi. Also, we're launching our Products section, starting small with our JD Edwards' Sandbox installation and hosting as well as our Orchestrator Masterclass. There's more to come! Take a look at our Services: all focused on EnterpriseOne innovations, from UX One Enablement, to our new Online Help Desk, where we'll serve your Business Analysts, Power Users, and End Users with instant messages to help with UX and User Defined Objects activities. All in a super affordable price, available per user / per month on subscription base. Want more? Our articles now have a new place! Started with...

How to use Orchestrator after you build an Orchestration?

How to use Orchestrator, once I build the Orchestration? How it works? You probably saw a lot of videos and explanations about how practical is Orchestrator, right? But, have you asked yourself after you build the Orchestration, how to use it, or how it works? In this Master Class, you'll learn not only how to build Orchestrations, but also the foundation that enables you to expose any JD Edwards applications and processes as a Web Service. That's the idea: not only come with the solution, but give a solid base in the foundation, so you'll have a complete understanding on how it works. This will help you when thinking - or designing - your own integrations: no matter if it is with another system or an IoT device. By the way, I'll show how to use a temperature sensor to send information to Orchestrator / JD Edwards. Let's learn together?