What is SAP?

SAP, started in 1972 by five former IBM employees in Mannheim, Germany, states that it is the world's largest inter-enterprise software company and the world's fourth-largest independent software supplier, overall.

The original name for SAP was German: Systeme, Anwendungen, Produkte, German for "Systems Applications and Products." The original SAP idea was to provide customers with the ability to interact with a common corporate database for a comprehensive range of applications. Gradually, the applications have been assembled and today many corporations, including IBM and Microsoft, are using SAP products to run their own businesses.

SAP applications, built around their latest R/3 system, provide the capability to manage financial, asset, and cost accounting, production operations and materials, personnel, plants, and archived documents. The R/3 system runs on a number of platforms including Windows 2000 and uses the client/server model. The latest version of R/3 includes a comprehensive Internet-enabled package.

SAP has recently recast its product offerings under a comprehensive Web interface, called mySAP.com, and added new e-business applications, including customer relationship management (CRM) and supply chain management (SCM).

As of January 2007, SAP, a publicly traded company, had over 38,4000 employees in over 50 countries, and more than 36,200 customers around the world. SAP is turning its attention to small- and-medium sized businesses (SMB). A recent R/3 version was provided for IBM's AS/400 platform.

SAP ABAP

What SAP says about ABAP's future

 

With Java and global outsourcing becoming more prevalent, what does the future look like for ABAP developers?

The future of ABAP (advanced business application programming) is seemingly on every SAP developer's mind. It's understandable -- no area of SAP has been harder hit by technical changes than ABAP development, but ABAP is far from dead.

Developers point to ominous signs: All new SAP programs are written in Java (not true), the NetWeaver CE (composition environment) is an exclusively Java-based environment (true), the NetWeaver Developer Studio is also almost exclusively Java-based (true). When we take the impact of global outsourcing into account as well, we can safely say that it's been a rockier road for ABAP programmers than for any other SAP skill set.

 

True to form, one of the hottest topics at TechEd 2007 was the changing nature of the SAP developer skill set. It's easy to see why people care so much about this topic: SAP customers don't want to find themselves with a development team that lacks the skills to implement the latest SAP functionality, and SAP programmers are facing enough challenges without having to worry that their skills won't be needed on project sites.

So what's the latest on the future of ABAP?

ABAP is not as dead as some might think. At TechEd 2007, Vishal Sikka, SAP's chief technology officer, said that there are still 238 million lines of ABAP code in SAP. The message? ABAP is still entrenched in SAP, and SAP is still entrenched in ABAP. He also noted that while some new SAP programs are written in Java, some are written in ABAP too.

Some of the new NetWeaver PI (process integration) functionality was also written in ABAP. You may not see it when you work with PI, but the ABAP is there underneath, keeping things humming along. I did talk to some SAP representatives who didn't even know whether ABAP was part of NetWeaver at this point, but the SAP Labs team assured me that it is.

Thomas Jung of SAP Labs, who writes a developer's blog on SDN (SAP Developers' Network), said some of the underlying NetWeaver functions were written in ABAP, and of course there is the Web Dynpro for ABAP. Jung also said that the ABAP Workbench is indeed part of NetWeaver and is being equipped with many of the bells and whistles that the Java side of NetWeaver is receiving.

So, although it's not going away anytime soon, we can't say that the ABAP outlook is dreamy. ABAP is still a valid part of the SAP landscape, but there's no question that when it comes to designing new enterprise services, Java is the language of choice in most cases.

On the other hand, we must remember the warning Sikka gave me during our interview: The entire SAP landscape is changing, and the emphasis on ABAP versus Java is not the right way to understand the transitions that are under way.

The design of the new enterprise service-oriented architecture (eSOA) NetWeaver development platform is specifically intended to make the programming language used irrelevant. The eSOA layer is designed to work with any open standard, so between eSOA and PI, programmers should be able to use their environment of choice and be interoperable with SAP.

Sikka went further, as did many executives, to stress that SAP's modeling tools (Visual Composer, the upcoming Aris for NetWeaver, as well as a new Eclipse modeling environment) are all designed to change the development process and emphasize the design of reusable components over arduous hand-coded customizations.

Soon, these modeling environments may even generate enough automated code to make it possible for the "Business Process Experts" of the future to do all the development work. Some have suggested that as much as 70% of all hand-coding will go away once these tools are fully realized.

That goes beyond the ABAP-versus-Java debate to a much broader debate on the future of development work in an SOA and visual modeling world -- inside and outside of SAP. My advice for developers is to try to get their hands on all the new modeling tools and to check out the new composition environment on SDNand the BPX (business process expert) community in order to get a better feeling for the convergence of IT and business.

SAP Front-ends

SAP front-end is becoming more accessible and user-friendly, but developers need a diverse skillset to cover it all. Get information on Adobe interactive forms, Duet business scenarios, enterprise widgets and the mobile Java client here.

 

SAP News:

 

1. SAP Muse graphical interface could be next business browser

 

LAS VEGAS – SAP's graphical interface upgrade called Project Muse will be released in phases beginning at the end of the year and could represent the first business browser for end-users.

SAP gave attendees at its TechEd conference here a closer look at the preliminary results of its graphical interface upgrade. While users said the interface was primed for a much needed update, some expressed confusion over the future of SAP Portal and the viability of supporting multiple interfaces for end-users.

"They're offering almost too much choice without any guidance," said Don Allen, a manager at IT consultancy, Accenture. "There's no real hard and firm rules, so portal usage as a client might be diminished."

But Shai Agassi, president of SAP's product and technology group, said SAP didn't want to force end-users into a standard interface for tapping business data. Instead, using SAP Portal as the underlying technology, multiple graphical interfaces – SAP Enterprise Portal, Muse, Duet, widgets and voice – would be supported, Agassi said.

"We don't force users into the world of SAP. We take SAP into what users are doing," he said. "We're giving our customers the option to tie the core portal engine in NetWeaver to whatever user experience their users want to be delighted with."

Muse gives the interface client the look of a slick Web site with a shell area that gives end users access to specific data and a canvas, which can be changed for a specific job function. The style is similar to SAP's Business One interface with the ease of use of the SAP-Microsoft joint Duet product, which connects SAP processes with familiar Microsoft Office products.

Questions remain about the new interface. SAP executives haven't said whether it is easy to deploy. SAP is also still determining whether to release Muse as an update or sell it as a separate product.

Muse will be released in phases with specific SAP modules for customers running Microsoft Windows. Support for Apple OS and Linux will be added later, said Filip Misovski, an SAP product strategist. SAP is also seeking customers to beta test the interface, he said.

"It's all the same underlying portal infrastructure that the different clients take advantage of," Misovski said.

SAP will still support, but will begin gradually phasing out use of former SAP UI technologies like the SAPGUI, BSP, and HTMLB Misovski said. The Muse client in addition can run HTML/AJAX and FLEX/Flash based apps.

The minimum basic requirement to use Muse is mySAP ERP 2004s. The new Muse interface standardizes on Web Dynpro and uses the tooling environment of Visual Composer, Eclipse for Web Dynpro and ABAP Workbench for Web Dynpro.

For Marc Manuel, an ABAP programmer with Shell Oil Co., Muse gives end-users a slick new look, but he said like many other SAP firms, Shell has standardized on its own custom portal application.

"We use a portal and we're happy with it," Manuel said. "But Muse adds value by giving end-users more control over company data."

2. SAP aims at ISVs with on-demand model

 

By Robert Westervelt, News Editor
13 Dec 2005 | SearchSAP.com

 

LAS VEGAS -- SAP plans to launch software in an on-demand model in 2006, but according to executives at a recent SAP analyst summit here, the model would be quite different from that of Salesforce.com and other on-demand CRM vendors.

 

 

"We will come out with a product when we are ready to come out with [one] that actually answers the needs of customers, scales and integrates," said Shai Agassi, a member of SAP's executive board, who serves as president of SAP's product and technology group. "All the base functionality of an enterprise solution needs to be in place. … We have plans that will be clarified when we are ready to clarify them."

SAP executives at first brushed off the idea of an on-demand model for small and midsized businesses (SMBs). But SAP CEO Henning Kagermann told financial analysts earlier this year that the recent success of SalesForce.com and NetSuite Inc. caused SAP researchers to focus on an on-demand model for SMBs.

Agassi said the focus will be on simplicity for small businesses, and a resulting product would be different from the on-demand products currently on the market.

"We believe the issue is about simple products with a simple way to ramp up into the product, with the need for it to still be integrated into backbone systems and the ability to actually take it anywhere you want to go to," he said. "It [asks] a much more complicated set of questions than just do I have my data on my data center or some other data center."

SAP could be timing its on-demand release with Microsoft, which is planning on-demand products by making the applications support Web services and service-oriented architectures (SOAs) and adapt to customer-specific processes, said Sanjeev Aggarwal, a senior analyst at Boston-based Yankee Group, in a recent research brief to clients titled, "Appeal for On-Demand Solutions Is Expanding."

"To succeed, on-demand applications need to be purposefully architected and developed to function in a distributed Web-based environment through the support of Web services, XML standards and SOA concepts," Aggarwal said. "This is a key requirement for collaboration, data sharing, mobile/remote workforce, multi-location enterprises and supplier-partner collaboration."

SAP is also planning a model that could be aimed at small independent software vendors, according to Klaus Kreplin, a member of the SAP extended executive board, who focuses on NetWeaver development. In his briefing to industry analysts, Kreplin said up to 90% of ISVs are small businesses and they don't have the systems to support major development on NetWeaver.

"We want to provide a hosted sandbox development system for ISVs," he said.

Kreplin called the new system the "mySAP Sandbox," and said it would support ISVs by providing the tools necessary via the Web to test modifications in a real-world environment. The development could speed new NetWeaver development from SAP partners and boost the time it takes to bring new products to market, he said.

The sandbox could be used to build composite applications, called xApps, which draw data from several sources to solve a specific business problem.

SAP Interface Technologies

Get the know-how you need about technologies like SAP XI (exchange infrastructure), PI (process integration), SAP JCo (Java Connector), RFC (remote function calls), BAPIs and much more in this collection of SAP interface tools, tips and expert advice

News:

1. SAP is Hampton's co-pilot
2. Scripting in a Box adds new languages for SAP ABAP developers
3. SAP Interface Technologies                                                                            

   

SAP is Hampton`s co-pilot  (NEWS)

A lengthy and intensive performance management technology selection process was thrown for a loop for one local government organization this year when its final choice was acquired by SAP.

Hampton, Va., selected Pilot Software for its strategy and performance management project, just before SAP bought the company. After some hand-wringing, Hampton stuck with SAP and so far the results have been encouraging.

Hampton went through a rigorous selection process and chose Pilot Software from a group of 10 competitors, according to John Eagle, assistant city manager for the City of Hampton.

"The Pilot solution was the clear leader," Eagle said. "It had a product that was easy to use, and it was one of the most affordable."

Hampton, a city of about 150,000 people located on the Chesapeake Bay, was looking to organize information across city departments -- from libraries to the police department -- so it could find efficiencies and reduce redundant processes.

"[Hampton has] probably 30 different business units; there's lots of potential for redundancy," Eagle said. "How do we manage and take a hard look at that? That's where we started talking about strategy management and performance management."

In February, just when Hampton was making its final decision on which vendor to go with, SAP acquired Pilot Software for an undisclosed sum. One of the major attractions for SAP was the Mountain View, Calif.-based software maker's PilotWorks analytics application, which had a strong customer base in the government sector, according to analysts.

The acquisition gave Hampton -- not an SAP shop -- second thoughts. Officials with the city scrutinized the decision, Eagle said, grilling SAP on what the acquisition would mean for customers, service and products.

"It was kind of a surprise and a shock to us that they got acquired," Eagle said. "We asked a lot of questions. SAP sent in a lot of people and had us on the phone with a lot of folks." PilotWorks will be "tucked in" to SAP's existing product suite, filling a hole in the company's offering, SAP said at the time of the acquisition. In the future, PilotWorks will be integrated with SAP's other applications and built on its NetWeaver platform. This started to assuage officials' concerns, but Hampton didn't just take SAP at its word. The city turned to about a dozen SAP and Pilot customers going through the transition.

"Without exception, the Pilot customers said they saw the SAP acquisition as a good thing and had a good experience with the transition up to that point," Eagle said. "We asked a lot of questions, and we got a resounding affirmation of where we were going."

Although it is still fairly early in the project, the city is happy with its decision to stick with SAP.

"The product is very easy to use," Eagle said. "It's a very straightforward tool that has a lot of power to do analysis that you don't typically have in Excel."

One place the city is seeing dividends is in measuring the performance of its 3-1-1 call center, a non-emergency number similar to 9-1-1 but designed to handle issues like potholes or burned-out street lights. Hampton uses Pilot to evaluate call abandonment rate and wait time. The city believed there was a correlation between the two metrics, but it was difficult to quantify using the old system. Both values were plotted on a graph using different scales -- wait time in seconds and call abandonment rate in percentage.

"With the old system, trying to show correlation by plotting actuals on a graph was tough," Eagle said. "In the new system, we were able to show that relationship in literally about three minutes."

Eagle would do some things differently if he were to do the project over, starting with hiring people to work full-time on the project.

"It's not the product. The product is pretty easy," he explained. "But you're talking about culture change, changing the very nature of how people do work and what they pay attention to."

A full-time resource would be able to focus on the project's technical and cultural issues exclusively, without being pulled away by other duties, and could also provide an outside perspective, according to Eagle.

He also cited some relatively minor detailed, technical issues, such as users receiving financial information in the form of full data dumps, rather than in a more summarized, usable form. Rather than problems specific to the SAP installation, Eagle chalked those up to part of doing business.

"There are some devils in the details, and you'll always have those," he said.

Phase one of the project is almost complete, with its rollout of one interface to four departments, and so far SAP has delivered on what it told Hampton from the beginning.

"So far they've come through," Eagle said. "We've been pretty happy with the service we've gotten, and we've had a lot of conversations with them. No complaints as far as that goes, knock on wood."

The city will continue a measured, division-by-division install until all of its departments are complete.

"It's a tough thing to look at, measuring outcomes and results as opposed to things you do, your activities," Eagle said. "Getting an entire organization to do that takes a lot of time and effort."

Scripting in a Box adds new languages for SAP ABAP developers (NEWS)

SAP developers may no longer have to find and install all the different SAP connectors and correct versions needed to use alternative scripting languages.

An SAP employee has developed Scripting in a Box, which packages a full open source scripting environment onto a computer desktop or USB stick. Through a single script file, a development environment is automatically configured on a drive of a developer's choice. Preloaded sample applications inside the package are ready to connect to SAP back-end systems through a login screen.

"It shows how easily it is to connect to systems and make calls and modifications on the fly," said Craig Cmehil, who developed the free product. "Refresh the page and they can have the customized changes right then and there."

The environment supports Perl, PHP, and Python and Ruby and support for Ruby on Rails will be released as early as this week in version 1.0, Cmehil said. The package includes development tools, including MySQL open source database and Apache open source server, as well as the SAP RFC library, Perl, and Python SAP connectors.

Cmehil, who serves as an SAP evangelist at the SAP Developer Network, said that scripting is being used mainly by firms that are running a Web server with a PHP or Perl engine. Companies that don't have the resources to purchase SAP Portal also can choose scripting as an alternative, he said.

"It doesn't make sense for a company to tell its Java guys that they have to learn the scripting language," Cmehil said. "I hope Scripting in a Box will give the option to a company that is sitting there with five ABAP developers and they have a PHP or Perl based intranet set up and they want to start putting data from SAP into it."

Scripts are typically used to program graphical interfaces, but developers also use them to write programs. For example, a simple address book within an SAP application or a customer based application can be written in one of the scripting languages to reduce the size of the footprint.

"If a company is running a NetWeaver installation, you can use Web services with these languages as well," Cmehil said.

Prior to Scripting in a Box, developers had to install a connector to connect to the SAP component they wanted to work with a scripting language. Scripting languages are usually shorter and take up less space, Cmehil said. For example, a program written in Java could take 100 lines of code, but if it was written in PHP or another open source language it would likely be about 20 lines of code, he said.

Cmehil said he has been working to build out the scripting language community on the SAP Developer Network. Many developers have been calling for a package to make demonstrations to company managers about how the company can use PHP to create applications that integrate with SAP, he said.

"Often the initial conversation with a manager involved saying the cost benefits of scripting are there but in order to go with a project, you've got to get a number of different pieces," Cmehil said. "It was just far too complicated. A lot of people were having a problem getting the proper versions together"

The scripting community has been growing, Cmehil said. A recent survey shows that out of 37 million domains, 9 million had PHP installed. While most SAP developers are experienced in ABAP and Java, a growing number are learning PHP and other languages, he said.

"With Scripting in a Box, the SAP guy can unpack it to his drive and the PHP guy can unpack it to his drive and they both can try it out for themselves," Cmehil said. "It's an easy way for people in two different worlds to see the same thing together in the same environment."

SAP to support Cisco technology ( NEWS)

LAS VEGAS -- Can a business run more efficiently if its network is smart enough to analyze application-based data?

Cisco Systems Inc. said yes, and today it unveiled the first components in its long-anticipated strategy to help companies manage network traffic derived from enterprise applications.

At its annual North American Networkers 2005 Conference, the San Jose, Calif.-based vendor announced the first product and services from its application-oriented networking (AON) group, a new division created to foster the network's ability to recognize and manage packets carrying application data.

The new products, AON modules for Cisco's data center switches and branch office routers, are intended to complement existing gear by providing insight into how much application data is traversing the network at any given time and confirming that data reaches its destination.

((Content component not found.))

For example, Cisco said in a statement, customer e-commerce services firm BT Radianz said it has been using Cisco's new AON products to help its clients determine when data from financial applications passes through their network boundaries and arrives at partners' networks, measuring the total time for a transaction to be completed.

In addition to the AON modules, Cisco announced that it is working with partners such as SAP, IBM, VeriSign Inc. and Tibco Software Inc. on a portfolio of professional services that align the business and technical requirements of customers' networks and applications.

Cisco previewed its AON technology at the recent SAP AG Sapphire user conference. It has been suggested that the company's AON gear would boost Cisco into the XML and Web services data management market, perhaps challenging a number of startups focusing on Web services management and XML firewalls.

The networking giant set the stage for today's announcements last month when it announced its purchase of application performance management startup FineGround Networks Inc.

It is believed that FineGround's technology, which enhances end user application response times, cuts down application bandwidth usage and reduces the load placed on application servers, will be incorporated in future AON products.

SAP Java / J2EE

1. Scripting in a Box adds new languages for SAP ABAP developers

2. Book Excerpt: The ABAP Developer's Guide to Java

3. SAP Developer Network spreads NetWeaver message

Scripting in a Box adds new languages for SAP ABAP developers

SAP developers may no longer have to find and install all the different SAP connectors and correct versions needed to use alternative scripting languages.

An SAP employee has developed Scripting in a Box, which packages a full open source scripting environment onto a computer desktop or USB stick. Through a single script file, a development environment is automatically configured on a drive of a developer's choice. Preloaded sample applications inside the package are ready to connect to SAP back-end systems through a login screen.

"It shows how easily it is to connect to systems and make calls and modifications on the fly," said Craig Cmehil, who developed the free product. "Refresh the page and they can have the customized changes right then and there."

The environment supports Perl, PHP, and Python and Ruby and support for Ruby on Rails will be released as early as this week in version 1.0, Cmehil said. The package includes development tools, including MySQL open source database and Apache open source server, as well as the SAP RFC library, Perl, and Python SAP connectors.

Cmehil, who serves as an SAP evangelist at the SAP Developer Network, said that scripting is being used mainly by firms that are running a Web server with a PHP or Perl engine. Companies that don't have the resources to purchase SAP Portal also can choose scripting as an alternative, he said.

"It doesn't make sense for a company to tell its Java guys that they have to learn the scripting language," Cmehil said. "I hope Scripting in a Box will give the option to a company that is sitting there with five ABAP developers and they have a PHP or Perl based intranet set up and they want to start putting data from SAP into it."

Scripts are typically used to program graphical interfaces, but developers also use them to write programs. For example, a simple address book within an SAP application or a customer based application can be written in one of the scripting languages to reduce the size of the footprint.

"If a company is running a NetWeaver installation, you can use Web services with these languages as well," Cmehil said.

Prior to Scripting in a Box, developers had to install a connector to connect to the SAP component they wanted to work with a scripting language. Scripting languages are usually shorter and take up less space, Cmehil said. For example, a program written in Java could take 100 lines of code, but if it was written in PHP or another open source language it would likely be about 20 lines of code, he said.

Cmehil said he has been working to build out the scripting language community on the SAP Developer Network. Many developers have been calling for a package to make demonstrations to company managers about how the company can use PHP to create applications that integrate with SAP, he said.

"Often the initial conversation with a manager involved saying the cost benefits of scripting are there but in order to go with a project, you've got to get a number of different pieces," Cmehil said. "It was just far too complicated. A lot of people were having a problem getting the proper versions together"

The scripting community has been growing, Cmehil said. A recent survey shows that out of 37 million domains, 9 million had PHP installed. While most SAP developers are experienced in ABAP and Java, a growing number are learning PHP and other languages, he said.

"With Scripting in a Box, the SAP guy can unpack it to his drive and the PHP guy can unpack it to his drive and they both can try it out for themselves," Cmehil said. "It's an easy way for people in two different worlds to see the same thing together in the same environment."

Book Excerpt: The ABAP Developer's Guide to Java

As the weather heats up, ABAP developers can cool their beans with SearchSAP.com's June feature chapter from SAP PRESS. The ABAP Developer's guide to Java is aimed at correcting the information deficit for ABAP developers facing twin-track developing in a Web Application Server environment.

The ABAP Developer's guide to Java is aimed at correcting the information deficit for ABAP developers facing twin-track developing in a Web Application Server environment. Java is often an unfamiliar arena for the ABAP community, and this book will help bridge that gap. Even experienced developers will appreciate the well-defined path to Java outlined in this book. Chapter six will delve into the application layers in each development language.

 

 

SAP Developer Network spreads NetWeaver message

SAP technology strategist Jeff Word is heading up SAP's Developer Network, an online community that represents SAP's new outlook on life. The company is giving away code samples and Web-based training, and providing a forum for users to swap war stories: the good, the bad and the ugly. SAP programmers are standing by, to offer help and suggestions -- and address complaints about things like documentation almost immediately. Word sat down with SearchSAP.com to tell us why SDN is taking off, and why it took so long to get here.

Why didn't SAP start SDN before now?
Jeff Word: Because for the longest time, SAP has pretty much ignored developers, though not on purpose. It's just that the SAP experts who were out there really were a tight knit group. They really didn't need an online community. They already had kind of an informal community.

What changed that?

Word: NetWeaver. Now we have a Java identity and a.NET identity. We are really combining the traditional SAP guys with the more Web-based, front-end guys. Traditionally, when a Java guy needed to write an application and pull data out of an SAP system, he just kind of threw it over to the SAP guys and said 'Hey, write me an interface for this.' Now that we have a full Java engine inside the SAP Web Application Server, every Java developer is now a SAP developer. They don't have to know all the gory details of SAP. We have really opened up the world to a whole new category of developers.

Is this making your BAPI guys nervous?
Word: No, it's making their life easier. Now they just have to publish a list of the BAPIs for all the Java guys to call from. And the Java guys work in the same environment that the ABAP guys do now. SO the ABAP guys have just offloaded a lot of headaches, basically. Now they can do the job that they want to do -- which is building cool stuff in ABAP.

And SDN is running on NetWeaver?
Word: Yes. It's 100% based on the SAP NetWeaver platform. It's our portal. It's our knowledge management. It's our collaboration. It's our Web application server. NetWeaver is running the whole thing.

How technical do you have to be to use it?
Word: An end user probably wouldn't find much that they would be interested in. But if you are remotely technical, you will. Even business analysts have to know some of the details of NetWeaver, as far as what the portal can do, and they are going to find great stuff here. We have different areas. If you are a developer, then you are going to see very different stuff on portals than if you are a business analyst.

Are the SDN users surprising you with innovations?
Word: Yup. One of the best things is these Web logs. I want to show you one by a guy named Joe Albert. He is the portal architect for Chevron Texaco, obviously a very large SAP customer. He's in charge of an entire portal implementation for, I think, 24,000 employees. He's an ex-ABAP guy. Now he's a NetWeaver guy. One of his best stories was about going live with Employee Self Service.

What happened?

Word: Well, he has rants. Basically, the documentation sucked. That's basically what he said. Now if you are an implementation partner, this is amazing stuff to read. Now you can avoid the same trouble. Even better, all of SAP's people, our product managers, the guys who write the documentation, they read this stuff, too. The product manager for this actually read this the same day that he posted it, and changed the documentation. He incorporated the new stuff within 24 hours.

Once people see this they flip out. Honestly. You can't imagine the reaction. They say 'My God. Thank you. This is the best thing SAP has ever done.'</P

SAP is not known for saying things like 'Chevron had a bit of a nightmare problem -- and now you can all read about it.'
Word: I can only say that's the Shai effect. SAP is opening up in every way possible. Shai's vision for this is that every person in the SAP eco-system will participate in this community and share knowledge. That is the grand vision of NetWeaver