How To Work With UWL and MDM Workflows in The Portal

SAP NetWeaver
How-To Guide
How To Work with UWL and MDM

Workflows in the Portal
Applicable Releases:
SAP NetWeaver Master Data Management 7.1 SP07 and higher
Topic Area:
Enterprise Information Management
Capability:
Master Data Management
Version 3.2
December 2013
Copyright 2013 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, 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, z/OS, AFP,
Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix,
i5/OS, POWER, POWER5, OpenPower and PowerPC are
trademarks or registered trademarks of IBM Corporation.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader
are either trademarks or registered trademarks of Adobe
Systems Incorporated 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 trademarks of 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 over the world.
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.
These materials are provided as is without a warranty of
any kind, either express or implied, including but not
limited to, the implied warranties of merchantability,
fitness for a particular purpose, or non-infringement.
SAP shall not be liable for damages of any kind including
without limitation direct, special, indirect, or consequential
damages that may result from the use of these materials.
SAP does not warrant the accuracy or completeness of the
information, text, graphics, links or other items contained
within these materials. SAP has no control over the
information that you may access through the use of hot
links contained in these materials and does not endorse
your use of third party web pages nor provide any warranty
whatsoever relating to third party web pages.
SAP NetWeaver How-to Guides are intended to simplify
the product implementation. While specific product
features and procedures typically are explained in a
practical business context, it is not implied that those
features and procedures are the only approach in solving a
specific business problem using SAP NetWeaver. Should
you wish to receive additional information, clarification or
support, please refer to SAP Consulting.
Any software coding and/or code lines / strings (Code)
included in this documentation are only examples and are
not intended to be used in a productive system
environment. The Code is only intended better explain and
visualize the syntax and phrasing rules of certain coding.
SAP does not warrant the correctness and completeness of
the Code given herein, and SAP shall not be liable for
errors or damages caused by the usage of the Code, except
if such damages were caused by SAP intentionally or
grossly negligent.
Disclaimer
Some components of this product are based on Java. Any
code change in these components may cause unpredictable
and severe malfunctions and is therefore expressively
prohibited, as is any decompilation of these components.
Any Java Source Code delivered with this product is only
to be used by SAPs Support Services and may not be
modified or altered in any way.
Document History
Document Version
3.2
Description
Correction: You can only configure a Result Set iView for different roles
and for different groups. This is not relevant for Result Set Web Dynpro
components.
For more information, see Configuring the Result Set on page 22.
Update of links to SAP MDM Documentation Page.
3.1
Added a note that a Split to Job button is only shown if a Result Set
iView was launched from an Approve step of a workflow job in MDM
Universal Worklist (UWL).
3.00
As of MDM 7.1 SP07, MDM Workflow in the Universal Worklist is

supported by MDM Portal Content (iViews) and MDM Web Dynpro
Components. Throughout the course of this guide we have explained
the configuration options for both implementations including
configuration of the delivered mdm.xml configuration file.
A recommendation has been added on how to configure the UWL for

large system landscapes.
For more information, see Prerequisites on page 3.
2.00
This guide has been enhanced with special emphasis on customizing

the delivered XML configuration file and the MDM standard portal
content.
For more information, see Configuring the Universal Worklist (UWL) on
page 2.
A new section has been added which covers the configurations that can
be implemented in the portal to determine what portal content is
available to portal users. These include: Portal Roles, UWL iView
Launcher, and Step-based Item Types.
For more information, see Portal Configurations on page 28.
1.00
First official release of this guide
Typographic Conventions
Icons
Type Style
Description
Icon
Example Text
Words or characters quoted

from the screen. These include
field names, screen titles,
pushbuttons labels, menu
names, menu paths, and menu
options.
Cross-references to other
documentation
Example text
Emphasized words or phrases

in body text, graphic titles, and
table titles
Example text
File and directory names and

their paths, messages, names of
variables and parameters,
source text, and names of
installation, upgrade and
database tools.
Example text
User entry texts. These are

words or characters that you
enter in the system exactly as
they appear in the
documentation.
<Example
text>
Variable user entry. Angle

brackets indicate that you
replace these words and
characters with appropriate
entries to make entries in the
system.
EXAMPLE TEXT
Keys on the keyboard, for

example, F2 or ENTER.
Description
Caution
Note or Important
Example
Recommendation or Tip
How To Work with UWL and MDM Workflows in the Portal
Table of Contents
1
Overview ........................................................................................................................................ 1
1.1
Introduction ......................................................................................................................................1
1.2
Business Scenario .......................................................................................................................... 2
Configuring the Universal Worklist (UWL) ..................................................................................... 2

2.1
Prerequisites ................................................................................................................................... 3
2.2
The Universal Worklist (UWL) User Interface .............................................................................. 4
2.3
2.2.1
Subviews ........................................................................................................................... 5
2.2.2
UWL Buttons..................................................................................................................... 5
2.2.3
Personalizing the UWL View ............................................................................................ 7
2.2.4
Displaying Details about MDM Linked Records in UWL................................................ 8
Configuring the Universal Worklist XML File .............................................................................. 10

2.3.1
Background..................................................................................................................... 10
2.3.2
What is the mdm.xml file? ............................................................................................... 11
2.3.3
Configuring the mdm.xml file for MDM Portal iViews.................................................. 12
2.3.4
Configuring the mdm.xml file for MDM Web Dynpro Components ........................... 19
Configuring the Result Set .......................................................................................................... 22
End User Tips and Guidelines ...................................................................................................... 27

4.1
Creating a New Workflow in the UWL ......................................................................................... 27
Portal Configurations .................................................................................................................. 28

5.1.1
Portal Roles .....................................................................................................................28
5.1.2
UWL iView Launcher ..................................................................................................... 30
December 2013
Overview
1.1
Introduction
Universal Worklist (UWL)

Universal Worklist (UWL) is a SAP NetWeaver Portal framework for integrating a user's business tasks from
SAP Master Data Management Workflow (MDM Workflow) or from other sources. UWL provides a central
overview of all workflow steps and tasks that portal users carry out, by bringing together assignments from
different workflow systems (using connectors) into a single list.
SAP NetWeaver MDM Workflow

MDM Workflow is shipped with SAP NetWeaver MDM and is a module consisting of a sequence of steps that
are carried out for one or more master data records. When master data is created, it very often requires review
and approval processes and MDM's workflow capabilities facilitate these processes.
MDM Workflow's design time environment is based on a Microsoft Visio plug-in that facilitates modeling the
workflows logic. You can create a flow diagram using an MDM-specific set of steps as shown in the diagram
below:.
Example:
The runtime environment is a Workflow tab within the MDM Data Manager client of MDM. Assigned users carry
out the steps of the workflow. For example, a user adds records to a workflow and launches the workflow as a
job. Each job consists of the records that move through each step of the workflow as a series of tasks, which
eventually show up in the user's inbound box for processing.
Integration of UWL and MDM Workflow

Integrating the UWL functionality with MDM Workflow enables users to access their MDM tasks from the UWL
inbox. MDM iViews (or MDM Web Dynpro Components as of MDM 7.1 SP07), enables SAP NetWeaver Portal
users to view the tasks/jobs associated with MDM repository records.
In this guide we show you how to configure the delivered MDM UWL configuration file as well as the MDM
standard iViews or MDM Web Dynpro components so that they integrate and work with MDM Workflow in the
portal.
For more information about UWL, see SAP Help Portal at http://help.sap.com/netweaver choose
your SAP NetWeaver release and search for SAP NetWeaver Portal Universal Worklist.
For more information about MDM Workflow, see SAP Help Portal at http://help.sap.com/nwmdm71
SAP NetWeaver Master Data Management 7.1 System Administration and Maintenance Information
MDM Data Manager Reference Guide MDM Workflows.
For more information about MDM Portal iViews and MDM Web Dynpro Components, see the following
guides located on SAP Help Portal at http://help.sap.com/nwmdm71 SAP NetWeaver Master Data
Management 7.1:
MDM Portal Content Development Guide
MDM Web Dynpro Components Reference Guide
December 2013
1.2
Business Scenario
The following process describes a typical business scenario that includes integrating UWL and MDM Workflow
with MDM iViews and MDM Web Dynpro components in the portal:
P r o...
The workflow owner creates a new (empty) workflow in UWL by choosing Create Job on the UWL user
interface.
A portal user selects records in a preconfigured MDM Result Set iView or MDM Web Dynpro component
in the portal and adds these records to the empty workflow job.
Depending on the design time settings in the MDM Data Manager client, the MDM Workflow is launched
either manually or automatically.
Once the MDM Workflow is launched, a workflow step appears in the UWL inbox of the person who will
be modifying the record (the modifier).
The modifier chooses Show Record Details on the UWL user interface and a Result Set (iView or Web
Dynpro component) displays the workflow records that can be edited.
The modifier updates the records and chooses a button (for example, Send for Approval) to move the
workflow to the Approval step.
A workflow step appears in the UWL inbox of the person who must approve the record (the approver).
The approver chooses Show Record Details and the records are displayed in a Result Set (iView or Web
Dynpro component).
The approver reviews the record changes, approves the changes, and moves the workflow to the Stop
step. If the approver does not approve the changes he/she changes the status of the record to Not
Approved and chooses Send Previous to return the record to the modifier for further changes.
Configuring the Universal Worklist (UWL)
This part of the guide is divided into four sections:
A list of prerequisites that must be set up in order to integrate UWL, MDM Workflow, and MDM standard
iViews or MDM Web Dynpro components in the portal.
For more information, see Prerequisites on page 3.
General overview of the user interface of the UWL in an MDM implementation focusing on subviews,
buttons, and MDM-specific attributes. We also explain how to display MDM record details on the UWL
user interface so that portal users can identify the records that are linked to their workflow jobs or
tasks.
For more information, see The Universal Worklist (UWL) User Interface on page 4.
In the third and fourth sections we provide a step by step explanation of how to configure the delivered
UWL XML configuration file for both Portal iView and Web Dynpro component implementations.
For more information on how to configure the mdm.xml file for Portal iViews, see Configuring
the mdm.xml file for MDM Portal iViews on page 12.
For more information on how to configure the mdm.xml file for Web Dynpro components, see
Configuring the mdm.xml file for MDM Web Dynpro Components on page 19.
December 2013
2.1
Prerequisites
Recommendation
When UWL is initially installed, a single UWL is defined. One of the configuration properties is the
Configuration Groups property, which is left blank. The default behavior of the blank setting
is that when a user logs on to UWL, it tries to log the user on to all registered backend systems.
When a large number of systems are accessed during log on, the overall portal load increases
substantially. Also, the user receives error messages from those backend systems that have no
user account for the particular UWL user.
For more information on how to configure the UWL for large system landscapes, see Registering
the Provider Systems.
To enable integration of UWL, MDM Workflow with MDM Portal iViews or MDM Web Dynpro components,
ensure that the following prerequisites are instituted:
You have installed one of the following supported SAP NetWeaver releases, together with SAP
NetWeaver Application Server (AS) Java:
SAP NetWeaver 7.0
SAP NetWeaver Composition Environment (CE) 7.11 SP04 (or higher)
SAP NetWeaver Composition Environment (CE) 7.2 SP03 (or higher)
SAP NetWeaver 7.3
The following software components have been deployed on your SAP NetWeaver Application Server
Java:
For Portal iViews:
Portal Content for NW 7.0 instance that includes the following software components:
BP MDM APPLICATON 7.1
BP MDM TECHNOLOGY 7.1
MDM Java API
Portal Content for NW 7.3 instance that includes the following software components:
BP MDM APPLICATON 7.1 7.3
BP MDM TECHNOLOGY 7.1 7.3
MDM EP 7.1 7.11 (UWL software component that contains the UWL connector)
MDM Java API and MDM CONNECTOR 7.1 7.11
For Web Dynpro Components:

Java WebDynpro for NW 7.11 instance that includes the following software components for SAP
NetWeaver CE 7.11 and higher:
MDM Java WD Framework 7.1 7.11
MDM EP 7.1 7.11 (UWL software component that contains the UWL connector)
MDM Java API and MDM CONNECTOR 7.1 7.11
Deployment of the MDM EP 7.1 7.11 automatically creates the MDM UWL configuration called, mdm.
December 2013
Troubleshooting tip for SAP NetWeaver 7.0

If mdm and MdmUwlConnector configurations are not available, we recommend that you carry out the
following procedure:
a. Refresh the com.sap.netweaver.bc.uwl application by choosing the following path:
System Administration Support Portal Runtime Application Console. You will see the
com.sap.mdm.uwl dependent application.
b. Check if the configuration name, mdm exists as follows:
i.
Navigate to System Administration System Configuration Universal Worklist &

Workflow Universal Worklist Administration.
ii.
Scroll down the main page and choose Click to Manage Item Types and View Definitions.
The Universal Worklist Configuration Content pane opens.
iii.
In the Current Configurations tab, you should see the MDM configuration file called mdm.
c. Check that the MdmUwlConnector connector is visible in the Connector Type dropdown list
as follows:
Navigate to System Administration System Configuration Universal Worklist & Workflow
Universal Worklist Administration. The Universal Worklist Systems pane opens. In the
Connector Type field, you should see MdmUwlConnector.
Recommendation
If the above configuration name and connector type are not available, see SAP
Note 1437590.
The SAP MD M 7.1 so ftwar e comp one nts ( MDM Ser ver , MD M Da ta Man ager , a nd MDM Co nsol e) ar e inst alled .
SAP MDM 7.1 software components (MDM Server, MDM Data Manager, and MDM Console) are
installed.
Your custom MDM repository is available.
Note
If you are using the default configuration for an iView implementation, then the Business Partner
and Product standard repositories must be available.
If you are using the default configuration for a Web Dynpro component implementation, then
the Product standard repository must be available.
You have verified that the workflow template and the workflow scenario are operational in the MDM
Data Manager.
You have prior knowledge of UWL and MDM Workflow.
2.2
For more information about UWL, see SAP Help Portal at http://help.sap.com/netweaver
choose your SAP NetWeaver release and search for SAP NetWeaver Portal Universal
Worklist.
For more information about MDM Workflow, see SAP Help Portal at
http://help.sap.com/nwmdm71 SAP NetWeaver Master Data Management 7.1 System
Administration and Maintenance Information MDM Data Manager Reference Guide . Read
the chapter called MDM Workflows.
The Universal Worklist (UWL) User Interface
When you access the UWL, depending on your configuration, the following tabs (navigation controls) are
visible on the UWL user interface: Tasks, Alerts, Notifications, SAPoffice Mails, and Tracking).
In an MDM implementation, only the Tasks tab is relevant. From the Tasks tab, you can select and navigate
between various subviews. The buttons that appear on the UWL interface depend on the subview that you
select.
December 2013
2.2.1
Subviews
Subviews enable you to select and navigate between different views.

In an MDM implementation, from the Tasks tab, you can choose one of the following available subviews from
the dropdown list:
My Open MDM Jobs
My Open MDM Tasks
Completed MDM Tasks
2.2.2
UWL Buttons
In an MDM implementation, the buttons on the user interface of the UWL depend on the following:
The MDM workflow step

The buttons dynamically reflect the actions according to the MDM workflow step. For example, an
Approve button would only be visible for an Approval workflow step.
The configuration of the UWL XML configuration file

All or some buttons can be enabled or disabled when configuring the UWL XML configuration file.
For more information about UWL, see SAP Help Portal at http://help.sap.com/netweaver
choose your SAP NetWeaver release and search for SAP NetWeaver Portal Universal
Worklist.
For more information about MDM Workflow, see SAP Help Portal at
http://help.sap.com/nwmdm71 SAP NetWeaver Master Data Management 7.1 System
Administration and Maintenance Information MDM Data Manager Reference Guide. Read the
chapter called MDM Workflows.
For more information on how to configure the UWL XML configuration file, see Configuring the
Universal Worklist XML File on page 10.
The subview that you have selected

You can only see the buttons that are applicable for the current subview. For example, if the current
subview is My Open MDM Jobs, you see the Launch and Add/Remove Records buttons, but you do not
see the Show Record Details button.
The following table shows which MDM-relevant buttons appear on the user interface of the UWL for the
different subviews:
Button
Subview
Action
Launch
My Open
MDM Jobs
Launches the MDM workflow job
Add/Remove
Records
My Open
MDM Jobs
Opens a popup window where you can add records to or remove records from
a workflow job
Delete
My Open
MDM Jobs
Deletes a selected job or task
December 2013
Button
Subview
Action
My Open
MDM Tasks
Completed
MDM Tasks
History
My Open
MDM Tasks
Opens a popup window showing the transaction log of the MDM workflow
Completed
MDM Tasks
Show Record
Details
My Open
MDM Tasks
Completed
MDM Tasks
Opens a popup window that displays records belonging to a workflow job or

task.
Note
There are two ways in which a user can view the records in a workflow job or
task:
Choosing the Show Record Details button. The advantages are:
The popup window that opens can be configured in the UWL

configuration XML file to be role-based.
Specific popup iViews or Web Dynpro components can be

configured for each step of a workflow
Placing a Result Set iView or Web Dynpro component on the same page
as the UWL.
P lacing a n MD M Resul t Set iView on the s ame pa ge as the UW L
When you select a row in the UWL, it automatically raises an

itemSelected portal event. The MDM Result Set iView or Web
Dynpro component displays the records for the corresponding Job ID
selected in the UWL.
Assume
Next Step
My Open
MDM Tasks
Allows the user to assume control of a selected MDM workflow task.
My Open
MDM Tasks
Sends a workflow task to the next step. A Next Step of Workflow popup
window opens showing what the next step is and the users who have to carry
out these steps.
For more information, see MDM Data Manager Reference Guide MDM
Workflows Executing Workflow Jobs.
Recommendation
For portal iViews we recommend that you change the default value of the
Display only the active MDM workflow actions property to
Yes. In this way, only the active workflow actions are displayed in the Next
Step of Workflow popup window.
To locate the Next Step of Workflow iView in the portal, carry out the following
steps:
...
December 2013
1.
Log on to the portal as a content administrator.
2.
In the portal, navigate to Content Administration Portal Content

Management. The Portal Content Studio opens.
3.
In the Portal Catalog, navigate to Portal Content Content Provided by

SAP specialist MDM Application iViews Next Step of
Workflow.
Button
Subview
Action
Create Job
(top right
hand corner)
All subviews
Opens a popup window where the portal user can select a workflow template
and create an empty MDM workflow job.
For more information, see Creating a New Workflow in the UWL on page 27.
If there is not at least one MDM workflow item in the UWL, the Create Job
button is not visible. This is default UWL behavior.
Recommendation
To enable the Create Job button to always appear on the UWL
user interface, add an Action to the currently uploaded XML
configuration that contains the following Views:
DefaultView
AllItemsView
WorkItemsCompletedView
These Views contain the tag Action reference,

com.sap.mdm.createJob.
2.2.3
Personalizing the UWL View
You can personalize the UWL user interface by selecting any display attributes in the dropdown list from the
Personalize View menu these display attributes appear as columns on the UWL user interface.
Apart from the generic UWL columns, the following MDM-specific display attributes are included in the MDM
XML configuration file that is delivered as part of the MDM portal content:
Step Name
Step ID
MDM Status
Records
Job ID
User Names
Workflow Table
Diagram showing some generic UWL columns and some MDM-specific columns
Note
In the Records column (a generic UWL column), you can configure the UWL to show the display
value of the linked records of a workflow job or task.
For more information, see Displaying Details about MDM Linked Records in UWL on page 8.
Note
In the Sent column, the timestamp can be seen in a tool tip.
December 2013
2.2.4
Displaying Details about MDM Linked Records in UWL
The UWL is designed to display work items (for example, MDM workflow tasks and jobs) including details
about these work items (for example, task ID, start date, end date, and so on). There is no meaningful
information pertaining to the MDM record or records that are linked to each work item.
Use Case
A user needs to be able to determine at a single glance which record or records they need to update in the
listed jobs or tasks in the UWL.
To show which MDM records are linked to a specific workflow job or task in the UWL, configure the system
object property, Workflow with Tables as follows:
1.
Enter the <tableCode> followed by ~<number>, where <number> represents the number of
records to display in the UWL for the workflow jobs of a specific MDM table.
For example: Products~2
If you enter only the table code, or the table code followed by ~0, the Record Counter displays the
number of records found in the search but no records are displayed.
2.
To enable multiple tables for a workflow, enter each <tableCode> separated by a comma.
For example: Products~2, Vendors~3
Example
Ten MDM records are linked to a job:
If you enter only the table code, or the table code followed by ~0, the Record Counter displays
the number 10 indicating that ten records were found in the search (the actual records are not
displayed).
If you enter the table code followed by any other number (for example, <tableCode>~6), the
Record Counter displays [6/10] indicating that10 records were found in the search and for 6
out of the 10 linked records, the actual display values appear in the Workflow Records column of
the UWL.
For more information, see SAP Help Portal at http://help.sap.com/nwmdm71 SAP NetWeaver Master Data
Management 7.1 Integration of SAP Components with MDM MDM Portal Content Development Guide .
Read the chapter called Configuring a System Object.
CAUTION
Due to performance and user interface usability issues, we do not recommend that you
configure this property to more than 10 displayed values.
The screen captures below show the configuration of the Workflow with Tables property during
design time and runtime.
Design Time (System Object Property Editor)
December 2013
Runtime (user interface of UWL)
Note
You can also show details of a record by placing an MDM Result Set iView or Web Dynpro
component on the same portal page as the UWL. However, this option only lists the MDM
records linked to a single, selected workflow item. You would need to select each workflow item
in the UWL to see which records are linked to it.
December 2013
2.3
2.3.1
Configuring the Universal Worklist XML File

Background
Delivered portal content supports both MDM Portal iViews (iViews) and MDM Web Dynpro components (WD
components) and includes a preconfigured UWL XML configuration file called mdm.xml.
For Portal iViews

The delivered mdm.xml file references both the Business Partners (BuPa) and the Products MDM
repositories. As a result, the delivered mdm.xml file contains two similar configurations, each referencing one
of these repositories. You can also configure the delivered mdm.xml file to reference a custom repository.
For more information on how to configure the mdm.xml file for iViews, see Configuring the mdm.xml file for
MDM Portal iViews on page 12.
The following diagram shows the mdm.xml file referencing both shipped repositories;
BuPa.MDM_BUSINESS_PARTNERS and Prod.MDM_PRODUCTS.
For Web Dynpro Components

By default, the delivered mdm.xml file references only the Prod.MDM_PRODUCTS repository (see the
diagram of the mdm.xml configuration below). However you can configure the delivered mdm.xml file to
reference a custom repository by replacing the Prod.MDM_PRODUCTS repository name with the custom
repository name.
For more information on how to configure the mdm.xml file for Web Dynpro components, see Configuring the
mdm.xml file for MDM Web Dynpro Components on page 19.
December 2013
10
Note
In the MDM Data Manager, before you delete a job or task in a workflow, you can check in all
records that have been checked out for editing. A popup window appears and you can select the
preferred action: Yes to check in, No to roll back, and Cancel to cancel the delete operation.
A similar feature is now available in the UWL Result Set iView or the UWL Result Set Web Dynpro
component, but the action is automatic. All records that were previously checked out for editing
are automatically rolled back before the job or task is deleted.
Note
For technical support of the MDM UWL configuration, use the MDM-FN-TC OSS component.
2.3.2
What is the mdm.xml file?
The mdm.xml file is a standard UWL XML structure. Originally the mdm.xml file contained elements for
iViews only. As of MDM 7.1 SP07, the mdm.xml file also includes elements for Web Dynpro components. By
default, only the iView related elements are active and the section of the XML structure pertaining to Web
Dynpro components is commented out.
The structure of the new mdm.xml file is divided up into segments. In order to facilitate referencing these
segments in our procedure, we will call them segment 1, segment 2, and segment 3.
Segment 1
This is the  segment of the XML file and differs from the original XML file that was supplied
with iViews in that it only includes two elements Actions and Item Types; the Views element is
excluded.
Action
In the Action element, we define what actions a user can carry out in a view for the View and Item
Type elements in the UWL XML structure. An Action element is often visualized as a button on the
December 2013
11
user interface of the UWL (depending on the job or task selected and on the value of the Item Type
element in the XML configuration), but can also be visualized as a menu entry.
For more information about UWL Action elements, see SAP Help Portal at
http://help.sap.com/netweaver choose your SAP NetWeaver release and search for SAP NetWeaver
Portal Configuring the Universal Worklist Configuration DTD Action.
The following are examples of Action elements that are available in the MDM UWL structure:
nextStep
showHistory
createJob
showDetails
Item Type
In the Item Type element we define the specific type of workflow item and how it behaves. For
example, you can define which page is launched from the UWL on which users can perform their tasks.
The following Item Type elements are available in the UWL XML structure:
jobs maps to all unlaunched MDM workflows
tasks maps to all launched MDM workflows
completedtask maps to completed jobs
Segment 2
This is the Web Dynpro component segment of the XML structure and is displayed as .
b. Uncomment Segment 2 which is the Web Dynpro segment of the XML structure by removing
the tags .
c. Since segment 3 is active for both iViews and Web Dynpro components, do not change
anything.
December 2013
19
5.
Configure the XML as follows (similar to the iView customized XML):

a. Change the following properties so that the showDetails action references the standard Web
Dynpro components:
WebDynproApplication
Replace the reference to the Master Application Utility with the custom application
name.
WebDynproDeployableObject
Replace the value of the Master Application Utility with the custom application's
deployable object path.
DynamicParameter
Replace the parameters of the Master Application Utility with the parameters of the
custom application.
Note
In the shipped Web Dynpro content, we use the Master Application Utility to check the
user's configured MDM Web Dynpro components. The custom application's parameters
eventually replace those of the Master Application Utility.
If the user wishes to use the URL parameters for the delivered Master Application Utility,
the property values are valid for the DynamicParameter property and do not have to
be changed.
For more information, see SAP Help Portal at http://help.sap.com/nwmdm71 SAP
NetWeaver Master Data Management 7.1 Development Information MDM Web
Dynpro Components: Reference Guide . Read the chapter called Master Application Utility
for Viewing Configured Components.
b. Replace the SystemAliasName and ProductTableCode properties with the custom
application's system alias and MDM workflow table code (correspondingly) for
completedtask, job and task Item Types. The naming convention is:
uwl.task.mdm.jobs.<System Alias>.<table code>.
December 2013
20
For example:
c. To add records to a job, in the jobs Item Type, change the three Web Dynpro component
properties (shown in the example below) of the addRecordsToJob action.
d. Change the default mode of the Result Set iView. This step is optional. There are two modes in
which you can view the MDM Workflow Result Set iView:
result_set mode, which displays all MDM records from the repository
view_task mode, which only displays the MDM records linked to the job or task
For more details and examples of the two view modes, see Configuring the mdm.xml file for
MDM Portal iViews Step 3: Create a Custom XML File step 8e on page 17.
6.
We recommend that you validate your customized XML file using an XML editor (for example XML Spy)
by referencing the standard UWL DTD schema file.
Note
The uwl_configuration.dtd file can be downloaded from the Current Configuration tab
by choosing Download DTD (at the bottom of the screen).
December 2013
21
7.
When you have completed the configuration of the mdm_custom.xml file, add it to the
mdm_custom.zip file.
Step 4: Upload the custom mdm_custom.zip configuration file

8.
For more information, see Configuring the mdm.xml file for MDM Portal iViews Upload the custom
mdm.custom.zip configuration file on page 18.
Step 5: Clear the UWL cache (optional)

9.
For more information, see Configuring the mdm.xml file for MDM Portal iViews Clear the UWL Cache
on page 18.
Step 6: Check that the UWL displays the MDM workflows for the custom repository
10.
For more information, see Configuring the mdm.xml file for MDM Portal iViews Check that the UWL
displays the MDM workflows for the custom repository on page 19.
Configuring the Result Set
To display MDM records of an MDM workflow item in the UWL as a Result Set iView or Web Dynpro
component, you must create at least one iView or Web Dynpro component and reference it from the UWL.
In an actual scenario, you would configure more than one Result Set iView or Web Dynpro component (and/or
page) for the following reasons:
You may need different Result Set iViews or Web Dynpro components for different Item Type
elements (tasks, jobs, or completed tasks). For example, a Result Set generated from the UWL Add to
Job button (jobs Item Type), would differ from a Result Set popup window generated from a UWL
Show Details button (tasks Item Type).
For more information, see Item Type on page 12.
This approach is implemented in the standard delivered configuration file, where each Item Type has
already been configured to reference a different PCD path of the Result Set applicable to a particular
use. For example, a Result Set used for adding or removing records from unlaunched jobs, or a Result
Set used for showing the records of a workflow task.
You may need different popup Result Set iViews for different roles and for different groups respectively.
Note
Not applicable for MDM Web Dynpro components.
For more information, see Role-Based iView Launcher and Group-Based iView Launcher respectively on
page 30.
You would need different popup Result Set iViews or Web Dynpro components for different steps of a
workflow.
For more information, see Step-Based Item Types on page 30.
December 2013
22
In this section we explain how to reference a Result Set from the UWL and how to configure the Result Set to
show the MDM records in a workflow job.
Step 1: Create and configure at least one MDM Result Set iView or MDM Web
Dynpro component to reference from the UWL
Configuring the Result Set iView
1.
Create a standard MDM Result Set iView.

For more information, see http://service.sap.com/installmdm71 MDM Portal Content
Development Guide Creating a Result Set iView.
2.
In the context menu of the Result Set iView, choose Open.
3.
In the iView Property Editor, select Customization from the Property Category dropdown list.
4.
Set the following Workflow Result Set iView customization options according to the action button on the
UWL:
Customization
Property
Description
UWL Action
Button
Add/Remove
Records
UWL Action
Button
Show Record
Details
Default
Is Add to
Job Enabled?
If enabled, the Add to

Job button appears on
the UI of the Result Set
iView.
Yes
No
No
Is Remove
From Job
Enabled?
If enabled, the Remove

from Job button appears
on the UI of the Result
Set iView.
Yes
No
No
Is Resultset
Mode
Enabled?
If disabled, the user sees

only the records related
to a job.
Yes
No
Yes
Is ViewTask
Mode
Enabled?
If disabled, the user

cannot view the records
of a workflow.
Yes
Yes
Yes
Is Workflow
Enabled?
If enabled, the workflow

context menu is visible
on the Result Set iView.
No
No
No
Is Refresh
UWL Enabled?
If enabled, the system

triggers a UWL refresh
upon actions done in the
Result Set iView that are
related to UWL (for
example, Add to Job,
Remove from Job, and
so on)
Yes
No
No
December 2013
23
5.
From the Property Category dropdown list, select Show All

Show All
Property
Description
UWL Action
Button
Add/Remove
Records
UWL Action
Button
Show Record
Details
Default
Parameters
to Pass
from Page
Request
Enables the current Result

Set iView subscription to a
Enter an asterisk
(*) next to this
property
Enter an asterisk
(*) next to this
property
Empty
ViewTaskRecordsHand
ler URL event. If the
event is an EPCF
viewTask event, this
property is not required.
Recommendation
6.
Add the Result Set iView that you have created to your portal page as a delta link.
Configuring the Web Dynpro Component

1.
Create a standard MDM Web Dynpro Result Set component.

For more information, see SAP Help Portal at http://help.sap.com/nwmdm71 SAP NetWeaver
Master Data Management 7.1 Development Information MDM Web Dynpro Components:
Reference Guide . Read the chapter called Configuring a Result Set Web Dynpro Component.
2.
In the Component Properties tab (step 2 of the wizard), set the following MDM Workflow and UWL
setting options according to the action button on the UWL.
The table below shows the specific workflow configuration properties and how they should be set for
each Result Set WD component:
Customization Property
Description
Default
Enable Add to
Job
If enabled, the Add to Job button appears on the

user interface of the Web Dynpro Result Set
Component.
False
Enable Remove
From Job
If enabled, the Remove from Job button appears on

the user interface of the Result Set Web Dynpro
Component.
False
Enable View Task
If disabled, the user cannot view the records of a

workflow.
False
Step 2: Locate the PCD address of the portal page

1.
In the Portal Catalog, add the page to a portal role as a delta link.
2.
Open the portal role for editing, and select the page with the MDM iViews.
3.
Choose Properties to open the Property Editor.
4.
Select Information from the Property Category dropdown list.
5.
Locate the PCD Location property to obtain the PCD address.
December 2013
24
Note
For a launched workflow, an MDM Result Set automatically supports the following steps:
Approve
Disapprove
Split Job
Validation
For example, when a given workflow reaches an Approve step, an MDM Result Set iView or Web
Dynpro component is launched with the Approve or Disapprove action buttons. A Split to Job
button is only shown if the Result Set iView was launched from an Approve step in MDM UWL.
CAUTION
If there are too many records in a Result Set iView or Web Dynpro component, loading a
workflow takes a long time because the system attempts to load all records on one page (paging
is not supported).
Step 3: Configure the Result Set to display the records of a UWL MDM Workflow
Item
MDM records of a UWL MDM workflow item can be displayed in a Result Set in one of the following ways:
Using the Add/Remove Record or the Show Record Details buttons

A user chooses either the Add/Remove Record or the Show Record Details actions from the UWL user
interface to launch a popup Result Set.
...
Placing the MDM Result Set on the Same Page as the UWL
If you place a Result Set iView or Web Dynpro Result Set component on the same page as the UWL, the
Result Set displays the records for the corresponding Job ID selected in the UWL. Optionally, you can
configure the Result Set to show only workflow records and disable all other functions.
Note
The Result Set iView /WD component and the UWL must have the same System Alias.
Note
The Web Dynpro Result Set component and the UWL must have the same connection
properties (in other words, the same MDM server, repository name referenced from the
Destination, and the portal system object
December 2013
25
Selecting a row in the UWL

automatically raises an
itemselected portal event.
UWL
Job ID
Subject
User Name
Due
101
Workflow with Validation Process Portal User
July 8
222
Workflow with Validation Process Portal User
July 8
Result Set Listener for UWL on Row Select

Workflow with Validation [101] (3) Step: Process
Record 1
Record 2
Record 3
Records corresponding
to the workflow job
selected in the UWL
The header displays the selected

job/task ID, number of linked
records, and step.
The MDM Web Dynpro Result Set
component displays the linked
MDM records for the job or task.
Note
The UWL raises the event at given intervals even if no record is selected in the UWL.
December 2013
26
End User Tips and Guidelines
4.1
Creating a New Workflow in the UWL
You can create a new, empty workflow in the UWL and later add records to the workflow in the MDM Result Set
iView or Web Dynpro component. (This option is not supported in MDM Data Manager).
Prerequisites
You have configured the UWL XML configuration file.

For more information, see Configuring the Universal Worklist XML File on page 10.
You have created an MDM Result Set iView or MDM Result Set Web Dynpro component.
Adding Records to a Workflow Job

...
...
1.
From the UWL user interface, choose the Create Job button to open a popup window.
Note
In the popup window you see that all valid workflow templates are defined as follows:
The trigger action is defined as manual in the MDM Data Manager
The workflow is active
All the valid templates are grouped under the relevant System Object MDM workow-enabled Table
Code template as follows:
For example:
System
Table Code
Valid Template 1
Valid Template 2
2.
Select the valid template. A message appears that the workflow job has been created.
For example, Job 12345 created in MDM Server<XXX>, repository<YYY>, table
<products> using Workflow Template <WWW>
3.
Close the popup window and refresh the UWL.
4.
Select the new workflow job and choose Add/Remove Records. A popup window shows that no records
are linked to the job.
5.
Select the records you want to add to the job.
6.
Choose Add to Job <number>. For example, Add to Job<12345>.
December 2013
27
Portal Configurations
There are some configurations that can be implemented in the portal to determine what portal content is
available to portal users. These include:
Defining roles for portal users

You can limit the access of portal users to the MDM repository workflow by assigning them a portal role
for the UWL system. When an MDM Workflow is executed in the portal, you may want to implement the
workflow so that portal users only see the tasks that they are required to work on. This configuration
can be used for Portal iViews and Web Dynpro components.
For more information, see Portal Roles on page 28.
Note
For MDM portal iViews you can also achieve this scenario by using the UWL
MDMIViewLauncher to launch different popup MDM Result Set iViews or pages depending
on the users Portal role and Portal group assignments.
For more information, see UWL iView Launcher on page 30.
Launching dedicated popup Result Set iViews or Web Dynpro components for each step of a workflow
When a portal user selects the Show Record Details button, a popup window can be launched
depending on the workflow step name the same user who is responsible for different steps in the
workflow, will see different popup Result Sets.
For example, the Show Record Details button can launch Portal Page 1 for a Create step in the workflow
and Portal Page 2 for an Approval step.
For more information, see Step-Based Item Types on page 30.
These features are shipped with the standard MDM software, but the actual configuration is NOT. Therefore
configuration steps are required by the portal administrator according to the customer's requirements.
In the following sections we explain how to carry out these configurations.
5.1.1
Portal Roles
User access to portal content is determined by role definitions. You can limit the access of portal users to the
MDM repository workflow by assigning them a portal role to the UWL system.
...
1.
Navigate to User Administration Identity Management.
2.
Enter the following search criteria: Role Portal Role *mdm* to locate the required MDM role. You
will enter this role name in the User Roles property when configuring the UWL.
December 2013
28
3.
Navigate to System Administration System Configuration Universal Worklist-Administration.

In the User Roles property of the UWL, enter the role name that you have located. Only portal users
assigned to this role will be able to see the MDM repository workflows.
December 2013
29
5.1.2
UWL iView Launcher
The UWL iViewLauncher is an action handler that is used to launch any iView or page in the portal.
For more information, go to the SAP Help Portal, at http://help.sap.com/netweaver and search for
the SAP NetWeaver Portal Administration Guide. Read the chapter called iViewLauncher.
The direct link is: iViewLauncher.
The MDMIViewLauncher is a customized version of the UWL iViewLauncher and is used to launch
different popup iViews or pages according to:
Portal role
For more information, see Role-Based iView Launcher on page 30.
Portal group
For more information, see Group-Based iView Launcher on page 30.
Note
To enable functionality of the MDMIViewLauncher:
The iViewLauncher action handler must be replaced by MDMIViewLauncher in

the XML configuration file (the shipped standard MDM UWL configuration file refers to
the UWL iViewLauncher).
Ensure that the URL of the target iView has the correct syntax (see examples below).
When a portal user chooses the UWLs Show Record Details button, the relevant popup iViews are launched.
Role-Based iView Launcher

To launch a portal role-dependent iView or page from UWL for adding or removing records from unlaunched
jobs, or showing the records of a workflow task, carry out the following steps in the UWL XML configuration
file:
...
1.
Enter the name of the enhanced iView launcher, MDMIViewLauncher instead of the delivered
iViewLauncher.
2.
Enter the correct syntax for the URL of the target iView
For example:
<portalRole1>,<iViewpcdId1>;<portalRole2>,<iViewpcdId2>.
For more information, go to the SAP Developer Network (SDN) at http://sdn.sap.com and search for the How
to Implement the UWL Role Based Master Data Management iView Launcher guide. Read the chapter called
UWL role based iView Launcher.
Group-Based iView Launcher

To launch a user group-dependent iView or page from the UWL for adding or removing records from
unlaunched jobs, or showing the records of a workflow task in the UWL XML configuration file:
...
1.
Enter the name of the enhanced iView launcher, MDMIViewLauncher instead of the delivered
iViewLauncher.
2.
Enter the correct syntax for the URL of the target iView
For example:
<portalUserGroup1>,<iViewpcdId1>;<portalUserGroup2>,<iViewpcdId2>
Step-Based Item Types

When a portal user chooses the Show Record Details button on the UWL user interface, a popup iView or Web
Dynpro component is launched. Using step-based Item Type elements, you can launch a dedicated popup
iView or Web Dynpro component for each step of a workflow the same user, who is responsible for different
December 2013
30
steps in the workflow, sees different popup Result Sets for each step. For example, ResultSet1 can be
launched for a Create step in the workflow and Result Set2 can be launched for an Approval step in the
workflow.
To launch step-based popup Result Sets, you need to create an Item Type for each workflow step.
The shipped Item Type for a task has the following structure:
uwl.task.mdm.tasks.<MDM_Alias_name>.<MDM_table_code>
For example,
uwl.task.mdm.tasks.SAP_MDM_Repository_BuPa.MDM_BUSINESS_PARTNERS
To create step-based Item Type elements, add the workflow template name and the step ID as a suffix to
the above notation as follows:
uwl.task.mdm.tasks.<MDM_Alias_name>.<MDM_table_code>.<MDM
workflow_template_name>.<MDM_workflow_template_step_Id>
Example
An MDM Workflow template, WFTemplate1 consists of two workflow steps, WFStepID1 and WFStepID2
(these are the step IDs).
Tip
To retrieve the ID of a step, see How to Identify MDM Workflow Step IDs on page 32.
The configured UWL step-based Item Type elements appear as follows in the XML structure:
uwl.task.mdm.tasks.SAP_MDM_Repository_BuPa.MDM_BUSINESS_PARTNERS.
WFTemplate1.WFStepID1
uwl.task.mdm.tasks.SAP_MDM_Repository_BuPa.MDM_BUSINESS_PARTNERS.
WFTemplate1.WFStepID2
The following XML configuration shows an example of one of the Item Type elements:
- <ItemType
name="uwl.task.mdm.tasks.SAP_MDM_Repository_BuPa.BUSINESS_PARTNERS.WFTempla
te1.2" connector="MdmUwlConnector" defaultView="MdmViewTasks"
defaultAction="com.sap.mdm.bupa.showDetails" executionMode="default">
- 
- <Actions>
<Action reference="com.sap.mdm.showHistory" groupAction="no"
returnToDetailViewAllowed="yes" launchInNewWindow="no" />
<Action reference="com.sap.mdm.nextStep" groupAction="no"
<Action reference="com.sap.mdm.bupa.showDetails3" groupAction="no"
<Action reference="com.sap.mdm.priorityLow" groupAction="no"
<Action reference="com.sap.mdm.priorityNormal" groupAction="no"
<Action reference="com.sap.mdm.priorityHigh" groupAction="no"
<Action reference="com.sap.mdm.priorityVeryHigh" groupAction="no"
</Actions>
December 2013
31
</ItemType>
CAUTION
Be sure to use the MDM workflow template name and not the workflow template code. In our
example WFTemplate1 represents the MDM workflow template name.
Workflow template names are case sensitive and cannot include any spaces.
How to Identify MDM Workflow Step IDs

Before you can create a step-based Item Type, you must first identify the step IDs of each step of the
workflow. As you can see in the screen capture below, workflow step IDs are not visible in the workflow Visio
diagram in MDM Data Manager.
December 2013
32
You can only see a specific step ID in the Step ID column of the UWL.
...
1.
To retrieve the step IDs, simulate each step of the workflow. As you move through the different steps,
the UWL displays the step ID in the Step ID column.
The Step ID column is added to the UWL using the UWL Personalize View options. For more
information, see Personalizing the UWL View on page 7.
2.
In the XML configuration file, enter the workflow step ID for each step of the task that you want to view
in a popup window.
CAUTION
For a specific MDM workflow template, you cannot have both step-based Item Types and
generic Item Types. The UWL will interpret an MDM workflow as belonging to both Item
Types and you will end up having duplicate buttons at runtime. Therefore be sure to remove all
the other generic Item Types.
Note
Only configure steps that need to be visible in the UWL runtime with a corresponding Item
Type. For example, you would not configure an Item Type for a syndication step.
December 2013
33
www.sdn.sap.com/irj/sdn/howtoguides

How To Work With UWL and MDM Workflows in The Portal

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

How To Work With UWL and MDM Workflows in The Portal

Transféré par

Droits d'auteur :

Formats disponibles

SAP NetWeaver

How To Work with UWL and MDM

Copyright 2013 SAP AG. All rights reserved.

These materials are subject to change without notice.

Update of links to SAP MDM Documentation Page.

As of MDM 7.1 SP07, MDM Workflow in the Universal Worklist is

A recommendation has been added on how to configure the UWL for

This guide has been enhanced with special emphasis on customizing

First official release of this guide

Words or characters quoted

Emphasized words or phrases

File and directory names and

User entry texts. These are

Variable user entry. Angle

Keys on the keyboard, for

How To Work with UWL and MDM Workflows in the Portal

Business Scenario .......................................................................................................................... 2

Configuring the Universal Worklist (UWL) ..................................................................................... 2

The Universal Worklist (UWL) User Interface .............................................................................. 4

Personalizing the UWL View ............................................................................................ 7

Displaying Details about MDM Linked Records in UWL................................................ 8

Configuring the Universal Worklist XML File .............................................................................. 10

What is the mdm.xml file? ............................................................................................... 11

Configuring the mdm.xml file for MDM Portal iViews.................................................. 12

Configuring the Result Set .......................................................................................................... 22

End User Tips and Guidelines ...................................................................................................... 27

Creating a New Workflow in the UWL ......................................................................................... 27

Portal Configurations .................................................................................................................. 28

Portal Roles .....................................................................................................................28

UWL iView Launcher ..................................................................................................... 30

How To Work with UWL and MDM Workflows in the Portal

Universal Worklist (UWL)

SAP NetWeaver MDM Workflow

Integration of UWL and MDM Workflow

MDM Portal Content Development Guide

MDM Web Dynpro Components Reference Guide

How To Work with UWL and MDM Workflows in the Portal

Configuring the Universal Worklist (UWL)

This part of the guide is divided into four sections:

How To Work with UWL and MDM Workflows in the Portal

SAP NetWeaver 7.0

SAP NetWeaver Composition Environment (CE) 7.11 SP04 (or higher)

SAP NetWeaver Composition Environment (CE) 7.2 SP03 (or higher)

SAP NetWeaver 7.3

For Portal iViews:

BP MDM APPLICATON 7.1

BP MDM TECHNOLOGY 7.1

MDM Java API

BP MDM APPLICATON 7.1 7.3

BP MDM TECHNOLOGY 7.1 7.3

MDM Java API and MDM CONNECTOR 7.1 7.11

For Web Dynpro Components:

MDM Java WD Framework 7.1 7.11

MDM Java API and MDM CONNECTOR 7.1 7.11

How To Work with UWL and MDM Workflows in the Portal

Troubleshooting tip for SAP NetWeaver 7.0

Navigate to System Administration System Configuration Universal Worklist &

Your custom MDM repository is available.

You have prior knowledge of UWL and MDM Workflow.

The Universal Worklist (UWL) User Interface

How To Work with UWL and MDM Workflows in the Portal

Subviews enable you to select and navigate between different views.

My Open MDM Jobs