Wednesday, June 26, 2013

Adding extension fields to your mobile Cloud for Sales solution

Since we first published our series of blogs on the SAP CRM cloud solution we have seen a lot of changes where each new release offers new and improved functionality. For details about the current release 13.02 see this blog.

There has been some confusion about the actual name of the CRM cloud solution. From the start it was called SAP Sales OnDemand. When SAP introduced new functionality the name was changed to Customer OnDemand extended with SAP Service onDemand and SAP Social onDemand.

During last SAPPHIRE event in Orlando, a new naming convention was announced. The CRM cloud solution now includes Cloud for Sales, Cloud for Service, Cloud for Marketing, Cloud for Social Engagement and Social Media Analytics by Netbase. All in all a complete package called SAP Cloud for Customer.

In this blog we focus on the Cloud for Sales solution for mobile devices. The SAP Cloud solution provides add ins for iOS, Android and Blackberry smartphones or tablets. SAP does not charge you extra for the use of these apps, they just come with your solution and are included in the license fee.

Wednesday, June 19, 2013

Using Composite operations in SAP Mobile Platform to improve performance

SAP Mobile Platform is SAP’s mobile application development platform. With SMP you are able to build complex mobile applications quickly for multiple devices. SMP provides out of the box synchronisation capabilities and security features. 

With the release of SUP 2.2 PL3 there was a new feature called “Composite operation”. This nice new feature can be used to get better performance in your SUP MBO application. With this feature you are able to split a large MBO in multiple smaller MBO’s, but still use the larger (webservice) operations.

Wednesday, June 12, 2013

The other side of the Business Object Layer (BOL)

When working with a CRM 7.0 system, especially when enhancing it, you very soon get to know some aspects of the framework behind its WebClient. The following picture gives an overview of the different layers.




For instance, if you want to change a screen configuration you need tools that are offered by the Presentation Layer. This layer is responsible for presenting the CRM data to the user and handling user interactions. The necessary data is not directly read from tables but instead are offered in a object oriented way by the layer below, the Business Layer.


The Business Layer presents the CRM data and logic in a nice uniform way by encapsulating data in Business Objects. These objects have attributes and may have, and this is a very powerful aspect, relations with other objects. The actual data is accessed through what is called the Generic Interaction Layer, or GenIL. This, CRM specific, layer is formed by ABAP classes that access the data by calling Application Programming Interfaces and provide it to the Business Object Layer.


In this blog I want to zoom in on the Business Layer and show a little bit of how it can be accessed from ABAP code, how the GenIL is implemented for a Business Partner and then...


...switch to the other side of the Business Object Layer and, instead of being a consumer of Business Objects, show how to enhance existing objects with new additional fields and relations and how to create completely new Business Objects.



Wednesday, June 5, 2013

Most important reasons for choosing SAP Web Channel Experience Management

The new SAP WCEM (Web Channel Experience Management) offering has been on general release for over a year. The question that I often get from my customers is to help them with preparing the business case for their managers. As I developed these business cases, I've found some commonality or emerging patterns to consider for choosing the standard e-commerce solution (SAP WCEM) of SAP in stead of a third party e-commerce solution integrated with a SAP Backend (SAP ERP/SAP CRM).