Showing results for 
Search instead for 
Did you mean: 

web dynpro

Former Member
0 Kudos

what is exact difference between component controller and interface controller

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos


<b>Component Controller</b> is the Master Controller for a WebDynpro Component.It controls the interaction with

- All other Controllers

- Child Component Instances

- Model Objects.

It is a <b>Global Controller</b>.

Whereas,<b>Interface Controllers</b> are used for Communication from One Controller to the Next Controller.



Former Member
0 Kudos



A custom controller is usually not indicated, but there are special cases where you may

want to use one. In most cases, you want to use component controller. You will find

yourself primarily using:

Views (These are really controllers also just map from context in component controller what you need)

Component Controller

Component Interface Controller (But always delegate to Component Controller).

Basically, you should use Component Controller to access model and build initial context

then just map what you need. 90% of time Custom Controller is not needed.

Rarely put methods on component interface controller that do not just delegate to methods on component controller. If you are creating WD it is important to use project

type DC of type WD rather than just WD app. To really structure a WD app have a look

at the use of DCs. A Model DC, UI DC, Root DC etc.




Message was edited by:

Alvaro Tejada Galindo

Developer Advocate
Developer Advocate
0 Kudos

Interface controller is exposed, so that you have access to the component from another component. It is all around the component reuse.


RIch Heilman

Former Member
0 Kudos

Hi see this

Web Dynpro ABAP

Hope that the following also helps you.

Web Dynpro for ABAP (WD4A, WDA) is the SAP standard UI technology for developing Web

applications in the ABAP environment. It consists of a runtime environment and a graphical

development environment with special Web Dynpro tools that are integrated in the ABAP

Workbench (SE80).

Web Dynpro offers the following advantages for application developers:

The use of declarative and graphical tools significantly reduces the implementation


Web Dynpro supports a structured design process

Strict separation between layout and business data

Reuse and better maintainability by using components

The layout and navigation is easily changed using the Web Dynpro tools

Stateful applications are supported – that is, if the page is changed and the required

data remains intact so that you can access it at any time throughout the entire

application context.

Note that stateless applications are not possible.

Automatic data transport using data binding

Automatic input check

Automatic operation of the Web Dynpro application using the keyboard

User interface accessibility is supported

Full integration in the reliable ABAP development environment

Web Dynpro Architecture


Web Dynpro is the SAP NetWeaver programming model for user interfaces (UIs).

The Web Dynpro model is based on the Model View Controller paradigm, and has the

following features that build on the classic dynpro model:

Clear separation of business logic and display logic

Uniform metamodel for all types of user interfaces

Execution on a number of client platforms.

Extensive platform independence of interfaces


Metamodel Concept

Web Dynpro provides support for developing Web representation of a business application.

You use specific tools to describe the properties of a Web Dynpro application in the form of

Web Dynpro metadata. The necessary source code is then generated automatically and

executed at runtime. In addition to the events offered by the framework, you can also define

your own events for a Web Dynpro application. However, the event handling must always be

programmed in separate source code areas which are executed automatically when the event

is triggered at runtime.

In Web Dynpro, each user interface is always made up of the same basic elements. These

elements of the metamodel can be statically declared using Web Dynpro tools.

It is also possible to implement elements of the metamodel at runtime and to change them or

reintegrate them at runtime. Using these implementations, you can make any changes or

enhancements to a user interface that has been created by declarative methods by

generating new interface structures at runtime.

This means that you can combine declarative processes and the implementation of source


Graphical Development Tools

To support this declarative concept, both the SAP NetWeaver Developer Studio and the

ABAP Workbench contain a range of Web Dynpro tools. You can therefore generate a large

proportion of a Web Dynpro application using the tools provided, without having to create your

own source code. This applies to the following parts of the application:

Data flow between the front end and back end

Layout of the user interface

Properties of user interface elements

The Web Dynpro tools enable you to create source text areas manually within generated

source texts. These areas are not changed if the source code is regenerated.

Separation of Business and Application Logic

Using Web Dynpro enables a clear separation of business logic and display logic. A Web

Dynpro application runs on the front end and has local or remote access to the back end

system via a service. This means that the display logic is contained in the Web Dynpro

application, while the business logic and the persistence of the business objects run in the

back end system. The following options are currently available for connecting Web Dynpro

applications and the back-end system:

An interface generated using adaptive RFC, through which BAPIs of an SAP system

can be called

An interface for calling Web services

A self-generated interface

The source code required for connecting the Web Dynpro application can be generated

from a UML definition of the Web Dynpro interface. A UML definition can be imported

into the Web Dynpro tools as an XML file.

Conversion of the Model-View-Controller

Conversion of the Model-View-Controller Programming Model

Every Web Dynpro application is structured according to the Model View Controller

programming model:

The model forms the interface to the back end system and thus enables the

Web Dynpro application access to data.

The view is responsible for the representation of the data in the browser.

The controller lies between the view and the model. The controller formats

the model data to be displayed in the view, processes the user entries made by the

user, and returns them to the model.