Skip to Content

I am just wrapping up our recent rollout of “Sybase Mobile Sales for SAP CRM”. Our sales team has been requesting a mobile application for a while that they could use to access SAP CRM from their beloved iPhones. We soon established that version 1.0 of this SAP / Sybase co-innovation product already provides all the basic CRM functionality that our account managers use on a daily basis, including viewing and updating accounts, contacts, leads, opportunities and activities. Obviously we’ve customized our CRM system to our needs so a few additional opportunity fields were required. When I scoped the work our commercial director made it quite clear that without these additional fields the application wouldn’t be of much use. “Just add the extra fields to the existing screens”, he said…


I was sceptical whether it would be that easy considering that the data needs to be passed through SAP NW Mobile and the Sybase Unwired platform before it can be rendered on the mobile device. To my relief an enhancement concept is already designed into the solution that allowed us to do this without much hassle. This blog explains the basic concepts behind the custom enhancement tables to show what they can be used for.


Each data object modelled on the data orchestration engine (DOE) has a corresponding “CE” data object that can be used to pass extra custom fields back and forth between the CRM backend and the mobile device. The screenshot below shows the opportunity header CDS table (IT_OPPT_HEADER) and its corresponding enhancement table (CE_ET_OPPT_HEADER) in the DOE Workbench.




The enhancement table contains one key / value pair per opportunity for each custom field that you want to add.


To illustrate this, below is what the CE_ET_OPPT_HEADER table contains for the custom field “Project Start” for opportunity “2958”.









Project Start






Therefore the only thing we had to do was to fill the CE tables with values from CRM and update SAP CRM with any changed records that come back from the mobile device.


This can be achieved via a set of standard BAdIs, e.g. for opportunities the implementation of BAdI method CRM_BADI_OPPT_MOBILE_GETDETAIL contains the read code, while CRM_BADI_OPPT_MOBILE_CHANGE has the update code.



The iPhone application, like the other mobile clients, automatically picks up the additional fields and adds them to the opportunity screen as shown below.




Caution needs to be taken with this approach in a multi-language environment and when many custom fields are required. For us however this did the trick and allowed us to “Just add the additional fields to the existing screens”…

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply