Skip to Content

Dear community members,

I guess almost every Internet user already has ordered products from a web-shop or has done a registration for such an application. So this topic is familiar for almost everybody but some aspects are really difficult and important if you run a Web Shop.

/wp-content/uploads/2012/04/logon_95235.jpg

Illustration 1: Logonview for the Web Shop Application

On the one hand side the shop operator is interested that every user does a registration. This is important for the customer retention. On the other hand site (even more important) he wants to avoid every obstacle the user hinders to buy.

This makes the whole decision about the registration to one of the most important decisions for the web-shop.

In many business applications the user is forced to register and to login. In most of the cases he even has no choice to use the application or not. For a B2C web-shop this is totally different. Here the user has a lot of freedom … also the freedom to leave the shop after 2 seconds.

Therefore it is important to let the user decide if and when he wants to register himself; if and when he wants to login.

For the shop operator it is important to decide which logon-type is the best for his customers.

Logon-Types

With Web Channel Experience Management different logon-types are possible

  • eMail
    For a B2C-Shop the logon-type “eMail” is the usual one. This means the logon is done with the entry of the eMail-address and a password. The advantage is that the user doesn’t need to think about a good user-name.
  • User-Alias
    The logon-type “User-Alias” is also supported. This means the user has to use his name or an alias for the logon.
  • Technical ID
    A third option is the logon with technical ID. This is a BADI-implementation the customer can set-up within the project. Technical ID could be a phone-number, a license plate or any kind of number which is unique and sufficient to identify the user.

/wp-content/uploads/2012/04/config_user_95236.jpg
Illustration 2: Configurationoption in Web Channel Builder (User Module)

Since Web Channel Experience Management Release 2.0 the “Contact Scenario” is also supported. This means the logon as B2B user is possible. Here the logon is pretty much the same as it is in the B2C scenario. Only in the case the user is assigned to multiple companies he has to select the right Sold-To Party directly after the logon.

However the direct registration in B2B is not yet possible. The shop operator has to do the registration and as to inform the customer about the login.

Registration Settings

For a B2C-Shop different options for the registration are possible. The shop operator has to decide which options he wants to enable for his shop.

  1. Single page registration versus registration via guided flow
    Single page registration means that the user has to enter all required data in one page. For the guided flow the registration is done in several steps and the user can navigate back and forth.
  2. Immediate User Activation
    Immediate activation means that the user is logged in directly after he has done the registration. There will be no eMail send out which includes an activation-key. Immediate User Activation or activation with activation with activation-key is again a trade-off decision between usability and security. The activation key can help to ensure the correctness of the eMail-Address the user has entered.

Late Logon and Guest User Scenario

In a B2C Scenario it is critical to show a logon directly. Many decisions are rather impulse buying decisions and the logon can have a negative impact on this buying decision.

In principle the user can use the Web-Shop without to logon. In this case not all areas are visible for the user but he can use the product catalog and even add articles to his shopping cart (this works only for the JAVA Basket). The user can now do the logon very late in the checkout-process. It is also possible to do the registration very late in the checkout-process. One prerequisite is the immediate user activation as setting for the Web Shop-Configuration. Otherwise there would be a process-break and this would be annoying for the user and he could lose the products he already has added to the shopping cart.

With release 2.0 it is also possible to do the checkout directly without a logon and registration. We call this “Guest User Scenario”. You could also call this “Onetime Customer Scenario” or “Express Checkout”.

The advantage for the user is that he doesn’t need to register and think about a password and user name. The disadvantage is that he cant change the order afterwards easily and he can’t benefit from the advantages the shop offers for recurring users (discounts, special offers).

Further Information

Related to Web Channel Experience Management in general

Related to User Management

To report this post you need to login first.

11 Comments

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

  1. C. Eikeland

    Hi,

    More a question than a comment but… we are using wcem 1.0 and I wonder why the web shop users are created for role consumer. For the ERP integration even though the business partner has an other account group and number range (which is available in ERP) it tries to create a consumer in ERP. In middleware I get the error message saying I have to check the number range for the an account group 0170 which is for consumer.

    regards Camilla

    (0) 
    1. Arno Meyer Post author

      Hi Camilla,

      the Account Group is like a control Parameter/classification for the customer master. It mainly controls the visibility of fields and the number range. So in general the B2C bus. It is not a must that the  Business Partner  is a consumer. This could also be a regular sold-to party. I’m not aware of any restrictions regarding the accounting group. This has to be checked in detail.

      Best regards,

      Arno

      (0) 
      1. R V

        Hi Arno,

        Good evening! Can you clarify this for me? We are using WCEM2.0 with ERP as back end.

        In the above scenario for B2B you have mentioned that..

        “Since Web Channel Experience Management Release 2.0 the “Contact Scenario” is also supported. This means the logon as B2B user is possible. Here the logon is pretty much the same as it is in the B2C scenario. Only in the case the user is assigned to multiple companies he has to select the right Sold-To Party directly after the logon”

        But this is not the case as I see. We are testing WCEM2.0 in our development box (Contact Scenario with multiple Companies) and we have one (same) contact person (KNVK) assigned to multiple Sold To’s as a partner function in KNVP, and the email address is used to login. Have maintained the SU01 ID and have maintained the Contact ID for Object BUS1006001 under reference. With all this setup, we still do not see the system showing a screen or an option to select a Sold To. It is defaulting to one Sold To.

        We also tried another option (2) to see if this would work – creating unique contacts (with same email id for all contacts) for each of the Sold To’s and assigned all these contacts in SU01 reference object BUS1006001. Even with this setup we have not seen an option to select a Sold To in Web Channel.

        SAP documentation (release notes for 2.0 and logging on with contact scenario) for WCEM 2.0 also states the user will be allowed to select the Sold To. But this is not happening.

        Can you help clarify this issue?

        Thanks

        RV

        (0) 
  2. Arno Meyer Post author

    Hi RV,

    I guess my statement is missleading and technically not 100% correct. It is not the user assigned to multiple sold-to parties – it is the assignment of the Contact Person (Business Partner of type Person) who can get assigned to multiple Sold-To Parties via a Contact Person Relationship.

    This kind of scenario is only possible in CRM as in ERP Contact Person Relationships are not supported.

    Best regards,

    Arno

    (0) 
    1. R V

      Arno,

      Thanks for clarifying. For the benefit of the WCEM folks, can I request to bring this (Mutiple Sold to selection is only possible with SAP CRM and not with ERP backend) to the concerned team with in SAP WCEM to update the help documentation and in other related documents as well.

      Thanks

      RV

      (0) 
      1. Arno Meyer Post author

        Hello RV,

        yes I will inform my colleagues to update the documentation regarding the handling of multiple Sold-Tos.

        Thank you for addressing this issue. There are always some things we can improve.

        Best regards,

        Arno

        (0) 
        1. R V

          No problem! Any idea if handling mutiple Sold-Tos in ERP backend is included as standard in future versions of WCEM?

          Thanks

          RV

          (0) 
          1. Arno Meyer Post author

            Hi RV,

            it’s not intended for WCEM. Here WCEM leverages the capabilities of the backend.

            In ERP the handling of Contact Persons is different – not via relationships.

            Best regards,

            Arno

            (0) 
  3. Robert Baethe

    Hi Arno,

    Technical ID

    A third option is the logon with technical ID. This is a BADI-implementation the customer can set-up within the project. Technical ID could be a phone-number, a license plate or any kind of number which is unique and sufficient to identify the user.

    Regarding the BADI implementation, which BADI can be implemented. I did not find it in the security guide in the section so far?

    Thanks,

    Robert

    (0) 

Leave a Reply