A few months ago I wrote the blog Activating FIORI-Apps in S/4 HANA – not so hard after all!.
Now I’m moving its content to a document, as I intend to share new findings I have and think
that updating an old blog over and over again is not the best thing to do.
I used to think that activating FIORI apps is a cumbersome task and I have to admit I had to give it a
few attempts before I got some success.
But then I got four of them running in a short time, so I really got “in the flow”. Now I think that it’s not
that hard, after all.
[Please note: I’m working on an sandbox system, that is not even accessible from the “outside world”
– if you’re in a productive environment you probably have to pay a lot more attention to security-
concerns.
(Like, thinking twice and checking back with others, before activation services in SICF; or fine-tuning
the authorizations)]
Our frontend (gateway server) has SAP Fiori for SAP S/4HANA 1511 installed:
For configuring those systems, I use a document called “SAP Fiori Technical Foundation
Configuration(EE0)” https://fioriapps-
rds.dispatcher.hana.ondemand.com/docu/EE0_NWG20_BB_ConfigGuide_EN_XX.pdf
Other prerequisites:
Have a equally named user in both the front- and the backend.
For testing, I give them quit a lot of authorization in fron- and backend (like SAP_ALL).
In the backend, let it have role SAP_SM_S_RFCACL .
(if not mentioned otherwise, things are done on the front end = gateway server).
5. Assign the role given in “PFCG role for Business Catalog” (SAP_BR_PURCHASER) to your user
and start testing:
8. Find the one you wanted (Manage Purchase Orders) and klick on it.
9. It’s quite possible that it will not work right away, but don’t let that stop you:
The F12-Key is your friend!
There are usually 2 main error sources you can identify by those messages:
a)
GET
http://[hotsname]/sap/bc/ui5_ui5/sap/mm_purdoc_lsts1/~29C6FEC22735BB70BBE819198D78D~5/Componen
t.js 403 (Forbidden)
-> go to the SICF-Node given in the URL (here: /sap/bc/ui5_ui5/sap/mm_purdoc_lsts1) and activate it.
b)
You probably have to repeat those steps (reload, Click, Look, activate something in b) a few times,
but in the end you should have your running app:
Bonus-steps:
You already see the other apps (provided by the PFCG-Role) so why not make the usable, too!?
-> you can use the same “klick, look, activate”-cycle for it.
Conclusion:
As always you have to invest some time and get acquainted with the problem domain. As you gain
experience, the solution hidden behind an error message will get more and more obvious to you.