First, it'll start from the WD application - interface view - then plug name. From Plug name, that is where the initial process takes place within the interface view. Specifically, it is found in the inbound plug. From The that plug, there is a handler method that calls the outbound plug. From the navigation link (switch window editor view), you will see the navigation link in outbound plug only. That is where the next target view and target plug is defined.
Monday, May 08, 2017
Web Dynpro - Navigation Link
First, it'll start from the WD application - interface view - then plug name. From Plug name, that is where the initial process takes place within the interface view. Specifically, it is found in the inbound plug. From The that plug, there is a handler method that calls the outbound plug. From the navigation link (switch window editor view), you will see the navigation link in outbound plug only. That is where the next target view and target plug is defined.
Wednesday, March 01, 2017
SAP Transaction Code Authorization
Are you wondering if your transaction code is accessible by anybody or not? The answer is very simple. Just make sure that in PFCG the roles or at least one of its role of a certain user (can be accessed through SU01) has the Authorization class AAAB (Cross-Application Authorization Objects) and with Auth. Obj S_TCODE. That is, that S_TCODE should have the value of the transaction code in Auth. field TCD that you would like the user to have access to. This is the first check the system will do before any other authorization checks you have. From S_TABU_DIS to S_USER_GRP.
Thanks!
Subscribe to:
Posts (Atom)