Skip to main content
Question

IFS Cloud B2B issues - Visually separate B2B from MAIN

  • December 30, 2025
  • 0 replies
  • 25 views

Forum|alt.badge.img+3

Hello,

 

We are using B2B as a customer shop portal with some CRIM’s to approximate the functionality to a webshop/B2C. The functionality is limited and suboptimal given that our basic need is a B2C portal. However, the implementation project chose this option over a third party webshop. We have approx 20 000 B2B users.

 

Sidenote: I am starting to wonder if any other IFS customers in the world are using the B2B portal like we do. If someone has any references, experiences or know anything about this, please DM me. 

 

The matter at hand: Is there any way to separate B2B from MAIN visually, to help the end-user understand where he is? Currently the only distinction is the URL, which is not intuitive for end-users:

MAIN: https://ifs.prod.no/main/(...)

B2B: https://ifs.prod.no/b2b/(...)

The following is tested in our CFG environment:

  • Apperance designer
    • Bar logo: Add information text in a picture. Format is not optimal, and it looks unprofessional
    • Welcome text on start: not a viable option as we are using role-sepecific lobbies as start pages. They are assigned to user profiles via migration jobs when creating the user
    • Configurations in the appearance designer is independent on whether you are in B2B or main, so every config applies to everyone in the same company or the other available attributes

We are often experiencing users unintentionally trying to access B2B lobbies and pages through MAIN, and sometimes the other way around. Especially users who:

  1. Has one or more full user permission sets, and LTU permission set(s)
  2. Are sole LTU users that somehow has accessed the landing page, pressing “Open IFS Cloud”, sending them to MAIN where they dont have any permissions. They are able to open the B2B startlobby in MAIN (all lobbies are accessible through main as long as the lobby is granted to a permission set), but gets error message when trying to access for instance page “Products” from the lobby.

Sole LTU users are somehow able to access MAIN, even though they only have LTU permission sets granted. For B2B access, we are using IFS administrated LTU permission sets:

  • B2B_SALES_LTU
    • Grants FND_WEBENDUSER_B2B
      • Grants FND_CONTACT_WIDGET_USER_ENTERP (only projection GetPartyTypeWidgetInfo)
      • Grants FND_WEBENDUSER_B2B_FNDWF (only projection CamundaRestInterface
  • B2B_SERVICE_ORDER_MGNT_LTU
    • Grants FND_WEBRUNTIME
    • Grants FND_WEBENDUSER_B2B
      • Grants FND_CONTACT_WIDGET_USER_ENTERP (only projection GetPartyTypeWidgetInfo)
      • Grants FND_WEBENDUSER_B2B_FNDWF (only projection CamundaRestInterface

These are all permission sets that we can not edit (FND or LTU). When granting only these to a user, the user is able to access MAIN, probably because there are projections and pages that are shared between MAIN and B2B. This is unfortunate.

Been in production for 2 months. Current release is 24R1, upgrading to 25R1 this spring. 25R2 tentatively Q32026.

Anyone able to help us with this, or share any knowledge or experiences?

 

BR,

Henning