Skip to Content

Fiori Travel options for on-premise Gateway on NW7.4


I'm a little lost when it comes to Travel in Fiori possibilities... SAP has versions 1.6 and 1.7 available. Then we have My Inbox 2.0 which could be used for Tr Request and Expense claim approvals - but only for Travel 1.7.

What are the options if the customer has on-premise NW 7.4 based Front-end server? Backend is ERP6 with Ehp7. Is it best to go with the "older" 1.6 Travel apps with separate approval apps for request and claims in this case? Or could we just as easily go with the 1.7 apps and My Inbox 2.0?


br, Ossi M

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Dec 15, 2016 at 03:11 PM


    SAP Note 2374476 - FIORI Travel Applications 1.7 Roadmap summarizes several information on Version 1.7. of FIORI Travel Apps.



    Add comment
    10|10000 characters needed characters exceeded

    • Thanks Monika,

      I have that note and that's partly the reason why I'm confused :) The note doesn't say anything about Front-end server so I'm wondering is it possible to go for the newer 1.7 path in our case. Probably some component upgrades are needed in the Gateway but does it require upgrading the underlying NW version to 7.5x or could we get away with 7.4?

      Also the backend component requirement seems so high that an SPS upgrade would be needed, which makes the customer probably very hesitant to go this way.

      What about this kind of scenario:

      - use the older 1.6 MTE and MTR apps but do the approvals in My Inbox 1.0? Is this possible and viable option? The customer has a custom workflow so I'm wondering is My Inbox route more flexible than the dedicated Approve Travel expenses app.