Skip to Content

Note 2444103 Context Sensitive Filters in Cellerator

After about 1.5 year away from product support, I found there are a lot of new functions introduced in CRM Web UI area. Let me try to learn from others to write them down to help me learn in more organized and quicker way. This time let me touch a tiny topic which is related to Note 2444103 Context Sensitive Filters in Cellerator. I’d like to explain the function introduced by this note and also explain the screen shot attached to this note in detail.

Firstly, let’s explain what is the function introduced by this note. Reading by title “Context Sensitive Filters in Cellerator” it means we’d like to adjust the display of the filter based on the specific situation the cellerator is in. Then what is a Filter? Please check the follow example. In an advanced search, the search result, when we click on the column header, there will be a dropdown list. The entries after the first line will be all the possible values for the current column in the current search. The following screen shot is search result of Opportunity. This filter listed all the possible Prospect name in current search. If I click on any of the entries, the search result will show only entries for this Prospect.

Isn’t it too easy and no need to use a blog to explain it? Now here is the problem we are facing. If I’ve set a filter one column A already. Then if I’d like to click on the filter dropdown on column B, what entries should be there?

Take the previous example, let’s set filter on Status = In process. We can observe the Prospect values were restricted into only 3 possibilities. Then what should be displayed on the filter dropdown? Should it be only the 3 values or all?

Our developer is perfectionist, and very considerate. They wish to bring easier life for users. This gives birth to Note 2444103 Context Sensitive Filters in Cellerator. Let’s check the system behavior after this note, the result of the filter dropdown will be the following

With this change, if we would like to do further filter based on existing filters, we can simply select the entries before the line. If I found that the interested Prospect is below the line, this might give me important information that the previous filter might not fit.

Up till now, isn’t this function tiny but still cool? We never get satisfied that easily. How about if we select one value to filter on column B also, what will the filter dropdown look like?

If we click the column header of Prospect, it will show as following. The current selected value will be displayed in bold.

After the above testing, I finally managed to understand fully about the description and screen shot in Note 2444103 Context Sensitive Filters in Cellerator (excuse me for the slow process in my mind). Let’s melt the description into the screen shot, it will be like this.

When examining the screen shot for the first time, I got confused with the “(No Entry)” entry. Maybe you don’t have the trouble. “(No Entry)” means there is empty Prospect. We can treat “(No Entry)” as one of possible values for Prospect, nothing special.

The above function can work when use omnifilter. What is omnifilter? It is the following box which suddenly shows on top right corner of the cellerator after certain package, another cool function introduced by our developer. For detail, please check Note 2322719 – Omnifilter for the Table and Tree

This note introduced a tiny helper, but it might touch some complex scenarios. I suspect it might lead to some potential bugs. Take one recent customer incident for example, customer discovered when there is a picklist type field in search result, if I would like to click filter dropdown with omnifilter active, there will be REFERENCE_IS_INITIAL short dump. The fix for this issue is on the way.

Added in Jun 2018

The bug was fixed by note 2610946 Dump at column filter after using omni filter .


You must be Logged on to comment or reply to a post.
  • Things sometimes are too simple in my mind. (KISS - Keep it simple because I am Stupid)

    When I'm reading a note, I don't usually search after I have it. I try to implement it. And if it isn't written very well I look for other notes, or create a message. I would not google it or look for it in SAP community. (Maybe I should.)

    Could you let me know - why the note can't be fixed?

    Thank you,


    • Hi Michelle,

      Thanks a lot for reading. May I know if what issue you've met when implement note 2444103?

      Maybe my poor English lead to some confusion, the note 2444103 itself is introducing a new function as described in this blog. But as far as I know there is one known issue, REFERENCE_IS_INITIAL short dump, which only happens when there is a picklist type field in search result. And the correction is being prepared already in another note.

      What kind of issue do you want to fix?



      • Hi Hongyan,

        Your English is perfect. In fact it is better than mine when I am writing a thought down quickly. So from what I understand, this is a reference to 2444103. However, it's not regarding the same thing.

        • 244103 introduces the functionality
        • This blog is a followup on what to do when the functionality doesn't work as expected.

        And that is what we do here - follow up with our experience. My confusion is if the note causes the issue, then why not create another note and reference it in the support area.

        If this doesn't happen all the time, it makes sense to blog. But if it does happen all the time I would expect another note. Not a blog.

        By the way I am looking at blogs for future use. I'm still on an older version, but I have bookmarked a lot of them to use later.  These steps most likely work perfectly. And I did bookmark this. Just shaking my head that the note system caused the issue, and didn't step by step fix the issue. Since you are from SAP I figured you would be a good person to ask. 🙂 This is that type of thing that I would love to see in a note.

        Thank you for the quick response - and a really nice blog if I have issues later,



        • Hi Michelle,

          Thank you so much for explain for me.

          Good summary about the points I'd like to put for this blog, but please allow me to adjust it a bit like the following:

          • 2444103 introduces the functionality
          • This blog is to explain what this functionality exactly is. For fear the explanation in the note is still not enough to explain it clearly.
          • At the bottom of this blog, it also mentions one or more issues after introduce this functionality.

          And for the last point, I've met about three issues (to be frankly):

          1. REFERENCE_IS_INITIAL short dump, which only happens when there is a picklist type field in search result. <<< Customer reported this issue to SAP support, thus a new note is being prepared. Yes, you are right, if it is a problem, it will be fixed by a note. 🙂
          2. Two other issues, I met them during my play around in one of our internal systems. Both of them shows no operation stop like dump, but the display of the filter dropdown is not exactly the same as described in the note 2444103 and this blog. <<< I've reported this to my developers, and they are looking into it. If it is verified to be a bug, new notes will definitely be created.

          I am trying to use blogs more often in future to explain some of my findings or thoughts like this blog, which is not exactly a bug topic which should be in a note itself. To help myself organize the knowledge more efficiently. This blog is a first try. Thanks a lot for the encourage.