Skip to Content

Since Thursday, SAP NetWeaver 7.5 has been available. This includes (among a few other features 😉 ) a new PFCG type, which lets you easily add Fiori apps to a normal PFCG role.

If you ‘re not ready to upgrade to NW 7.5, you will find the same feature in SAP NetWeaver UI Add-Ons, version 2, SP0.

If you have NWBC 5.0, PL7 or later, you can now integrate Fiori apps in a standard PFCG role.

You actually have 2 options – one for the “standalone apps”, and one for all the apps in the Fiori catalog.

NOTE: You can do all this in NWBC 5.0; you don’t need Business Client 6.0. If you want to know more about SAP Business Client 6.0, see SAP Business Client 6.0: Released!

How this fits into our overall UX Strategy

I have posted a slide deck, which I hope will explain the overall strategy: SAP Business Client and SAP Fiori Integration .

Standalone apps

This option is available for 10 apps with the biggest reach. They are all ESS/MSS scenarios and they are all self-contained – they don’t require the end user to navigate app-to-app.

This is the simplest option: You need to configure the Fiori launchpad in the standard way, you need the relevant Gateway service activated, the relevant authorizations, and so on, BUT you don’t need FLPDesigner – ie you don’t need to define catalogs, tiles, or target mapping, or assign catalogs and groups in PFCG.

For a list of the 10 apps, see: SAP Note 2103156 . For more information on how to configure these apps, see the documentation: SAP Help: Running a Fiori Application Standalone . For information on the Gateway service you need, see SAP Fiori Reference Apps Library .

All apps

OK, this option is still relatively simple, but you do need to need to configure the relevant catalogs, tiles, target mapping etc in the Fiori Launchpad Designer, and then assign these in PFCG.

The benefit is, firstly, you have access to all the Fiori apps you have installed. Secondly – crucially – you can configure genuine intent-based navigation for these apps. This is a really powerful Fiori concept: Instead of getting a developer-based view of a transaction with all functions visible to everyone, and having to pick your way through different tabs to fill the fields you want, the admin can now set up different intents for different users – ie different end users can perform different actions on the same semantic object. (I still love to Graham Robinson’s description of this: What is SAP Fiori? Maybe it’s more than you think ).

What you need to do

  • Before you start: Make sure the app is working in a browser (just saying).
  • Also, you need to be familiar with creating new PFCG entries in general. (If not, it’s all here: Role Maintenance: Navigation Tree . )
  • Even if you are inserting a Fiori app/ launchpad from the same system, you need to create RFC destinations in SM59 mapping the local system (ie where the PFCG role is stored) to the ABAP Frontend Server (ie where the Fiori apps and Launchpad are stored), since the Fiori Launchpad start-up URL must be defined here. The ABAP connection must be specified in the “Target System” field.

The ABAP connection GM6CLNT001 contains information used for establishing SAP GUI connections (message server, port) as well as logon options (e.g. client); the HTTP connection contains server and port information as well as the relative Fiori Launchpad start-up URL

  • you must create RFC destinations in transaction SM59, specifying server addresses, ports, logon information, and in particular, the SAP Fiori launchpad start-up URL (for more information about this, see the NWBC space on SCN Configuring Remote Systems in SM59Information published on SAP site).

Then in PFCG:

  1. Either open an existing role or create a new one.
    (Note: For test purposes, I have tended to lump all my Fiori apps in one role. In general, for a real end user though, that’s obviously not good practice.)
  2. In the Menu tab, create a new app of type SAP Fiori App.
    You get this dialog (I’m using the example MyLeaveRequests):
  3. Choose Intent (not Fiori Launchpad).

Now you have 2 options:


For a standalone app:

There is no real intent:

  • Semantic object always = Shell;
  • Action always = runStandaloneApp.

You then enter the name/value pair for the component and the location. To get the correct values, again see: SAP Note 2103156 . (The “location” is actually an ICF node):

FApps_saApp.png

For any app in the Fiori catalog

Intent = Semantic object + Action

To get the semantic object and action for the app, simply open the Fiori Apps Reference Library and choose Implementation Information:

FApps_catApp.png

4. Choose Enter.

That’s your entry created. You must, however, do one more thing:

5. Double-click the menu entry you have just created, and choose Other Node Details. Under Target System, enter the target system, where all your Fiori apps are located – ie your “Frontend Server. ” – ie the system you configured in SM59.

OK, that’s it! At runtime, the end user should see something like this:

ShowSAlesPipeline.png

ie when he logs on to the system, he gets the standard index page with all the usual SAP GUI transactions, FPM applications – plus the new application type, Fiori app.

To report this post you need to login first.

19 Comments

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

    1. Julie Plummer Post author

      Hi Arieh,

      By all means, if you want to integrate Fiori Launchpad in SAP BC, try BC 6.0.

      However, my point is that you can integrate Fiori apps in NWBC 5.0, PL7 or later, already, even if you don’t yet have BC 6.0.

      Which of the 2 versions you need, depends on what you want to do.

      For more details of which version to use and when, see my blog:

      When to use NWBC

      Best wishes

      Julie Plummer.

      (Product Manager, SAP Business Client).

      (0) 
  1. Jason Scott

    We’ve just installed SAP_UI 7.50 sp1 on our 7.40 sp11 ABAP system.

    Following the instructions above I’m trying to put a Fiori app in a NWBC role menu. The app is the leave request manage app and its working fine from the Fiori Launchpad.

    I’m using the Intent-based navigation.

    When I launch the app from NWBC (version 5 pl9) I get a http 500 error which I’ll copy below…

    Looking at the dump in ST22 just says the same thing.

    Any ideas? Maybe this *really* only works properly with ABAP 7.50 and not just SAP_UI 750.

    I’ll probably test with NWBC 6 next as it seems to have better integration with Fiori launchpad. Ideally I’d just use FLP for everything but we don’t seem to be there yet….

    =========================================

    ERROR: The user does not have a role called “sap-nwbc-context=03DA333033D633D3333233348D8AF70B77728E77710D73F5F10F700D8A0F710D0E3130B2B0343036D53330303270330001E3A05023036343101300” assigned (review with transaction PFCG), nor does there exist a cockpit called “sap-nwbc-context=03DA333033D633D3333233348D8AF70B77728E77710D73F5F10F700D8A0F710D0E3130B2B0343036D53330303270330001E3A05023036343101300” or it might be inactive (see transaction SICF). Please review the startup URL to see if it correct. (termination: RABAX_STATE)

    (0) 
  2. Guillaume Bruyneel

    hello,

    maybe a stupid question: How do you that: In the Menu tab, create a new app of type SAP Fiori App.

    In my PFCG Menu tab I don’t have the SAP Fiori App type. I am on a NW 740 SPS13.

    could you detail that point ?

    Best regards.

    (0) 
    1. Julie Plummer Post author

      I am on a NW 740 SPS13.

      Hi Guillaume,

      I’m afraid that is your answer: You need EITHER SAP NetWeaver 7.5 OR SAP UI NW Add-Ons, V2.0, SP00.

      We had to make significant changes to the back end to enable this, which is why you need the new back end to guarantee that it works.

      Best wishes Julie.

      (0) 
      1. Guillaume Bruyneel

        I have installed the SAP UI 750 SP01 on top of SAP UI 740. But I still do not have the “SAP Fiori App”  but instead “FLP_APP_PROVIDER” which seems to be the one.

        is that correct ?

        Best regards

        (0) 
        1. Julie Plummer Post author

          Hi Guillaume,

          Just one simple point: Are you using a French language version? If so, it is just _possible_ that there is a translation issue. If there is, then you can get this fixed via OSS ticket. In ther meantime, we can check that your option “FLP_APP_PROVIDER” = “SAP Fiori App”. It should look like this:

          FioriApp1.png

          FioriApp2.png

          If so, then you are correct: It is the same thing.

          If not, could you please provide a screen shot?
          Best wishes,

          Julie.

          (0) 
        2. Rainer Betrich

          Hi, Guillaume,

          this is a translation issue. We addressed that in an oss message. That will be fixed in the next release (s) as it cannot be fixed with a correction note.

          Best regards,

          Rainer

          (0) 
  3. Jason Scott

    Hi Julie,

    Thanks for this blog.. I have a question about the SM59 RFC destinations you have mentioned above.

    You say “destinations” (plural) and speak of an ABAP destination and a HTTP destination where you enter the Fiori Launchpad URL.

    However when configuring the NWBC menu role in PFCG there is only once place to enter a Target destination…. It only allows an ABAP Destination in this field so where do I specify the HTTP destination?.

    Any ideas?

    (0) 
    1. Julie Plummer Post author

      Hi Jason,

      Sorry about the delay. In fact, you only have to specify the ABAP destination. The system then derives the HTTP info. However, tbh, I’m not sure how. I shall find out and get back to you. In the meantime, I just wanted to clarify that you only have to enter the ABAP destination info. I have corrected the text.

      Thanks and best wishes,

      Julie.

      Update: I don’t find the docu particularly clear: You are advised to use a particular naming convention, but it is not actually spelt out how the system maps from one connection type to another when you use this convention.

      However, here is a blog for your reference:

      http://scn.sap.com/community/netweaver-business-client/blog/2015/06/01/configuring-remote-systems-in-sm59

      And the docu:

      Remote Systems


      HTH Julie.

      (0) 
  4. Matt Harding

    Hi Julie,

    Just a quick question? Assuming we’re using a recent patch level of NWBC 5.0 or 6.0 in NWBC mode as opposed to SAPGUI or Fiori mode; is there any guide or help on what selecting Fiori Launchpad does in PFCG as opposed to Intent? 

    e.g. I added a Fiori Launchpad node in PFCG to my menu and included the Gateway/Fiori ABAP destination (with my https destination configured also) and expected to have a link which opened the Fiori Launchpad, but the item is completely hidden from navigation and hence I’m assuming this is for a different purpose???

    Cheers,

    Matt

    (0) 
    1. Matt Harding

      Hi Julie,

      After some clarification, I discovered it does work as you would expect it to, but the functionality is not available if you are still using the old (and not really supported anymore) link to NWBC in your configuration.

      e.g. /sap/bc/nwbc doesn’t work; while /sap/bc/ui2/nwbc does.

      Might be a good idea in your next support pack to do something similar to what the Fiori people did, and redirect from /sap/bc/nwbc to /sap/bc/ui2/nwbc so that people need to resolve the differences and be on a supported API for NWBC – just a thought…

      Thanks,

      Matt

      (0) 
      1. Julie Plummer Post author

        Hi Matt,

        We looked at the FLP services (ICF nodes) – the old service and the new service have the same handler. We could theoretically do this. However, this would cause other problems, since several backend configuration tables would no longer work (eg NWBC_CFG – theme, welcome message, branding image etc) – or other tables need to be used (SAP GUI tag table).

        Even if we were to implement this, we would have to manage the change. ie we can’t just mention it in a “What’s New” for an SP. This could lead to a large number of OSS tickets (and justifiable anger, I think).

        This is why we can’t just switch like the FLP team. We are, however, trying to “nudge” – ie always recommending “Server runtime for SAP NetWeaver user interface services” in docu and presentations , eg in Server Configuration .

        Best wishes,

        1. Julie.
        (0) 
    2. Julie Plummer Post author

      Hi Matt, hi everyone (just reproducing  the email here, in case it helps someone else in future):

      Hi Matt,

      If I understand you correctly, I can’t reproduce this.

      1. I created a role and added the FLP as you implied.
      2. I put it into a new folder. (Tbh,  this is not documented as such; I do it for test purposes, to make it easy to find the new folder, and hence the new entries).
      3. I also added 2 TXs – so that if the FLP entry didn’t work, I could still see that the folder and TXs were working.
      4. I added the target system (defined already in SM59).
      5. At runtime, I clicked on the link in the Index Page – it opened my Fiori Launchpad in a new tab.

      I see from your subsequent post what the issue was. I will pass this on to the Product Dev team.

      Thanks for letting me know,

      Julie.

      (0) 
  5. Andreas Seifried

    Hi Julie,

    it still does not work for me. What I did:

    – Created a PFCG Folder with a transaction (both just to see anything in the menu) and a mode of type FLP_APP_PROVIDER with a different Target System

    – Assigned the role to the user

    – I can see folder and both nodes in SAP Gui (good!)

    – I can see only the folder and the transaction in NWBC (via URL /sap/bc/ui2/nwbc). The FLP_APP_PROVIDER node is not visible (bad!).

    – If I start the FLP_APP_PROVIDER node from SAP Gui, the browser is started but with the wrong URL. The host of the system logged on via SAP Gui is used and not the host from the maintained target system (bad!)

    Any idea?

    Kind regards,

    Andreas

    (0) 
    1. Julie Plummer Post author

      Hi Andreas,

      I may not be able to help. However, it strikes me that you are testing 2 things at once:

      – a new node type (F. app)

      – a remote system connection

      So, if I were you, I would test:

      1. (If possible) the Fiori app node type in a PFCG menu locally, inside the system where the Fiori app resides (if you have authorization to do that);

      2. Test the remote system connection – can you successfully call another app (preferably HTTP-based – eg WDA) via the remote connection?

      Best wishes,

      Julie.

      (0) 

Leave a Reply