Scribd
Upload
3 views2 pages

Web Dynpro Component Overview Guide

The document outlines the components of Web Dynpro, focusing on the Component Controller as a central element. It details the phases of the OVS configuration process, including defining texts, setting search structures, and applying results. Each phase has specific tasks and implications for how data is displayed and managed within the application.

Uploaded by

tlninfo
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
3 views2 pages

Web Dynpro Component Overview Guide

The document outlines the components of Web Dynpro, focusing on the Component Controller as a central element. It details the phases of the OVS configuration process, including defining texts, setting search structures, and applying results. Each phase has specific tasks and implications for how data is displayed and managed within the application.

Uploaded by

tlninfo
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Table of Contents

Introduction...........................................................................................................................................2
Introduction
Web Dynpro contains following 4 components;

1. Component Controller: Backbone of Web Dynpro. One Web Dynpro has one controller,
which is global to whole module. Whatever we do in component controller, is visible and
accessed from all parts of Web Dynpro.
2.

OVS
Phase 0 -configuration phase, may be omitted
 In this phase you have the possibility to define the texts,
 If you do not want to use the defaults (DDIC-texts)

Phase 1 - Set search structure and defaults

 In this phase you can set the structure and default values
of the search structure.
 If this phase is omitted, the search
fields will not be displayed, but the selection table is
* displayed directly.
* Read values of the original context (not necessary, but you
* may set these as the defaults). A reference to the context
* element is available in the call back object.

Phase 2 –
If phase 1 is implemented, use the field input for the
selection of the table.
* If phase 1 is omitted, use values from your own context.

Phase 3 - apply result

You might also like