Skip to Content

Admin Personalization of your SAP Standard WDA application – How To?

So you want to adapt/change your SAP standard Web Dynpro ABAP (WDA) application but you’d like to avoid using code enhancements if possible. One way to achive this is Administrator Personalization and in this blog I’ll explain and give examples of this. There are other ways to achieve the same which are not covered by this blog. The other methods to achieve code free changes to WDA applications are called Component Customization and code free Enhancements which I might cover in a future blog.

The list of options is not exhaustive and the recommendations are my personal opinions and not necessarily based on SAP recommendations.

1. Admin Personalization (Application Customization)

If you want to perform small changes like hiding an input field, changing a label, rearranging a table column or field then this is the way to go. If you come from a Web Dynpro Java background the options at your hand using this technique are very similar to the old “ctrl+right click” technique.

To get started log on to your development system and simply locate the Web Dynpro application in SE80 or SE84. Now you might want to take a copy of the SAP standard application to perform the customization on so that you keep a clean SAP version. I would recommend taking a copy but up to you and your companies policies. If you chose to customize directly on the standard application your changes will not be lost during an upgrade and you can always go back and check which elements where changed and reset the changes (I will show that towards the bottom of this blog).

You now need to execute the application using “shift+F8” or “Web dynpro application->Test-> In browser – admin mode”.

You can also do the same from your development portal by executing the iview in preview mode (but I have not tested this out in the portal so can’t say if you get prompts for transports etc?).

Then locate the UI object you wish to change, right click it and chose “Settings for current configuration”. Below I’ve given a couple of examples and hints:

  • If you clicked on a table column you will be able to rearrange it and Add/Remove columns


  • If you click on an input field you can change text, make it invisble, add a tooltip and even mark it as mandatory using the state property
    • NOTE: If you mark a field as mandatory it simply gives you a * indicator on the field and you need to ensure that a check for mandatory attributes has or is also implemented for example using cl_wd_dynamic_tool=>check_mandatory_attr_on_view( view_controller = l_view_controller display_messages = abap_true ).


  • If you want to rearrange the input fields you have to click on the container element for example “Grouping of UI Elements” as shown below. You then press the Re-Sort link and you will be able to move them Up and Down.


When your done and click the “Save and Close” button in the bottom right hand corner you will be prompted to save your changes in a customization transport. As a result you only need to do this on your development system/client – nice!

I have sometimes experienced that this customization seems to be done on the application NOT the application configuration which means:

a) The admin personalization of the application will be available on all the application configurations associated with it

b) You can perform admin personalization even if the application doesn’t have a configuration

However, other times it is done on the application configuration as Vikrant Raj also points out in his comments to this blog. I believe there is a bug that gives this inconsistency but the intention from SAP is probably that it should be saved on the application configuration as I think that makes most sense. If anyone can shed any further light on this (eg. refer to a SAP note) please let me know.

If you want to check which parts of an application has been customized select the drop down option “Personalized Elements” and you will get a list of customized elements and be able to reset them to standard.


So this is one way to achieve the described changes. As mentioned in the introduction there aare also other ways to do the same not covered by this blog.

NOTE: In a lot of SAP standard applications it is also possible to achieve similar things in IMG customizing so ask your functional IMG expert first.

Here are some useful links:

End User and Administrator Personalization (SAP Library – Web Dynpro for ABAP)


Personalization and Customizing – Web Dynpro ABAP Configuration Framework – SAP Library

And even though this document is written for FPM it has a brilliant section regarding adaptation options that some of the way are also applicable for standard WDA applications:

Best Regards, Jan

You must be Logged on to comment or reply to a post.
  • Hi Jan,

    Thanks for blog and waiting for section 2.

    One query- Some of the std. SRM webdynpro components (ex: /SAPSRM/WDC_DO_SOCO_GAF_1) doesnt have webdynpro application. This is based on GAF FPM (FPM_GAF_COMPONENT). Then in this case, how to do the Admin Personalization?



    • Hi Vinoth,

      Even if your GAF component does not have an application included in the component it is still associated to an executable application (an application that consists of several components).

      If you go to Web Dynpro component FPM_GAF_COMPONENT and look under Web Dynpro Applications you can see all the executable applications associated with GAF and the one you need to execute in admin mode (shift+F8) should also be there.

      If you have problem figuring out the application name then try to right click in the application where you want the changes done and chose “More field help” – then you should see the application name eg.:

      General Information About the Application and Component

      By the way I hope to do part 2 within the next couple of weeks.

      Br Jan

  • Hey Jan,

    nice blog covering this topic. I personally think the technique itself is superflous, especially since EHP5 and the whole rework of the WDA Framework adapting to FPM applications making Component Configurations etc a lot mightier than before.. but still, the technique exists and you explained it very well (I even learned something new, didn’t know you can actually manipulate the matrix of the UI-Tree with the ‘resort’ function 😉 )

    I hope you will do more blogs/documents in the future!

    Cheers, Lukas

    • Hi Lukas,

      Thank you for the comment. I don’t advocate one method over the other and use different methods based on the scenario. The FPM document I link to in the bottom of my post has some good points regarding pros and cons of the different methods.

      For people that were used to ctrl+right click option for admin personalization of WDJ applications I guess this method is what comes closest and it is a very quick and easy (maybe dirty? 😀 ) way of achieving a result compared to eg. having to copy a standard component configuration into own version etc.

      Component configuration I agree is very powerfull and I plan (have planned for a long time now 😉 ) to do a follow up to this blog regarding customization and code free enhancement of this.

      Br Jan

      • Hey Thomas

        Excellent Bloog.

        Actually i am facing an issue related to this.

        I did some iview Personalisation (Preview of Iview) for one country SAPIN.

        But it is being reflected on all the country users, which we dont want.

        We Want it to be SAPIN country specic.

        Your help will be highly appreciated.



        • Thank you for your comments. For country specific purposes I think you have to look into creating a country specific application configuration. Else if you share the configuration it will be visible for everyone running it. Let me know if you succeed 🙂

          • Thanks Thomas,

            Thanks for quick reply, If you could provide me some links related to personal information field changes (Webdynpro ABAP).



  • Hi Jan,

    Excellent Blog with lots of clarity.Thanks for posting. Also I have one question regrading one of your statement

    Remember this customization is done on the application NOT the application configuration which means:

    a) The admin personalization of the application will be available on all the application configurations associated with it”

    When I tried these changes, they actually happen on currently associated Application Configuration not everywhere because they were not present in other screen which has a diffferent configuration for that application.

    You might want to check it.



    • Hi Vikrant,

      Thanks for your comments.

      I have updated the blog as I have experience both scenarios. It might be a bug that I have experienced that can be fixed with a SAP note but not sure.

      BR Jan