Or, we've got the ability to actually cache Web information down onto the devices so that if I want to see results of an analysis or a query at a later point in time and view them, I can do that. If I'm out at a customer site and I'm taking a survey, I can fill in my different information on a form and synchronize that, either wirelessly or not, via a cradle. So, basically, we've addressed the gap in wireless connectivity via a Mobile Engine by allowing for intermittent connectivity.

Obviously, that's not going to be needed, hopefully, forever. Over the next few years, as the connectivity wars straighten each other out, they'll come up with a solid online plan for the country and the world. Obviously, they aren't ready for that because everything is built using the standards-based approach: XML (Extensible Markup Language), Java, etc. But, we've got the solution that's available and ready now and can be used, now, regardless of the connectivity.

DG: This is really interesting. Everyone can picture how an online system like yours can connect in when you're talking about wireless, because you've got dynamic access; you can immediately check and see, if a certain product is in stock, for example. How does the HotSync variant of that work?

HB: There are, obviously, some applications that make sense online, such as the ATP (Available To Promise) application that we were mentioning. But there's a need out there today, for an application, let's call it van sales. Van sales is, when we've got customers that drive around in their vans selling stock off the truck.

What we've built is an application that works in an offline mode and then can synchronize back. What it's doing is tracking the inventory on the truck that he can sell. So, as a driver is selling so much inventory off his truck, he's going and it's updating the application on the device, so he always knows that there are forty widgets left. But, it's also taking that next step and updating SAP, either through the cradle or wirelessly, saying that he's sold a total of two hundred widgets already and confirming that he still has that forty left on the truck. [You can see a sample order processing application in Figure B. - DG]

FIGURE B

You can instantly request the status of an order.

DG: And, that happens each time that the HotSync happens?

HB: It can happen each time the HotSync happens or it can be a wireless synchronization.

DG: We've heard the term "roles" a number of times when it comes to SAP services. What does that mean and how does that relate to the mobile product?

HB: The roles are really how we differentiate the different types of users we have using our products, and they're driven out of our enterprise portal. We've talked about the delivery drivers. That delivery driver is a role. Same as your typical service manager or service technician. Those would also be roles. And, those roles are really what we're mobile-enabling.

So, if I've got a service technician out on the road and he's repairing elevators, as he goes out to the different sites to do the repairs, he can clock-in and clock-out from his device. He can monitor what equipment needed to be repaired, the last service calls of the people that were out there, what had been done, requests for materials, requests for a follow-up visit, etc. All are applications that are under that service technician role, on the mobile device, via the Mobile Workplace.