logo资料库

webdynpro 教程 NET313 - Floorplan Manager for Web Dynpro ABAP.PDF

第1页 / 共251页
第2页 / 共251页
第3页 / 共251页
第4页 / 共251页
第5页 / 共251页
第6页 / 共251页
第7页 / 共251页
第8页 / 共251页
资料共251页,剩余部分请下载后查看
toc
Icons in Body Text
toc
Introduction
Lesson:
Web Dynpro Architecture
Internally visible Component Entities
Externally visible Component Entities
Navigation
Controller Methods
Controller Attributes
Controller Events
Component Reuse
Preparing Component Reuse
Embedding Interface Views
Accessing the Interface Controller of a Component Usage
Cross Component Context Mapping
Phase Model
First, the action handling is conducted:
Adaptation
Adaptation Hierarchy
Implicit / Explicit Adaptation
First a new custom controller has to be created. The context of
Configuration
Defining a Component Configuration
1. On the first screen, enter the id of the component configurat
1. On the first screen, enter the id of the application configur
Implicit Customizing / Personalization
The UI element the user has clicked on can be hidden.
Explicit Customizing / Personalization
Lesson:
Floorplans and Floorplan Manager (FPM) for Web Dynpro ABAP
Advantages of creating Web Dynpro Application based on the FPM
Using the FPM ensures that user interfaces behave the same way i
Floorplans in Web Dynpro ABAP
Object Instance Floorplan (OIF):
A - Application title and window title:
A - Application title and window title:
Architecture of Web Dynpro Applications based on the FPM Framewo
A Web Dynpro application allows to start the business applicatio
Exercise 1: Create Package and copy template Components
Developing FPM Applications
Lesson:
Definition of UI Building Blocks (UIBBs)
Creating simple FPM applications
Component = FPM_OIF_COMPONENT (for OIF or QAF)
The Configuration Editor for FPM components
Configuration editor for the OIF component
Configuration editor for the GAF component
Configuration editor for the IDR component
Embedding UI Building Blocks
Basic Configuration of the OIF Component
After having finished the creation process, a component configur
Basic Configuration of the GAF Component
After having finished the creation process, a component configur
Basic Configuration of the IDR Component
Click on the entry IDR Baisc in the hierarchy view to edit the a
Initial Screen and Confirmation Screen
Provide a non-editable confirmation of the activity accomplished
Configure the Toolbar
The Initial Screen Toolbar
The OIF Toolbar
The GAF Toolbar
Final action:
Configure Explanation Texts
Exercise 2: Create FPM Applications
Exercise 3: Define Initial Screen and Confirmation Screen
Exercise 4: Configure Toolbar and Explanation Texts
Lesson:
Toolbar and FPM-Events
Toolbar element:
Reacting on FPM-Events
FLUSH( ):
Triggering FPM-Events from the Application
Get a reference to a singleton FPM service object, which allows
Accessing the FPM Toolbar at Runtime
OIF: IV_SERVICE_KEY = CL_FPM_SERVICE_MANAGER=>GC_KEY_CNR_OIF
Methods acting on toolbar buttons:
Toolbar element:
IV_MAINSTEP_ID:
Activation of Roadmap Sub Steps
First, an event object being an instance of class CL_FPM_EVENT h
Accessing the IDR at Runtime
Methods acting on the header area:
Using the FPM Message Manager
Methods used to report messages:
For each text category (simple text, T100 text, text from except
Exercise 5: Implement Methods of FPM-Interface
METHOD process_event. DATA lv_interface_view TYPE string.
METHOD process_event . DATA lv_result TYPE wdy_boolean. C
METHOD needs_confirmation . DATA lt_change_log TYPE wdr_contex
METHOD wddoinit . DATA lo_componentcontroller TYPE REF TO ig_c
METHOD wddoinit . DATA lo_componentcontroller TYPE REF TO ig_c
Exercise 6: Access the Toolbar at Runtime
METHOD wddoinit . * get text displayed on introduction screen
METHOD process_before_output . DATA lv_interface_view TYPE s
Exercise 7: Access the IDR at Runtime
METHOD wddoinit . DATA lo_componentcontroller TYPE REF TO ig_
METHOD init_idr . DATA lo_nd_customer TYPE REF TO if_wd_conte
METHOD init_idr . ... wd_this->go_fpm_idr->set_application
METHOD flush . DATA lt_change_log TYPE wdr_context_ch
METHOD set_idr_ticket . DATA lv_ticket_top TYPE strin
METHOD init_idr . ... * optional part: initialize ticket area
METHOD flush . ... * Optional parts *************************
METHOD process_event . ... * if update was successful,
METHOD set_idr_items . DATA lt_items TYPE if_fpm_idr=>t_items
Exercise 8: Use the FPM Message manager
METHOD wddoinit . * get reference to FPM service object wd_t
METHOD process_event. DATA lv_interface_view TYPE stri
METHOD wddoinit . * get text displayed on introduction screen
METHOD process_event . DATA lv_result TYPE wdy_boolean. DATA
Generic UI Building Blocks (GUIBBs)
Lesson:
Architecture
Feeder Classes
FORM GUIBB:
Methods processed during initialization of the feeder class:
Impact on the Phase Model
Lesson:
Component Configuration and GUIBB Method Implementation
First, the component configuration of the FPM component (OIF or
The configuration editor for Web Dynpro will be opened in a new
If parameters have not been defined in the feeder class, a popup
Next, the view s layout needs to be structured. Here, one or mul
Form fields may be assigned to any group (or melting group). Thi
The form field has to be marked in the hierarchy view.
Runtime Aspects: INITIALIZE( )
get the references to the FPM service object
Runtime Aspects: FLUSH( )
check for changes of the form field values
Runtime Aspects: PROCESS_EVENT( )
identify the FPM-Event triggered by the user or by the applicati
Runtime Aspects: GET_DATA( )
check if the data to be displayed by the form has been changed p
Runtime Aspects: NEEDS_CONFIRMATION( )
Exercise 9: FORM GUIBB - Define Feeder Class, use Central Data M
METHOD if_fpm_guibb_form~get_definition. DATA lt_component_ta
METHOD if_fpm_guibb_form~flush. DATA ls_change_log TYPE fpmg
METHOD if_fpm_guibb_form~get_data. DATA ls_field_usage LIKE
METHOD wddoinit . wd_this->set_intro_text( ). * wd_this->go
METHOD flush. DATA lv_interface_view TYPE string. DA
METHOD needs_confirmation . CASE io_event->mv_event_id. W
METHOD process_before_output . wd_this->go_fpm_oif->define_bu
METHOD process_event . ENDMETHOD.
Lesson:
Configuration of the GUIBB and Implementation of the Feeder Clas
First, the component configuration of the FPM component (OIF or
The configuration editor for Web Dynpro will be opened in a new
Next, the list s properties needs to be configured. After having
Click the button Configure Columns .
The column has to be marked in the hierarchy view.
Runtime Aspects: INITIALIZE( )
Runtime Aspects: FLUSH( )
Runtime Aspects: PROCESS_EVENT( )
The line index (parameter key FPM_GUIBB_LIST_INDEX ).
Runtime Aspects: GET_DATA( )
Runtime Aspects: NEEDS_CONFIRMATION( )
Exercise 10: LIST GUIBB - Define Feeder Class and configure Comp
METHOD if_fpm_guibb~get_parameter_list. DATA ls_parameter_de
METHOD if_fpm_guibb~initialize. DATA ls_parameter LIKE LINE O
METHOD if_fpm_guibb_list~get_definition. DATA lo_structdescr
METHOD if_fpm_guibb_list~get_data. * Actualize data IF gv_da
METHOD needs_confirmation . ENDMETHOD.
METHOD process_before_output . ENDMETHOD.
METHOD wddoinit . wd_this->set_intro_text( ). * wd_this->go_c
tables
Toolbar Elements
Toolbar Buttons
Toolbar Button-Choices
Toolbar Elements
Methods defined in the Interface IF_FPM_UI_BUILDING_BLOCK
NET313 Floorplan Manager for Web Dynpro ABAP SAP NetWeaver Application Server - ABAP Date Training Center Instructors Education Website Participant Handbook Course Version: 91 Course Duration: 3 Day(s) Material Number: 50094991 An SAP course - use it to learn, reference it for work
Copyright Copyright © 2009 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Trademarks • • • • • • • • • • Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation. IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation. ORACLE® is a registered trademark of ORACLE Corporation. INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered trademarks of Informix Software Incorporated. UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group. Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA® is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies. Disclaimer THESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE, INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTS CONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANY KIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOST PROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDED SOFTWARE COMPONENTS. g2009112114144
About This Handbook This handbook is intended to complement the instructor-led presentation of this course, and serve as a source of reference. It is not suitable for self-study. Typographic Conventions American English is the standard used in this handbook. The following typographic conventions are also used. Type Style Example text Example text EXAMPLE TEXT Example text Example text Description Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths, and options. Also used for cross-references to other documentation both internal and external. Emphasized words or phrases in body text, titles of graphics, and tables Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example SELECT and INCLUDE. Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, and passages of the source text of a program. Exact user entry. These are words and characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries. 2009/91 © 2009 SAP AG. All rights reserved. iii
About This Handbook NET313 Icons in Body Text The following icons are used in this handbook. Icon Meaning For more information, tips, or background Note or further explanation of previous point Exception or caution Procedures Indicates that the item is displayed in the instructor's presentation. iv © 2009 SAP AG. All rights reserved. 2009/91
Contents Course Overview ......................................................... vii Course Goals ...........................................................vii Course Objectives .....................................................vii Unit 1: Introduction........................................................ 1 Web Dynpro ABAP Fundamentals ...................................2 Floorplan Manager - Overview ...................................... 36 Unit 2: Developing FPM Applications ............................... 55 Configuring FPM Components ...................................... 56 FPM Programming - Basics ........................................100 Unit 3: Generic UI Building Blocks (GUIBBs) ....................159 Generic UI Building Blocks - general Aspects ...................160 The FORM GUIBB...................................................167 The LIST GUIBB .....................................................201 Index .......................................................................233 2009/91 © 2009 SAP AG. All rights reserved. v
Contents NET313 vi © 2009 SAP AG. All rights reserved. 2009/91
Course Overview This course deals with the creation and configuration of Web Dynpro for ABAP applications that are based on the Floorplan Manager (FPM) framework. Target Audience This course is intended for the following audiences: • Developers of Web Dynpro ABAP applications based on the FPM framework. Course Prerequisites Required Knowledge • NET310 - Fundamentals of Web Dynpro for ABAP Course Goals This course will prepare you to: • • Understand the architecture of Web Dynpro applications based on the FPM framework Create Web Dynpro applications based on the Object Instance Floorplan (OIF) and the Guided Activity Floorplan (GAF) Course Objectives After completing this course, you will be able to: • • • • • • • Configure FPM components statically Define toolbar buttons and handle toolbar events Add initial screens and confirmation dialogs to the floorplans Understand the FPM phase model basically Define messages making use of the FPM message manager Define forms and lists by means of generic UI building blocks (GUIBBs) Provide data to be displayed by GUIBBs by means of feeder classes 2009/91 © 2009 SAP AG. All rights reserved. vii
Course Overview NET313 viii © 2009 SAP AG. All rights reserved. 2009/91
分享到:
收藏