I'm having really trouble understanding what is the correct landscape to use in a Sybase/SAP environment (I don't really care about other scenario, just SAP + SUP), and I don't believe I'm alone. SAP seems to change things in each support package since 2.0, even ESD seem to contain substantial changes.
Consider a mobile sales force automation application with offline capabilities. I have multiple questions:
I've been reading this whitepaper: http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0db38c6-0e86-2f10-7482-d80cf09ee7a0?QuickLink=index&overridelayout=true&55130200211809 and it has left me even more confused then I was before reading it...
I had SUP 1.5 training and by now I find it was completely useless as SAP changes everything upside down in every release (even minor ones). With so many components, and comparing to the simplicity of custom web services approach, I wonder how anyone can actually sell this to a customer.
SAP needs to streamline this fast.
Maybe I can help a little.
You are right, SAP/Sybase are changing the SUP product really fast, specially when you are used to the speed of innovation SAP applies to ECC/NetWeaver. I don't think this will stop very soon as the mobile market is just evolving very fast. Thats good and bad at the same time.
I think SAP is changing too fast for partners and for customers. Aquisitions like Syclo which aren't explained and cause client confusion. I have had clients say that they are postponing mobile investments until the "SAP landscape" becomes more stable.
The market is evolving, but SAP doesn't seem to have a clear roadmap. Clientes (and partners) need to understand which products to use, and SAP is messing things up.
And honestly, I can make a custom sales force automation solution, which connects directly to the ERP, with full deltas and little load on the central system. It's not rocket science, and it's so much simpler. Yes, you lose device provisioning and control, but the alternative is installing a completly absurd landscape with SUP + Gateway + ERP....
If you are talking about SAP CRM Sales mobile application. Followings are required.
+ CRM backend server + CRM Sales add-on
+ SAP NetWeaver Mobile 7.1 + Gateway 1.1 to NetWeaver Mobile add-on = people call it DOE
+ SUP 2.1.* + Sybase SAP Connector add-on
+ SAP CRM Sales 2.0 mobile application.
See more details in http://scn.sap.com/docs/DOC-26601
If you are talking about custom application, there are several ways to implement.
Please note that "Gateway 1.1 to NetWeaver Mobile add-on" and "SAP NetWeaver Gateway" are completely different software components.
Right, for every specific solution like CRM its not just SUP and maybe Gateway, you also have to check what the product needs in your SAP system. For CRM Sales mobile you need a SAP CRM system and for mobile apps that need HCM you also have to check what HCM functionality is needed. Depending on the requirement you'll have to upgrade your backend and/or active a business function.
As if SAP wasn't already complicated enough :-)
For Mobile Development Platform, "SUP" is the mobile platform from SAP.
Right now the "SAP Mobile Platform" is not restricted to SUP. Like people stated in the this thread, you have SUP, Gateway, SUP DOE (which is actually SAP MI), so it's a little bit more complicated than that.
Saying that SUP is the mobile plataform is marketing. The reality is not so simple.
I've read your replies and I also build a demo environment for testing. Now the data can be downloaded from CRM IDES. But I have a question that I find if I want to see other data which is not created by my account, I can't see. I created an OSS for this issue and they replied the data will combined by account.
According for this reason, if a department leader wants to see the data, such as contracts, he will not see because the contracts are not created by his account. The replier says that I should create a new distribution model for different purpose.
Do you face this issue??