First of all, thanks to the SDN team for introducing the CRM BPX community website. Also, many thanks to our friend Gregor for his What‘s so easy with SAP CRM 2007 and what‘s (still) not so easy. In my last blog, I had discussed about the strategies behind the latest releases of SAP CRM (although there has been some minor strategic changes), it’s much talked about new web UI and how to go about enhancing a CRM component.
Like Gregor and others, to highlight the all new avatar of SAP CRM, let me contribute some of the other main differentiators of the new CRM UI framework and to address some of common questions of the new CRM web UI about which I keep getting mails from the community. I would like to keep blogging about the new web UI in a series of parts starting from this one and I hope I get motivated to live up to my promise from the feedback I get from you.
Uniqueness of CRM UI Framework:
SAP CRM 2006s 1, 2 and now CRM 2007 introduces one holistic UI framework for all its applications as basis for the UI Unification (UIU). CRM consultants working from release 4.0 onwards would all know the Interaction center (IC) framework which is largely meant for the IC agent. But we have a new framework in store now; UIU framework with its own layout profile.
Flexibility comes in with its support for different application variants like IC, on-demand and CRM unification (UIU; which I just discussed). Portability in multiple browsers and just one central UI configuration tool are next.
It is the same age old ABAP-based BSP pages except the use of its unique tag library (chtmlb, thtmlb) and basic html content which enhances the performance as compared to its predecessors.
The new concept of UI componentization for all CRM applications and the feature of AJAX – enabled load on request find specific mention for enhancing the scalability of the UI framework.
What you will not get in PCUI or the earlier versions of ICWC:
- You will not get a configuration tool so easy that even business users can configure views like add/remove/move fields or columns, rename labels, set fields as read-only or mandatory and define load options for views without any user training. I will divulge more of about this tool in the next parts.
- You will not get to use parameters like role config key, object type and subtype to save different configurations for the same view or screen.
- You will not get to define and copy business roles using role customizing in IMG.
- You will not get to implement the same configuration content for several views.
- You will get to define input helps for customer-specific fields easily as part of design layer customizing.
- You will not get to use of web 2.0, Flex and drag-and-drop features. This especially comes along with CRM 2007. A demo for this is already posted SAP CRM 2007: It’s so easy… #9.
What is the most unique or great aspect of the new web UI of SAP CRM?
How easy or difficult will business users find to configure CRM applications from CRM 2006s onwards?
What technology is the CRM 2007 Front End built on? It’s not PCUI nor WebDynpro; then what?
If we are to customize the screens delivered (like add / delete fields etc), what is the underlying code written in?
These are few of the frequently asked questions I get from prospective SAP CRM customers intending to adopt CRM 2006s or CRM 2007 and I hope I have shared a few goodies out of the CRM Christmas bag offered by SAP this year.