Skip to Content

E-recruitment – Candidate scenarios using Webdynpro ABAP (WDA)

We are all more than aware that Web Dynpro ABAP, also referred to as WDA or WD4A, is the latest SAP UI technology. As of SAP E-Recruiting 600 SP08, SAP has  provided the option to develop user interface for candidate scenarios using WDA. Candidate scenarios include activities like maintaining profile, applying for job, etc.There are advantages in using either BSP or WDA ( from a developer’s point of view) however from an E-recruiting perspective, there are certain processes like Hot Jobs, Recommendation of job posting and Job Agent, which are only possible in WDA. 

 WDA like BSP sounds technically daunting to functional consultants like me who have limited technical skills, therefore I thought this blog may be of help to those functional consultants who would like to use WDA for candidate scenarios without having to depend too much on technical development.

To begin with the picture below shows how the start page looks for a candidate using WDA.



                                                                            Picture 1 -Candidate Start Page 

One can customise the  tabs that define the First level and the entries that appear in the Second Level. You can also create your own Level 1 entries. Whether the overview screen is displayed as above is something you can control via configuration.


My approach was to read up anything I could lay my hands on in SDN, SAP help portal, etc, which would provide me with an understanding of WDA, however the best start I got was by going through a tutorial on the help portal.( tutorial does not require any prior knowledge of WDA and helps put the different elements of a Web Dynpro Component into perspective. I strongly recommend you go through this tutorial if you are new to WDA.

The key elements of a WDA component are a Controller, Window, View and an associated WDA application. Most elements of a component get created automatically when you create a component. The WDA application associated with a component needs to be created manually though. You can then create the related WDA application from the context for the component (Right click on the component and click on create – > Web Dynpro Application).

The standard package delivered by SAP for E-recruitment related WDA components is PAOC_RCF_UI_SELF_SERVICES. You can access the package from the Object navigator via transaction SE80. Once you select the package you can see the standard Web Dynpro components and applications in a tree structure.

Configuration of WDA Components:

As opposed to the configuration carried out in IMG, one can carry out configuration of WDA components and applications from the transaction SE80. This ability provides a lot of flexibility in tailoring the candidate screens based on user requirements. It also does away the need for development work.

The standard package – PAOC_RCF_UI_SELF_SERVICES – delivers various WDA components that are used to define the candidate start page. These include personal details, Education, Work Experience, etc. As an example we can look at the WDA component HRRCF_C_PERSONL_DATA_UI which is used to capture personal information like name, address and communication details of a candidate. This screen appears when candidates maintain their profile in ‘Candidate Profile’ or while applying for a job posting in the application wizard. (See figure 2 below)



                                                                                           Picture 2 – Roadmap


You can see the layout of the screen by selecting the view VW_PERSONALDATA contained in this component. All the fields and texts contained in this screen are placed in a hierarchy under the ROOTUIELEMENTCONTAINER.  In order to alter the screen, you can create a configuration for the WDA component.

Select the component and right click on it. Select Create/Change configuration which will open up a browser window. The component name will be auto populated in the window. Give a name for the configuration ID e.g. ZHRRCF_……( advisable to follow a uniform naming convention) and  click on ‘Create’. Give a meaningful description and save against a custom package or as a local object.

Tip: You can rename the configuration or change the object assignment later if required.

Once you have created a configuration id, you will need to refresh the screen and the configuration will appear under a new node called ‘Component Configurations’ below the component. Click on the ‘Start Configurator’ button in the Tool area of the object navigator, in order to start the configuration. You can now carry out the configuration as per your requirements. Likewise you can create different configurations for all components where the standard does not meet your requirement.

Tip: Do not change the text for any fields or labels here. Go to Object Text repository (transaction SOTR_EDIT) in order to do that.

Typical things you can do in configuration are hiding certain fields or making them mandatory. If you want you can change the text but make sure to change the mapping for the field in the view. In case you want to add new fields make sure you do it in an enhancement.

Configuration of WDA Application:

You can create a configuration ID for a WDA application in the same manner as you create a configuration ID for a WDA component (Right click and select change/create configuration). I have used an example to illustrate the steps involved in application configuration.



                                                                                           Picture 3


Z_APPWIZ_EXT_VN is a configuration ID for the Web Dynpro Application HRRCF_A_REG_APPLWIZARD_EXT.Once you have created a configuration ID, click on ‘Start Configurator’ in the Tool Area in order to carry out the configuration. 

The Web Dynpro application shown in the above example  HRRCF_A_REG_APPLWIZARD_EXT is used to control the application wizard for external candidates. The application wizard takes a candidate through different steps like Personal Details, Education, Work Experience, Qualification, etc before they can submit their application for a job. Each of these steps has a related web Dynpro component in the background.  

The configuration opens in a new browser window and you can assign the appropriate configuration for the various components over here. The saved configurations are usually available in the F4 help. The picture below shows how the standard screens in the application wizard have been replaced by configurations for different components like cover letter, Education, Personal Data, etc.



                                                                                       Picture 4


Once you have saved the configuration you have created a custom application wizard. In order to test the configuration, right click on the configuration ID and select Test.

Tip: Remember to activate the application/view/controller every time you make any changes.

Therefore WDA provides a lot of flexibility to create as many variants for the web Dynpro components and the applications as required.

Changing the Roadmap

The sequence in which the different components or steps appear in the application wizard, compose the roadmap for the application (See Picture 2). If you would like to change the order for the roadmap you can do this by

  1. creating a unique configuration ID for the component HRRCF_C_ROADMAP_UI
  2. Assigning this configuration ID in the application wizard (as explained above, see Picture 4).
  3. Assigning the same unique config ID while creating the roadmap pattern in IMG. (E-recruitment -> Technical Settings ->User Interfaces -> Flexibilization – > Backend – >  Create Roadmap Pattern

Creating a Start Page:

Picture 1 shows how a start page looks like and how it is composed of Level 1 and Level 2 elements. One can define their own Level 1 and Level 2 entries. Once you have done that,


  1. Create a configuration ID for the Web Dynpro component HRRCF_C_STARTPAGE.
  2. Create a Config Id for the WebDynpro Application HRRCF_A_STARTPAGE_EXT_CAND ( There is a  separate start page for internal candidates)
  3. Assign the component configuration in this step
  4. Use the same Component Configuration ID while defining the start page in IMG.

Therefore the Component Configuration ID is the common parameter which links the Web Dynpro component to the configuration variant of the Web Dynpro application and the configuration of start page in the IMG. What I have described above is a simple example of using WDA for candidate scenarios. One can also modify the theme and colour using configuration.

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

    I’m not agreeing with you in saying that BSP is being replaced by WDA. BSP is still a viable solution if a development team needs greater freedom over design, look and feel.

    WDA can allow more rapid development, less JavaScript, less validation and better session management, but comes at the “price” of moving inside the WDA rendering framework. Flash Islands will give WDA a slightly different twist, but my main point remains.

    I agree that WDA is the future for web app development from the ABAP stack, but don’t forget that the latest CRM (2007) release was written in BSP, for example.

    Kind regards,
    Michael Koch

    • Hi Michael,
      Thanks for your comment and I agree it was a wrong choice of words when I wrote that WDA is fast replacing BSP. I agree BSP still exists as an option and WDA is the way forward for web app development. I have now edited the blog.

      Thanks for your insight on BSP and WDA as well.


  • Hi,
    statements like this “BSP is beeing replaced by WDA” are not true and make me real problems. I can give lots of examples, where I would use BSPs instead of WDA.

    Customers read things like this and I already spended many hours of my time to argue, why it is better to develop a project in BSPs more than in WDA.

    WDA is great and I love to do projects in WDA, but somtimes I have to say: Better do this with BSP.

    As far as I know the statement of SAP is that BSPs will live beside WD.

    Some years ago lots of people said that BSP will replace the ITS. Now we have a new ITS version (internal ITS), which is probably to born to die as fast as possible.

    BSP will live between ITS and WDA, an this is good.

    Best regards

    • Hi Renald,

      Thanks for your comments. As you will have seen, I have removed the offending statement. I take your feedback on board.


  • Hi Vinay,

    I think the blog is good & very informative. There is a lot of information available about configuring BSP start pages & modifying the container sequences inside that. This is the first time i was a detailed description for the modification of the Webdynpro pages of eRecruiting.It is very useful. Thanks.


  • There are three tabs provided in the picture 4 Column 1.Component Usage
    can u plz brief out these things…
    • Hi Prabaharan, If its a standard E-rec WDA component or application then you need to go to the IMG for configuring the front end pages for candidates.

  • Hi Vinay ,

    Thanks a lot for this amazing article , i am a fresher and our article helped a lot.

    I am able to configure personal data page and can hide some fields by following your article.

    I further need to add some fields on the prsonal data page and am not able to figure out how?

    kindly guide me how to do so??

    • Hi Vibhor,

      You cannot add new fields through configuration. You will need to enhance the WD4A in order to add custom fields. You will need the help of a technical consultant in order to do this.

    • Hello Vibhor,

        You can try using Enhancement.Go to WDA component you want to enhance&Go to the view. And then from Menu choose View->Enhance.Go ahead and create an Enhancement implementation.Once done you can click ctrl+F4 to choose created.From now on you will be able to add new fields to the view.