Skip to Content

This blog deals with the idea of pushing your abap webdynpro context into configuration. The configuration could be maintained at once using configuration editor and then be consumed into any application using application configuration.

Step By Step Procedure:

1)      Create a webdynpro component without any views or window. Right Click on the component and create a custom controller.

Create Webdynpro Component

2)      You will be asked to Enter Controller Name and Description.Once the controller is created don’t forget to mark the controller as ‘CONFIGURATION CONTROLLER’.

Create Configuration Controller

3)        Create a context against which you want to store configuration as shown below.

Create Configuration Context

4)   Map the configuration Controller context with component controller context simply by drag and drop. Now in order to store your configuration against these context you need to create component configuration for the component you have just created.

Create Component Configuration 

5)      You would see Component editor as shown below.

Component Editor Screen

6)  Provide a configuration ID and say create configuration.

Provide COnfiguration ID

7)      Now depending on the cardinality of the context you can maintain one or multiple values against this component as shown below. (The context used in the example is just a illustration, you can have your own application specific configuration context ).

Set values for your Configuration

Press on save to preserve these configuration forever. Now these configurations are ready to be used with any webdynpro application. The stored values are made available to external webdynpro application by application configuration containing this component configuration.  The approach above could be used to maintain high level UI Configuration/ UI exits. 

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. Thomas Jung
    This appears to just be a step by step guide and many of these steps are already available in the help.sap.com documentation. Really shouldn’t you post this content into the WIKI instead?
    (0) 
  2. Stefan Bungert
    Please once and for all: Blogs are meant to present something creative or at least informative.
    It doesn’t make sense to blog something which is already in the official documentation.

    regards
    Stefan

    (0) 

Leave a Reply