LinkedIn Twitter
Co-Founder at Diginomica, independent analyst and SAP Mentor. Named best writer by the ERP Focus 2014 and 2016 writer awards

12 responses to “SAP Sales OnDemand – Addressing the Lingering Questions”

  1. Dennis Moore

    Jon –

    Excellent analysis. One thing though: I still don’t understand SAP’s “Edge” strategy, why ByD can’t be used for Edge applications, and how SAP plans to enable seamless integration for Edge applications with Core applications.

    Thanks!

  2. SAP Sales OnDemand – Addressing the Lingering Questions #SAP « BrenG

    […] SAP Sales OnDemand – Addressing the Lingering Questions […]

  3. Jon Reed

    Dennis – maybe we can get someone from SAP to respond to this thread as well, because I am still getting a handle on some of the fine tuning around the core and edge on demand distinctions. However, I’ll give it a shot for you.

    I suspect in the long run SAP may move beyond the “core and edge” language as these may not be the most accurate ways to describe the differences. A better way might be to think of the “edge” apps as the lightweight, “open” apps that can more easily leverage open standards. For example, the “core” ByD and Large Enterprise OnDemand platform runs on a new, pared down NetWeaver platform (ABAP) and the SDK for ByD is C#/Visual studio based.

    The “edge” apps lineup is still emerging but most if not all I have heard of are Java-based and lightweight in nature (Carbon OnDemand being about 16 screens for example). StreamWork might be a good example here as a Java-based app that is integrated with all kinds of open standards and other on-demand platforms (Google, OpenSocial, Evernote). I’m not speaking for SAP here, but I get the sense that SAP views the edge apps as a way to get more juice out of open source and Java-based development communities and collaborate with them in a way that the ByD SDK, targeted for C# and to a lesser extent ABAP peeps, wouldn’t do. For example, I’m working with a small group of SAP Mentors designing an “edge” app that has to do with making skills searchable (I can say more about the app once we make more strides on it and if it sees the light of day). The app is currently a combo of BI OnDemand, StreamWork, River, and soon Xcelsius. In this case the app doesn’t really need to touch on enterprise or ERP data at all, at least not in this incarnation, and that might be one other distinction for the “edge” apps – less heavily tied into ERP-based processes, security authorizations and other dependencies.

    Perhaps down the line if this Mentor app sees the light of day and becomes something companies might want to use (note: this is totally a hypothetical example), then it might make sense to look into options for ERP-integration (for example to extend into HR talent management) either in SAP or ByD or someday Career OnDemand. Then the “core” OnDemand SDK might come into play to beef it out as a more complex and ERP-connected component.

    One of the reasons “edge” may be still somewhat confusing is that two key pieces of this, River (lightweight on-demand development environment) and Gateway (for lighter ERP integration, including mobile) are still not publicly available to tinker with. River is closer as there is some access to the platform by request as in the project the Mentors are working on, and I know of other projects underway or out in the wild. (The River team by the way has been exceptional about letting folks learn more about the platform and tinker with it). Gateway as you know is only live in the context of Duet Enterprise.

    We should hear a lot more about Gateway at TechEd, particularly in terms of mobile integration, but Gateway can just as easily be applied to these lightweight on-demand scenarios. My best guess is that we’ll have an even clearer understanding of the “Core” OnDemand side of things at ASUG/SAPPHIRE (with more info on the SDK), and then in the fall at TechEds we should have a clearer sense of how the “edge” is solidifying in SAP’s architecture.

    However, SAP might say differently so perhaps they will chime in here.

    Hope you are slightly less confused now, though possibly I created more confusion as can happen when talking SAP. 🙂

    – Jon

  4. Jon Reed

    Err, Carbon Impact actually. 🙂 I don’t think the world needs a “Carbon OnDemand” app. Funny typo, sorry.

  5. Dennis Moore

    Jon –

    Great explanation, but stil murky as to why two entirely unconnected/unrelated platforms are needed, especially if one of them is for general purpose apps that have little or nothing to do with SAP back-end functionality/processes/data. It would seem that good services available to all platforms would be preferred over some platform from SAP that seems like it will always lack the kind of investment you’d see from Microsoft, the open source community, or even from Salesforce.com. Thanks for the clarifications …

    – Dennis

  6. Jon Reed

    Dennis, I think SAP will argue that the platforms I described are connected, or will be. I suspect we’ll have a clearer sense of this later this year, perhaps even at Sapphire….but that answer is the best I can do for now…:)

  7. Pete Scholtens

    Hi Jon — one small clarification: SAP StreamWork added the @mention protocol with the March 18th release.

    Thanks,
    Pete

  8. Judson Wickham

    Looking forward to implementing Sales OnDemand at Pinkberry, especially once it can be integrated with ByD.

  9. Jon Reed

    @Pete – thanks for the clarification. I haven’t noticed it in my StreamWork projects yet so I’ll have to try it – good add!

    – Jon

  10. SAP Sapphire Now 2011: Blazing on Process, Tepid on People | Pretzel Logic - Social and Collaborative Business

    […] this topic in this older post). That’s what Sales On Demand does and here’s Paul Greenberg and Jon Reed on the […]

  11. SAP Sapphire Now 2011: Blazing on Process, Tepid on People | Constellation Research

    […] this topic in this older post). That’s what Sales On Demand does and here’s Paul Greenberg and Jon Reed on the […]

  12. How RIAs are Impacting the SAP User Experience | ERP Executive

    […] Sales OnDemand is one such example. “It’s clear that someone spent a lot of time thinking about the user, the sales person sitting in front of the application and trying to do his job,” says Mrinal Wadhwa, a software developer who is also an SAP Mentor and an Adobe Community Champion. (Sales OnDemand is currently in ramp-up with General Availability expected to be announced soon). […]