how to work with uwl and mdm workflows in the portal · pdf filesap netweaver how-to guide how...

SAP NetWeaverHow-To Guide

How To Work with UWL and MDMWorkflows 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 ortransmitted in any form or for any purpose without theexpress permission of SAP AG. The information containedherein may be changed without prior notice.

Some software products marketed by SAP AG and itsdistributors contain proprietary software components ofother software vendors.

Microsoft, Windows, Outlook, and PowerPoint areregistered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, ParallelSysplex, 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 aretrademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Readerare either trademarks or registered trademarks of AdobeSystems Incorporated in the United States and/or othercountries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registeredtrademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame,WinFrame, VideoFrame, and MultiWin are trademarks orregistered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks orregistered trademarks of W3C®, World Wide WebConsortium, 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 andimplemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAPNetWeaver, and other SAP products and servicesmentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world.All other product and service names mentioned are thetrademarks of their respective companies. Data containedin 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 affiliatedcompanies ("SAP Group") for informational purposes only,without representation or warranty of any kind, and SAPGroup shall not be liable for errors or omissions withrespect to the materials. The only warranties for SAPGroup products and services are those that are set forth inthe express warranty statements accompanying suchproducts and services, if any. Nothing herein should beconstrued as constituting an additional warranty.

These materials are provided “as is” without a warranty ofany kind, either express or implied, including but notlimited to, the implied warranties of merchantability,fitness for a particular purpose, or non-infringement.

SAP shall not be liable for damages of any kind includingwithout limitation direct, special, indirect, or consequentialdamages that may result from the use of these materials.

SAP does not warrant the accuracy or completeness of theinformation, text, graphics, links or other items containedwithin these materials. SAP has no control over theinformation that you may access through the use of hotlinks contained in these materials and does not endorseyour use of third party web pages nor provide any warrantywhatsoever relating to third party web pages.

SAP NetWeaver “How-to” Guides are intended to simplifythe product implementation. While specific productfeatures and procedures typically are explained in apractical business context, it is not implied that thosefeatures and procedures are the only approach in solving aspecific business problem using SAP NetWeaver. Shouldyou wish to receive additional information, clarification orsupport, please refer to SAP Consulting.

Any software coding and/or code lines / strings (“Code”)included in this documentation are only examples and arenot intended to be used in a productive systemenvironment. The Code is only intended better explain andvisualize the syntax and phrasing rules of certain coding.SAP does not warrant the correctness and completeness ofthe Code given herein, and SAP shall not be liable forerrors or damages caused by the usage of the Code, exceptif such damages were caused by SAP intentionally orgrossly negligent.

Disclaimer

Some components of this product are based on Java™. Anycode change in these components may cause unpredictableand severe malfunctions and is therefore expressivelyprohibited, as is any decompilation of these components.

Any Java™ Source Code delivered with this product is onlyto be used by SAP’s Support Services and may not bemodified or altered in any way.

Document HistoryDocument Version Description

3.2 · Correction: You can only configure a Result Set iView for different rolesand for different groups. This is not relevant for Result Set Web Dynprocomponents.

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 SetiView was launched from an Approve step of a workflow job in MDMUniversal Worklist (UWL).

3.00 · As of MDM 7.1 SP07, MDM Workflow in the Universal Worklist issupported by MDM Portal Content (iViews) and MDM Web DynproComponents. Throughout the course of this guide we have explainedthe configuration options for both implementations includingconfiguration of the delivered mdm.xml configuration file.

· A recommendation has been added on how to configure the UWL forlarge system landscapes.

For more information, see Prerequisites on page 3.

2.00 · This guide has been enhanced with special emphasis on customizingthe delivered XML configuration file and the MDM standard portalcontent.

For more information, see Configuring the Universal Worklist (UWL) onpage 2.

· A new section has been added which covers the configurations that canbe implemented in the portal to determine what portal content isavailable to portal users. These include: Portal Roles, UWL iViewLauncher, and Step-based Item Types.

For more information, see Portal Configurations on page 28.

1.00 First official release of this guide

Typographic ConventionsType Style Description

Example Text Words or characters quotedfrom the screen. These includefield names, screen titles,pushbuttons labels, menunames, menu paths, and menuoptions.

Cross-references to otherdocumentation

Example text Emphasized words or phrasesin body text, graphic titles, andtable titles

Example text File and directory names andtheir paths, messages, names ofvariables and parameters,source text, and names ofinstallation, upgrade anddatabase tools.

Example text User entry texts. These arewords or characters that youenter in the system exactly asthey appear in thedocumentation.

<Exampletext>

Variable user entry. Anglebrackets indicate that youreplace these words andcharacters with appropriateentries to make entries in thesystem.

EXAMPLE TEXT Keys on the keyboard, forexample, F2 or ENTER.

IconsIcon Description

Caution

Note or Important

Example

Recommendation or Tip

How To Work with UWL and MDM Workflows in the Portal

December 2013 1

Table of Contents

1 Overview ........................................................................................................................................ 1

1.1 Introduction ......................................................................................................................................11.2 Business Scenario .......................................................................................................................... 2

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

2.1 Prerequisites ................................................................................................................................... 32.2 The Universal Worklist (UWL) User Interface .............................................................................. 4

2.2.1 Subviews ........................................................................................................................... 52.2.2 UWL Buttons ..................................................................................................................... 52.2.3 Personalizing the UWL View ............................................................................................ 72.2.4 Displaying Details about MDM Linked Records in UWL ................................................ 8

2.3 Configuring the Universal Worklist XML File .............................................................................. 102.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

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

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

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

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

5.1.1 Portal Roles ..................................................................................................................... 285.1.2 UWL iView Launcher ..................................................................................................... 30


December 2013 1

1 Overview

1.1 Introduction

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

SAP NetWeaver MDM WorkflowMDM Workflow is shipped with SAP NetWeaver MDM and is a module consisting of a sequence of steps thatare carried out for one or more master data records. When master data is created, it very often requires reviewand 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 theworkflow’s logic. You can create a flow diagram using an MDM-specific set of steps as shown in the diagrambelow:.

Example:

The runtime environment is a Workflow tab within the MDM Data Manager client of MDM. Assigned users carryout the steps of the workflow. For example, a user adds records to a workflow and launches the workflow as ajob. Each job consists of the records that move through each step of the workflow as a series of tasks, whicheventually show up in the user's inbound box for processing.

Integration of UWL and MDM WorkflowIntegrating the UWL functionality with MDM Workflow enables users to access their MDM tasks from the UWLinbox. MDM iViews (or MDM Web Dynpro Components as of MDM 7.1 SP07), enables SAP NetWeaver Portalusers 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 MDMstandard iViews or MDM Web Dynpro components so that they integrate and work with MDM Workflow in theportal.

· For more information about UWL, see SAP Help Portal at http://help.sap.com/netweaver ® chooseyour 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 followingguides located on SAP Help Portal at http://help.sap.com/nwmdm71 ® SAP NetWeaver Master DataManagement 7.1:

¡ MDM Portal Content Development Guide

¡ MDM Web Dynpro Components Reference Guide

http://help.sap.com/netweaver

http://help.sap.com/saphelp_nw73/helpdata/en/34/585bf950c34f6ab6a35bc3465fb5ba/frameset.htm

http://help.sap.com/nwmdm71



December 2013 2

1.2 Business ScenarioThe following process describes a typical business scenario that includes integrating UWL and MDM Workflowwith MDM iViews and MDM Web Dynpro components in the portal:Pro...

· The workflow owner creates a new (empty) workflow in UWL by choosing Create Job on the UWL userinterface.

· A portal user selects records in a preconfigured MDM Result Set iView or MDM Web Dynpro componentin 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 launchedeither manually or automatically.

· Once the MDM Workflow is launched, a workflow step appears in the UWL inbox of the person who willbe modifying the record (the modifier).

· The modifier chooses Show Record Details on the UWL user interface and a Result Set (iView or WebDynpro 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 theworkflow 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 WebDynpro component).

· The approver reviews the record changes, approves the changes, and moves the workflow to the Stopstep. If the approver does not approve the changes he/she changes the status of the record to NotApproved and chooses Send Previous to return the record to the modifier for further changes.

2 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 standardiViews 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 UWLuser interface so that portal users can identify the records that are linked to their workflow jobs ortasks.

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 deliveredUWL 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 Configuringthe 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, seeConfiguring the mdm.xml file for MDM Web Dynpro Components on page 19.


December 2013 3

2.1 Prerequisites

RecommendationWhen UWL is initially installed, a single UWL is defined. One of the configuration properties is theConfiguration Groups property, which is left blank. The default behavior of the blank settingis 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 increasessubstantially. Also, the user receives error messages from those backend systems that have nouser account for the particular UWL user.

For more information on how to configure the UWL for large system landscapes, see Registeringthe 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 SAPNetWeaver 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 ServerJava:

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

http://help.sap.com/saphelp_nw04/helpdata/en/92/a88931f2dd4631b9e8d530697d89c9/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/92/a88931f2dd4631b9e8d530697d89c9/content.htm


December 2013 4

Troubleshooting tip for SAP NetWeaver 7.0

If mdm and MdmUwlConnector configurations are not available, we recommend that you carry out thefollowing 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 thecom.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 listas follows:

Navigate to System Administration ® System Configuration ® Universal Worklist & Workflow® Universal Worklist Administration. The Universal Worklist Systems pane opens. In theConnector Type field, you should see MdmUwlConnector.

RecommendationIf the above configuration name and connector type are not available, see SAPNote 1437590.

The SAP MD M 7.1 so ftware comp one nts ( MDM Server, MD M Da ta Man ager, a nd MDM Co nsol e) are inst alled .

· SAP MDM 7.1 software components (MDM Server, MDM Data Manager, and MDM Console) areinstalled.

· Your custom MDM repository is available.

NoteIf you are using the default configuration for an iView implementation, then the Business Partnerand Product standard repositories must be available.

If you are using the default configuration for a Web Dynpro component implementation, thenthe Product standard repository must be available.

· You have verified that the workflow template and the workflow scenario are operational in the MDMData Manager.

· You have prior knowledge of UWL and MDM Workflow.

¡ 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 ® UniversalWorklist.

¡ For more information about MDM Workflow, see SAP Help Portal athttp://help.sap.com/nwmdm71 ®SAP NetWeaver Master Data Management 7.1 ® SystemAdministration and Maintenance Information ® MDM Data Manager Reference Guide . Readthe chapter called MDM Workflows.

2.2 The Universal Worklist (UWL) User InterfaceWhen you access the UWL, depending on your configuration, the following tabs (navigation controls) arevisible 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 navigatebetween various subviews. The buttons that appear on the UWL interface depend on the subview that youselect.

https://css.wdf.sap.corp/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=0001437590






December 2013 5

2.2.1 SubviewsSubviews 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 fromthe dropdown list:

· My Open MDM Jobs

· My Open MDM Tasks

· Completed MDM Tasks

2.2.2 UWL ButtonsIn 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, anApprove 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 ® UniversalWorklist.

¡ For more information about MDM Workflow, see SAP Help Portal at ®http://help.sap.com/nwmdm71 ®SAP NetWeaver Master Data Management 7.1 ® SystemAdministration and Maintenance Information ® MDM Data Manager Reference Guide. Read thechapter called MDM Workflows.

¡ For more information on how to configure the UWL XML configuration file, see Configuring theUniversal 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 currentsubview is My Open MDM Jobs, you see the Launch and Add/Remove Records buttons, but you do notsee the Show Record Details button.

The following table shows which MDM-relevant buttons appear on the user interface of the UWL for thedifferent subviews:

Button Subview Action

Launch My OpenMDM Jobs

Launches the MDM workflow job

Add/RemoveRecords

My OpenMDM Jobs

Opens a popup window where you can add records to or remove records froma workflow job

Delete My OpenMDM Jobs

Deletes a selected job or task






December 2013 6


My OpenMDM Tasks

CompletedMDM Tasks

History My OpenMDM Tasks

CompletedMDM Tasks

Opens a popup window showing the transaction log of the MDM workflow

Show RecordDetails

My OpenMDM Tasks

CompletedMDM Tasks

Opens a popup window that displays records belonging to a workflow job ortask.

NoteThere are two ways in which a user can view the records in a workflow job ortask:

· Choosing the Show Record Details button. The advantages are:

¡ The popup window that opens can be configured in the UWLconfiguration XML file to be role-based.

¡ Specific popup iViews or Web Dynpro components can beconfigured for each step of a workflow

· Placing a Result Set iView or Web Dynpro component on the same pageas the UWL.

Placing 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 anitemSelected portal event. The MDM Result Set iView or WebDynpro component displays the records for the corresponding Job IDselected in the UWL.


Assume My OpenMDM Tasks

Allows the user to assume control of a selected MDM workflow task.

For more information, see MDM Data Manager Reference Guide ® MDMWorkflows ® Executing Workflow Jobs.

Next Step My OpenMDM Tasks

Sends a workflow task to the next step. A Next Step of Workflow popupwindow opens showing what the next step is and the users who have to carryout these steps.

Recommendation

For portal iViews we recommend that you change the default value of theDisplay only the active MDM workflow actions property toYes. In this way, only the active workflow actions are displayed in the NextStep of Workflow popup window.

To locate the Next Step of Workflow iView in the portal, carry out the followingsteps:...

1. Log on to the portal as a content administrator.

2. In the portal, navigate to Content Administration ® Portal ContentManagement. The Portal Content Studio opens.

3. In the Portal Catalog, navigate to Portal Content ® Content Provided bySAP ® specialist ® MDM Application ® iViews ® Next Step ofWorkflow.


December 2013 7


Create Job(top righthand corner)

All subviews Opens a popup window where the portal user can select a workflow templateand 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 Jobbutton is not visible. This is default UWL behavior.

RecommendationTo enable the Create Job button to always appear on the UWLuser interface, add an Action to the currently uploaded XMLconfiguration 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 ViewYou can personalize the UWL user interface by selecting any display attributes in the dropdown list from thePersonalize 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 MDMXML 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

NoteIn the Records column (a generic UWL column), you can configure the UWL to show the displayvalue 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.

NoteIn the Sent column, the timestamp can be seen in a tool tip.


December 2013 8

2.2.4 Displaying Details about MDM Linked Records in UWLThe UWL is designed to display work items (for example, MDM workflow tasks and jobs) including detailsabout these work items (for example, task ID, start date, end date, and so on). There is no meaningfulinformation pertaining to the MDM record or records that are linked to each work item.

Use CaseA user needs to be able to determine at a single glance which record or records they need to update in thelisted 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 systemobject property, Workflow with Tables as follows:

1. Enter the <tableCode> followed by ~<number>, where <number> represents the number ofrecords 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 thenumber 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 displaysthe number 10 indicating that ten records were found in the search (the actual records are notdisplayed).

¡ If you enter the table code followed by any other number (for example, <tableCode>~6), theRecord Counter displays [6/10] indicating that10 records were found in the search and for 6out of the 10 linked records, the actual display values appear in the Workflow Records column ofthe UWL.

For more information, see SAP Help Portal at http://help.sap.com/nwmdm71 ® SAP NetWeaver Master DataManagement 7.1 ® Integration of SAP Components with MDM ® MDM Portal Content Development Guide .Read the chapter called Configuring a System Object.

CAUTIONDue to performance and user interface usability issues, we do not recommend that youconfigure this property to more than 10 displayed values.

The screen captures below show the configuration of the Workflow with Tables property duringdesign time and runtime.

Design Time (System Object Property Editor)



December 2013 9

Runtime (user interface of UWL)

NoteYou can also show details of a record by placing an MDM Result Set iView or Web Dynprocomponent on the same portal page as the UWL. However, this option only lists the MDMrecords linked to a single, selected workflow item. You would need to select each workflow itemin the UWL to see which records are linked to it.


December 2013 10

2.3 Configuring the Universal Worklist XML File

2.3.1 BackgroundDelivered portal content supports both MDM Portal iViews (iViews) and MDM Web Dynpro components (WDcomponents) and includes a preconfigured UWL XML configuration file called mdm.xml.

For Portal iViewsThe delivered mdm.xml file references both the Business Partners (BuPa) and the Products MDMrepositories. As a result, the delivered mdm.xml file contains two similar configurations, each referencing oneof 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 forMDM 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 ComponentsBy default, the delivered mdm.xml file references only theProd.MDM_PRODUCTS repository (see thediagram of the mdm.xml configuration below). However you can configure the delivered mdm.xml file toreference a custom repository by replacing the Prod.MDM_PRODUCTS repository name with the customrepository name.

For more information on how to configure the mdm.xml file for Web Dynpro components, see Configuring themdm.xml file for MDM Web Dynpro Components on page 19.

December 2013 11

NoteIn the MDM Data Manager, before you delete a job or task in a workflow, you can check in allrecords that have been checked out for editing. A popup window appears and you can select thepreferred 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 Dynprocomponent, but the action is automatic. All records that were previously checked out for editingare automatically rolled back before the job or task is deleted.

NoteFor 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 foriViews only. As of MDM 7.1 SP07, the mdm.xml file also includes elements for Web Dynpro components. Bydefault, only the iView related elements are active and the section of the XML structure pertaining to WebDynpro components is commented out.

The structure of the new mdm.xml file is divided up into segments. In order to facilitate referencing thesesegments in our procedure, we will call them segment 1, segment 2, and segment 3.

Segment 1This is the  segment of the XML file and differs from the original XML file that was suppliedwith iViews in that it only includes two elements – Actions and Item Types; the Views element isexcluded.

· Action

In the Action element, we define what actions a user can carry out in a view for the View and ItemType elements in the UWL XML structure. An Action element is often visualized as a button on the

December 2013 12

user interface of the UWL (depending on the job or task selected and on the value of the Item Typeelement in the XML configuration), but can also be visualized as a menu entry.

For more information about UWLAction elements, see SAP Help Portal athttp://help.sap.com/netweaver ® choose your SAP NetWeaver release and search for SAP NetWeaverPortal ® 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. Forexample, 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 2This is the Web Dynpro component segment of the XML structure and is displayed as <!--MDM WDCustomization .... This segment references only one repository and by default is commented out andignored by the UWL. To enable this segment, you must remove the tags that comment out this segment.

Segment 3This is the <Views> segment of the XML configuration file and is used by both an iView or Web Dynprocomponent implementation. Defines the view name and the look and feel of the UWL (column order, sortorder, filter conditions, and many more visual properties).

The customized View elements available in the UWL XML structure are:

· Jobs

· Tasks

· Completed

RecommendationWe recommend that you use UWL with either iViews or Web Dynpro components; do not useboth together.In both cases, you must configure the mdm.xml file. The sections below explain theconfiguration procedures for both an iView and Web Dynpro component implementation.

2.3.3 Configuring the mdm.xml file for MDM Portal iViewsThis section explains how to customize the mdm.xml file to connect to and display MDM workflows for acustom MDM repository.

The process includes the following main steps:......Create a sys tem o bjec t a nd d efin e a sys tem alia s to uni quel y ide nti fy t he sys tem.

1. Create a system object and define a system alias to uniquely identify the system.

2. Define a new UWL connector to connect to the MDM repository.

3. Create and configure a custom XML file .

4. Upload the customized XML file.


http://help.sap.com/saphelp_nw73/helpdata/en/4a/f9ad1a7b721115e10000000a42189c/frameset.htm


December 2013 13

5. Clear the UWL cache and restart the UWL (optional).

6. Check that the UWL displays the MDM workflows for the custom repository and that the MDM jobs andtasks are visible.

The following procedure provides more details for each of the above steps.

ProcedureStep 1: Create a system object and define a system alias to uniquely identify thesystem

NoteIf you have already created a system object while using standard MDM iViews, you do not haveto create a dedicated system object - in this case, start with Step 3 below.

...For more inf ormatio n, see

1. Create a system object.

For more information, see http://help.sap.com/nwmdm71 ® SAP NetWeaver Master DataManagement 7.1 ® MDM Portal Content Development Guide ® Configuring a System Object.

2. Define a system alias.

For more information, see http://help.sap.com/nwmdm71® SAP NetWeaver Master DataManagement 7.1 ® MDM Portal Content Development Guide ® Defining a System Alias.

3. Configure the Tables with Workflows property in the UWL to show details about the recordslinked to each job or task.

For more information, see Displaying Details about MDM Linked Records in UWL on page 8.

Step 2: Define a UWL Connector to connect to the MDM repository4. Navigate to System Administration ® System Configuration ® Universal Worklist & Workflow →

Universal Worklist – Administration ® New.

5. Enter values for the following properties:

System Alias The MDM system alias name that you defined for theMDM system object in Step 1 – point 2 above.

Connector Type Choose MdmUwlConnector from the dropdown list.

Role You can limit the access of portal users to the MDMrepository workflow by assigning a portal role to the UWLsystem.

This property is optional.

For more information, see Portal Roles on page 28.

Step 3: Create and configure a custom XML fileThe best practice for configuring the UWL for a custom repository is to leave the delivered standard mdm.xmlfile untouched and apply your changes to a copy of the mdm.xml file, which you have saved with a new name.

In this example, we have copied the mdm.xml file and renamed it mdm_custom.xml. This is the file we willcustomize.

6. Prepare the mdm_custom.xml as follows:

a. Download the standard delivered mdm.zip file (that contains the mdm.xml file) as follows:

i. Navigate to System Administration → → System Configuration Universal Worklist &Workflow → Universal Worklist – Administration.

ii. Scroll down the page and choose Click to Manage Item Types and View Definitions.

iii. In the Current Configurations tab, select the mdm configuration file. The content of theXML file is displayed below.




December 2013 14

iv. Scroll down to the bottom of the screen and choose Download Configuration todownload the mdm.zip file.

NoteThe mdm.zip file contains the mdm.xml file as well as the mdm.properties and themdm_<code>.properties files. (The *.properties files are the translation files).

b. Rename the mdm.zip file to mdm_custom.zip.

c. Extract the mdm.xml file from the mdm_custom.zip file.

d. Rename the extracted mdm.xml file. In our example, we have renamed it mdm_custom.xml.

e. Go back to the mdm_custom.zip file and delete the original mdm.xml file. Your modified XMLfile (mdm_custom.xml), will eventually replace it.

7. Edit the copied mdm_custom.xml file, so that it includes only those elements that need to be updatedfor the specific properties of the custom repository; all other generic elements should remain only in themdm.xml file.

8. Customize the mdm_custom.xml file to include the custom repository properties and semantics.

TipWhen customizing the mdm_custom.xml file, if you are creating a new configuration for asingle custom repository, you do not need references to both the Products and the BuParepositories. To remove the duplicate references, delete the references to the Productsrepository and leave only the references to the BuPa repository and adapt them to your customrepository. You can see an example in the diagram below.

Grid View of the XML configuration before removing duplicated references:


December 2013 15

Grid View of the XML configuration after removing duplicated references:

9. Modify the XML as follows:

a. In the Actions node → showDetails, change the action namecom.sap.mdm.bupa.showDetails to your customized name.

For example, com.sap.mdm.<your_name>.showDetails

Change the name in all occurrences which reference this action.

b. The showDetails action also references the standard content iView via the PCD address. Forexample, of the MDM Result Set iView or page (consisting of the Result Set iView as well asother iViews) that you want to reference. Replace this reference with your customized PCDaddress.

For more information, see Configuring the Result Set ® Step 2: Locate the PCD address of theportal page on page 24.

In the following example, you can see where these changes are made:

c. Change the system aliases and the table code names in all the Item Type elements.


December 2013 16

The name of the Item Type contains the alias name and the table code of the table thatcontains the workflows.

The naming convention is: uwl.task.mdm.jobs.<System Alias>.<table code>

For example:uwl.task.mdm.jobs.SAP_MDM_Repository_BuPa.MDM_BUSINESS_PARTNERS

Completed Task

Jobs

Tasks

The name o f t he

d. In the jobs Item Type, change the iView PCD path of the addRecordsToJob action to thePCD path of the Result Set iView you created.

For more information, see Configuring the Result Set ® Step 2: Locate the PCD address of theportal page on page 24.


December 2013 17

In the following example, you can see where this change has been made:

e. You can also change the default mode of the Result Set iView. This step is optional. There aretwo 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 example:

&mode=[view_task,result_set] – we set the mode to view_task.

CAUTIONEnsure that this configuration does not conflict with the configuration settings in the Result Setproperty editor. For example, if you set the property Is Result Set Mode enabled toNo, you cannot use the result_set mode as the default view.

For more information about the configuration settings in the Result Set Property Editor, seeConfiguring the MDM Result Set ® Step 1: Create at least one MDM Result Set iView or MDMWeb Dynpro component to be referenced from the UWL on page 23.


December 2013 18

Runtime - Result Set iView in view_task mode:

Runtime - Result Set iView in result_set mode:

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

NoteThe uwl_configuration.dtd file can be downloaded from the Current Configurations tabby choosing Download DTD (at the bottom of the screen).

11. When you have completed the configuration of the mdm_custom.xml file, add it to themdm_custom.zip file.

Step 4: Upload the custom mdm_custom.zip configuration file12. Navigate to Universal Worklist Administration→ Universal Worklist Content Configuration→ Click to

Manage Item Types and View Definitions.

13. Choose the Upload New Configuration tab.

14. Enter values for the properties.

For more information about these properties, see SAP Help Portal at http://help.sap.com/netweaver® Configuring the Universal Worklist ® UWL Content Configuration ® Uploading NewConfigurations.

NoteYou can enter any name for the Configuration Name property.

15. Choose Upload and Save.

Step 5: Clear the UWL cache (optional)

RecommendationAfter you customize the UWL configuration file, you should clear the UWL caches to ensure thatyour configuration applies to all workflow items in the UWL. If these items remain in the cache,they appear in their pre-changed state.


http://help.sap.com/saphelp_nw73/helpdata/en/4a/f9a2bf7b721115e10000000a42189c/frameset.htm

December 2013 19

16. Navigate to System Administration→ System Configuration → Universal Worklist & Workflow →Universal Worklist - Administration → Cache Administration Page → Clear Cache.

For more information about clearing the cache, see SAP Help Portal at http://help.sap.com/netweaver® Configuring the Universal Worklist ® UWL Content Configuration ® Clearing Cache.

Step 6: Check that the UWL displays the MDM workflows for the custom repository17. Log on to the portal with the relevant role. The top-level navigation workflow displays the UWL with

MDM workflow jobs and/or tasks of the connected repositories.

2.3.4 Configuring the mdm.xml file for MDM Web DynproComponents

The process includes the following main steps:......

1. Create a system object and define a system alias to uniquely identify the system.

2. Define a new UWL connector to connect to the MDM repository.

3. Create and configure a custom XML file.

4. Upload the customized XML file.

5. Clear the UWL cache and restart the UWL (optional).

6. Check that the UWL displays the MDM workflows for the custom repository and that the MDM jobs andtasks are visible.

The following section provides more details for each of the above steps:

ProcedureStep 1: Create a system object and define a system alias to uniquely identify thesystem

1. Carry out the same steps as you did for Portal iViews.

For more information, see Configuring the mdm.xml file for MDM Portal iViews ® Create a systemobject and define a system alias to uniquely identify the system on page 13.

Step 2: Define a UWL Connector to connect to the MDM repository2. Carry out the same steps as you did for Portal iViews.

For more information, see Configuring the mdm.xml file for MDM Portal iViews ® Define a UWLConnector to connect to the MDM repository on page 13.

Step 3: Create a custom XML file3. Carry out the steps 5-7 as you did for Portal iViews.

For more information, see Configuring the mdm.xml file for MDM Portal iViews ® Create a CustomXML file ® on page 13.

4. Modify the XML configuration file as follows:

a. Remove Segment 1, which is the iViews segment of the XML structure or comment it out byinserting the following tags .

b. Uncomment Segment 2 which is the Web Dynpro segment of the XML structure by removingthe tags.

c. Since segment 3 is active for both iViews and Web Dynpro components, do not changeanything.


http://help.sap.com/saphelp_nw73/helpdata/en/4a/f9a2bf7b721115e10000000a42189c/frameset.htm


December 2013 20

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 WebDynpro components:

§ WebDynproApplication

Replace the reference to the Master Application Utility with the custom applicationname.

§ WebDynproDeployableObject

Replace the value of the Master Application Utility with the custom application'sdeployable object path.

§ DynamicParameter

Replace the parameters of the Master Application Utility with the parameters of thecustom application.

NoteIn the shipped Web Dynpro content, we use the Master Application Utility to check theuser's configured MDM Web Dynpro components. The custom application's parameterseventually 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 tobe changed.

For more information, see SAP Help Portal at http://help.sap.com/nwmdm71 ® SAPNetWeaver Master Data Management 7.1 ® Development Information ® MDM WebDynpro Components: Reference Guide . Read the chapter called Master Application Utilityfor Viewing Configured Components.

b. Replace the SystemAliasName and ProductTableCode properties with the customapplication's system alias and MDM workflow table code (correspondingly) forcompletedtask, job and task Item Types. The naming convention is:uwl.task.mdm.jobs.<System Alias>.<table code>.



December 2013 21

For example:

c. To add records to a job, in the jobs Item Type, change the three Web Dynpro componentproperties (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 inwhich 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 forMDM 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.

NoteThe uwl_configuration.dtd file can be downloaded from the Current Configuration tabby choosing Download DTD (at the bottom of the screen).


December 2013 22

7. When you have completed the configuration of the mdm_custom.xml file, add it to themdm_custom.zip file.

Step 4: Upload the custom mdm_custom.zip configuration file8. Carry out the same steps as you did for Portal iViews.

For more information, see Configuring the mdm.xml file for MDM Portal iViews ® Upload the custommdm.custom.zip configuration file on page 18.

Step 5: Clear the UWL cache (optional)9. Carry out the same steps as you did for Portal iViews.

For more information, see Configuring the mdm.xml file for MDM Portal iViews ®Clear the UWL Cacheon page 18.

Step 6: Check that the UWL displays the MDM workflows for the custom repository10. Carry out the same steps as you did for Portal iViews.

For more information, see Configuring the mdm.xml file for MDM Portal iViews ®Check that the UWLdisplays the MDM workflows for the custom repository on page 19.

3 Configuring the Result SetTo display MDM records of an MDM workflow item in the UWL as a Result Set iView or Web Dynprocomponent, 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/orpage) for the following reasons:

· You may need different Result Set iViews or Web Dynpro components for different Item Typeelements (tasks, jobs, or completed tasks). For example, a Result Set generated from the UWL Add toJob button (jobs Item Type), would differ from a Result Set popup window generated from a UWLShow 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 hasalready been configured to reference a different PCD path of the Result Set applicable to a particularuse. For example, a Result Set used for adding or removing records from unlaunched jobs, or a ResultSet 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.

NoteNot applicable for MDM Web Dynpro components.

For more information, see Role-Based iView Launcher and Group-Based iView Launcher respectively onpage 30.

· You would need different popup Result Set iViews or Web Dynpro components for different steps of aworkflow.

For more information, see Step-Based Item Types on page 30.


December 2013 23

In this section we explain how to reference a Result Set from the UWL and how to configure the Result Set toshow the MDM records in a workflow job.

Step 1: Create and configure at least one MDM Result Set iView or MDM WebDynpro component to reference from the UWLConfiguring the Result Set iView

1. Create a standard MDM Result Set iView.

For more information, see http://service.sap.com/installmdm71® MDM Portal ContentDevelopment 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 theUWL:

CustomizationProperty

Description UWL ActionButtonAdd/RemoveRecords

UWL ActionButtonShow RecordDetails

Default

Is Add toJob Enabled?

If enabled, the Add toJob button appears onthe UI of the Result SetiView.

Yes No No

Is RemoveFrom JobEnabled?

If enabled, the Removefrom Job button appearson the UI of the ResultSet iView.

Yes No No

Is ResultsetModeEnabled?

If disabled, the user seesonly the records relatedto a job.

Yes No Yes

Is ViewTaskModeEnabled?

If disabled, the usercannot view the recordsof a workflow.

Yes Yes Yes

Is WorkflowEnabled?

If enabled, the workflowcontext menu is visibleon the Result Set iView.

No No No

Is RefreshUWL Enabled?

If enabled, the systemtriggers a UWL refreshupon actions done in theResult Set iView that arerelated to UWL (forexample, Add to Job,Remove from Job, andso on)

Yes No No

http://service.sap.com/installmdm71


December 2013 24

5. From the Property Category dropdown list, select Show All

Show AllProperty

Description UWL ActionButtonAdd/RemoveRecords

UWL ActionButtonShow RecordDetails

Default

Parametersto Passfrom PageRequest

Enables the current ResultSet iView subscription to aViewTaskRecordsHandler URL event. If theevent is an EPCFviewTask event, thisproperty is not required.

Enter an asterisk(*) next to thisproperty

Enter an asterisk(*) next to thisproperty

Empty

Recommendation6. 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 NetWeaverMaster 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 UWLsetting options according to the action button on the UWL.

The table below shows the specific workflow configuration properties and how they should be set foreach Result Set WD component:

Customization Property Description Default

Enable Add toJob

If enabled, the Add to Job button appears on theuser interface of the Web Dynpro Result SetComponent.

False

Enable RemoveFrom Job

If enabled, the Remove from Job button appears onthe user interface of the Result Set Web DynproComponent.

False

Enable View Task If disabled, the user cannot view the records of aworkflow.

False

Step 2: Locate the PCD address of the portal page1. 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 25

NoteFor 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 WebDynpro component is launched with the Approve or Disapprove action buttons. A Split to Jobbutton is only shown if the Result Set iView was launched from an Approve step in MDM UWL.

CAUTIONIf there are too many records in a Result Set iView or Web Dynpro component, loading aworkflow takes a long time because the system attempts to load all records on one page (pagingis not supported).

Step 3: Configure the Result Set to display the records of a UWL MDM WorkflowItemMDM 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 userinterface 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, theResult Set displays the records for the corresponding Job ID selected in the UWL. Optionally, you canconfigure the Result Set to show only workflow records and disable all other functions.

NoteThe Result Set iView /WD component and the UWL must have the same System Alias.

NoteThe Web Dynpro Result Set component and the UWL must have the same connectionproperties (in other words, the same MDM server, repository name referenced from theDestination, and the portal system object


December 2013 26

UWL

Subject

101

Result Set Listener for UWL on Row Select

Record 1Record 2Record 3

Records correspondingto the workflow jobselected in the UWL

Job ID

Workflow with Validation Process

User Name Due

Portal User July 8

Workflow with Validation [101] (3) Step: Process

222 Workflow with Validation Process Portal User July 8

Selecting a row in the UWLautomatically raises anitemselected portal event.

The MDM Web Dynpro Result Setcomponent displays the linkedMDM records for the job or task.

The header displays the selectedjob/task ID, number of linkedrecords, and step.

NoteThe UWL raises the event at given intervals even if no record is selected in the UWL.


December 2013 27

4 End User Tips and Guidelines

4.1 Creating a New Workflow in the UWLYou can create a new, empty workflow in the UWL and later add records to the workflow in the MDM Result SetiView 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.

NoteIn 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 workflow-enabled TableCode ® template as follows:

For example:

SystemTable Code

Valid Template 1Valid 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 recordsare 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 28

5 Portal ConfigurationsThere are some configurations that can be implemented in the portal to determine what portal content isavailable 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 rolefor the UWL system. When an MDM Workflow is executed in the portal, you may want to implement theworkflow so that portal users only see the tasks that they are required to work on. This configurationcan be used for Portal iViews and Web Dynpro components.

For more information, see Portal Roles on page 28.

NoteFor MDM portal iViews you can also achieve this scenario by using the UWLMDMIViewLauncher to launch different popup MDM Result Set iViews or pages dependingon the user’s 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 launcheddepending on the workflow step name – the same user who is responsible for different steps in theworkflow, will see different popup Result Sets.For example, the Show Record Details button can launch Portal Page 1 for a Create step in the workflowand 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. Thereforeconfiguration 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 RolesUser access to portal content is determined by role definitions. You can limit the access of portal users to theMDM 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. Youwill enter this role name in the User Roles property when configuring the UWL.


December 2013 29

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 usersassigned to this role will be able to see the MDM repository workflows.


December 2013 30

5.1.2 UWL iView LauncherThe 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 forthe 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 launchdifferent 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.

NoteTo enable functionality of the MDMIViewLauncher:

§ The iViewLauncher action handler must be replaced byMDMIViewLauncher inthe XML configuration file (the shipped standard MDM UWL configuration file refers tothe UWL iViewLauncher).

§ Ensure that the URL of the target iView has the correct syntax (see examples below).

When a portal user chooses the UWL‘s Show Record Details button, the relevant popup iViews are launched.

Role-Based iView LauncherTo launch a portal role-dependent iView or page from UWL for adding or removing records from unlaunchedjobs, or showing the records of a workflow task, carry out the following steps in the UWL XML configurationfile:...

1. Enter the name of the enhanced iView launcher, MDMIViewLauncher instead of the deliverediViewLauncher.

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 Howto Implement the UWL Role Based Master Data Management iView Launcher guide. Read the chapter calledUWL role based iView Launcher.

Group-Based iView LauncherTo launch a user group-dependent iView or page from the UWL for adding or removing records fromunlaunched 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 deliverediViewLauncher.

2. Enter the correct syntax for the URL of the target iView

For example:

<portalUserGroup1>,<iViewpcdId1>;<portalUserGroup2>,<iViewpcdId2>

Step-Based Item TypesWhen a portal user chooses the Show Record Details button on the UWL user interface, a popup iView or WebDynpro component is launched. Using step-based Item Type elements, you can launch a dedicated popupiView or Web Dynpro component for each step of a workflow – the same user, who is responsible for different


http://help.sap.com/saphelp_nw04/helpdata/en/b1/cc1357eead454bb144face4a66be7d/frameset.htm

http://sdn.sap.coms/

December 2013 31

steps in the workflow, sees different popup Result Sets for each step. For example, ResultSet1 can belaunched for a Create step in the workflow and Result Set2 can be launched for an Approval step in theworkflow.

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 tothe above notation as follows:

uwl.task.mdm.tasks.<MDM_Alias_name>.<MDM_table_code>.<MDMworkflow_template_name>.<MDM_workflow_template_step_Id>

ExampleAn MDM Workflow template,WFTemplate1 consists of two workflow steps, WFStepID1 and WFStepID2(these are the step IDs).

TipTo 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:

- <ItemTypename="uwl.task.mdm.tasks.SAP_MDM_Repository_BuPa.BUSINESS_PARTNERS.WFTemplate1.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"returnToDetailViewAllowed="yes" launchInNewWindow="no" />

<Action reference="com.sap.mdm.bupa.showDetails3" groupAction="no"returnToDetailViewAllowed="yes" launchInNewWindow="no" />

<Action reference="com.sap.mdm.priorityLow" groupAction="no"returnToDetailViewAllowed="yes" launchInNewWindow="no" />

<Action reference="com.sap.mdm.priorityNormal" groupAction="no"returnToDetailViewAllowed="yes" launchInNewWindow="no" />

<Action reference="com.sap.mdm.priorityHigh" groupAction="no"returnToDetailViewAllowed="yes" launchInNewWindow="no" />

<Action reference="com.sap.mdm.priorityVeryHigh" groupAction="no"returnToDetailViewAllowed="yes" launchInNewWindow="no" />

</Actions>


December 2013 32

</ItemType>

CAUTIONBe sure to use the MDM workflow template name and not the workflow template code. In ourexample WFTemplate1 represents the MDM workflow template name.

Workflow template names are case sensitive and cannot include any spaces.

How to Identify MDM Workflow Step IDsBefore you can create a step-based Item Type, you must first identify the step IDs of each step of theworkflow. As you can see in the screen capture below, workflow step IDs are not visible in the workflow Visiodiagram in MDM Data Manager.


December 2013 33

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 moreinformation, 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 viewin a popup window.

CAUTIONFor a specific MDM workflow template, you cannot have both step-based Item Types andgenericItem Types. The UWL will interpret an MDM workflow as belonging to both ItemTypes and you will end up having duplicate buttons at runtime. Therefore be sure to remove allthe other generic Item Types.

NoteOnly configure steps that need to be visible in the UWL runtime with a corresponding ItemType. For example, you would not configure an Item Type for a syndication step.

www.sdn.sap.com/irj/sdn/howtoguides

how to work with uwl and mdm workflows in the portal · pdf filesap netweaver how-to guide how...

Documents