I'm flying to the less glamorous Sapphire this afternoon. Us Europeans don't do that conference thing as well as our American cousins do. They get Sheryl Crow and we don't. Nevertheless it is a good opportunity to dig deeper into some of the messages announced in the US, and talk to customers and partners.

I remember attending the 1996 Sapphire in Vienna, where most of the presentations were in German with a form of English translation. If you think understanding SOA, ESA etc is tough today, imagine the poor translators simultaneously expounding on the benefits of R/3 three-tier-client server  and BAPIS back then. We had just as many slides, but the graphics and grammar were worse. The conference bag was nice though, and I got to hear lots of Mozart and waltzes.

I googled Sapphire 96, and found very little. Much has changed in 10 years it seems.

This is how AMR covered the event then:

Next Releases of R/3: The primary focus was on the newest release, R/3 3.1, which adds Internet and intranet capabilities to R/3 and is scheduled to ship by year end. This will be followed by Release 4.0, scheduled for first customer shipment in 3Q96. Release 4.0 will feature the "componentization" of R/3 – SAP intends to divide its software into discrete software components or business objects without sacrificing the integration for which R/3 is known. At the SAPPHIRE conference in Vienna (see The AMR Alert on Manufacturing June 21), SAP had announced its intent to divide R/3 into three pieces: Financials, Human Resources, and Logistics (includes Manufacturing). Instead, Financials and Logistics will stay together until Release 5.0.

BAPI's are the first major delivery of components that will make up SAP's new Business Framework architecture – announced at SAPPHIRE 96. The Business Framework architecture consists of SAP business objects which have been developed with input from customers and partners to ease the task of integrating add-on products and customizations with R/3. The low level complexity of the SAP application (and the ABAP/4 development environment) are hidden from the user. Microsoft's COM/DCOM broker technology is used to allow any external application to call methods of the objects housed in SAP's business object repository. The business objects then utilize an internal SAP broker to interact directly with the correct SAP R/3 remote function calls (RFC's). This allows SAP, their customers, and partners to code to a common abstraction layer, eliminating the rework that is usually required when any of these parties changes their application code

Hmmm, somethings change and somethings stay the same.

Technorati tags


About these ads