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_MODEL
The 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_EXTENDED
The 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_MODEL) consists of the DEFAULT_COLUMNS field: This enables you to specify whether the column objects are to be generated or not.
You now have all the objects needed to configure the ALV output as required.
You can specify a new internal data table for the ALV output at a later stage. To do this, use method SET_DATA. However, by using this method you also automatically delete the entire ALV configuration model with all fields and column objects. To make the configuration model available again to the new data table, use method GET_MODEL or method GET_MODEL_EXTENDED.
Cross-Component Programming, Dynamic Programming, Integrating Forms, Integration, Integration of ALV, Interview Questions, List Viewer in Web Dynpro Portal Integration, TCodes, Web Dynpro ABAP
Wednesday, June 25, 2008
Subscribe to:
Post Comments (Atom)
Archive
-
▼
2008
(169)
-
▼
June
(61)
- Using the ALV Views List Viewer in Web Dynpro for ...
- Objects of the ALV Configuration Model List Viewer...
- Getting the ALV Configuration Model List Viewer in...
- Class Diagram List Viewer in Web Dynpro, Integrati...
- Archiving Workbench SAP Transaction Code
- AuC Assignment of Dist. Rule SAP Transaction Code
- C AM Maint. list vers. gen. line it SAP Transactio...
- Display Dist. Rule Allocation SAP Transaction Code
- Block Asset Master Record SAP Transaction Code(TCode)
- Web Dynpro ABAP
- Web Dynpro Architecture
- Web Dynpro Component
- Web Dynpro Component View
- Web Dynpro Component View Set
- Web Dynpro Component Plugs and Navigation Links
- Web Dynpro Window
- Web Dynpro Component Window Plugs
- Web Dynpro Component Controller
- Web Dynpro Component Context
- Web Dynpro Component Context Node Properties
- Web Dynpro Component Data Binding and Mapping
- Web Dynpro Component Event
- Web Dynpro Component Action
- Interfaces of Web Dynpro Components
- Web Dynpro Application
- Web Dynpro Model
- Web Dynpro for ABAP Configuration
- Active Services in SICF Web Dynpro ABAP
- Fully Qualified Domain Names (FQDN)
- Web Dynpro ABAP: Development in Detail
- Web Dynpro ABAP
- Web Dynpro ABAP Component
- Web Dynpro ABAP View
- Web Dynpro ABAP UI Elements of the View
- Web Dynpro ABAP Structure of the View Context
- Web Dynpro ABAP Data Binding
- Web Dynpro ABAP UI Element Actions
- Web Dynpro ABAP Parameter Mapping
- Web Dynpro ABAP Action Event Handlers
- Web Dynpro ABAP Component Controller
- Web Dynpro ABAP Context Mapping
- Web Dynpro ABAP Programming Controller Methods
- WD_CONTEXT Reference Variable
- Reference Variable WD_THIS and Local Controller In...
- Methods of the Local Controller Interface
- Hook Methods: Methods Called by the Runtime Web Dy...
- Predefined Methods of the Local Controller Interfa...
- Events and Event Handlers Web Dynpro ABAP
- Web Dynpro ABAP Supply Function
- Free Methods in Application Development Web Dynpro...
- Web Dynpro ABAP Cross-Controller Method Call
- Web Dynpro ABAP Runtime APIs
- Web Dynpro ABAP Filling the Context
- Web Dynpro ABAP Phase Model
- Web Dynpro ABAP Client Implementation
- Web Dynpro Window
- Navigation Between Two Views
- Web Dynpro ABAP Window Plugs: Startup and Exit
- Web Dynpro Application
- Web Dynpro ABAP URLs and Namespaces
- Using Parameters to Call a Web Dynpro Application
-
▼
June
(61)
No comments:
Post a Comment