Develop a Common Process for Single and Mass Processing in MDGF

SAP COMMUNITY NETWORK scn.sap.com

2012 SAP AG 1

Develop a common process for

single and mass processing in

MDGF

Applies to:

MDGF in ECC 6.0 EhP5/EhP6

Summary

In MDG(F) the standard change requests provide the possibility to the requester maintain master data in case of a single object change request. For multi object change requests, the requester can just define the IDs of the master data records that he wants to be changes.

This document shows how to enhance the standard MDGF workflow in order to have a common process flow for the requester by enabling data maintenance for multi object change requests

Author: Ren Klumberg

Company: SAP Switzerland

Created on: 13 November 2012

Author Bio

Ren Klumberg is working for SAP as a senior technology consultant. In the last 5 years he focused on master data management topics in various implementation projects. In his projects he covers various roles from business process expert to solution architect and project manager.

Technology wise he provides expert knowledge in SAP MDG, SAP NW MDM, SAP NW Portal and SAP NW PI.

Develop a common process for single and mass processing in MDGF


2012 SAP AG 2

Table of Contents

Copy the workflow .............................................................................................................................................. 3

Enhance the copied workflow ............................................................................................................................. 4

Create custom class ........................................................................................................................................ 4

Call custom method from workflow ................................................................................................................. 6

Evaluate result .............................................................................................................................................. 10

Copy activities ............................................................................................................................................... 11

Related Content ................................................................................................................................................ 12

Copyright........................................................................................................................................................... 13



2012 SAP AG 3

Copy the workflow

In order to provide a data maintenance step for the requester you should first of all create a copy of delivered MDGF workflow WS75700040. This can be done in transaction SWDD by opening the workflow and the saving it using save as.



2012 SAP AG 4

Enhance the copied workflow

Create custom class

In our new workflow we want to do a check whether it is a single or a multi object workflow. If it is a multi-object workflow, we will add an additional step to provide the possibility to the user to maintain data. In order to identify the workflow type we create a custom ABAP class using SE24.

You can do this in e.g. SE80 via the context menu.

As the class will be called from our workflow, you have to add the interface IF_WORKFLOW:

Now you can add a new method to your class. This should be Static Public.



2012 SAP AG 5

As import parameter we will receive the change request id. As outbound parameter we will just provide a flag that we set to X if the change request is a single object one.

The method will read the change request type and the checks the MDG customizing. The sample code can be seen below:

METHOD cr_single_object.

DATA: lo_gov_api TYPE REF TO if_usmd_gov_api.

DATA: ls_crequest TYPE usmd_s_crequest.

data: ls_crtype type USMD110C.

*TRY.

CALL METHOD cl_usmd_gov_api=>get_instance

EXPORTING

iv_model_name = '0G'

* iv_classname = 'CL_USMD_GOV_API'

RECEIVING

ro_gov_api = lo_gov_api.

* CATCH cx_usmd_gov_api .

*ENDTRY.

*TRY.

CALL METHOD lo_gov_api->if_usmd_gov_api_cr_data~get_crequest_attributes

EXPORTING

iv_crequest_id = crequest

RECEIVING

rs_crequest = ls_crequest

.

* CATCH cx_usmd_gov_api_core_error .

* CATCH cx_usmd_gov_api .

*ENDTRY.

select single * from usmd110c into ls_crtype where USMD_CREQ_TYPE = ls_crequest-

USMD_CREQ_TYPE.

if sy-subrc = 0.

SINGLE_OBJECT = ls_crtype-USMD_SINGLE_OBJ.

endif.

ENDMETHOD.



2012 SAP AG 6

Call custom method from workflow

In order to be able to process our code, we have to add a new activity to our workflow. This activity will call our method.

Drag and drop a new activity directly after the start event



2012 SAP AG 7

Enter the activity and create a task. The task should be defined as shown below.



2012 SAP AG 8

Then you have to define the binding. This has to be done twice. From the activity to the task and from the task to the method. But before this is possible you have to add a container element to the workflow.



2012 SAP AG 9



2012 SAP AG 10

Evaluate result

Now we know in the workflow whether we have a single or a multi object change request. The next step is to evaluate the result. Therefor you have to drag and drop a condition to the workflow.

Add the condition to the activity and define the outcomes.



2012 SAP AG 11

Copy activities

Now we can add the additional maintenance step to the workflow. This can easily be done by copying the two existing activities and pasting them into the multi branch.

Now enter the Execution of Changes activity and change the agent assignment in order to route the workflow back to the requester.



2012 SAP AG 12

Related Content

For more information about MDG(F) please check the following documents:

Sending an Email notification during the governance process

SAP How-To Guide Develop a Custom Master Data Object in SAP Master Data Governance (ERP 6 EhP 5 and EhP 6)

Monitoring cross-system workflows with SAP Process Observer



2012 SAP AG 13

Copyright

Copyright 2012 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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

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 Oracle Corporation.

JavaScript is a registered trademark of Oracle Corporation, used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

Date post:	17-Oct-2015
Category:	Documents
Upload:	harsha
View:	73 times
Download:	1 times

Develop a Common Process for Single and Mass Processing in MDGF

Documents