Jurjen Heeck wrote:
I am afraid this concept is moving too far away from the SAP standards.
I've actually known SAP to recommend this design strategy. On a previous project we had 2 SAP authorization experts fly in for two days to assist with the start of the authorization design and their recommendation was to use the split concept as described in this thread.
In the end we still set it up task based (as the other SAP systems in the landscape already had a task-based conecept) but I've always wondered how it would have been if we had given it a go.
On a side note, I doubt it's really as horrible as it is being depicted in this thread. Keep in mind the project was for an HCM implementation where there's already hardly any connection between tcodes and authorization values so it may have made more sense in that context than it would in a classic SD/MM.