Hello Guys,

The other day I received some questions regarding what can be made mandatory and what cannot in the C4C system.
Based on this questions I thought that a blog post would be good to clarify things.

Important thing to remember when trying to make fields mandatory is that not all fields are can be made mandatory.

One example is:

When adding a Product to an Opportunity, on the QV (Quick View) you have the Product Category field, however, you will not be able to make it mandatory. This happens because on Quick Views, you are not creating any data, you are just adding existing data to another screen. Assuming that you know what you are adding, you do not need any mandatory fields on this part of the system.

Another thing is, only fields that you can “fill” are available to make mandatory. For example: on Customers Workcenter, inside an Account you have the Contact tab, there you have some Columns that filter the Contacts list and those cannot be made mandatory as well. However, you can make that specfic field mandatory on the Contact QC and it would achieve the same resutls.

So, in summary:

– Only fields that you can fill can be made mandatory;

– But even then, they might not in case they are in QV’s (Quick Views).

I hope you guys enjoy it.

Please provide your feedback! 😀

Thank you and best regards,

Felipe Fraga

Support Consultant

SAP Cloud Product Support

To report this post you need to login first.

5 Comments

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

  1. Alejandro Kinsbrunner

    Felipe,

    My understanding was the other way regarding Product Category as based on the Prod. Category, available Products will be filtered.

    Also, from a business point of view, imagine you are working on a Lead or Opportunity and Customer is desiring to buy “Last model of Android phones” but not sure which of all Androids phones he wants to buy. So, it would be good to be able to fill only the Product Category as customer still does not know which exact Product he wants….

    Hope this helps for future releases.

    Regards.

    Alejandro.

    (0) 
    1. Felipe Fraga Post author

      Hello Alejandro,

      Awesome input!

      In fact, you can fill Product Category before filling Products. The behavior I described was only related to make the field mandatory.

      Thank you and best regards,

      Felipe Fraga

      Support Consultant

      SAP Cloud Product Support

      (0) 
      1. Alejandro Kinsbrunner

        Ola Felipe 🙂

        The thing is that I believe it would be definitelly useful to be able to set Product Category as mandatory and leave Product without being entered.

        The business case would be the one I mentioned before, i.e. there is a customer that know he wants to but something (mobile phones released to the market during 2015) but still not sure which from all the products (iphone 6S, latest samsung, etc).

        Is this something on C4C’s roadmap?

        Thanks and regards.

        Alejandro.

        (0) 
        1. Felipe Fraga Post author

          Ola Alejandro,

          Ok, now I got it. I am not sure if this is on backlog.

          I will check with some colleagues and get back to you in case I find something out.

          Thanks and regards,

          Felipe

          (0) 
          1. Felipe Fraga Post author

            Ola Alejandro,

            I’ve talked to some colleagues from the UI Team and they clarified the behavior. Product Category on the case I was asked about was in a Quick View (for adding products in this case). This fields cannot be made mandatory at all, not only the Category. Once you are adding a product to an opportunity, you must know what you are looking for and this is the reason for not making such fields mandatory.

            I’ve also corrected the blog post with this new information.

            Thank you and best regards,

            Felipe Fraga

            Support Consultant

            SAP Cloud Product Support

            (0) 

Leave a Reply