quick starter guide for collaborative material master data creation

7/29/2019 Quick Starter Guide for Collaborative Material Master Data Creation

1/44

SAP Net Weave r

Quic k St ar t er Guide

Mast er Dat a Management : Quic k

St ar t er for Co l laborat ive Mat er ia l

Mast er Dat a Creat ion

Appl icable Releases:

SAP NetWeaver Master Data Management 7 .1

Topic Area:

Enter pr ise In format ion Manageme nt

Capabi l i ty :

Master Data Management

Version 1.0

May 2010


2/44

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 withrespect 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 consequentialdamages 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 apractical 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 ofthe Code given herein, and SAP shall not be liable for

errors or damages caused by the usage of the Code, except

if such damages were caused by SAP intentionally or

grossly negligent.

Disclaimer

Some components of this product are based on Java. Any

code change in these components may cause unpredictable

and severe malfunctions and is therefore expressively

prohibited, as is any decompilation of these components.

Any Java Source Code delivered with this product is only

to be used by SAPs Support Services and may not be

modified or altered in any way.


3/44

Document H is to ry

Document Version Description

1.00 First official release of this guide


4/44

Typographic Convent ions

Type Style Description

Example Text Words or characters quotedfrom the screen. These

include field names, screen

titles, pushbuttons labels,

menu names, menu paths,

and menu options.

Cross-references to other

documentation

Example text Emphasized words or

phrases in body text, graphic

titles, and table titles

Example text File and directory names and

their paths, messages,

names of variables and

parameters, source text, and

names of installation,

upgrade and database tools.

Example text User entry texts. These are

words or characters that you

enter in the system exactly as

they appear in the

documentation.

Variable user entry. Angle

brackets indicate that you

replace these words and

characters with appropriate

entries to make entries in the

system.

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

Icons

Icon Description

CautionNote or Important

Example

Recommendation or Tip


5/44

Table of Content s

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


6/44

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

May 2010

1

1. General Desc r ipt ion

SAP 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 a

working scenario for master data management processes on top of MDM and in some cases on top of

SAP NetWeaver Business Process Management (BPM).

This QS package provides the relevant content for a collaborative creation process for material master

data based on MDM and BPM. It serves as a starting point and can be easily tailored to suit specific

business needs. Technically MDMs functionality is exposed as Web services and web-based data

goverenance 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 following

elements:

Preconfigured BPM process (flow)

Custom Web Dynpro components (for example, Enrich and Approveuser interface) that use

standard MDM Web Dynpro components (for example MDM Item Details Web Dynprocomponent).

Request form

P r e c o n f i g u re d M D M W e b S e r v ic e s (f o r e x a m p l e , CreateMaterial)

P o r t a l R o l e s ( B u s in e s s U s e r , D a t a S t e w a r d )

Data model based on the standard MDM Material data model

E n te rp r i s e S e rv i c e C a l l ( fo r ex am p l e , Ma te r i a l C rea t i on )

2. Business Sc enar ioConsider that a Business User requires a new material for further processing in the supply chain. The

following 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 doesnt already exist in the central repository, he submits the new material

creation request. (This triggers the records actual creation in MDM).

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

Steward.

3. The Data Steward can either:

Enrich and approve the request

The Data Steward runs specific validations and enriches and edits the material

record with missing information. At this point, the high quality record is available in

the central MDM system.


7/44


May 2010

2

When the Data Steward submits the approval, the Business User who initially

made the request is notified of the available data and receives a new task, Review

and Confirmin 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 Users UWL inbox.

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

confirms the changes.

5. If the changes are rejected, the Data Steward receives the Enrich and Approvetask again in his

UWL inbox.

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

ECC.

7. If the material record creation in ECC fails, the Data Steward receives the Enrich and Approve

task 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 thematerials ECC remote key and checks in the MDM material record.


8/44


May 2010

3

t heDa taS tewardc ana l s o re j ec t t he request , t hen thec rea tedmate ri a l i nMDMi s ro ll edbac k ,and theB us i nes s Userge ts No t i f i ca t i on

3. Prerequis i t es

This section covers the necessary installations required prior to configuring and running the MDM

Quick 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 R equi rements I nsta l la t i on

Deploy the following components into your SAP NetWeaver Application Server Java (AS Java):

ComponentRequired/

OptionalFile Name More Information

SAP NetWeaver

Composition Environment

(CE) 7.1 EnhancementPackage 1 SP04

(including Business

Process Management

(BPM), SAP NetWeaver

Developer Studio, and the

SAP NetWeaver Portal)

Required For more information, see

Installing SAP NetWeaver

Composition Environment(CE) 7.1 EHP1 SP04on

page 5.

SAP NetWeaver Master

Data Management (MDM)

7.1 SP4:

For more information, see

http://service.sap.co

m/installmdm71

Installation and Upgrade

choose the installation guideaccording to the platform that

you are using (for example,

Windows or Unix).

Master Data Server(MDS)

Required

MDM Console Required

MDM Data Manager Required

MDM Import

Manager

Optional

MDM Syndicator Optional

Master Data Import

Server (MDIS)

Optional

Master Data

Syndication Server

(MDSS)

Optional
http://service.sap.com/installmdm71http://service.sap.com/installmdm71http://service.sap.com/installmdm71http://service.sap.com/installmdm71


9/44


May 2010

4

ComponentRequired/

OptionalFile Name More Information

SAP NetWeaver MDM

Web Dynpro Framework

7.1 SP4

Required MDMJAVAWDFRWK04

_x.SCA



m/installmdm71

Development and

Customization MDM Web

Dynpro Components Guide.

Refer to sections:

Installing the MDM

Web Dynpro

Environment

Deploying MDM Web

Dynpro Components

SAP NetWeaver MDMWeb Services Generator

7.1 SP4

Required MDMWEBSERVICES04_x.SCA

For more information, seehttp://service.sap.co

m/installmdm71 MDM

Web Services Guide

Installation and Deployment

(design time)

SAP NetWeaver MDM

Web Services Runtime 7.1

SP4

Required MDMWEBSERVRUNT0

4_x.SCA



m/installmdm71 MDM

Web Services Guide

Installation and Deployment

(runtime)

SAP NetWeaver MDM

Java Connector 7.1 SP4

Required MDMJAVAAPI04_

xxx.SCA



m/installmdm71

Development and

Customization MDM Java

and .NET APIGetting

StartedGetting Started

with Java API Installing

and Referencing the MDM

Connector.

SAP Enhancement

Package 4 for SAP ECC

6.0

(Enterprise Services)

Required For more information, see

the section below this table.

For demonstrations or proof-

of-concept (POC) purposes,

you can use the SAP ES

Workplace (you will need to

register on the SAP

Developer Network (SDN) at:

http://sdn.sap.com/ir

j/sdn/soareg)
http://service.sap.com/installmdm71http://service.sap.com/installmdm71http://help.sap.com/saphelp_nwmdm71/helpdata/en/4a/de4b01fcb42472e10000000a42189c/frameset.htmhttp://help.sap.com/saphelp_nwmdm71/helpdata/en/4a/de4b01fcb42472e10000000a42189c/frameset.htmhttp://help.sap.com/saphelp_nwmdm71/helpdata/en/4a/de4b01fcb42472e10000000a42189c/frameset.htmhttp://help.sap.com/saphelp_nwmdm71/helpdata/en/4a/b90771f2b93d86e10000000a421937/frameset.htmhttp://help.sap.com/saphelp_nwmdm71/helpdata/en/4a/b90771f2b93d86e10000000a421937/frameset.htmhttp://service.sap.com/installmdm71http://service.sap.com/installmdm71http://help.sap.com/saphelp_nwmdm71/helpdata/en/49/06eac7dc78132ee10000000a421937/frameset.htmhttp://service.sap.com/installmdm71http://service.sap.com/installmdm71http://help.sap.com/saphelp_nwmdm71/helpdata/en/49/06eac7dc78132ee10000000a421937/frameset.htmhttp://service.sap.com/installmdm71http://service.sap.com/installmdm71http://service.sap.com/installmdm71http://service.sap.com/installmdm71http://help.sap.com/saphelp_nwmdm71/helpdata/en/49/06eac7dc78132ee10000000a421937/frameset.htmhttp://service.sap.com/installmdm71http://service.sap.com/installmdm71http://help.sap.com/saphelp_nwmdm71/helpdata/en/49/06eac7dc78132ee10000000a421937/frameset.htmhttp://service.sap.com/installmdm71http://service.sap.com/installmdm71http://help.sap.com/saphelp_nwmdm71/helpdata/en/4a/b90771f2b93d86e10000000a421937/frameset.htmhttp://help.sap.com/saphelp_nwmdm71/helpdata/en/4a/b90771f2b93d86e10000000a421937/frameset.htmhttp://help.sap.com/saphelp_nwmdm71/helpdata/en/4a/de4b01fcb42472e10000000a42189c/frameset.htmhttp://help.sap.com/saphelp_nwmdm71/helpdata/en/4a/de4b01fcb42472e10000000a42189c/frameset.htmhttp://help.sap.com/saphelp_nwmdm71/helpdata/en/4a/de4b01fcb42472e10000000a42189c/frameset.htmhttp://service.sap.com/installmdm71http://service.sap.com/installmdm71


10/44


May 2010

5

Installing SAP NetWeaver Composition Environment (CE) 7.1 EHP1 SP04

Any customer with a valid SAP Service Marketplace User ID license can download the SAP

NetWeaver 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).

Note

Links to the installation documentation can be found on the Info pagebelow theapplication name.

You can also download a Preview Versionfrom SAP Developer Network (SDN) athttp://www.sdn.sap.com/irj/sdn Downloads EHP1 for SAP NetWeaver Composition

Environment 7.1 - Preview Version.

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

Note

Update to the highest Support Package (SP)

Inst al l ing SAP NetWeaver Developer St udio (NWDS)

If not already available, download and install a NWDS matching the SAP NW CE EHP1 installation

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

Note

Links to the installation documentation can be found on the Info pagebelow 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/swdchttp://service.sap.com/swdchttp://www.sdn.sap.com/irj/sdnhttp://www.sdn.sap.com/irj/scn/downloads?rid=/library/uuid/00846edd-355b-2b10-f38c-df94ec96eb74http://service.sap.com/swdchttp://service.sap.com/swdchttp://service.sap.com/swdchttp://service.sap.com/swdchttp://service.sap.com/swdchttp://service.sap.com/swdchttp://www.sdn.sap.com/irj/scn/downloads?rid=/library/uuid/00846edd-355b-2b10-f38c-df94ec96eb74http://www.sdn.sap.com/irj/sdnhttp://service.sap.com/swdc


11/44


May 2010

6

3. Continue navigating on the main web page as follows: SAP Application Components SAP

ERP SAP ERP Enhance Package EHP4 FOR SAP ERP 6.0

3.2 T rust ed Con ne ct i on s

The 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 server

where the MDM Java API is deployed, and the server where MDM is running.

For more information on how to define a trusted connection, see

http://service.sap.com/installmdm71 Development and Customization MDM Web

Dynpro Components Guide Defining a Trusted Connection

4 . Conf igur ing t he Qu ic k Sta r t er Envi ronmen t

4.1 In t roduc t ion

This section contains the necessary steps required to configure and run the MDM Quick Starter for

Collaborative Material Master Data Creation.

Make sure that your Quick Starter package contains the following:

Component File Name More Information

MDM Quick Starter

(QS) Material

Repository

MDM_QS_Material_Repository_7.1SP4.a2a Unarchive this file and load it on

to your MDS.

The MDM QS Material repository

is based on the Material MDMBusiness Content repository.

For more information about the

Material repository, see

https://websmp104.sap-

ag.de/installmdm71 MDM

Business ContentMaterial

SAP Note 1355137
http://service.sap.com/installmdm71http://help.sap.com/saphelp_nwmdm71/helpdata/en/4a/8c20a0dc93203be10000000a42189b/frameset.htmhttps://websmp104.sap-ag.de/installmdm71https://websmp104.sap-ag.de/installmdm71https://websmp104.sap-ag.de/installmdm71https://websmp104.sap-ag.de/installmdm71http://help.sap.com/saphelp_nwmdm71/helpdata/en/4a/8c20a0dc93203be10000000a42189b/frameset.htmhttp://service.sap.com/installmdm71


12/44


May 2010

7

Component File Name More Information

MDM Quick Starter MDMBPMMATE04_x.sca Deploy the MDM Quick Starter

SCA file into your SAP

NetWeaver Application Server

Java (AS Java). This SCA file

contains the following:

An MDM Material Quick

Starter Process

Development Component

(DC)

A custom MDM Web

Dynpro Development

Component

A stand-alone MDM Web

Dynpro Development

Component running on the

Portal

MDM Quick Starter

Web Service

MDM_QS_Material_WS_7.1SP4.ear Deploy this MDM Quick Starter

EARfile into your SAP

NetWeaver Application Server

Java (AS Java). The file contains

the MDM Web Service which was

generated from the MDM Web

Service Generator on top of the

Material MDM Business Content

repository.

MDM Web Dynpro

Configuration XML

file

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: Impor t ing t he MDM Quick Star t er Por ta l Content Archive Fi le

Info

This step adds the Request Formto 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 Material

folder is created in the Portal.

5. To view the folder, in the Portal, choose Content Administrationand then navigate in the Portal

Catalog to Portal Content Content Provided by SAP packages MDM QuickStarter

Material.


13/44


May 2010

8

Note

If you want to change the sort order so that the Hometab is the first Top LevelNavigation (TLN) entry point, you can modify the Sort Order Priorityproperty for theHomeworkset, 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 Start er (QS) Roles

Info

Each 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 Administratorpermissions.

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 Ac t ions for the MDM QS Roles

Info

This step defines specific permissions for each QS role.


14/44


May 2010

9

Action Description Roles

MDM_Material_Creation_Request Permission to view the

Request New Material

Form


MDM_Business_User

MDM_WD_CONFIGURATOR Permission to configure

Web Dynpro components

using the MDM Web

Dynpro Configurator


MDM_WS_Generator Permission to generate

MDM Web services using

the MDM Web Service

Generator


Step 4: Assign Roles to Us ers

User Assigned Role

All MDM QS Users Every User Core Role

BPEM End User

MDM QS Super User MDM_Process_SuperUser


15/44


May 2010

10

User Assigned Role

MDM QS Business User MDM_Business_User

Master Data Management

Note

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

Tip

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


16/44


May 2010

11

Step 5: Assign the SAP_BPM_SuperAdmin ro le to t he defaul t SAP NetWeaver Guest

User

Info

To enable the Web service call to start the BPM process, assign theSAP_BPM_SuperAdmin role to the default SAP NetWeaver Guestuser (see screen

capture below)

Step 6: Create Use rs in MDM

Info

This 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 Dest inat ion

Info

You 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, see

http://service.sap.com/installmdm71 Development and Customization MDM Web

Dynpro 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 Datastep, the Destination Nameis MDM_QS_Material.
http://service.sap.com/installmdm71http://help.sap.com/saphelp_nwmdm71/helpdata/en/4a/cdd7c31ca822ace10000000a42189b/frameset.htmhttp://help.sap.com/saphelp_nwmdm71/helpdata/en/4a/cdd7c31ca822ace10000000a42189b/frameset.htmhttp://service.sap.com/installmdm71


17/44


May 2010

12

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

Step 8: Impor t the MDM Web Dynpro Conf igurat i on

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

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

User r o l e .

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 and

CustomizationMDM Web Dynpro Components Guide Transporting.

The direct link is: Transporting.
http://service.sap.com/installmdm71http://help.sap.com/saphelp_nwmdm71/helpdata/en/4a/72ebd6056d61a4e10000000a421937/frameset.htmhttp://service.sap.com/installmdm71


18/44


May 2010

13

Step 9: Create Comm unicat ion Prof i les

Info

By 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 Administratorpermissions.

2. Navigate to SOA Management Technical Configuration System Connections.

3. Select Communication Profiles.

4. Choose Newto open the New Profilewizard.

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

MDM Web Services

MDM QS BPM

SAP ECC Enterprise Services


19/44


May 2010

14

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

MDM Web Servic es

Step 1: General

Enter MDM_WS as the Profile Nameand

enter a Profile Description.

Step 2: Security

Select Noneas the Authenticationmethod.

Step 1: General

Step 2: Security

MDM QS BPM

Step 1: General

Enter MDM_QS_BPM_WS as the ProfileNameand enter a Profile Description.

Step 2: Security

Select Noneas the Authenticationmethod.

Step 1: General

Step 2: Security

See screen capture above (for MDM Web Services)


20/44


May 2010

15

SAP ECC Enterpr ise Servic es

Step 1: General

Enter SAP_ES as the Profile Nameand

enter a Profile Description.

Step 2: Security

Select all the authentication options.

Step 1: General

Step 2: Security

7. Choose Finish.

Step 10: Create Provider Syst ems

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 Newto launch the New Provider Systemwizard.


21/44


May 2010

16

5. Create a provider system for:

MDM BPM Web Service

Note

This Web service starts the MDM Material Creation Process.

MDM Web Service

SAP ECC Create Material Basic DataEnterprise Service

SAP ECC Change Material Basic DataEnterprise Service

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

MDM BPM Web Servic e

Step 1: Provider System

Select the Javaradio button.

Enter QSS as the System Name.

Enter the name of your Web

Application 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 Profile

Name.

Step 4: Services Search Settings

Select Single Service.

Enter the following WSDL URL:

http://:/mdm/bpem/demosapcom2

Fmdm2Fqs2Fmaterial2Fproces

s2FPool2FMaterialCreation6

ab68d036d4c26e856f16b9b594

55176?wsdl&mode=ws_policy





22/44


May 2010

17

MDM Web Servic e


Select the Javaradio button.

Enter MDMas the System Name.

Enter the name of your Web

Application 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 JAVA

httpport>/MDM_Material/HTT

PNone?wsdl&style=document&

mode=ws_policy

Steps 1 and 3:

SAP ECC Create Material Basic DataEnterpr ise Service


Select the ABAPradio button.

Enter ES1 as the System Name.

Enter the Host, Client, and

Installation Numberof your ECC.

Enter a System Description.


Enter User Name and Password


Enter SAP_ERP_ES as the Profile Name.



Enter the correct WSDL URL for

Create Material Basic Data ESfor

your ESS system.

Steps 1 and 3:


23/44


May 2010

18

SAP ECC Change Material Basic DataEnterpr ise Servic e


Same as above for Create Material Basic

Datawith the following changes:.

In step 1, enter ES2 as the System

Name.

In step 4, enter the correct WSDL

URL for Change Material Basic

Data ESfor your ESS system.

Step 11: Define a User Name and Passw ord for ECC Ente rpr ise Servic es


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

Management.

3. Choose the Maintenancetab.

4. Choose Newto open the New User Accountwizard.

5. Complete the wizard as follows:

Step 1 General

The name of the ECC is ECC_ES_Material.


24/44


May 2010

19

Step 2 Credentials

Choose WebService Security and Systemkey for both Web Service Securityand forHTTPs.

6. Choose the Assignmenttab.

7. Choose New to open the New User Account Assignmentwizard.

8. Complete the wizard as follows:

Step 1: User Account

Choose the User Accountthat you created in step 5 above.


25/44


May 2010

20

Step 2: Provider

Choose the ES1 provider system for the Create Material Basic Dataand then repeat this step

and choose ES2 provider system for the Change Material Basic Data.

Step 12: Configure a Prox y

Info

Configure 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 Proxytab.

4. Enter the proxy Hostand Portnames.


26/44


May 2010

21

5. Check Bypass proxy server for local addresses.

6. Choose Save.

7. Choose the WS Navigatortab.

8. Enter an asterisk (*) in the Allowed Hostsfield.

Note

This 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 Mater ia l DC

Info

For 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 Application

Communication.

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

of the screen.


27/44


May 2010

22

4. Choose Editand 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. Saveyour settings.

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

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

Note

To 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 Application

Communication.


28/44


May 2010

23

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

the top of the screen.

4. Choose Editand 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. Saveyour settings.

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

Step 15: Define t he MDM Web Servic e User...


2. Navigate to Configuration Management Infrastructure Java System Properties.

3. Choose the Applications tab.

4. Highlight the MDM_Material_ENTAPP application in the Detailspane.

5. Choose WS.RunTime.Mdm.User from the Extended Detailspane.


29/44


May 2010

24

6. Choose Modify.

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

8. Choose Save As.

5 . Ho w t o Ex t e n d t h e MDM Qu ic k St a rt e r a nd

Develop a Cust om ized Proc ess

You can extend the MDM Quick Starter Material implementation and create your own customized

implementation. The MDM Quick Starter release contains the source code, so you can import the

source code into your local workspace and continue developing the MDM Material process on top of

the MDM Quick Starter release.

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

Step 1: Impor t the SCA Fi le...

1. In the SAP NetWeaver Developer Studio (NWDS), choose the Development Infrastructure

perspective as follows:

Window Open Perspective OtherDevelopment Infrastructure.

2. In the Component Browserchoose the LocalDevelopmentnode.

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

a. In the context menu of the LocalDevelopmenttrack, choose Import SC to open the

Import SC from Filescreen.


30/44


May 2010

25

b. Locate the SCA file using the Browsebutton.

c. Choose Finish. The import is complete. You can see the components with the SC

technical name that have been created, under the node.


31/44


May 2010

26

4. To work with the imported components, you need to create a new project for each of the

Development Components. From the context menu of each development component, choose

Sync/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 Dynpro

components:

Custom

A Web Dynpro componentconsisting of an Enrich andApproveBPM activity wrapped in an MDM ItemDetails Web Dynprocomponent

Notification

A Web Dynpro componentfor a notification activity


32/44


May 2010

27

Development Component Name Type Description

mdm/qs/material/functions/ear Enterprise

Application

Contains the

mdm/qs/material/functions/

ejb module

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

functions

mdm/qs/material/process Process

Composer

Contains the MDM material

creation processes

mdm/qs/material/standalone/secu

rity

UME

Permissions

Contains the security action

definition for the material request

form

mdm/qs/material/standalone Web Dynpro Contains the stand-alone Web

Dynpro component, which is the

material requester form

Step 2: Solve t he Dependency Errors

6. Choose the Development Infrastructureperspective.7. In the context menu of the LocalDevelopmentnode, choose Import SC....

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

9. Choose Finish.


33/44


May 2010

28

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


34/44


May 2010

29

11. Refresh the LocalDevelopmentnode to see the added SCA file.

12. Highlight the MDM-BPM-MATERIAL-SAMPLE SCA and select the Dependenciestab in the

Component Propertiesperspective.

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.


35/44


May 2010

30


36/44


May 2010

31

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


37/44


May 2010

32

6.1 New Mat er i al Request

User Interface

This step consists of a custom wrapper application (New Material Request Form) that includes the

following elements:

Embedded MDM Item Details Web Dynpro component

MDM Search popup page (when choosing Searchon the UI). The popup page consists of MDM

Search, Result Set, and Item Details Web Dynpro components. A custom Use as template

button was added to the search page.

An application consisting of a Notesarea

The above mentioned MDM Web Dynpro components are configured in the MDM Web Dynpro

Configurator and can be adapted to suit any business scenario. For example, you can choose which

fields to display on the user interface of the Web Dynpro component (you choose from a list of fields in

the MDM repository).

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

Components Guide.


38/44


May 2010

33

Note

When 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 errorsandcontinue with the material creation request without entering values in the fields.

.

Procedure

A 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 Business

User role.

Tip

Instead of logging on to the portal, you can run the New Material Request Formas astand-alone application using the following URL:

http://:/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 record

exists. If so, you can choose Use as templateto copy the values of the similar record to your

New Material Request Form.

CAUTION

Not 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 are

ignored.

3. Choose Editnext 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 the

copied record).

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

6. Choose Submit Requestto initiate the BPM process.


39/44


May 2010

34

Functionality

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

1. A record is created as a checked out as newrecord 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 the

Data Stewards UWL inbox.

6.2 Enr ic h and Approve

User Interface

This step consists of a custom wrapper application that uses the MDM Web Dynpro Search, Result

Set, and Item Details components as used components.

The user interface consists of:

An embedded MDM Item Details Web Dynpro component with configured Approve, Reject, and

Searchbuttons.

An MDM Search popup page (when choosing Searchon the UI) consisting of MDM Search,

Result Set, and Item Details Web Dynpro components. A custom Use as templatebutton was

added to the search page. A Notesarea and an Errorsarea.


40/44


May 2010

35

Procedure

The Enrich and Approvestep 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 materialscreen.

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 Use

as templateto copy the values of the similar record to the New Material Request Form

and update the values accordingly.

Choose Editnext to each field to change a value. The popup window for each field

includes a list of values that exist in the MDM repository.

5. Saveyour changes.

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

Note

The validations are configured in the MDM Web Dynpro Configurator. For moreinformation, see http://service.sap.com/installmdm71 MDM Web Dynpro

Components 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 Noteslink in theBPM standard task bar.

BPM standard task bar

Canc el t hec rea tenewmate ri a l requesto rA pprov es tep ,s avec hanges andmov e the reques t to thenextB P Ms tep fo rrev i ewby reques to r.

Canc el t hec rea tenewmate ri a l requesto rA pprov es tep ,s avec hanges andmov e the reques t to thenextB P Ms tep fo rrev i ewby reques to r.

FuntionalityWhen the Data Steward chooses Approvethe 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 process

to the next task and a new BPM task (Review and Confirm) is added to the Business Users

UWL inbox.

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

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

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

deleted from the MDM repository.


41/44


May 2010

36

3. The BPM process is terminated.

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

6.3 Review and Conf i rm

User Interface

This step consists of a custom Web Dynpro wrapper application, with an MDM Web Dynpro Item

Details component in read-only mode.

Procedure

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

1. Review the changes made by the Data Steward.

2. Confirmor Rejectthe 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 and

Approvetask in his UWL inbox.

6 .4 Cr ea t i on o f Mate ri al i n ECC

If the creation in ECC fails, the Data Steward once again receives the Enrich and Approvetask in his

UWL inbox. In the Errorspane 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 Web

Services, which updates the material ECC remote key and checks in the MDM material record. If one

of the Web Service calls fails, the Data Steward receives the Enrich and Approvetask in his UWL

inbox with a list of errors in the Errorspane.


42/44


May 2010

37

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 lookup

record IDs.

For each lookup field defined, MDM Web services are intiated to obtain the relevant lookup record

codes. 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 Services

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

There are two Enterprise Service calls:

Create Basic Data


43/44


May 2010

38

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 created

records remote key.


44/44


6 .5 Final izing the MDM Crea t ion Process

The final MDM creation process consists of the following three automated steps using MDM Web

services:

Join Check Out

Update Key Mapping

Check In

6.6 Not i f ic at ion

The Business User who initially made the request is notified of the available data and receives a

notification in his UWL inbox.

quick starter guide for collaborative material master data creation

Documents