Creating a UI Configuration and Integrating it

with the MDG Communicator

www.sap.com
TABLE OF CONTENTS

BUSINESS SCENARIO .................................................................................................................................... 3
IMPLEMENTATION .......................................................................................................................................... 3
Copy the Component Configuration .............................................................................................................. 3
Connect your Configuration to the MDG Communicator ............................................................................ 5

Creating a UI Configuration and Integrating it with the MDG Communicator
3
BUSINESS SCENARIO
You can copy an existing UI Configuration and adapt it to your needs. As an example, we copy the
Component Configuration of the Overview Floorplan (OVP) USMD_SF_CARR_OVP and delete the attachment
User Interface Building Block (UIBB).
IMPLEMENTATION
Copy the Component Configuration
1. Run transaction Object Navigator (SE80).
2. Go to Workbench -> Object Navigator -> Enhanced Options and enter USMD_SF_CARR_OVP as the
Component Configuration.


Creating a UI Configuration and Integrating it with the MDG Communicator
4
3. In the Component Configuration screen, choose Additional Functions -> Deep Copy.


4. Choose an appropriate prefix and suffix for the name of your Target Configuration ID, by choosing the
Change Affixes button. In this example we add the prefix Z to the already existing names. The system
automatically adds an underscore (_).


Creating a UI Configuration and Integrating it with the MDG Communicator
5
5. Delete the Attachment User Interface Building Block (UIBB) and the corresponding wiring from the
Component Configuration of OVP Z_USMD_SF_CARR_OVP_CP.



Connect your Configuration to the MDG Communicator
To ensure you can dynamically integrate the change request UIBB and its wiring into your communicator
application, you must add a configuration to the Component Configurations for the communicators Web
Dynpro component.
1. Open the WebDynpro component MDG_BS_GOV_COMMUNICATOR and either create a new
Component Configuration for it or copy an existing one.
IMPORTANT: Give the new component configuration for the communicator configuration the same
name as the WebDynpro application configuration (in this case, Z_USMD_SF_OVP_CARR_CP).
Creating a UI Configuration and Integrating it with the MDG Communicator
6


2. In this case, you want to integrate the communicator with the change request UIBB, but not with
additional features such as the search control for MDGs search concept. Consequently, it is sufficient
to maintain crWires under node settings. In the OVP floorplan that requires integration with the
change request UIBB, enter the Page ID of your main page, and define relevant wiring information.
For example, relevant wiring information can include the connector class together with the source
UIBB (Source Component), and the type of wiring involved (Port Type and Port Identifier). All of these
settings are dynamically added during runtime in the target OVP. The source UIBB is the one that is
wiring to the change request using either a relation or, as in this example, a query. By default the
deep copy function copies the included UIBBs.
IMPORTANT: You must change the Source Config Name because the relevant Page Id is not
automatically changed by the deep copy.




Creating a UI Configuration and Integrating it with the MDG Communicator
7
3. Ignore all other settings or nodes available in communicators Component Configuration, as they are
not relevant for you (currently).



Creating a UI Configuration and Integrating it with the MDG Communicator
8

2013 SAP AG. All rights reserved.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP
BusinessObjects Explorer, StreamWork, SAP HANA, 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 other countries.
Business Objects and the Business Objects logo, BusinessObjects,
Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and
other Business Objects products and services mentioned herein as
well as their respective logos are trademarks or registered trademarks
of Business Objects Software Ltd. Business Objects is an SAP
company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL
Anywhere, and other Sybase products and services mentioned herein
as well as their respective logos are trademarks or registered
trademarks of Sybase Inc. Sybase is an SAP company.
Crossgate, m@gic EDDY, B2B 360, and B2B 360 Services are
registered trademarks of Crossgate AG in Germany and other
countries. Crossgate is an SAP company.
All other product and service names mentioned are the trademarks of
their respective companies. Data contained in this document serves
informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials
are provided by SAP AG and its affiliated companies ("SAP Group")
for informational purposes only, without representation or warranty of
any kind, and SAP Group shall not be liable for errors or omissions
with respect to the materials. The only warranties for SAP Group
products and services are those that are set forth in the express
warranty statements accompanying such products and services, if
any. Nothing herein should be construed as constituting an additional
warranty.