Master Data Management: Quick Starter for Collaborative ......Master Data Management: Quick Starter for Collaborative Material Master Data Creation May 2010 3 the Dat a Stewa rd c

SAP NetWeaver

Quick Starter Guide

Master Data Management: QuickStarter for Collaborative MaterialMaster Data Creation

Applicable Releases:

SAP NetWeaver Master Data Management 7.1

Topic Area:Enterprise Information Management

Capability:Master Data Management

Version 1.0

May 2010

© Copyright 2010 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 SAP’s Support Services and may not be

modified or altered in any way.

Document HistoryDocument Version Description

1.00 First official release of this guide

Typographic ConventionsType Style Description

Example Text Words or characters quotedfrom the screen. Theseinclude field names, screentitles, pushbuttons labels,menu names, menu paths,and menu options.

Cross-references to otherdocumentation

Example text Emphasized words orphrases in body text, graphictitles, and table titles

Example text File and directory names andtheir paths, messages,names of variables andparameters, source text, andnames of installation,upgrade and database 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

Table of Contents

1. General Description.........................................................................................................1

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

3. Prerequisites....................................................................................................................3

3.1 System Requirements – Installation ..........................................................................3

3.2 Trusted Connections .................................................................................................6

4. Configuring the Quick Starter Environment ...................................................................6

4.1 Introduction ...............................................................................................................6

5. How to Extend the MDM Quick Starter and Develop a Customized Process .............. 24

6. Story Flow ...................................................................................................................... 31

6.1 New Material Request ............................................................................................. 32

6.2 Enrich and Approve ................................................................................................ 34

6.3 Review and Confirm ................................................................................................ 36

6.4 Creation of Material in ECC ..................................................................................... 36

6.5 Finalizing the MDM Creation Process...................................................................... 39

6.6 Notification .............................................................................................................. 39

Master Data Management: Quick Starter for Collaborative Material Master Data Creation

May 20101

1. General DescriptionSAP NetWeaver Master Data Management (MDM) Quick Starter (QS) packages are preconfigured,packaged solutions that are intended to enable MDM customers to rapidly deploy and implement aworking scenario for master data management processes on top of MDM and in some cases on top ofSAP NetWeaver Business Process Management (BPM).

This QS package provides the relevant content for a collaborative creation process for material masterdata based on MDM and BPM. It serves as a starting point and can be easily tailored to suit specificbusiness needs. Technically MDM‘s functionality is exposed as Web services and web-based datagoverenance user interfaces which are combined in a logical process flow using BPM.

The Quick Starter solution for Collaborative Material Master Data Creation consists of the followingelements:

Preconfigured BPM process (flow)

Custom Web Dynpro components (for example, Enrich and Approve user interface) that usestandard MDM Web Dynpro components (for example MDM Item Details Web Dynprocomponent).

Request form

Preconfigured MDM Web Services (for example, CreateMaterial)

Portal Roles (Business User, Data Steward)

Data model based on the standard MDM Material data model

Enterprise Service Call (for example, Material Creation)

2. Business ScenarioConsider that a Business User requires a new material for further processing in the supply chain. Thefollowing would be the overall process carried out:...

1. The following initial steps are carried out by the Business User:

a. Checks if a specific material record exists in the ERP Central Component (ECC) system.

b. If not, he enters the details of a new material request using a new material request form.

c. Searches the MDM repository to check if a similar record exists.

d. If the record doesn’t already exist in the central repository, he submits the new materialcreation request. (This triggers the record’s actual creation in MDM).

2. The material creation request appears in the Universal Worklist (UWL) inbox of a designated DataSteward.

3. The Data Steward can either:

Enrich and approve the request

The Data Steward runs specific validations and enriches and edits the materialrecord with missing information. At this point, the high quality record is available inthe central MDM system.


May 20102

When the Data Steward submits the approval, the Business User who initiallymade the request is notified of the available data and receives a new task, Reviewand Confirm in his UWL inbox.

Rejects the request

In this case the created material in MDM is rolled back. Notification that the request hasbeen rejected and the reason appears in the Business User‘s UWL inbox.

4. The Business User reviews the changes made by the Data Steward and either rejects orconfirms the changes.

5. If the changes are rejected, the Data Steward receives the Enrich and Approve task again in hisUWL inbox.

6. If the changes are confirmed, a series of automatic activities creates the material record in theECC.

7. If the material record creation in ECC fails, the Data Steward receives the Enrich and Approvetask again in his UWL inbox. A description of each error appears in the Errors pane.

8. If the material record creation in ECC is successful, a series of automated activities updates thematerial’s ECC remote key and checks in the MDM material record.


May 20103

the Dat a Stewa rd c an also r eject the req uest, the n th e cr eate d m ateri al in MDM is rolle d ba ck, a nd th e Busin ess Use r g ets Noti ficatio n

3. PrerequisitesThis section covers the necessary installations required prior to configuring and running the MDMQuick Starter for Collaborative Material Master Data Creation. Installation is done according to therelevant installation and configuration guides. Links to the relevant guides are provided below.

3.1 System Requirements – InstallationDeploy the following components into your SAP NetWeaver Application Server Java (AS Java):

Component Required/Optional File Name More Information

SAP NetWeaverComposition Environment(CE) 7.1 EnhancementPackage 1 SP04

(including BusinessProcess Management(BPM), SAP NetWeaverDeveloper Studio, and theSAP NetWeaver Portal)

Required For more information, seeInstalling SAP NetWeaverComposition Environment(CE) 7.1 EHP1 SP04 onpage 5.

SAP NetWeaver MasterData Management (MDM)7.1 SP4:

For more information, seehttp://service.sap.com/installmdm71Installation and Upgradechoose the installation guideaccording to the platform thatyou are using (for example,Windows or Unix).

Master Data Server(MDS)

Required

MDM Console Required

MDM Data Manager Required

MDM ImportManager

Optional

MDM Syndicator Optional

Master Data ImportServer (MDIS)

Optional

Master DataSyndication Server(MDSS)

Optional

http://service.sap.com/installmdm71



May 20104

Component Required/Optional File Name More Information

SAP NetWeaver MDMWeb Dynpro Framework7.1 SP4

Required MDMJAVAWDFRWK04_x.SCA

For more information, seehttp://service.sap.com/installmdm71Development andCustomization MDM WebDynpro Components Guide.

Refer to sections:

Installing the MDMWeb DynproEnvironment

Deploying MDM WebDynpro Components

SAP NetWeaver MDMWeb Services Generator7.1 SP4

Required MDMWEBSERVICES04_x.SCA

For more information, seehttp://service.sap.com/installmdm71 MDMWeb Services GuideInstallation and Deployment

(design time)

SAP NetWeaver MDMWeb Services Runtime 7.1SP4

Required MDMWEBSERVRUNT04_x.SCA

For more information, seehttp://service.sap.com/installmdm71 MDMWeb Services GuideInstallation and Deployment

(runtime)

SAP NetWeaver MDMJava Connector 7.1 SP4

Required MDMJAVAAPI04_xxx.SCA

For more information, seehttp://service.sap.com/installmdm71Development andCustomization MDM Javaand .NET API GettingStarted Getting Startedwith Java API Installingand Referencing the MDMConnector.

SAP EnhancementPackage 4 for SAP ECC6.0

(Enterprise Services)

Required For more information, seethe section below this table.

For demonstrations or proof-of-concept (POC) purposes,you can use the SAP ESWorkplace (you will need toregister on the SAPDeveloper Network (SDN) at:http://sdn.sap.com/irj/sdn/soareg)



http://help.sap.com/saphelp_nwmdm71/helpdata/en/4a/de4b01fcb42472e10000000a42189c/frameset.htm



http://help.sap.com/saphelp_nwmdm71/helpdata/en/4a/b90771f2b93d86e10000000a421937/frameset.htm

http://help.sap.com/saphelp_nwmdm71/helpdata/en/4a/b90771f2b93d86e10000000a421937/frameset.htm



http://help.sap.com/saphelp_nwmdm71/helpdata/en/49/06eac7dc78132ee10000000a421937/frameset.htm



http://help.sap.com/saphelp_nwmdm71/helpdata/en/49/06eac7dc78132ee10000000a421937/frameset.htm




May 20105

Installing SAP NetWeaver Composition Environment (CE) 7.1 EHP1 SP04Any customer with a valid SAP Service Marketplace User ID license can download the SAPNetWeaver Composition Environment (CE) from the SAP Service Marketplace (SMP) as follows:...

1. Log on to the SAP Software Distribution Center (SWDC) at http://service.sap.com/swdc.

2. From the navigation tree on the left, choose Download Installations and Upgrade - Entry byApplication Group

3. From the main page navigate to SAP NetWeaver SAP NETWEAVER.

4. Select the SAP EHP1 for SAP NW CE7.1 application.

5. Choose the installation according to the platform that you are using (for example, Windows orUnix).

NoteLinks to the installation documentation can be found on the Info page below theapplication name.

You can also download a Preview Version from SAP Developer Network (SDN) athttp://www.sdn.sap.com/irj/sdn Downloads EHP1 for SAP NetWeaver CompositionEnvironment 7.1 - Preview Version.

The direct link is: EHP1 for SAP NetWeaver Composition Environment 7.1 - Preview Version

NoteUpdate to the highest Support Package (SP)

Installing SAP NetWeaver Developer Studio (NWDS)

If not already available, download and install a NWDS matching the SAP NW CE EHP1 installationabove. Any customer with a valid SAP Service Marketplace User ID license can download the NWDSfrom the SAP Service Marketplace (SMP) as follows:...


2. From the navigation tree on the left, choose Download Support Packages and Patches -Entry by Application Group

3. From the main page, navigate to SAP NetWeaver SAP NETWEAVER.

4. Select the SAP EHP1 for SAP NW CE7.1 application.

5. Navigate to Entry by Component NWDS Update Site CE7.11.

6. Choose #OS independent.

7. Choose a NWDS application that matches the SAP NW CE EHP1 installation above.

NoteLinks to the installation documentation can be found on the Info page below theapplication name.

SAP Enhancement Package 4 for SAP ECC 6.0 (Enterprise Services)...


2. From the navigation tree on the left, choose Download Support Packages and Patches Support Packages and Patches - Entry by Application Group.

http://service.sap.com/swdc

http://www.sdn.sap.com/irj/sdn

http://www.sdn.sap.com/irj/scn/downloads?rid=/library/uuid/00846edd-355b-2b10-f38c-df94ec96eb74




May 20106

3. Continue navigating on the main web page as follows: SAP Application Components SAPERP SAP ERP Enhance Package EHP4 FOR SAP ERP 6.0

3.2 Trusted ConnectionsThe SAP NetWeaver Application Server Java user must also exist as an MDM User (defined in theMDM Console).You can authenticate a session by using a trusted connection between the serverwhere the MDM Java API is deployed, and the server where MDM is running.

For more information on how to define a trusted connection, seehttp://service.sap.com/installmdm71 Development and Customization MDM WebDynpro Components Guide Defining a Trusted Connection

4. Configuring the Quick Starter Environment

4.1 IntroductionThis section contains the necessary steps required to configure and run the MDM Quick Starter forCollaborative Material Master Data Creation.

Make sure that your Quick Starter package contains the following:

Component File Name More Information

MDM Quick Starter(QS) MaterialRepository

MDM_QS_Material_Repository_7.1SP4.a2a Unarchive this file and load it onto your MDS.

The MDM QS Material repositoryis based on the Material MDMBusiness Content repository.

For more information about theMaterial repository, seehttps://websmp104.sap-ag.de/installmdm71 MDMBusiness Content MaterialSAP Note 1355137


http://help.sap.com/saphelp_nwmdm71/helpdata/en/4a/8c20a0dc93203be10000000a42189b/frameset.htm

https://websmp104.sap-ag.de/installmdm71

https://websmp104.sap-ag.de/installmdm71


May 20107

Component File Name More Information

MDM Quick Starter MDMBPMMATE04_x.sca Deploy the MDM Quick StarterSCA file into your SAPNetWeaver Application ServerJava (AS Java). This SCA filecontains the following:

An MDM Material QuickStarter ProcessDevelopment Component(DC)

A custom MDM WebDynpro DevelopmentComponent

A stand-alone MDM WebDynpro DevelopmentComponent running on thePortal

MDM Quick StarterWeb Service

MDM_QS_Material_WS_7.1SP4.ear Deploy this MDM Quick StarterEAR file into your SAPNetWeaver Application ServerJava (AS Java). The file containsthe MDM Web Service which wasgenerated from the MDM WebService Generator on top of theMaterial MDM Business Contentrepository.

MDM Web DynproConfiguration XMLfile

MDM_QS_Material_WDCONFIG_7.1SP4.xml See step 8 below

Portal Content MDM_QS_Material_EP_Content_7.1SP4.epa See step 1 below

Step 1: Importing the MDM Quick Starter Portal Content Archive File

InfoThis step adds the Request Form to a Portal page.

...

1. Log on to the SAP NetWeaver Portal as Administrator.

2. In the Portal, navigate to System Administration Transport.

3. In the Portal Catalog, navigate to Transport Packages Import.

4. Import the following file: MDM_QS_Material_EP_Content_7.1SP4.epa. A new Materialfolder is created in the Portal.

5. To view the folder, in the Portal, choose Content Administration and then navigate in the PortalCatalog to Portal Content Content Provided by SAP packages MDM QuickStarterMaterial.


May 20108

NoteIf you want to change the sort order so that the Home tab is the first Top LevelNavigation (TLN) entry point, you can modify the Sort Order Priority property for theHome workset, which you can find at:pcd:portal_content/com.sap.pct/every_user/general/worksets/com.sap.uwl.home_core_ws

Step 2: Create MDM Quick Starter (QS) Roles

InfoEach Quick Starter role enables the user to carry out specific functions during theadministrative and creation process.

...

...

1. Log on to the SAP NetWeaver Administrator (NWA) with Administrator permissions.

2. Navigate to Configuration Management Identify Management.

3. Create the following roles in the User Management Engine (UME):

MDM_Process_SuperUser

This role includes the following:

Administrator for the material creation pool

MDM WS Generator user

MDM WD Configurator user

MDM_Business_User

Owner of the Business User lane

MDM_Data_Steward

Owner of the Data Steward lane

Step 3: Assign Actions for the MDM QS Roles

InfoThis step defines specific permissions for each QS role.


May 20109

Action Description Roles

MDM_Material_Creation_Request Permission to view theRequest New MaterialForm


MDM_Business_User

MDM_WD_CONFIGURATOR Permission to configureWeb Dynpro componentsusing the MDM WebDynpro Configurator


MDM_WS_Generator Permission to generateMDM Web services usingthe MDM Web ServiceGenerator


Step 4: Assign Roles to Users

User Assigned Role

All MDM QS Users Every User Core Role

BPEM End User

MDM QS Super User MDM_Process_SuperUser


May 201010

User Assigned Role

MDM QS Business User MDM_Business_User

Master Data Management

NoteThis role is automatically created when the transportpackage is imported. See step 1 above.

TipTo search for the Master Data Management role, enterthe following search term: *requester


May 201011

Step 5: Assign the SAP_BPM_SuperAdmin role to the default SAP NetWeaver GuestUser

InfoTo enable the Web service call to start the BPM process, assign theSAP_BPM_SuperAdmin role to the default SAP NetWeaver Guest user (see screencapture below)

Step 6: Create Users in MDM

InfoThis step is carried out so that a trusted connection can be established.

Create the same user in the MDM Console as created in the UME. (see step 4).

Step 7: Create an MDM Destination

InfoYou create an MDM destination from which the MDM Web Dynpro components canretrieve MDM Server communication details.

For more information on how to create an MDM destination, seehttp://service.sap.com/installmdm71 Development and Customization MDM WebDynpro Components Guide Creating a Destination for the MDM Repository.

The direct link is: Creating a Destination for the MDM Repository

Take note of the following steps:

In the General Data step, the Destination Name is MDM_QS_Material.


http://help.sap.com/saphelp_nwmdm71/helpdata/en/4a/cdd7c31ca822ace10000000a42189b/frameset.htm


May 201012

In the Logon Data step, enter your MDM server and repository names.

Step 8: Import the MDM Web Dynpro Configuration

InfoYou use the MDM Web Dynpro configuration to define the MDM Web Dynpro runtimeuser interfaces (for example, the Enrich and Approve human activity).

1. Log on to the MDM Web Dynpro Components Configuration Manager with your MDM QS SuperUser role.

2. Import the MDM QS Material configuration.The name of the file is: MDM_QS_Material_WDCONFIG_7.1SP4.xml.

For more information, see http://service.sap.com/installmdm71 Development andCustomization MDM Web Dynpro Components Guide Transporting.

The direct link is: Transporting.


http://help.sap.com/saphelp_nwmdm71/helpdata/en/4a/72ebd6056d61a4e10000000a421937/frameset.htm


May 201013

Step 9: Create Communication Profiles

InfoBy creating Communication Profiles, you provide runtime configuration settings so thatthe various systems can communicate with one another.

...

...

1. Log on to the SAP NetWeaver Administrator (NWA) page with Administrator permissions.

2. Navigate to SOA Management Technical Configuration System Connections.

3. Select Communication Profiles.

4. Choose New to open the New Profile wizard.

5. Create a new Communication Profile for each of the following:

MDM Web Services

MDM QS BPM

SAP ECC Enterprise Services


May 201014

6. Enter the following values in each of the steps:

MDM Web Services

Step 1: General

Enter MDM_WS as the Profile Name andenter a Profile Description.

Step 2: Security

Select None as the Authentication method.

Step 1: General

Step 2: Security

MDM QS BPM

Step 1: General

Enter MDM_QS_BPM_WS as the ProfileName and enter a Profile Description.

Step 2: Security

Select None as the Authentication method.

Step 1: General

Step 2: Security

See screen capture above (for MDM Web Services)


May 201015

SAP ECC Enterprise Services

Step 1: General

Enter SAP_ES as the Profile Name andenter a Profile Description.

Step 2: Security

Select all the authentication options.

Step 1: General

Step 2: Security

7. Choose Finish.

Step 10: Create Provider Systems

InfoThe Provider Systems specify the policies of communication between the systems thatare defined as Communication Profiles above.

...


2. Navigate to SOA Management Technical Configuration System Connections.

3. Select Provider Systems.

4. Choose New to launch the New Provider System wizard.


May 201016

5. Create a provider system for:

MDM BPM Web Service

NoteThis Web service starts the MDM Material Creation Process.

MDM Web Service

SAP ECC Create Material Basic Data Enterprise Service

SAP ECC Change Material Basic Data Enterprise Service

6. Enter the following values in each of the steps:

MDM BPM Web Service

Step 1: Provider System

Select the Java radio button.

Enter QSS as the System Name.

Enter the name of your WebApplication Server as the Host.

Enter a system description.

Step 2: Metadata User

Do not enter any values in this step.

Step 3: Communication Profile

Enter MDM_QS_BPM_WS as the ProfileName.

Step 4: Services Search Settings

Select Single Service.

Enter the following WSDL URL:http://<AS JAVA servername>:<httpport>/mdm/bpem/demosapcom2Fmdm2Fqs2Fmaterial2Fprocess2FPool2FMaterialCreation6ab68d036d4c26e856f16b9b59455176?wsdl&mode=ws_policy





May 201017

MDM Web Service


Select the Java radio button.

Enter MDM as the System Name.

Enter the name of your WebApplication Server as the Host.

Enter a system description.


Do not enter any values in this step.


Enter MDM_WS as the Profile Name.



Enter the following WSDL URL:http://<Your SAP AS JAVAname>:< Your SAP AS JAVAhttpport>/MDM_Material/HTTPNone?wsdl&style=document&mode=ws_policy

Steps 1 and 3:

SAP ECC Create Material Basic Data Enterprise Service


Select the ABAP radio button.

Enter ES1 as the System Name.

Enter the Host, Client, andInstallation Number of your ECC.

Enter a System Description.


Enter User Name and Password


Enter SAP_ERP_ES as the Profile Name.



Enter the correct WSDL URL forCreate Material Basic Data ES foryour ESS system.

Steps 1 and 3:


May 201018

SAP ECC Change Material Basic Data Enterprise Service


Same as above for Create Material BasicData with the following changes:.

In step 1, enter ES2 as the SystemName.

In step 4, enter the correct WSDLURL for Change Material BasicData ES for your ESS system.

Step 11: Define a User Name and Password for ECC Enterprise Services


2. Navigate to SOA Management Application and Secnario Communication User AccountManagement.

3. Choose the Maintenance tab.

4. Choose New to open the New User Account wizard.

5. Complete the wizard as follows:

Step 1 – General

The name of the ECC is ECC_ES_Material.


May 201019

Step 2 – Credentials

Choose WebService Security and System–key for both Web Service Security and forHTTPs.

6. Choose the Assignment tab.

7. Choose New to open the New User Account Assignment wizard.

8. Complete the wizard as follows:

Step 1: User Account

Choose the User Account that you created in step 5 above.


May 201020

Step 2: Provider

Choose the ES1 provider system for the Create Material Basic Data and then repeat this stepand choose ES2 provider system for the Change Material Basic Data.

Step 12: Configure a Proxy

InfoConfigure a proxy so that you can call services outside of your Intranet. (For example, ifyour ECC is located outside of your Intranet).


2. Navigate to SOA Management Technical Configuration SOA Middleware Global Settings.

3. Choose the HTTP Proxy tab.

4. Enter the proxy Host and Port names.


May 201021

5. Check Bypass proxy server for local addresses.

6. Choose Save.

7. Choose the WS Navigator tab.

8. Enter an asterisk (*) in the Allowed Hosts field.

NoteThis enables you to use the Web service test page to call a Web service outside of theIntranet.

9. Choose Save.

Step 13: Assign a Provider System to the MDM BPM Material DC

InfoFor the material creation process to call MDM Web services and Enterprise Service calls,you need to assign the correct Provider System (communication policies) for eachService Group.

...


2. Navigate to SOA Management Application and Scenario Communication ApplicationCommunication.

3. Select demo.sap.com/MDM-BPM-MATERIAL-SAMPLE from the list of configurations at the topof the screen.


May 201022

4. Choose Edit and assign the following Service Groups to the correct Provider System:

Service Group Provider System

MDM_Material MDM

Create_Material_Basic_Data_ES ES1

Change_Material_Basic_Data_ES ES2

5. Select the Service Group and choose Assign Provider System.

6. Choose the relevant Provider System from the popup window.

7. Choose OK.

8. Save your settings.

9. Refresh and check that all configured Service Groups are in a Processed state.

Step 14: Assign a Provider System to the MDM QS Stand-Alone Web Dynpro DC

NoteTo start the BPM process for the stand-alone Web Dynpro application, you need toassign the correct Provider System (communication policies).


2. Navigate to SOA Management Application and Scenario Communication ApplicationCommunication.


May 201023

3. Select demo.sap.com/MDM~qs~material~standalone~wd from the list of configurations atthe top of the screen.

4. Choose Edit and assign the following Service Groups to the correct Provider System:

Service Group Provider System

MaterialCreationProcessSG QSS

MdmMaterialCreationSG MDM

5. Select the Service Group and choose Assign Provider System.

6. Choose the relevant Provider System from the popup window.

7. Choose OK.

8. Save your settings.

9. Refresh and check that all configured Service Groups are in a Processed state.

Step 15: Define the MDM Web Service User...


2. Navigate to Configuration Management Infrastructure Java System Properties.

3. Choose the Applications tab.

4. Highlight the MDM_Material_ENTAPP application in the Details pane.

5. Choose WS.RunTime.Mdm.User from the Extended Details pane.


May 201024

6. Choose Modify.

7. Define the MDM password for the assigned MDM user name.

8. Choose Save As.

5. How to Extend the MDM Quick Starter andDevelop a Customized Process

You can extend the MDM Quick Starter Material implementation and create your own customizedimplementation. The MDM Quick Starter release contains the source code, so you can import thesource code into your local workspace and continue developing the MDM Material process on top ofthe MDM Quick Starter release.

To import the MDM Quick Starter source code, follow these steps:

Step 1: Import the SCA File...

1. In the SAP NetWeaver Developer Studio (NWDS), choose the Development Infrastructureperspective as follows:

Window Open Perspective Other Development Infrastructure.

2. In the Component Browser choose the LocalDevelopment node.

3. Import the software component to your LocalDevelopment development track as follows:

a. In the context menu of the LocalDevelopment track, choose Import SC… to open theImport SC from File screen.


May 201025

b. Locate the SCA file using the Browse button.

c. Choose Finish. The import is complete. You can see the components with the SCtechnical name that have been created, under the node.


May 201026

4. To work with the imported components, you need to create a new project for each of theDevelopment Components. From the context menu of each development component, chooseSync/Create Project.

5. Repeat this step for each DC in the table below:

Development Component Name Type Description

mdm/qs/material/custom/wd Web Dynpro Contains two kinds of Web Dynprocomponents:

Custom

A Web Dynpro componentconsisting of an Enrich andApprove BPM activity –wrapped in an MDM ItemDetails Web Dynprocomponent

Notification

A Web Dynpro componentfor a notification activity


May 201027

Development Component Name Type Description

mdm/qs/material/functions/ear EnterpriseApplication

Contains themdm/qs/material/functions/ejb module

mdm/qs/material/functions/ejb EJB Module Contains EJBs, consumed in theBPM mapping process as ejbfunctions

mdm/qs/material/process ProcessComposer

Contains the MDM materialcreation processes

mdm/qs/material/standalone/security

UMEPermissions

Contains the security actiondefinition for the material requestform

mdm/qs/material/standalone Web Dynpro Contains the stand-alone WebDynpro component, which is thematerial requester form

Step 2: Solve the Dependency Errors

6. Choose the Development Infrastructure perspective.

7. In the context menu of the LocalDevelopment node, choose Import SC....

8. Start the wizard by locating the MDMJAVAAPI04_xxx.SCA SCA file, using the Browse button.

9. Choose Finish.


May 201028

10. Repeat steps 7-10 for the MDMJAVAWDFRWK04_x.SCA file.


May 201029

11. Refresh the LocalDevelopment node to see the added SCA file.

12. Highlight the MDM-BPM-MATERIAL-SAMPLE SCA and select the Dependencies tab in theComponent Properties perspective.

13. Choose Add.

14. Select the MDM_JAVA_API and MDM_JAVA_WD_FRAMEWORK SCAs from the popup window.

15. Choose Finish.

The dependencies are set and you can start your custom implementation on top of the MDMQuick Starter implementation.


May 201030


May 201031

6. Story FlowThe story flow is outlined in the following process diagram:


May 201032

6.1 New Material Request

User InterfaceThis step consists of a custom wrapper application (New Material Request Form) that includes thefollowing elements:

Embedded MDM Item Details Web Dynpro component

MDM Search popup page (when choosing Search on the UI). The popup page consists of MDMSearch, Result Set, and Item Details Web Dynpro components. A custom Use as templatebutton was added to the search page.

An application consisting of a Notes area

The above mentioned MDM Web Dynpro components are configured in the MDM Web DynproConfigurator and can be adapted to suit any business scenario. For example, you can choose whichfields to display on the user interface of the Web Dynpro component (you choose from a list of fields inthe MDM repository).

For more information, see http://service.sap.com/installmdm71 MDM Web DynproComponents Guide.


May 201033

NoteWhen the request is submitted, an MDM validation is run in the background. If theBusiness User has chosen not to enter values in all the fields specified in the validation,a list of validation errors appears on the New Material Request Form. Either theBusiness User can enter values in these fields, or he can choose Save with errors andcontinue with the material creation request without entering values in the fields.

.

ProcedureA request for new material is initiated by the Business User as follows:...

1. Log on to the SAP NetWeaver Portal with the user name and password defined for the BusinessUser role.

TipInstead of logging on to the portal, you can run the New Material Request Form as astand-alone application using the following URL:http://<AS JAVA Server Name>:<HTTPPort>/webdynpro/dispatcher/demo.sap.com/mdm~qs~material~standalone~wd/Standalone?SAPtestId=2

2. Before you create a new request, first search the MDM repository to check if a similar recordexists. If so, you can choose Use as template to copy the values of the similar record to yourNew Material Request Form.

CAUTIONNot all field values of the similar record are copied over – only those that belong to theconfigured display fields on the New Material Request Form. All other field values areignored.

3. Choose Edit next to each field to change a value or enter a new value for your material request.The popup window for each field includes a list of values that exist in the MDM repository.

4. Complete the New Material Request Form (either from scratch or with the modifications of thecopied record).

5. Enter a reason for the request in the Notes area on the right. This step is mandatory.

6. Choose Submit Request to initiate the BPM process.


May 201034

FunctionalityWhen the Business User chooses Submit Request, the following actions are triggered:...

1. A record is created as a checked out as new record in the MDM repository.

2. A Web service call from the wrapper application initiates a BPM process with the request data.

3. The BPM engine moves the process to the first task and a new BPM work item is added to theData Steward’s UWL inbox.

6.2 Enrich and Approve

User InterfaceThis step consists of a custom wrapper application that uses the MDM Web Dynpro Search, ResultSet, and Item Details components as used components.

The user interface consists of:

An embedded MDM Item Details Web Dynpro component with configured Approve, Reject, andSearch buttons.

An MDM Search popup page (when choosing Search on the UI) consisting of MDM Search,Result Set, and Item Details Web Dynpro components. A custom Use as template button wasadded to the search page.

A Notes area and an Errors area.


May 201035

ProcedureThe Enrich and Approve step is carried out by the Data Steward as follows:...

1. Open your UWL inbox to see the submitted New Material Request Form.

2. Open the task to see the Enrich and approve new MDM material screen.

3. Review the request note and the material details.

4. If required, enrich the data (edit and save) as follows:

Search the MDM repository to check if a similar record exists. If so, you can choose Useas template to copy the values of the similar record to the New Material Request Formand update the values accordingly.

Choose Edit next to each field to change a value. The popup window for each fieldincludes a list of values that exist in the MDM repository.

5. Save your changes.

6. Choose Validate to run the configured validations as well as a mandatory field check.

NoteThe validations are configured in the MDM Web Dynpro Configurator. For moreinformation, see http://service.sap.com/installmdm71 MDM Web DynproComponents Guide Configuring an Item Details Component.

7. Choose one of the following buttons:

Approve

Reject

Before choosing Reject, enter a reason for rejection by opening the Notes link in theBPM standard task bar.

BPM standard task bar

Cancel t he c reat e new ma teri al re quest or A ppr ove st ep, s ave c han ges and mov e the re ques t to t he next BPM step for revi ew by req uesto r.

Cancel t he c reat e new ma teri al re quest or A ppr ove st ep, s ave c han ges and mov e the re ques t to t he next BPM step for revi ew by req uesto r.

FuntionalityWhen the Data Steward chooses Approve the following actions are triggered:

1. A validation is run in the background (all configured validations and mandatory fields).

2. If the task is successfully completed, and the record is valid, the BPM engine moves the processto the next task and a new BPM task (Review and Confirm) is added to the Business User’sUWL inbox.

When the Data Steward chooses Reject, the following actions are triggered:...

1. An automated step is triggered using an MDM Web Service Rollback operation.

2. The material request which was originally checked out as new is rolled back and the record isdeleted from the MDM repository.


May 201036

3. The BPM process is terminated.

4. A notification in the form of a task is sent to the Business User‘s UWL inbox for further review.

6.3 Review and Confirm

User InterfaceThis step consists of a custom Web Dynpro wrapper application, with an MDM Web Dynpro ItemDetails component in read-only mode.

ProcedureThis step is carried out by the Business User:...

1. Review the changes made by the Data Steward.

2. Confirm or Reject the changes.

Functionality If the Business User chooses Confirm, the BPM process moves to the next step.

If the Business user chooses Reject, the Data Steward once again receives the Enrich andApprove task in his UWL inbox.

6.4 Creation of Material in ECCIf the creation in ECC fails, the Data Steward once again receives the Enrich and Approve task in hisUWL inbox. In the Errors pane on the right side of the screen a description of all the errors appears.

If the creation of the material in ECC is successful, a series of automated activities calls MDM WebServices, which updates the material ECC remote key and checks in the MDM material record. If oneof the Web Service calls fails, the Data Steward receives the Enrich and Approve task in his UWLinbox with a list of errors in the Errors pane.


May 201037

The series of automated steps include: MDM Web Services for retrieving data from the MDM repository

Enterprise Services for creating the material in ECC

MDM Web Services:MDM Web Services are use to retrieve the record information from the repository including lookuprecord IDs.

For each lookup field defined, MDM Web services are intiated to obtain the relevant lookup recordcodes. In the Quick Starter example, this has been defined for the following four lookup tables:

MDM_UNITS (base unit)

MDM_MATERIAL_TYPES

MDM_INDUSTRY_SECTOR

MDM_UNITS ( height, width, length unit)

Enterprise ServicesThe Enterprise Services (ES) are used for creating the material in ECC.

There are two Enterprise Service calls:

Create Basic Data


May 201038

Creates the Material with values for the following fields:

Description

Material Type

Industrial Sector

Base Unit

Change Basic Data

Updates the Material with values for the following fields:

Width

Height

Length

Unit of Width / Height / Length

If the material creation is a success, the Enterprise Service response includes the newly createdrecord’s remote key.


May 201039

6.5 Finalizing the MDM Creation ProcessThe final MDM creation process consists of the following three automated steps using MDM Webservices:

Join Check Out

Update Key Mapping

Check In

6.6 NotificationThe Business User who initially made the request is notified of the available data and receives anotification in his UWL inbox.

Documents

Master Data Management: Quick Starter for Collaborative ......Master Data Management: Quick Starter for Collaborative Material Master Data Creation May 2010 3 the Dat a Stewa rd c