SAP CRM Release Timeline

SAP CRM timeline

Click on the pic to see the full size version.

I actually could not find such a chart, so I decided to learn how to use OmniGraffle Pro once and for all, and to produce it myself. I am not completely happy with it, but after 4 hours it does start to look good. I will update it in the future.

Well, what is it? Just a timeline with the dates on which each SAP CRM release went into ramp-up, general availability, and when the maintenance end.

Please note through years the release strategy and maintenance strategy changed and got more detailed.

Below the actual source data, collected from SAP official product availability matrix, and for the old releases (previous to 4.0) from release notes and my faulty personal memory.
SAPCRM.timeline

Share and Enjoy:
  • Digg
  • LinkedIn
  • del.icio.us
  • Facebook

Murphy’s Law of documentation

docs

  1. The largest part of documents produced quickly prove to be useless.
  2. The documentation which really prove to be essential and fundamental is the hardest to get but turn out to be the shortest.
  3. The shorter the document is the better it is.
  4. If a kid can’t understand the phrasing neither the consultant will.
  5. Templates are misused 97% of times, at end they often add visual complexity providing little or no help.
  6. Often the general bottom line among consultant seems to be “cut and paste as much useless stuff you can in order to make the document big”, the assumption probably is the client will be impressed by huge documentation. No matter how often this prove to be false the bottom line doesn’t seem to change.
Share and Enjoy:
  • Digg
  • LinkedIn
  • del.icio.us
  • Facebook

SAP CRM 2007

The New SAP CRM 2007 is here…On a Year ending note here are some of the screenshots from the new UI of SAP CRM.

A new SAP CRM section is added to bpx.sap.com too.

Links:  Video Library, ( At the End of every demo the Voiceover says “Isn’t that Cool”. That ain’t cool :-) )

    CRM In BPX

Some of the immediate things to notice

  • New UI, easy on the eye and the user, Not sure about the Consultant
  • MS Word Integration, Forms in MS Word
  • Excel Like Features for tables
  • OLTP Reporting
  • Drag and Drop the Homepage

The Homepage

home1.jpg

Drag and Drop the screen elements

dragdrop.JPG

Skins

skin.JPG

The Account Screen

account.JPG

The Excel Features

excel.JPG

Chart Options

chart.JPG

linechart.JPG

Pipeline Analysis- Note the URL

analysis.JPG

Share and Enjoy:
  • Digg
  • LinkedIn
  • del.icio.us
  • Facebook

Giving a look at Territory Management

I have heard this title few times and always thought: “Mhhh… Either it will never do what I need… Or it will be full of bugs… Or it’s probably a hell configuring it”

Well, no. It works, and it’s also a nice feature. If you have to deal with a complex geography which need to be mapped in CRM, for instance structuring Business Partner and Sales Representative relationships, Territory Management may turn very useful.

So let’s start giving a look at it.

Territory.blog

Territory Management

SAP CRM Territory Management component is specifically designed to structure and organize markets by dividing it into territories through a territory hierarchy.
A country geographic structure can be mapped into Territory Hierarchy through existing Standard Attributes or Additional Attributes according to customer flavour (attributes maps Business Partner Master Data fields). Hence Business Partners will be automatically assigned to the appropriate Territory Level accordingly.
Customers are able to assign a Territory Level to a Position in the Organizational Structure in order to indirectly assign the Employee Responsible assigned to that Position.

Territory Hierarchy can be changed anytime according to customer needs and market development, splitting and merging (logically) Territory Levels; business partner assignment is dynamic and will follow without any need to adjust existing data, de facto decoupling the assignment between BP Employee/Position from geographical area (it’s indirect through Territory). Hence, Sales Representative replacement can be achieved in a quick and simple way.

Also remember that a skilful Organizational Assignment Plan allow easy management of SR vacation and temporary replacement. Let me repeat that, once you have built your Territory Hierarchy and assigned Organizational Structure Positions to each Territory Level as needed, the appropriate Sales Representative is dynamically determined according to his assignement to the Position based on assignment plan and corresponding validity dates. That’s beautiful.

Additional benefits are the availability of standard determination procedure and replication rule to Mobile Application, based on Territory; in addition if pricing is done on CRM you can use it in condition tables to define pricing.

Territory Hierarchy Design

Territories are created according to few customizing options. Levels need to be defined as n-tier stack, each one with it’s own Territory ID length, hierarchy can thus be created accordingly strictly to the defined n-levels. But not every hierarchy level has to be sub-structured to the maximum n-tier.
Territory.blog.hier
Attributes need to be maintained in customizing. Attributes such as Country/Region/ZIP/City are assigned to territory levels in order to appoint to each Territory Level those BPs whose addresses matches appropriately.
A Territory Level could have been assigned ZIP ranging from 1100 to 1200 for Country Botswana, BP with the matching address would be appointed accordingly.
You can assign BP numbers directly, and you can code BADIs to better trim selections.

Among the missing functionalities I would surely count the display of assigned territory level in the standard BP transaction. You just don’t see it there. But nowadays there are plenty of option to customize it in order to show that piece of information.

A custom field can be added to BP MD using Easy Enhancement WorkBench, code generated can be easily changed to query the appropriate function module: CRM_TERRMAN_GET_TERR_BY_BUPA, in order to retrieve the assigned Territory Level to show, the sames goes for the assigned Sales Representative.

Conclusion

As I said it’s a nice feature, it’s quite easy to configure and does offer some customization. I suggest taking it into consideration and adopt it whenever it’s possible.

Share and Enjoy:
  • Digg
  • LinkedIn
  • del.icio.us
  • Facebook

E Commerce in banners- Tailgate

How many times have we been annoyed by the Banner Ads which take up screen real estate and some of the ones whose close button does not get enabled for a few seconds intially. A new system is set to add more value to the banner.

Techcrunch reports a Banner Ad system called Tailgate.

Tail gate

The USP of tailgate is that One can manage his shopping basket inside the banner and place the order also inside the banner and need not go to any other page to complete the transaction.

It claims that it can be integrated in the existing SAP platforms also. Seems a little tricky to me as this involves two way integration from the Banner to the backend. The products need to be fetched from the Back End and the orders need to be sent to the back end.

Corporate Fulfilment Database

Tailgate interfaces with your existing databases, for example CRM, fulfilment and/or logistics, seamlessly. This enables you to extend your eCommerce activities without additional investment in technology.

The technical design of Tailgate maximises integration capabilities with products from all the major database vendors, for example SAP, Oracle, Salesforce.com, Comtec, Pegasus and IBM.

Guarantee

Fhlame will guarantee that TailgateTM is compatible with your Corporate Fulfilment or eCommerce database or no fee will be charged.

The site does not talk about how this integration is brought about but this would open up an immense array of opportunities for Online Commerce. Integrating the AJAXy world with our header and items of SAP…..!

Future Possibilities include

1) Realtime Inventory Check 2) Customer behaviour analysis 3) Dynamic Product Proposals

Makes me think how we can use this for a service scenario…….

Share and Enjoy:
  • Digg
  • LinkedIn
  • del.icio.us
  • Facebook

The Internet face of SAP CRM and ASAP

SAP CRM has a few internet components which enhance the customer Interaction. Prominent among them is the Internet Sales. Though not a pure CRM Capability it opens up the Internal enterprise data for the customers. B2B and B2C are the 2 main scenarios with Sales and Service as the functionalities. It is about setting up a website which helps customers to log in and perform Order Entry, Request for Quotation, place an enquiry and self service. This involves some XML and java specialization.

ASAP(Accelerated SAP) is the De facto methodology that SAP Implementations follow. It has these 5 phases Project Preparation, Business Blueprint, Realization, Final Preparation and Go Live and Support. The highlight is that the Blueprint is frozen before the realization i.e the actual Configuration starts. This holds good for a standalone ERP or CRM implementation for the Internal Users. A customer facing Internet sales or service project runs on multiple tracks like SAP CRM Configuration along with the seamless Integration with THE R3, Java Development and Deployment, XCM Configuration and necessary ABAP Development. In this scenario the alpha, beta release methodology is more relevant than the ASAP Methodology.

The challenges here are three fold

Usability: Easy to Use for the End Users( The easier it is for the user the complex it is for the consultant)

No Disruption in the ERP Ecosystem( Balance the historical process ‘before’ and the new process ‘after’)

Balance of work and sharing of responsibility between Java and ABAP ( What in java and What in ABAP)

Considering these issues my strategy would be

1)Build up the website with a flow till the backend

2)Give a Demo to the business users and take feedback

3)Go back to the add the needed features to the website. Repeat Step 2 till the Final Demo

4)Release for test customers as a Beta Release, Iron out the edges and then a complete Release

The challenges become magnified in case of a B2C scenario which will be discussed in another post.

Update: Projectfailures.com talks about Demoing often to the customer in Don Dodge’s Interview. In fact this achieves two things 1. Customer buy-in 2. Team Motivation

Share and Enjoy:
  • Digg
  • LinkedIn
  • del.icio.us
  • Facebook

The Challenges of SAP CRM

 SAP CRM finds itself in a curious position in enterprise applications. On one hand it is the customer facing application catering to the salesforce,customers and on the other hand it needs to comply(Yes Comply) with THE R3. I am here as a fellow CRM chap to blog about how SAPCRM can overcome this challenge and bridge the gap(or is it the chasm). I would be discussing ways to reach out to the customer out there and help her solve her problems using SAP CRM. Though SAP CRM is a nightmare for us consultants I surely would not want the end users to feel the same…

 

Share and Enjoy:
  • Digg
  • LinkedIn
  • del.icio.us
  • Facebook

SAP CRM 5.0 SP07 vs 4.x

I had the rare pleasure to start working implementing SAP CRM with release 3.0 at the beginning of 2002 and through the following years gain experience on releases 3.1, 4.0 and now 5.0.

Said that, and considering what will follow in this post, I can say to the few of you who had similar nightmares that I completly share your view, releases 3.0 and 3.1 were a name and a hope, 4.0 was more credible, but the first pleasantly surprising release is the 5.0 SP07 (as far as I know SP07 was the first 5.0 release put in general availability).

The range of functions and processes supported, the available configuration options, the available customizing tools, the level of flexibility offered by the underlying technology; “all this stuff” reached such a quality level that I finally stopped feeling like Juda when selling solutions to customers (as a Consultant I am always selling something in a way).

What’s new on SAP CRM 5.0?

Well, there’s a lot of new stuff.

“SAP development investment in version 5.0 focused on Customer Driven Optimization of Best Practices End-to-End Processes and Joint Innovation Projects with industry leading companies.”
These are SAP words, which means that as usual they optimized Processes while working on real implementation cases, there’s nothing really bad with that.

“This unrivalled effort and commitment gave birth to a release which outnumbers anything seen so far in the CRM industry.”
This enthusiastic SAP quote sound funny, but for the first time I feel like agreeing, this SAP CRM release 5.0 is a nice one for real.

CRM is CRM not an SRM too, from release 5.0 SRM (Supplier Relationship Management) have become a separated product and it’s now shipped separately. SRM functionalities within CRM are no longer supported and are not documented within CRM.

Did you know that… ?

The total number of new functions or extended functions introduced by SAP CRM 5.0 as in SP07 total a number of 409, I am not sure if you like numbers or not, if you prefer a graph I hope you will enjoy the one which follow:

50diff
No surprise that Master Data, Business Transactions and Basic Functions have been heavily impacted, there have been always a certain constancy from SAP in its efforts to cover more and more Business Processes in every new release. (Of course we could be a little bit more cynic and say that all the money they spent in marketing, in conjunction with their great selling ability succedded in selling their product in early releases, when it was not necessarily so convenient for customers to buy it, getting great well payed opportunities to develop it.)

One thing we can assume from the graph above is that their effort to cover the gap SAP CRM always had in employing Internet in the solution is at least taken in to account, ICWC was surely a huge effort, and even if I am not fully satisfied by this solution (I had the “pleasure” to work on the much probably first ICWC implementation project to go live in Italy), the official statement that the “brand new” WebUI, which will be delivered in the next coming CRM release 5.2, is based on ICWC together with the unofficial one that it will address and solve the issues present in the actual release does satisfy me.
However my personal feeling (based on my experience with the underlying technology) is that they are seriously working on that, and also, to date, it’s already a valid product.

Well, there’s something else we can assume, they didn’t focus much on developing new funtions for Internet Sales and Internet Services, I think there’s a simple reason, ISA and ISE had never been well accepted by the market and in my opinion there’s a reason for that… But that’s just my opinion and it’s not based on a deep knowledge of these two solutions.

Now, for the ones who likes numbers:
50diff_counting

From a business process point of view, release 5.0 introduced broad coverage to the following processes:

• Warranty Claim Processing
• Rebate Processing
• Entitlement Management
• Complaints Management
• Service Plan Management
• Intellectual Property Management
• Shelf/ Planogram Management
• Credit Management

For the pleasure of the ones interested in customizing the system, we can add that although system configuration broadly cover requirements of most customers, to enable easy system customization are now available with release 5.0:

• Easy Enhancement Workbench (EEW ) for Business Transactions
• A larger number of business add-in (BADI );
(the total number reached 1618, release 4.0 had only 916 available BADI)

Now, I will stop wasting your time reading this, if you want to know more you can always hire me.
I will just confirm what I said at the beginning, I like SAP CRM as available with release 5.0 SP07, finally it’s a good product, and after so many years it have been on the market there are also, finally, a good number of implementation partners and consultants available.
Select it as your CRM solutions and you will have my blessing.

Share and Enjoy:
  • Digg
  • LinkedIn
  • del.icio.us
  • Facebook

I was reading this thread on sdn and this post inspired me

sdnI was reading this thread on sdn and this post inspired me…

I agree with most of what I read in Thomas post, but I think the following part explain pretty well what most of people still doesn’t understand about usability:

Companies want to spend their time and money investing in differeniating business functionality not necessarily UI.

This doesn’t mean that businesses don’t want good looking or nicely interactive UIs.

Nor do they necessarily want each application to interact or look differently – ie. training costs.

That’s sound ancient.

Design a coerent functional and reusable user interface is not fancy. People interact with software through UI, a poorly usable UI mean poorly usable software, and a poorly usable software has less value.

Business does understand that now, perfectly. Every SAP client now have experienced, in his work or leisure, different, more innovative, and more efficient UI and they do require SAP UI to conform to his average experience; and from SAP moves I can assume SAP knows that.

For instance, I recently went through a full SAP ICWC implementation and I can assure it was painful to keep explaining to the client it have to deal with the fact the user experience and the usability of the application was not the one of the average web application they experience every day; and they didn’t want something nice and cute, they just wanted their IC agent to be more productive.

Most of people laughed when the mouse was introduced, now most of people laugh at them.
Few companies I know are still using old cobol software with a UI 20 years old, they achieve a high productivity with it, and I suggest them to stuck with it. But these are exceptions nowadays.

The rule now is better usability = more productivity, and as far as I can notice business knows that.

Share and Enjoy:
  • Digg
  • LinkedIn
  • del.icio.us
  • Facebook

A better future

Shai AgassiReading this article about Shai Agassi talk on Oracle Fusion I had few laughs. It’s interesting either for the view about the business Agassi show (pretty pragmatic and old way in my opinion, which is not necesseraly bad), and for the answers given by Jesper Andersen from Oracle side.
I can’t referein myself from noticing if a member of the board of SAP is aware about the time (5 years to develop, 3 to stabilize) required to get a new software working properly enough to sell it to clients, well they should try harder to remember it when putting on the market some of their products.

Let me add I do agree completly with Dan Farber:
“For customers, the situation is going to be a better negotiating position than in past years.”
Also for consultants the future shouldn’t be bad. I assume there will be a lot of work to do…

Share and Enjoy:
  • Digg
  • LinkedIn
  • del.icio.us
  • Facebook