Skip to Content
0
Former Member
Mar 04, 2009 at 07:00 PM

Transaction iViews Best Practices

30 Views

Hi All,

We are in the process of planning our portal content development. Basically all of our iViews will be transaction iViews that will retrieve content from our backend sap ecc system. As you may already know in ecc, you can perform multiple tasks within the same transaction code. For example transaction code FM5U allows to perform 2 tasks: Change Funds & Delete Funds; and users depending on their authorizations in ecc can either perform one task or another or both. As a result, we are thinking of having 2 separate iViews on the portal side that point to the same transaction code (e.g. FM5U). One iView will be called "Change Funds" and the other iView will be called "Delete Funds". Both those iViews will be pointing to FM5U. Users who can only change funds will see one iView link in portal that says "Change Funds"; and users who have the authorization to perform both tasks will see 2 iView links "Change Funds" & "Delete Funds" that basically point to the exact same thing. Is there a recommended approach by SAP on how to handle cases like this? In other words, is it recommended to have multiple iViews that point to the same transaction code?

Thank you,

-Ghizlane Idrissi