Keynote: Karl Kessler

[00:00:03]We are now at the last session.

[00:00:06]This time it's the farewell session from Karl Kessler.

[00:00:10]And now I have to make the question, who of you does not know Karl Kessler or has never seen this face?

[00:00:19]>> Congratulations.

[00:00:21]>> [laughter] >> Well, you have to understand Karl Kessler is like you say in German, ein Urgestein der SAP.

[00:00:31]He was there, I don't know, they open up the building and you jumped simply popped up.

[00:00:36]>> Yeah, we'll we'll come to that.

[00:00:38]>> [laughter] >> And I really find interesting because didn't matter before Corona or after Corona where we were traveling for an SAP event, somehow he was always there.

[00:00:51]And you could always approach him with a question, maybe a smart question or not so smart question, but he always was listening. And he was so well connected or still is so well connected, Karl, that he would manage to always direct you to the right people to talk to.

[00:01:07]Yeah, even had nothing to do with the upper world or the NetWeaver world because he was in the NetWeaver product.

[00:01:14]>> SAP product management.

[00:01:15]>> Yeah, exactly.

[00:01:16]>> Not too bad.

[00:01:17]>> And he still knew everybody, so we were like, "Oh, I have a problem about solution manager." And he was like, "No problem, I will take care of this."

[00:01:26]Well, this is really the the level of SAP employee we really want. Do you still need the bonus?

[00:01:33]We really want.

[00:01:35]He is a role model for every SAP employee.

[00:01:39]And it's also a little bit sad that he's going. He's You're not going to extend your your stay at SAP, yeah?

[00:01:47]>> Uh I think end of October it's all gone.

[00:01:50]Sorry.

[00:01:51]>> End of October it's all gone. You didn't mention the year.

[00:01:55]>> [laughter] >> Karl didn't mention the calendar week.

[00:01:59]>> [laughter] >> The quarter?

[00:02:01]>> The quarter, the minute.

[00:02:02]>> Just the month.

[00:02:04]But okay. [snorts] >> Some October.

[00:02:06]>> Yeah, some So we still have you for 50 uh 5 years.

[00:02:09]Perfect.

[00:02:11]So but uh uh enough of this. We already have here a nice laptop and we have the Das Wetter laptop equivalent.

[00:02:18]And I'm done what did you work here but it's now your session. And I think it will be really really funny to see how you are doing your farewell.

[00:02:28]>> Thank you, Tobias. Thank you very much.

[00:02:31]I really feel honored to talk to you.

[00:02:34]Um tell share a little bit memories.

[00:02:37]I took the freedom to add our famous logo at that time.

[00:02:43]Uh so it's not up-to-date as you know.

[00:02:47]And uh let me let me start when I joined SAP. Tobias already alluded to that.

[00:02:52]That was back in 1992. I started 2nd January 1992. So it's now about 35 years all in all.

[00:03:01]And Waldorf was easy to discover, I would say, at that time. So we had basically three buildings.

[00:03:08]Uh the first one was the MBS Max-Planck-Strasse.

[00:03:11]That is where the founders built the first building. We had the Schulungszentrum ESZ. You see it here with the red rooftops at the left. And then uh in '92 the EVZ, the Waldorf 1, which is currently being renovated, had been just built. Yeah, it was ready to uh for move in.

[00:03:29]So I had the pleasure to move in about April time frame.

[00:03:33]And somehow it was also the 20th birthday of SAP. So it was perfect time to join new building, lots of parties, everything else. And life was easy compared to to today. Yeah, so if you look at uh we had one product. Imagine that.

[00:03:49]Just one product was called R/2.

[00:03:52]And it had 3,000 customers, so it was well established.

[00:03:55]Uh very easy going.

[00:03:57]Um you might ask how why did you join SAP? Yeah, there is a little bit of history. Um before R2, there was R1. Uh at that time it was not called R1, it was called RFM. Real-time finance and materialwirtschaft.

[00:04:13]Also, finance and materials management.

[00:04:15]And my father, he was actually uh EDV-Leiter, IT manager, uh elektronische Datenverarbeitung. And he was with L'Oréal.

[00:04:27]Uh hair cosmetics, as you know. And they had a factory in Karlsruhe, yeah?

[00:04:31]And he said, "Dear boy, I think SAP is a good point to start. Go go to those guys. They they know how to do it, yeah?" So, he was an early adopter. He was basically the 20th customer of R1, yeah? And L'Oréal stayed with SAP, as we know today we're talking AI and everything. I just had a recent conversation with them, they will celebrate their 50th SAP adoption year, yeah? So, that's also pending.

[00:04:57]Yeah, but now let's a little bit go more technology-wise. Um How does how did ABAP evolve? So, I'm always a little bit interested in history and sometimes I bother my dear colleagues with my history stuff. Um but I think it's interesting to see that ABAP also evolved from earlier reporting capabilities, so to speak. I think with AI it would be interesting to see whether we could sort of rerun this whole evolution through an AI context.

[00:05:26]Uh probably a little bit hard to read on the left-hand side. You see the so-called Y ABAP, Y ABAP. Why was it Why was it called the Y ABAP?

[00:05:35]Because uh it was assembler macro, yeah?

[00:05:38]It was assembler, and you see all of the macros, they already started with Y, yeah? So, we always uh have this habit at SAP to things start was said or with Y or with X.

[00:05:50]And these Y macros actually were reporting macros. Reporting macros that you could use for example in order to define the report. Here you see for example something like ZB, silent brighter 132.

[00:06:03]Or here you see the bookings price company code, account number, account some business area and so on and so forth.

[00:06:16]And just to look at it, it's hard to program I would say, how to debug, how to work with. And then a very creative guy, Gerhard Rode, he said cannot be, cannot stay with that one, so forever. And he had the task to write tons of reports and he said, "No, no, no, I won't do this. I will create my own programming language.

[00:06:38][clears throat] I will create my own reporting abstraction." And he invented ABAP/4, ABAP/4. Basically, it was a two-step approach. Some some tell it it's the ABAP/3. ABAP/3 was basically the first generator that was a two-pass. That means you had an ABAP syntax like here on the right-hand side.

[00:06:58]For the for the older guys here, logical database programming, get master segment, get detail segment, get SA SA SB SC, so Sachkonten.

[00:07:09]These type of things, accounts, account statements, and then it would process.

[00:07:13]So in in modern terms, that's for data service I would say. Yeah, so and and what he did, Gerhard Rode, he built basically a generator like we do today with AI and he took this as an input and generated the Y macros as a runtime. And then in a second step, he had to compile the Y macros one more time.

[00:07:34]And then it was big step forward because that was always a two-pass activity.

[00:07:39]Then he He his own interpreter or ABAP processor, or we call it today, which is still a little bit in place, I would say, because it produced those control blocks. Control blocks are basically the statements that you see if above code is being executed. So, for each statement a control block is basically being generated.

[00:08:00]And um uh one of the great achievements from from Gerhard was first at all that he invented this abstraction. Second, that he kept it completely downward compatible.

[00:08:13]Until today, the above code is compatible to those old versions. Of course, we have added a lot of stuff, um but even old programs from the '90s still run more or less unchanged. Yeah, and that was big achievement. It was a very important value prop also when we moved from R2 to R3 that we could move the code base as much faster um to the new client server paradigm.

[00:08:38]Okay, I should speed up a little.

[00:08:40]And now, we have a little bit of a video here.

[00:08:45]And uh let me explain what's happening.

[00:08:47]We are in connected to an R2 system.

[00:08:51]And you see um there's a transaction called TM38.

[00:08:55]I hope you can see it nicely uh captured. The TM38 roughly corresponds to the AC38 in the classical workbench.

[00:09:04]Um it's all in German, sorry. At that time, uh original language was always German, so you have to use your AI tools and translate it.

[00:09:11]Uh which isn't easy one.

[00:09:14]Um and uh now we start the TM38.

[00:09:18]And this is a wonderful menu. You see a program, and function keys, and attributes, debug variants, and the program directory, and batch. Who talked about batch today?

[00:09:30]Um I think it was Marcel. Um new programs, you could even print programs. Who does this any longer? And uh and we go inside the program editor.

[00:09:41]And we had those wonderful error 001 or Schulungs training reports. And then you see the above editor at that time.

[00:09:50]But it looks fairly well structured. You have a block of commands on the left hand side line numbers. You have a very defined line width, yeah, 72 characters, that's it.

[00:10:00]And then you see the report segments again, the data type data declaration, breakpoint statement and this famous get car. So car was the Kundensegment, Kunden A Segment, customer master. And then you have a write statement, print the account number, the name, the the location and the land.

[00:10:21]The country. Oh, okay.

[00:10:23]And then you have a little >> [laughter] >> command prompt here in the upper left.

[00:10:27]So you can run this beast. And there you have the selection screen. Now we don't specify anything important. And then you add a completely new world, the above debugger, the above four debugger at that time. And as a matter of fact Gerhard was very abstract guy, so very very knowledgeable mathematician, etc. And he said debugger, we don't need debugger. We we we abstract, we write, you know, we we we we we code, that's it. We prompt today with you would say we prompt, yeah. And but then the second guy in the above team, he used to be my boss. I believe he said, I think we should do for our application development we need a little bit of a test help. Is this is it okay, Gerhard, if I write a debugger for it?

[00:11:11]And that was the that was the basically the birth of slash H, yeah.

[00:11:16]Here Uwe is sitting.

[00:11:18]Yeah, so slash H, that was invented here, yeah.

[00:11:21]And you see nicely you see the fields on the left hand side, offset, options, C super C, a runtime, C index, C tabix, who knows that in term tables are so well known.

[00:11:33]Has not changed ever ever since, yeah.

[00:11:35]Okay, and then we go ahead.

[00:11:39]And yeah, yeah, come on, come on. And next step is then we go to a very deep dive into the runtime architecture.

[00:11:48]That looks fairly fairly assembler oriented. So, we won't go through all of the details and I I have not the knowledge, yeah. So, but but what you can see is uh above was always driven by those tables. Yeah, you had a header and you had a directory, the base table, trigger table, trigger because the events were event oriented, the reports were event oriented. A trigger like start of selection would then be executed. And these were basically the base addresses where the corresponding code was was uh compiled. And then you had symbol table, literal table, and constant table.

[00:12:20]And then you have op codes like in the assembler program, you see brea for breakpoint, it's the 38. So, if if there's the character the byte 38 38 in hex, um that is the code and then you would basically jump to the corresponding implementation of breakpoint. In that case, you would then call the debugger and you had dump analysis. Of course, this was not was not the user interface for the above developers, yeah. That was just for the designers of the above program and runtime environment. But it's it was always visible. It was even visible, I think, in R3 in the early days. Today, it's a little bit hidden. I read note the other day and it somehow you can still get it, but it's it's buried practically.

[00:13:00]And um and the next step is then uh yeah, I mean, we had dynpros. I forgot who knows that. And dynpros were in invented by our founders, yeah. That was Dietmar Hopp and Hasso Plattner.

[00:13:11]They invented the famous dynamisches Programm. And uh in the dynpro, you have fields and types and events. Uh um so, you have a flow logic, basically.

[00:13:23]And guess what? That also needs to be coded.

[00:13:26]So, we go a little bit further down the road.

[00:13:29]And what we see here is a Dynpro in design time mode. But guys, it's not above four. It's assembler. Yeah? So, what you can see here is uh assembler macros. Image formed by it.

[00:13:41]Buchungskreis Belegart Wareneingang. So, that means goods received.

[00:13:46]Etcetera. And then here you see correction numbers where the stuff has been added, a header field at the very bottom. Um so, the Dynpros So, that's the the that's the field list, if you will. And then let's go one one more.

[00:14:01]And then you see uh basically the logic.

[00:14:04]The events down here, the module steps.

[00:14:07]Yeah? M step and S step. And here we get some uh familiar guy, PBO, process before output. But we had many more.

[00:14:15]Yeah? So, we had field on value help and we had we had PBO, PAIDCO, data communication output, data communication input. They have been simplified in R3.

[00:14:24]That step went away, thank god. And uh and there was also an EOD, an end of Dynpro, where the next Dynpro would then be processed and would be followed. Who has some basics in R2? Hands up.

[00:14:36]Ah.

[00:14:37]>> [groaning] >> Hey guys.

[00:14:40]Jump in if I do if I explain something wrong, yeah?

[00:14:45]R2. All right.

[00:14:47]The community is still up and running.

[00:14:49]Good.

[00:14:50]Okay. And then uh last but not least, also a little bit of an application uh at the time.

[00:14:57]So, again we turn a transaction. It is a menu info system.

[00:15:01]Okay.

[00:15:02]Uh sometimes jumping a little bit back and forth between the the CICS, between those numbers. So, we see here uh where where was probably not the the the easiest way to find it. Uh so, now we are calling an OK code. Uh a slash N or the slash came with R3. So, it was just N.

[00:15:20]N and N info four characters, not so much and then you had things pretty familiar you should pretty familiar with with those corrections and development notes and error notes you know that nasty stuff that comes in real life practice and uh and then you go in and say okay I navigate into the corrections for example and da da da okay little pause here and then okay and then you have the famous search screen you might have seen that also in some other R3 online correction system you can search for for keywords and stuff so in this case we're looking for little application arson RS on and right and then you see our two corrections have been found one from my colleague uh Ditmar Ditmar Ditmar Ditmar and another one I don't know and it's release 508i 50 e you know at this at that point and at that time we did not deliver always the full let's say source code like we do today first the description sounds familiar the symptom the cause the solution I think our notes still look like that so we inherited this from R2 and one last thing and then we're done with the R2 stuff what you can see here is then again function code 17 so if you had not the chance to do corrections in above then you have to do it in assembler and then you get here the assembly codes yeah register access branch zero for those move character or horrible uh assembly codes so that was also possible you could fix basically your application programs also patching assembler code good I think that's enough Um, quickly move on.

[00:17:18]And uh then came R3.

[00:17:20]And the funny thing is that my my former boss, Harald Koch, he always said, "Karl, you joined the company when all the R3 work had been done already."

[00:17:28]Uh probably a little bit of a truth, yeah.

[00:17:31]In 1992, it was introduced to the market.

[00:17:34]And I looked much better, yeah. So, compare this to the 3270 terminals that we had with with uh from IBM. Uh now, it was graphic, it was workstation. We we had the famous Motif GUI here on the left-hand side with the very baroque menus, uh 3D, and what have you.

[00:17:52]But if you drill down then a little bit deeper, then you see it's still the old uh terminal stuff, yeah. So, we emulated terminals, basically, yeah. And it was was embedded into Windows, and you could have two or three of them. You could go to R2 and to R3. And yes, we did also some marketing, product management, adding some business graphics, uh but in essence, it was a screen, it was a terminal. I mean, it was called SAP terminal SAP terminal emulator at the time.

[00:18:15]But I found myself also being quite uh enthusiast going to conferences. I've done this over the last 35 years to talk many times. My first one was BASIC Congress. I would say it's a little bit of first upper pump.

[00:18:29]Uh was in Karlsruhe. I think it was Was it in German? I don't know whether it was in German or or international. But this is Karlsruhe, Gartenhalle Kongresszentrum.

[00:18:39]Exactly, yeah.

[00:18:41]So, um in R3, it was hit the market.

[00:18:44]That was super cool. It came out mid of 1992.

[00:18:48]But with a uh let's say a little bit uh old-fashioned user interface.

[00:18:53]And then uh to give you a little bit of an impression how things were discussed uh back in home again.

[00:18:59]Um uh here we have I we tried to capture the the fifth floor of EVZ. The whole basis team fit into the fifth floor. And please excuse that I have only put some names into it. That does not mean that they have done the job and the other ones are unimportant. No, it simply means you have a sort of a network contact network and I think it's important. First First axiom was always you're you're new here. Everybody reports to Hasso Plattner. That was clear from the very beginning. So, all reporting lines end with Hasso Plattner.

[00:19:31]And then we had large teams. I think the the dominant team was the above team on the left-hand side. You see here the above runtime, Yatto D. And then some some colleagues might know Andreas Blumenthal. That was our intellectual above objects guy with Jürgen Heiman and Reiner Brenlin and a couple of Helmut Pressel just left the year a year before the team. So, that is really our three team. We had the workbench with Willie and a couple of others.

[00:19:58]Um Walter Walter Kirchgessner.

[00:20:01]And we above team afforded the luxury to run a little APM team. That was my start here. Yeah, so because that was my colleague Andreas Ebeling.

[00:20:09]And then we had the database group. That was a super large team. Karl-Heinz Hess.

[00:20:15]That was the database runtime. That was the porting. That was the dictionary.

[00:20:18]That was the transport. And that was the archive. Everything that is close to database services was was managed with with Karl-Heinz.

[00:20:27]And then on the right-hand side that was a little bit and they they did a little bit the job on their own I would say.

[00:20:32]They were all connected but the database had to cover with database portings.

[00:20:36]Yeah, we started on Oracle. And we had too many Oracle dependencies in the beginning.

[00:20:41]So, they did a great job to get this also running on the other platforms like like SQL Server and others.

[00:20:48]And greetings to Holger. And uh And then we had another area I would say that was the other fraction. And they came then when when we decided to to build a GUI, not just a terminal and not just a terminal but the sub GUI. And that was Frank Bunswick and a couple of others. And then the client server team of course, with with Albert Becker, Harald, Edgar, Gunter Zachmann. And then also some interesting teams that were in the area more of office and workflow automation at that time.

[00:21:19]Um and the the I I would say from a from a bird's-eye perspective, the above team was a bit conservative at that point in time, yeah? They were we we control everything with above and it's the it's the grail, if you will, and we we own the language description and and innovation goes through the above compiler period, yeah?

[00:21:38]And then came the other teams.

[00:21:40]Sub GUI, they were pretty much object oriented, yeah? So, they said, "No, no, if you want to advance fast, you need to be object based or object oriented."

[00:21:49]They came with the Windows skills, with the Microsoft skills.

[00:21:52]Um and then suddenly client server, these guys, they were basically managing Harald and folks, they were managing performance on session management, shared memory, and pipes, and and and sockets, and all that stuff. That was more on those sides.

[00:22:08]So, um I would say um the above team was a bit challenged by those folks, especially by the Sub GUI team and also by the workflow team, because they said, "Let's go object orientation, yeah?

[00:22:17]Let's not only do data type conversion and stuff, structured data types."

[00:22:22]And uh uh but uh it's clear that that was the dynamic we had to um achieve, but we invested then into the workbench. And let's quickly move over to that. We have now a little bit of a pause.

[00:22:36]Because now it gets really tricky.

[00:22:40]And suddenly it's here up, no?

[00:22:43]It's going to get dark for a second.

[00:22:47]>> [snorts] >> And we went to our museum, SAP museum.

[00:22:54]And found uh old laptop.

[00:22:58]Careful, guys.

[00:23:00]It's like moving a piano.

[00:23:04]Super. Thank you.

[00:23:06]Perfect.

[00:23:07]Uh here is here is uh the HDMI, so this machine is not connected to the internet. It has no HDMI port. It has only a VGA port.

[00:23:17]But with some magic from Søren and folks Ah yeah, yeah, yeah.

[00:23:24]Now now comes the famous You need to pull pull FN and F3.

[00:23:30]Da da da da.

[00:23:34]Checking input.

[00:23:40]What is Thank you. Thank you. Too early. Too early. Too early. It's not It's not enough. I also need to see something here.

[00:23:46]So, maximum maximum risk. One more time.

[00:23:52]And It's mirroring. Woo.

[00:23:58]Windows NT is running. I hope the guys over there let's see something also.

[00:24:03]Cool. And then I take this mouse.

[00:24:07]And what I'm now doing is I'm starting all programs.

[00:24:11]And here is uh wait a sec. Where was it?

[00:24:15]Sup.

[00:24:17]R3 mini. Yeah, here.

[00:24:19]Here we go.

[00:24:23]Now, and we're starting a little system here.

[00:24:27]It's called the mini basis system.

[00:24:30]No? And you see that it's oh, a lot of failures. Dispatcher and work processes get started. And there was also a gateway program.

[00:24:38]But imagine at that point in time, no internet, no HTTP, no ICMP, no nothing.

[00:24:45]So, um let me now go here and to the to the well-known sub GUI that always that always should work.

[00:24:58]So, mini basis system.

[00:25:06]Ripples.

[00:25:07]Sebastian Ripples.

[00:25:13]>> [applause] >> VICTORY!

[00:25:19]>> USER, AND WHAT WAS THE PASSWORD? Nicely password directly on that logon screen.

[00:25:25]R3.

[00:25:26]Don't type wrong, otherwise it will kick you out.

[00:25:29]And then, da da da da, still a license.

[00:25:32]I have I have no clue. It was >> [laughter] >> Thank you, Microsoft, again.

[00:25:39]Who whoever donated us this license.

[00:25:42]Uh by the way, I might say that it's a sequel engine running. It's one of those early sequel engines.

[00:25:49]And it was still running.

[00:25:53]>> [gasps] >> Uh yeah, and then okay, some of the older guys still know that it was not SE80, it was SEU Entwicklungsumgebung. So.

[00:26:05]And then you have EntwicklungsKlasse, that's the term for package these days, yeah? Used to be development class.

[00:26:11]And then you have the selection screen, and you say display.

[00:26:16]Why not displaying this development class? Our workbench demos, nice.

[00:26:20]And then you can see I yes, here's the day dick, and here's the database tables. And you have here the jump to navigation.

[00:26:30]Uh navigation works.

[00:26:33]What do you say?

[00:26:35]Data elements, uh dictionary, so we were already semantically our programs.

[00:26:42]And you could even see the classic ABAP editor. You know you know this guy? Our classic ABAP editor with the block commands.

[00:26:51]Like this.

[00:26:54]Smells.

[00:26:55]>> [laughter] >> Okay.

[00:26:58]We have We have flashbacks here in the in the audience. People People don't feel well. Let's go back to the to the other stuff.

[00:27:05]Yeah, okay, the programs and then transactions.

[00:27:09]And here, yeah, at the time I was responsible for the product management of the tools together with my team.

[00:27:14]And we had already used We were a little bit better. Sorry. Um but we already used the controls. Yeah, the the objects.

[00:27:25]Ay, ay, ay, ay, ay. And you could you could then, for example, and this is now very historically very important because it's the only picture application that shows our nice EVZ building in old format. Yeah.

[00:27:37]Still there. And then, of course, a lot of other stuff you could you could do here, for example, the coding. Yeah.

[00:27:43]Just copy the coding. Also, why is that wipe coding? I don't know.

[00:27:47]And uh uh table control and where's the the grid The grid, yeah, here. Grid with menu button. Wow.

[00:27:54]Half grid, always popular. Oh, it it looked it looked a bit like a band dump already.

[00:27:59]Not bad.

[00:28:01]So, when we did the preparation and Bo helped me a great deal, uh Bo said, "Hey, this this workbench is fully functional. Why don't Why do we need something else?"

[00:28:11]>> [laughter] >> Yeah. So, and of course, I have to tell you So, there was just this guy and I also want to show debugging. Yeah, debugging, of course. So, so you Here generation was a little bit We had to make this more compliant.

[00:28:26]Yeah, that looks like atomic power. And and here you can then test and say debug. Not direct, but debug and laufzeit analyse, so And then all is everything there. Yeah, you say return, poof, and then you step through the code step by step. Oh, no, sorry, that was the wrong one. Return.

[00:28:45]Uh let's do this guy here and then layout, see you nama. Call function.

[00:28:51]And here is the describe table.

[00:28:55]And then you could say, "Yeah, I want to see this table, tabella."

[00:28:59]And double click.

[00:29:01]I'm sorry. Uh, that was breakpoint, yeah. Also good. Also useful. But I should double click the tree, and here as is the character is the tree, yeah.

[00:29:10]So, who Who needs Eclipse? Who needs VS Code?

[00:29:13]This is all working here.

[00:29:14]>> [laughter] >> All right. Okay, so that was our little excursion into the R3 world, but still I would say it was clear that that it was fine, and we did a lot in rollout and early tickets, etc. But I was still still screen-oriented at the time, yeah.

[00:29:35]So, the the the the tree list of all the details RS3 function is still in the system function module RS3 list display.

[00:29:42]You can look for it.

[00:29:43]Uh, and was So, controls were missing. They were added by in the workbench one release later.

[00:29:50]And but it was clear, and now we have to switch back to the other tool that there is even more ahead of us, yeah.

[00:29:59]So.

[00:30:01]Quick ball poser.

[00:30:04]Uh, jetzt muss ich den hier machen.

[00:30:06]Send it now. Ah, yeah. Thank you.

[00:30:09]You know, without assistance you have no chance.

[00:30:12]>> [laughter] >> Don't kill my VGA board.

[00:30:16]>> [cough] >> Three three three strap strap strap.

[00:30:20]>> [snorts] >> Thank you so much.

[00:30:24]Ooh, I'm so I'm so happy.

[00:30:28]Function.

[00:30:30]So, we we survived the VGA adventure.

[00:30:34]Life feels better now.

[00:30:36]And Ah, ja, genau. Danke.

[00:30:44]And then it was clear something needs to happen. We need to do even more.

[00:30:51]>> [clears throat] >> And it was always important also to convince our basically the king. The king has a blood now. I mean we had very mighty princes in development, yeah. Database and above and client server. You saw You saw the teams.

[00:31:04]Uh but it was clear now with the Also with my Microsoft had a lot of influence.

[00:31:10]At that time Bill Gates visited Waldorf, yeah. It was '94 or '95, '96, something like this. Bill Gates came to the canteen in EVI set. And I have to tell you they changed the canteen into a Microsoft building. It was really fun, yeah. So transparent windows and team, Microsoft SQL Server, everything you actually I'm Am I here with SAP? You know, looks like Microsoft job. Okay, but it was fun. It was really fun. And then we said, "Yeah, we need to move one step ahead." And then the internet came across, yeah. You You saw HTTP missing. So we had to enable all the internet.

[00:31:45]And at that time the idea was not only to, let's say, GUI and nice graphics here and there, but also think internet in the sense of we need now the next level. We need self-services, yeah. So far you You remember the transaction that was super complex, yeah. Tons of fields. Even if they were graphical, was even still complex to manage those fields and manage the database dependencies and what have you and and of course our board also he thought about we need We now We now to implement self-services.

[00:32:20]Moving along and then we said, "Okay, let's do that."

[00:32:23]That was You saw the the the workflow team. They had ideas to build self-services, Wolf and and Franz.

[00:32:30]And then we went to Sapphire.

[00:32:33]And said, "Okay, let's let's sell it.

[00:32:35]Let's sell the self-services to the market.

[00:32:38]And here we go.

[00:32:39]>> [cough] [clears throat] >> The next one is a fun application.

[00:32:48]Where's the Coca-Cola?

[00:32:50]>> The Coca-Cola is coming.

[00:32:53]>> Coca-Cola. Here's a Coca-Cola fast food application. It is just a demonstration what we can do as normal above four programming using using bitmaps and OLE communication.

[00:33:08]And we build applications which >> Also, one moment, please.

[00:33:13]>> [laughter] >> I think it's done here. Otherwise, it's we are losing too much uh Uh what is it here?

[00:33:22]I I'm at maximum.

[00:33:25]Also, in video. Okay.

[00:33:28]Okay. Uh here.

[00:33:30]Uh yeah, okay. I can add one more. Oof.

[00:33:33]Okay.

[00:33:34]>> [clears throat] >> Oh.

[00:33:48]There's one. Last chance.

[00:33:54]>> The next one is a fun application.

[00:33:58]Where's the Coca-Cola?

[00:33:59]>> The Coca-Cola is coming.

[00:34:02]>> Coca-Cola. Here's a Coca-Cola fast food application. It is just a demonstration what we can do as normal above four programming using using bitmaps and OLE communication.

[00:34:18]And we build applications which look totally different to the ones you know.

[00:34:23]And here and there you hear SAP is character-based and we are still in blah blah blah. It's not true. Again, we were so busy with mainline products that the little fun parts uh didn't really could materialize. We couldn't spend enough energy on these areas here. In the future, we will have more fun than in the last 8 years.

[00:34:45]I can guarantee that to you. So, how does the application work? Can we Can we pour in some cola?

[00:34:52]>> I'm just logging on now.

[00:34:56]>> [laughter] >> Okay, just selecting the above for editor.

[00:35:03]>> Is it pizza service? Actually, that's that's a service I want to be in I've great ideas how I can make money there.

[00:35:11]You do nothing. You just have a PC at home and that's all you do. And even the PC you can rent. Just the idea.

[00:35:19]>> Welcome to SAP Pizza Service.

[00:35:25]>> Voice animation is mandatory. So, now I want to order a a Coke.

[00:35:33]>> Another drink has been added to your order.

[00:35:38]>> Uh there's one little mistake.

[00:35:41]There's one little mistake. There is no Coca-Cola rendering machine offering Pepsi. So, Coca-Cola, please apologize.

[00:35:49]This is a major mistake.

[00:35:54]>> [applause] >> So, now There's some business sense for this type of application.

[00:36:11]When you When you When you look at the next generation ATM machine and you see someone counting your money >> been added to your order.

[00:36:19]>> Thank you.

[00:36:20]>> Okay, excuse me.

[00:36:21]>> And now we can do the same with the pizza and they will tell us that anchovies and broccoli, and and uh, and I don't know what is incompatible and will not work, or that the chef is not recommending this combination. So, any kind of artificial intelligence can be built into that product here.

[00:36:42]And I can tell you, I want to have applications of this type.

[00:36:46]They They are perhaps not able to uh, to to support super multinational, super multilingual, super super multi multi companies.

[00:36:56]But here and there we have a desire for just a plain Coke.

[00:37:00]And to pull the And you you know what I mean? This type of applications like um, the the ATM machines, like microwave ovens, will become part of enterprise applications like the SAP system. And we should not feel ashamed that this is less complex.

[00:37:20]Thank you very much.

[00:37:22]>> Thank you for ordering SAP Pizza Service. Your order will arrive within 30 minutes.

[00:37:29]>> [applause] >> All right, that was Hasso. Um, so, yeah, uh, now it's time to say a little thank you, a big thank you to many people involved.

[00:37:44]Um, first I have to thank Bodjo.

[00:37:48]You've done so much preparing with me the session, wonderful.

[00:37:52]THAT DESERVES AN APPLAUSE. [applause] >> [applause] >> UM, SO, JUST IMPRESSION, I I always like conferences, therefore I like so much also the above conference. Take it, it's coming back smoothly, step by step.

[00:38:11]We've done a lot of tickets, Berlin, you see you see the Stammtisch.

[00:38:15]Uh, you see um, yeah, ticket Las Vegas, we made nice trips to the Monument Valley and elsewhere.

[00:38:22]I really also want to thank our team. So that's Bojo, that's Sebastian. Where is Nora Nora?

[00:38:28]Um, wonderful two years we had together.

[00:38:32]Um, and uh, yeah. And then I really want to thank you for all your interest over the years. Uh, I've done a couple of sessions I guess.

[00:38:41]Take it sessions and so on.

[00:38:42]Um, and I also want to thank the our conf team.

[00:38:46]Uh, Tobias, Soren, Domi.

[00:38:48]First. Please come to the stage.

[00:38:52]I have a little present for you.

[00:38:56]I mean, it's it's kind of a return. This is uh, the Rückgabe von Kulturgütern.

[00:39:02]So the >> [laughter] >> return of cultural assets. These are the posters from uh, up up conf in Rot.

[00:39:10]>> [laughter] [applause] [applause and cheering] >> Yeah, and then thank you very much. I Did I manage with time?

[00:39:26]Well, I can be improved. Next time. Next time. Thank you.

[00:39:33]>> [applause] [applause] [applause] [applause] [applause] [applause] [laughter] >> You know we are from Austria, so of course we thought we we have to bring something for you.

[00:40:29]>> Oh.

[00:40:30]>> Uh we are we are not good in soccer, but we are good at >> In soccer.

[00:40:34]>> Good at [laughter] >> In in soccer.

[00:40:35]>> Good at in soccer.

[00:40:36]>> Not soccer, but soccer.

[00:40:38]>> But the soccer was good yesterday.

[00:40:41]>> Not good enough. Not good enough.

[00:40:43]And here also some a little bit wine.

[00:40:45]>> Oh, what was it?

[00:40:45]>> Sweet and Almdudler and all that.

[00:40:47]>> I'll I'll be we'll have nice fun. Thank you so much for this. Thank you all.

[00:40:50]>> You're welcome.

[00:40:51]It's very heavy. It's very heavy.

[00:40:52]>> Oh, oh.

[00:40:53]>> [applause and cheering] >> For the team. For the team.

[00:40:55]THANK YOU.

[00:41:00]>> SO.

[00:41:03]>> OH, >> [laughter] >> THE FRESH TUNA.

[00:41:09]>> UH YEAH, Carl going in.

[00:41:19]>> You [laughter] are the best of the best daddy OF THE WORLD.

[00:41:24]>> [applause] >> OH.

[00:41:37]AH, SO SO.

[00:41:38]>> [laughter] >> THIS IS THANK YOU SO MUCH.

[00:41:45]>> ALSO and one thing I have to uh say I'm still online. Uh I I have uh um this famous uh if you're only if you're interested. I have it on a USB stick. So it's six >> [laughter] >> It used to fit on one CD.

[00:42:06]It's uh sub GUI. It's uh data the database from Olga. It's uh the above stack on time no HTTP nothing and yeah it's up good RFC library I guess so you'll get it I have an idea.

[00:42:24]>> [laughter] >> We'll do this later.