Structural Authorisation Portal Vs Backend issues
Can you please help. We have structural authorizations in place and we also use ESS/MSS. Most of the portal applications require extensive authorizations ie access to info type 8. Currently we have an issue in as much as we want to give access to infotype 8 for the portal applications but we don't want the user to have access infotype in the backend.
So there is nothing in the standard that can handle this so I need to develop something but I am struggling with the logic. Can someone please help? My idea was to create a structure profile which has embedded function module, the function module retruns all the available portal applications. But I am struggling to link this with the PFCG authorizations ie to say give access to infotype * only for the application and not the user in the back end.
Your input will be greatly appreciated.