8/11/2019 Creating a UI Configuration and Integrating It With the MDG Communicator

1/8

Creating a UI Configuration and Integrating itwith the MDG Communicator

8/11/2019 Creating a UI Configuration and Integrating It With the MDG Communicator

2/8

www sap com

TABLE OF CONTENTS

BUSINESS SCENARIO .................................................................................................................................... 3

IMPLEMENTATION .......................................................................................................................................... 3Copy the Compo nent Conf igurat ion.............................................................................................................. 3Connect your Configuration to the MDG Communicator ............................................................................ 5

8/11/2019 Creating a UI Configuration and Integrating It With the MDG Communicator

3/8

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 Configurationof the Overview Floorplan (OVP) USMD_SF_CARR_OVPand delete the attachment

User Interface Building Block (UIBB).

IMPLEMENTATION

Copy the Compo nent Conf igurat ion

1. Run transaction Object Navigator(SE80).

2. Go to Workbench -> Object Navigator -> Enhanced Optionsand enter USMD_SF_CARR_OVPas the

Component Configuration.

8/11/2019 Creating a UI Configuration and Integrating It With the MDG Communicator

4/8

Creating a UI Configuration and Integrating it with the MDG Communicator

4

3. In the Component Configurationscreen, chooseAdditional Functions -> Deep Copy.

4. Choose an appropriate prefix and suffix for the name of your Target Configuration ID, by choosing the

Change Affixesbutton. In this example we add the prefix Zto the already existing names. The system

automatically adds an underscore (_).

8/11/2019 Creating a UI Configuration and Integrating It With the MDG Communicator

5/8

8/11/2019 Creating a UI Configuration and Integrating It With the MDG Communicator

6/8

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 withadditional features such as the search control for MDGs search concept. Consequently, it is sufficientto maintain crWires under node settings. In the OVP floorplan that requires integration with thechange request UIBB, enter the Page IDof your main page, and define relevant wiring information.For example, relevant wiring information can include the connector class together with the sourceUIBB (Source Component), and the type of wiring involved (Port Typeand Port Identifier). All of thesesettings are dynamically added during runtime in the target OVP. The source UIBB is the one that iswiring to the change request using either a relation or, as in this example, a query. By default thedeep copy function copies the included UIBBs.IMPORTANT: You must change the Source Config Namebecause the relevant Page Idis notautomatically changed by the deep copy.

8/11/2019 Creating a UI Configuration and Integrating It With the MDG Communicator

7/8

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 arenot relevant for you (currently).

8/11/2019 Creating a UI Configuration and Integrating It With the MDG Communicator

8/8

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 SAPcompany.

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 additionalwarranty.