8/12/2019 SDN MHO WDA Floorplan Exercise

1/15

BRING IT ALL TOGETHER WITH

FLOORPLAN MANAGER FOR WEB

DYNPRO ABAP

SDN MentorsHands-On

Exercises / Solutions

Ed Herrmann

8/12/2019 SDN MHO WDA Floorplan Exercise

2/15

2

Exercise 4

Web Dynpro Floorplan ManagerEstimated Time: 30 minutes

In exercise 3, we explored quite a few Web Dynpro topics, but the final application isnt really indicative of the way real,complex business transactions work. Often real-world applications are compose of multiple, interchangeable WebDynpro Components. For the final exercise, we will look at the Floorplan Manager tool for Web Dynpro. This is aconfiguration based tool that allows you to combine multiple components together into one Web Dynpro Application.We already have an existing Floorplan that has been configured for you. It contains a user interface for maintaining theSales Document data we have been working with. In this exercise we want to copy and then extend the Floorplanconfiguration to include the new component that you built in Exercise 3.

1. Start by creating a new Web Dynpro Application named ZMHO_XX_OIF (where XX is replaced with yourGroup Number). Save this Application as Local/Private.

2. Your application isnt actually ready to execute yet. The Floorplan component (FPM_OIF_COMPONENT)

needs configuration to tell it which of your components to load and how to arrange them. We will start thisconfiguration activity by creating a new Application Configuration.

8/12/2019 SDN MHO WDA Floorplan Exercise

3/15

3

Exercise 4 - Solution

Web Dynpro Floorplan ManagerIn exercise 3, we explored quite a few Web Dynpro topics, but the final application isnt really indicative of the way real,complex business transactions work. Often real-world applications are compose of multiple, interchangeable WebDynpro Components. For the final exercise, we will look at the Floorplan Manager tool for Web Dynpro. This is aconfiguration based tool that allows you to combine multiple components together into one Web Dynpro Application.We already have an existing Floorplan that has been configured for you. It contains a user interface for maintaining theSales Document data we have been working with. In this exercise we want to copy and then extend the Floorplanconfiguration to include the new component that you built in Exercise 3.

1. Start by creating a new Web Dynpro Application named ZMHO_XX_OIF(where XX is replaced with your

Group Number). Save this Application as Local/Private. This application will be different than the ones wehave created so far. It will reference a standard SAP Web Dynpro Component.

a. Right Mouse click on the Web Dynpro Applicat. option in the Object Hierarchy and choose Create.

8/12/2019 SDN MHO WDA Floorplan Exercise

4/15

4

b. Name the application ZMHO_XX_OIF(where XX is replaced with your Group Number). Save thisApplication as Local/Private

c. Fill in the following parameters for Component, Interface View and Plug Name

d. Switch to the Parameterstab and create a Parameter setting for WDCONFIGURATIONID. Supply a

configuration ID with the same name as your application. We will create this configuration in one of theproceeding steps.

e. Save your Application.

8/12/2019 SDN MHO WDA Floorplan Exercise

5/15

5

2. Your application isnt actually ready to execute yet. The Floorplan component (FPM_OIF_COMPONENT)needs configuration to tell it which of your components to load and how to arrange them. We will start thisconfiguration activity by creating a new Application Configuration.

a. Right mouse click on the newly created Web Dynpro Application in the object hierarchy and chooseCreate/Change Configuration.

b. This will launch the Web Dynpro Application Configuration in a new browser window (the configurationtool itself is a Web Dynpro ABAP application).

c. Create a new Application Configuration with the same name as your Application (ZMHO_XX_OIF

where XX is replaced with your Group Number) Press the Createbutton.

8/12/2019 SDN MHO WDA Floorplan Exercise

6/15

6

d. In the CreateConfigurationdialog, you can supply a short description and press the Local Objectbutton. Then press OKto continue.

e. You are now seeing your newly created Application Configuration. Next we will configure the FloorplanIDR (Identification Region) and the Floorplan main component.

f. For the IDR_USAGE, we have already supplied a Configuration named ZMHO_OIF_IDR. You can

simply type that into the Configurationcolumn.

8/12/2019 SDN MHO WDA Floorplan Exercise

7/15

7

g. For the Component Configuration you should enter a new nameZMHO_XX_OIF_COMP(where XXis your group number). You will then create this new Component Configuration in the next steps.

h. Press the Enter key and the Go to Component Configurationbutton will activate. Make sure your tableleadSelection is set to the FPM_OIF_COMPONENTconfiguration (the first row) and then press the Go

to Component Configurationbutton.

i. A new browser window will open with the Component Configurator. We dont want to have to createour component configuration from scratch. Instead we have a template component configuration thatwe can copy from. This way we only have to add our one new Component that we created in Exercise

3 to this Floorplan configuration. To start the copy process, change the Configuration IDtoZMHO_XX_OIF_EX4 and then press the Copybutton.

8/12/2019 SDN MHO WDA Floorplan Exercise

8/15

8

j. In the Configure Componentdialog, Change the Copied Configurationname fromZMHO_XX_OIF_EX4 to ZMHO_XX_OIF_COMP(where XX is replaced by your Group Number). Press

the local object button. Finally press OK to complete the copy.

k. Upon returning to the main screen, you can now choose to Changethe Component Configuration.

8/12/2019 SDN MHO WDA Floorplan Exercise

9/15

9

l. You are now in the Floorplan manager configuration tool. The left side of the screen shows you thehierarchy of the Floorplan. The right side of the screen shows you the preview of what you Floorplanlooks like and allows you to maintain detailed settings for the Floorplan UIBB (UI Building Blocks).

m. Click on the Sales Itemtab in the preview area to select that grouping of UI Building Blocks.

8/12/2019 SDN MHO WDA Floorplan Exercise

10/15

10

n. Now pressAdd Subviewto configure a UIBB to hold the component from Exercise 3. Give this newSubview the nameAdd Item to Order.

o. Click the Attributes button to configure the UIBB settings for this subview:

8/12/2019 SDN MHO WDA Floorplan Exercise

11/15

11

p. For the Componentof the UIBB, use the sample implementation of Exercise 3which was namedZMHO_SHOPPING_BASKET . For the Viewsupply the value W_MAIN.

q. Press the Savebutton

8/12/2019 SDN MHO WDA Floorplan Exercise

12/15

12

r. You can now close the browser window with the component configuration. You should still have thebrowser window open with the application configuration. Now that you have completed the componentconfiguration, you can save the application configuration as well.

s. You can then press the Testbutton to launch the application or you can return to SE80and test it via

the new application you created at the beginning of the exercise.

8/12/2019 SDN MHO WDA Floorplan Exercise

13/15

13

t. The first screen of the Floorplan manager makes you choose your processing mode and businessobject key (Sales Order ID). You can also lookup Sales Order by Partner Number. Select ChangeMode. Choose Sales Order 00000000005000000010 and Change Mode.

8/12/2019 SDN MHO WDA Floorplan Exercise

14/15

14

u. You should now see your new Sales Itemtab with the Add Items to Order sub level and be able to testyour FlashIslands Component from Exercise 3.

v. Feel free to experiment with other aspects of the Floorplan manger.

8/12/2019 SDN MHO WDA Floorplan Exercise

15/15

15

Copyright 2007 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. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries,

xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner,WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks orregistered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarksof Citrix Systems, Inc. HTML, XML, XHTML and W3C 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. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well

as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all overthe world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in thisdocument serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in anyform or for any purpose without the express prior written permission of SAP AG.

This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. Thisdocument contains only intended strategies, developments, and functionalities of the SAP product and is not intended to bebinding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document issubject to change and may be changed by SAP at any time without notice.

SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or scompleteness ofthe information, text, graphics, links, or other items contained within this material. This document is provided without a warran ty ofany kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particularpurpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damagesthat may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that youmay access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages norprovide any warranty whatsoever relating to third-party Web pages.

SAP assumes no responsibility for errors or omissions in these materials