|
| |
| |
| |
|
Statistics |
| Unique Visitors: 8 |
| Total Unique Visitors: 10600 |
| Visitors Out: 332 |
| Total Visitors Out: 332 |
|
|
|
| |
|
|
| |
|
| Integration of ALV in ApplicationList Viewer in Web Dynpro for ABAP |
| 2008-08-15 00:45:28 |
Purpose If you want to use an ALV output in your application, you have to follow various steps, depending on the required result. The following variants outline the most important ways in which you can call ALV: ● Simple call without ALV configuration model You only display an ALV output. You do not want to make any changes. ● Simple call with ALV configuration model You want to change the standard output using your application. To do this, you require the ALV configuration model. ● ALV output in external view without ALV configuration model ALV output is just one of many elements in a view. You do not want to change the ALV output. You do not need the ALV configuration model. ● ALV output in external view with ALV configuration model ALV output is just one...
|
| |
|
| Defining the Component Usage List Viewer in Web Dynpro, Integration of ALV |
| 2008-08-15 00:44:21 |
To use an ALV output in your application, use the component SALV_WD_TABLE. You can integrate this ALV component as an external component into your Web Dynpro component. To do this, you define the component usage. If you want to display multiple different ALV outputs, distinguish between these outputs by using unique names for the respective usage variants of the component. How you define the component usage depends upon how you want to use the ALV component. · If the ALV output is the only element on the screen, you define the component usage of the ALV component only in the component of your application (the top node in the hierarchy of the component, as it is displayed in the Component Editor). This is the simplest case. You cannot configure the ALV output before it is ...
|
| |
|
| Providing the Data List Viewer in Web Dynpro, Integration of ALV |
| 2008-08-15 00:43:55 |
To provide the data you want to display in the ALV output, perform the following three steps: ● Internal data table You provide an internal data table. ● Context nodes You provide a suitable context node and attributes in the context of your application. ● Transferring data to the ALV component You provide this context node for the ALV component. Internal Data Table The data of the internal data table must be available in flat structures. This is the only prerequisite. The easiest way to do this is to use an existing DDIC structure. Context Nodes The ALV component requires a context node that can contain the data of the internal data table. This context node has the following properties: ● It has the cardinality 0..n....
|
| |
|
| Web Dynpro ABAP Integration |
| 2008-08-15 00:42:40 |
Web Dynpro ABAP provides functions for integration in and with various technologies:● Portal Integration● Adobe Integration● Office integration● BI integration● FileUpload and FileDownload - File Export● SAP List Viewer Integration● CAF Guided Procedures IntegrationIn View Designer Category Integration is provided for relevant UI elements....
|
| |
|
| Web Dynpro ABAP Integrating Forms |
| 2008-07-30 12:01:56 |
For Web Dynpro user interfaces, forms can be created and used in the context of SAP Interactive Forms by Adobe. For efficient and straightforward development of the user interface, you can integrate the Adobe LiveCycle Designer tool with editor and the Adobe UI elements into the development workbench. As of NetWeaver 7.0 (NW 7.0) SPS10 forms can be integrated using Zero Client Installation (ZCI). As of NetWeaver 7.0 SPS10 we strongly recommend you use ZCI forms with an XML interface only. Because additional central features have been added in subsequent SPs (input help and dropdown list boxes), we generally recommend that you always use the most up-to-date Support Package for Web Dynpro ABAP. We recommend that you always use forms with an XML interfa...
|
| |
|
| Prerequisites for Form Integration Web Dynpro ABAP Integrating Forms |
| 2008-07-30 12:01:07 |
General Prerequisites SAP NetWeaver AS System with Adobe Document Services (ADS) To test the connection to ADS, run report FP_PDF_TEST_00. Version information about your ADS will be displayed. If this test is successful, run report FP_TEST_00. Select a printer and select the option for the print preview. The Adobe Viewer appears and displays a simple form. Language Settings To display the form is displayed in the language required, you have to specify a combination of language and locale (country) as well as provide the necessary translations. The logon language of the system is used as the language. You can specify the country in your user profile (transaction SU52) on tab page Parameters. Enter UCN as the Parameter ID and enter the short code of the r...
|
| |
|
| Integrating a PDF Form in a Web Dynpro Application Web Dynpro ABAP Integrating Forms |
| 2008-07-30 12:00:26 |
This chapter describes the procedure for using a PDF form in a Web Dynpro application with the various scenarios. Form Integration for the Various Scenarios Scenario Procedure Print Interactive Integrating (Interactive) Forms Offline Integrating Existing Forms Digital Signatures Digital Signatures in Form Integration Form Data in XML Format In the procedure for the print scenario and the interactive scenario, only the two properties templateSource and dataSource of InteractiveForm were bound to the view context. The templateSource property contains information about the form template, while the context node, to which the dataSource property was bound, contains ...
|
| |
|
| Inserting (Interactive) Forms Web Dynpro ABAP Integrating Forms |
| 2008-07-30 11:59:53 |
Use As there is very little difference between the print scenario and the interactive scenario for inserting a form in a Web Dynpro application, the procedure for both scenarios is provided together below. Forms with static content, such as PDF-based print forms, can be used to display or print data in Web Dynpro applications. In the case of interactive forms, you can reuse user entries stored in the Web Dynpro context for your own Web Dynpro application. In scenarios where the templateSource/dataSource are filled, the form can only be created if an ADS is available. On the other hand, the pdfSource property is ignored in this case. For the properties enabled and readOnly, note the following: ● If e...
|
| |
|
| Inserting Existing PDF Forms (MIME Objects) Web Dynpro ABAP Integrating Forms |
| 2008-07-30 11:59:13 |
Use Forms that are stored in systems as MIME objects in the MIME repository with MIME type application/pdf can be integrated and displayed in a Web Dynpro application. To do this, bind the pdfSource property to a context attribute of type XSTRING. In this case therefore, neither the templateSource nor the dataSource are set. In scenarios where only the pdfSource is set, the properties enabled and readOnly are ignored. The form can then be displayed for printing (and is displayed without the ADS or the ACF). Using the method call described below, the PDF document can be made ready for input, but there is no context binding. Instead, the changed document is retrieved from the pdfSource and processed in the specific application. Prerequisites You nee...
|
| |
|
| Digital Signatures in Form Integration Web Dynpro ABAP Integrating Forms |
| 2008-07-30 11:58:21 |
When editing forms whose content is critical to security, it is a good idea to use digital signatures, so that the origin of the form can be verified. This allows you to check whether the source is trustworthy and whether the form or its content has been changed subsequently (integrity). See also: Digital Signatures and Certification in Forms Digital Signatures in Forms Prerequisites ● ADS Connection For the signatures, you need a secure connection via SSL or HTTPS. For this, your system needs an RFC connection of type HTTP Connection to External Server for the ADS. The external server for the ADS is the J2EE Engine. See Adobe Document Services Configuration Guide ● D...
|
| |
|
| Supported Elements of the Adobe Library Web Dynpro ABAP Integrating Forms |
| 2008-07-30 11:57:50 |
Special UI elements in the Adobe Designer are available for form development in a Web Dynpro ABAP application. Go to the Layout tab page in the form builder. Depending on how the forms are integrated the following libraries are available for Web Dynpro ABAP in the Library group box. ZCI Forms If you have selected the entry ZCI Layout as the Layout Type in the form builder's Properties, as a developer of forms based on ZCI you can use the Web Dynpro Native library. The following elements are currently supported by the Web Dynpro ABAP environment: Send With the Web Dynpro form UI element Send, the input data of a PDF form is sent to an SAP backend syst...
|
| |
|
| Interactive Form Use Web Dynpro ABAP Integrating Forms |
| 2008-07-30 11:57:01 |
There are many reasons for including forms in a Web Dynpro application. Most embedded forms are used for printing and archiving and therefore do not have to be made available in interactive form. However, the Web Dynpro framework still allows you to use embedded PDF forms interactively. Using a PDF as an input template for a Web Dynpro application can be especially useful when a user is familiar with the appearance of a form and, for reasons of recognition, you would like to also make this form available in the system. An example of this is a tax return form. A further use case for interactive forms relates to legal considerations. It may be necessary to store not only the data content o...
|
| |
|
| Forms with ABAP Dictionary-Based Interface Web Dynpro ABAP Integrating Forms |
| 2008-07-30 11:56:35 |
Before the introduction of the XML-based interface, an ABAP Dictionary-based interface was created for a form during integration of the same. Such an interface, however, was not easily linked to the context of a Web Dynpro component. All the forms created from within the Web Dynpro context are not automatically equipped with an XML-based interface. In certain situations, however, it can be necessary to integrate an old form with a function module-based interface into a Web Dynpro application. The Web Dynpro runtime makes it possible, in principle, to display or print such a form within a Web Dynpro application. In special cases, it is even possible to integrate a form of this type in...
|
| |
|
| Hiding the Adobe Toolbar Web Dynpro ABAP Integrating Forms |
| 2008-07-30 11:55:39 |
You can make a setting to hide the Adobe Reader toolbar. In the default setting this toolbar is displayed. Example Showing the Toolbar You can hide the toolbar using method SET_HIDE_TOOLBARS of the UI element interface InteractiveForm IF_WD_IACTIVE_FORM_METHOD_HNDL: … lr_method_handler->set_hide_toolbars( abap_true ): Example with Toolbar Hidden Users can also hide (or show) the toolbar by choosing the function key F8 within the application....
|
| |
|
| File Export Web Dynpro ABAP Integrating Forms |
| 2008-07-30 11:54:50 |
Use You can export files in accordance with the FileDownload functionality, thereby fulfilling the usual security requirements. This download functionality is available in every action handler, for example, when clicking a Button, a LinkToAction or (what you should not do) when switching a TabStrip or clicking a RadioButton. When the user clicks the respective UI element, a binary data stream is generated. For this data stream, the appropriate URL is generated and the result is displayed in a separate browser window. Features For both cases, whether to export a single file or several files, the same ways of displaying and storing the file(s) exist: · Display in the same window Example: · Save query in...
|
| |
|
| Dynamic Programming Programming Web Dynpro ABAP |
| 2008-07-25 08:23:47 |
Web Dynpro offers the frame for you to lay out the user interface structures of your business application as declarative as possible. Nevertheless, with increasing complexity of the application, it may become necessary to make certain decisions only at runtime. The dynamic embedding of an interface view into a window in the context of a dynamically created component usage is an example for dynamic programming within a Web Dynpro application. In addition, you may influence, for example, the structure of a context at runtime; you may add elements to a context at runtime. Besides, you can change the layout of a view at runtime, which means that you can dynamically add UI elements....
|
| |
|
| Dynamic Layout Manipulation Dynamic Programming Programming Web Dynpro ABAP |
| 2008-07-25 08:23:25 |
Under certain conditions, it may be useful to change the layout of a view at runtime. In this context, you can add as well as remove UI elements. You can also change the dynamic properties of a UI element, bind an event to an action or manipulate the Parameter Mapping of Event Parameters. Basically, you should use the dynamic manipulation of the layout – just like the dynamic manipulation of the context – only if it is not possible to construct a component by declarative means. This may be the case if parts of the component are not yet knows at design time. To make changes to the structure of a view layout, you must use the method WDDOMODIFYVIEW (or a method called within it). For a complete list of all UI element classes and their methods, refe...
|
| |
|
| Working Dynamically with Parameter Mappings Dynamic Programming Programming Web Dynpro ABAP |
| 2008-07-25 08:22:50 |
The term parameter mapping is used for the bind of an event parameter to a parameter of an action handler method. Background A number of UI elements is able to trigger events. Each of these events has predefined parameters; for example, every event has the parameter ID. Depending on the type of the related UI element, other parameters may additionally be predefined. However, these event parameters are not represented individually in the development environment; for a complete list of all events and their related parameters for every UI element, see the reference part of this documentation. In the handler method of the action related to the event, you can now use this event parameter by creating a parameter with the same name for the method. The mapp...
|
| |
|
| Dynamic Context Manipulation Dynamic Programming Programming Web Dynpro ABAP |
| 2008-07-25 08:22:01 |
You can manipulate the context of a controller in different ways at runtime. To support the dynamic programming of contexts and view layouts, the Web Dynpro framework offers a number of methods in the service class CL_WD_DYNAMIC_TOOL. This class contains the frequently used methods in a predefined form. However, you can also implement yourself all the methods for dynamic context manipulation implemented in this class within the Web Dynpro framework. However, note that not all technically possible options are available in this class. In many cases, you will carry out your programming via the relevant framework interfaces to be able to use advanced functions. To get an overview of how this class is used, have...
|
| |
|
| Method Call in a Dynamically Created Component Usage Web Dynpro ABAP Dynamic Programming |
| 2008-07-25 08:21:37 |
If a used component of the using component wants to provide a method to be called, this method must be defined in the interface controller of the used component. In practice, the method to be called is generally declared in the interface controller of an interface definition and programmed in the component controller of an implemented component. The code fragment below shows a section of a method of a view controller of the using component: method MY_CONTROLLER_METHOD . data: L_INTF_CONTROLLER type ref to IWCI_, L_COMPONENT_USAGE type ref to IF_WD_COMPONENT_USAGE. L_INTF_CONTROLLER ?= L_COMPONENT_USAGE->GET_INTERFACE_CONTROLLER( ). L_INTF_CONTROLLER->( ). . . endmethod. L_COMPONENT_USAGE is a reference to the dynamically created compo...
|
| |
|
| Showing posts with label Dynamic Programming. Show all posts Dynamically Registering an Event Handler to an Event Web Dynpro ABAP Dynamic Programming |
| 2008-07-25 08:21:03 |
Components you use within another component can have events. An event of an interface definition is triggered in the component in which the interface definition is implemented. An event handler of the using component can register onto such an event. If the usage of a component has been created dynamically, then also the registration of the using component onto an event of the used component or the implemented interface must be created dynamically. The code fragment below shows an example of how to implement a dynamic registration. method MY_CONTROLLER_METHOD . data: L_COMPONENT_API type ref to IF_WD_COMPONENT, L_COMPONENT_USAGE type ref to IF_WD_COMPONENT_USAGE. L_COMPONENT_API = WD_COMP_CONTROLLER->WD_GET_API( ). L_COMPONENT_USAGE->ADD_EVEN...
|
| |
|
| Cross-Component Programming Web Dynpro ABAP |
| 2008-07-25 08:19:38 |
Web Dynpro components are reusable modules. This allows you to build Web Dynpro applications that consist of different components. From within a component, an interface enables you to use the data and functions of another component. The prerequisite for this is that the second component must be available at runtime in an active version. Within a distributed development project, it makes sense to create generic components to be used by different developers. For more information, see Working with Component Usages. In addition, it may be useful to create own components only as suppliers of the data required in other components. Such components are called model components; they only make sense whenever several components must access the same set of application data. Model components are comp...
|
| |
|
| Controllers of a Web Dynpro Component Cross-Component Programming Web Dynpro ABAP |
| 2008-07-25 08:19:16 |
Component Controller The component controller provides data and processing logic that it should be possible to display or change for all views of a component. It has three interfaces: · Interface IF_ for coding within the controller · Interface IG_ for cross-controller coding within the current component. · Interface IWCI_ for cross-component coding. On the ABAP language level it represents the interface controller (see below). Within the component, mapping is possible to any context element of the component controller. (See also Data Binding and Mapping). The attributes of a component controller are known to all methods that are called within a component and can be used by them, provided they have the Public property. Otherwise, their visibility is res...
|
| |
|
| Component Usages Web Dynpro ABAP |
| 2008-07-25 08:18:41 |
Embedding a Used Component To be able to use an external component (regardless of whether it is a faceless component or a complete component), you must first define a component usage. Follow the steps described below: Procedure Select the component that you want to process by double-clicking on it in the object list. The Component Editor is displayed. 1. Select a name for the new component usage and enter it in the first column in the table. 2. Select the component to be used (F4 help). 3. You should now consider the following: · If the external component should be used by a single view of your component, it makes sense to create the instance of the external component in a controller method of this view. · If the externa...
|
| |
|
| Component Usage without Controller Access Component Usages Web Dynpro ABAP |
| 2008-07-25 08:18:07 |
You can use an external component in two ways: If you only want to display the external component, but not change the data of its interface controller or use its functions, you can omit the explicit usage declaration of the external interface controller in the current controller. In this case, simply declare the usage of the external component in the currently edited controller (see figure). To do this, choose Sample Usage®Foreign_Component. This merely enters the usage of the component in the table, and you can call the component for display purposes from the current component. The usage was added to the metadata again. Instantiating the Used Component Regardless of whether you decided on a component usage with or without controller access, you now have to instantiate the used c...
|
| |
|
| Component Usage with Controller Access |
| 2008-07-25 08:17:28 |
If you want to enable access to the interface controller of the external component from the current component – that is, if you want to change this controller’s data or use its functions – you must choose on the Properties tab page of the selected controller Sample Usage ® Foreign_component ® Interface Controller. In this case, both the component and the interface controller are explicitly included into the table. The usage was added to the metadata again. Instantiating the Used Component In accordance with the procedure described in the section above, the used component must be instantiated in an appropriate method of the component (see Component Usage without Controller Access). Implementing Access to Methods of the Controller of a Used Component If you now want to acce...
|
| |
|
| Navigation Through Window Plugs Component Usages Web Dynpro ABAP |
| 2008-07-25 08:16:31 |
You can vary – at runtime – which link that was set up at design time you wish to follow. You can do this through navigation control with the help of event handlers from window plugs. In this manner you can control at runtime – within navigation in a window of an embedded component – which view of this embedded window is to be displayed first. Including the Window Plugs into Navigation An additional step in navigation is necessary to include a parameter for navigation control. Instead of linking the outbound plug of a view in the window editor with the inbound plug of a subsequent view, the outbound plug of the view is linked with an inbound plug of the embedded window. Each window automatically has the ...
|
| |
|
| Cross-Component Context Mapping Component Usages Web Dynpro ABAP |
| 2008-07-25 08:15:51 |
A third way of using the content of the interface controller of a used component is the cross-component context mapping. As soon as you have declared the usage of the interface controller and instantiated the external component as described in the procedure of the section above, the context of the external interface controller is available for mappings. On the Context tab page of a controller for which a usage of the external interface controller has been declared, you see the context of this interface controller on the right side of the editor and you can define a mapping for a node of your current controller context to a node of the interface controller context. ...
|
| |
|
| External Context Mapping Component Usages Web Dynpro ABAP |
| 2008-07-25 08:15:26 |
Cross-Component Context Mapping described the mechanism of a mapping across the borders of a Web Dynpro component. In the example, component A used a component B and for Node 1 of the component controller context of A a mapping was defined to the node of the same name of the interface controller context of component B. Both components are known at design time. For a better understanding, the figure below again shows the simple context mapping as explained in the section above: The mapping definition at runtime provides component A with the value for its component controller context from the interface controller of component B – with other words: The node of the interface controller context is the “source” node in this mapping relationship. O...
|
| |
|
| Working with Web Dynpro Component Interfaces Component Usages Web Dynpro ABAP |
| 2008-07-25 08:14:45 |
In every Web Dynpro component, the creation procedure implements an interface. This component interface contains exactly one interface controller and at least one interface view (for more information, see Interfaces of aWeb Dynpro Component in the Architecture manual). The interface controller contains a context, events and methods. The interface views of the component interface have no direct connection to the interface controller; they are generated automatically for every window that is created within the component. The component interface is implemented exclusively in its related component; it cannot be implemented in other components. The programming environment of Web Dynpros now allows you to enhance this pre-implemented interface by implementing additional interfaces, which ha...
|
| |
|
| Creating a Web Dynpro Component Interface Definition Component Usages Web Dynpro ABAP |
| 2008-07-25 08:12:49 |
Procedure 1. Start the Object Navigator and in the object list selection choose Web Dynpro Comp./Interf. 2. Enter a new name for your component interface definition and choose Display. 3. Confirm the Create Object dialog. 4. In the next dialog window enter a description of your component interface definition and in the list below mark the type Web Dynpro Component Interface. Confirm this dialog as well. 5. Create an object catalog entry by assigning the new object to the desired package and by choosing Save. You can now create methods and interface views for this interface definition....
|
| |
|
| Implementing a Web Dynpro Interface Definition Component Usages Web Dynpro ABAP |
| 2008-07-25 08:11:49 |
To implement a Web Dynpro interface definition in a component, enter it into the Implemented Interfaces table of the component editor of the component: ... 1. Select the component that you want to process by double-clicking on it in the object list. You are now in the Component Editor and can switch to the Implemented Interfaces tab page. 2. Enter the name of the desired interface definition in the first column of the table and save it. 3. In the third column of the table, Implementation State, a traffic light symbol appears.. As long as this traffic light shows red, the interface definition is not or not completely implemented. Choose New Implementation to trigger the implementation; the traffic light switches t...
|
| |
|
| Example for the Implementation of an Interface Definition Component Usages Web Dynpro ABAP |
| 2008-07-25 08:11:12 |
The example below illustrates the principle of the interface definition and implementation by means of an actual development situation. The static case described here is basically designed to demonstrate the principle; in the practice, it will be of limited use, because it requires all involved components of the using component to be known already at design time. And certainly, the implementation of interface definitions is most advantageous when this knowledge is missing at design time and the desired implementation of the interface is selected only at runtime. For more information on interface implementations, see the third part of this documentation: Dynamic Programming. ...
|
| |
|
| posts Working With Faceless Components Component Usages Web Dynpro ABAP |
| 2008-07-25 08:09:53 |
Features of Faceless Components Faceless components are Web Dynpro components without graphical elements – that is, without windows or views. They only include a component controller; optionally, custom controllers can be added. You use faceless components to separate the data used in the framework of a large-scale programming project. They are designed exclusively for receiving and structuring data. By declaring a component usage you embed them into other components; they then supply the embedding component with the required data. To create a faceless component, you create a new Web Dynpro component and delete the two visible elements – that is, the view and the window – from the object list. Using Faceless Components Correctly Whether ...
|
| |
|
| Class Diagram List Viewer in Web Dynpro, Integration of ALV |
| 2008-06-25 23:51:17 |
The object model for the ALV configuration model consists of the following classes and interfaces: This class diagram has been simplified. Some superclasses have been omitted. You can find the exact structures in the system in package SALV_WD_CONFIG....
|
| |
|
| Web Dynpro ABAP |
| 2008-06-25 23:48:15 |
Purpose Web Dynpro for ABAP or 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 effort ● 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 – th...
|
| |
|
| Using the ALV Views List Viewer in Web Dynpro for ABAP |
| 2008-06-25 00:42:43 |
The ALV component contains the following views, which you can use as required:•TABLEThis is the central ALV view. To display the ALV output, you require this view.The TABLE view is the container in which the ALV output is displayed. It is a fundamental part of the ALV component. You cannot, therefore, change the layout.•SERVICEThis view contains the Settings dialog box with which the user can make changes to the settings for column display, sorting, filtering, and so on.By default, the view is displayed above the ALV output when the user chooses the Settings hyperlink in the toolbar. You use this view when you want to display the dialog box elsewhere on the screen.Inserting a TABLE View You require the TABLE view if you want to display an ALV outp...
|
| |
|
| Objects of the ALV Configuration Model List Viewer in Web Dynpro, Integration of ALV |
| 2008-06-25 00:41:14 |
The following main areas are available for configuring your ALV output:•Table settingsThe data for the Table UI element includes the structure of the application data as well as the technical fields that determine the appearance or function of the ALV output. You can define, for example, whether the ALV output is to be displayed with a simple, two-dimensional table or as a hierarchy with a leading hierarchy column.•Field settingsThe fields describe the data that is used in the ALV output. The name of a field corresponds to the name of an attribute in the context node: All field objects are automatically generated from the specifications that you made in the context node. As a result, every attribute in the context node has a representative with the same name in the ALV configurat...
|
| |
|
| Getting the ALV Configuration Model List Viewer in Web Dynpro for ABAP |
| 2008-06-25 00:38:00 |
To make the ALV configuration model available, you use, for example, a method from class IWCI_SALV_WD_TABLE in WDDOINIT. You choose one of the following methods:...● GET_MODELThe system returns a complete ALV configuration model with all column objects and field objects.This is the default variant. The method does not have any parameters.● GET_MODEL_EXTENDEDThe system returns all field objects (as above), but only returns column objects when required.If, for example, you want to manage a large number of field objects but you only want to display a few columns, create the field objects first and later generate the column objects you require to display the content.Parameter S_PARAM from method GET_MODEL_EXTENDED (type IF_SALV_WD_TABLE=>S_TYPE_PARAM_GET_MO...
|
| |
|
| Web Dynpro Architecture |
| 2008-06-12 03:24:24 |
DefinitionWeb 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 interfacesWeb Dynpro is available both in the Java and the ABAP development environment. Platform-specific information is available under:Web Dynpro for JavaStructure linkWeb Dynpro for ABAPStructureMetamodel ConceptWeb Dynpro provides support for developing Web representation of a business application. You use specific tools to describe the properties of a Web Dynpro application i...
|
| |
|
| |
 |
