SAP How To Guide for Material How To Master Data Governance for Material BA d I Definition USMDSSWDYNAMICAGENTSELECT for flexible user determination Applicable Releases EhP5 EhP6 M ID: 824045
Download Pdf The PPT/PDF document "Master Data Governance" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
SAP How-To Guide Master Data Go
SAP How-To Guide Master Data Governance for Material How To... Master Data Governance for Material: BAdI Definition USMD_SSW_DYNAMIC_AGENT_SELECT for flexible user determination Applicable Releases: EhP5, EhP6, MDG6.1 Version 1.3 August 2013 © Copyright 2013 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, p
Series, xSeries, zSeries, z/OS, AFP, In
Series, 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 Microsyst
ems, Inc., used under license for techn
ems, 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 warranti
es for SAP Group products and services
es 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 material
s and does not endorse your use of thir
s 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 correc
tness and completeness of the Code giv
tness 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 History Document Version Description 1.00 First official release of this guide 1.10 Note 1700197 1.20 Note 1837696 1.30 More detailed explanation of BRF+-tables and BAdI-parameters Typographic Conventions Type Style Description
Example Text Words or characters qu
Example Text Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Cross-references to other documentation Example text Emphasized words or phrases in body text, graphic titles, and table titles Example text File and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Example text User entry texts. These are words or characters that you enter in the system exactly as they appear in the documentation. �text Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER. Icons Icon Description Caution Note or Imp
ortant Example Recommendation
ortant Example Recommendation or Tip Table of Contents 1. Business Scenario............................................................................................................... 1 2. Background Information ..................................................................................................... 1 3. Prerequisites ........................................................................................................................ 1 4. Step-by-Step Procedure ...................................................................................................... 2 4.1 Customizing .................................................................................................................. 2 4.1.1 Create new Change Request Type ................................................................. 2 4.1.2 Defi
ne Service Names .....................
ne Service Names ..................................................................................... 2 4.1.3 BRF+ Tables .................................................................................................... 3 4.2 Enhancement Spot USMD_SSW_SERVICE_PROCESSOR ...................................... 6 4.2.1 Create Enhancement Implementation ............................................................. 7 4.2.2 Create BAdI Implementation ............................................................................ 8 4.2.3 Create Filter ..................................................................................................... 8 4.2.4 Method IF_USMD_SSW_DYNAMIC_AGT_SELECT~GET_DYNAMIC_AGENTS ...... 8 4.2.5 Maintain your Z-Table ...................................................................................... 9 4.3 Check
Workflow Log ........................
Workflow Log ................................................................................................... 10 How To... Master Data Governance for Material:BADI Definition USMD_SSW_DYNAMIC_AGENT_SELECT for flexible user determination BAdI USMD_SSW_DYNAMIC_AGENT_SELECT July 2013 1 1. Business Scenario SAP Master Data Governance for Material (MDG-M) provides business processes to find, create, change, and mark material master data for deletion. It supports the governance of material master data in a central hub and the distribution to connected operational and business intelligence systems. The processes are workflow-driven and can include several approval and revision phases, and the collaboration of all users participating in the master data maintenance. MDG-M uses the rule-based workflow. The user agent decision table determines the agents. This scenario addre
sses the customer requirement to have a
sses the customer requirement to have a more flexible user determination de-pendent on own coding. 2. Background Information A BAdI is used to add customer specific coding and tables. You can use this BAdI to implement dynamic agent selection in the rule-based workflow. Therefore in addition to rules that have been predefined, with this BAdI you can change agent values in the work-flow by creating your own programs. This BAdI uses the method GET_DYNAMIC_AGENTS. The input for this BAdI is the change request number and the service name. By using the change request number, it is possible to access all data within this change request. The input parameter Service Name enables you to use the same BAdI implementation for multiple service names. For example, when two service names are used in the configuration of the same change request workflow, and the user wants to create only one BAdI implemen
tation, having the service name as the
tation, having the service name as the input parameter enables you to separate the processing logic based on the ser-vice name input. Requirements You have defined the filter value Service Name in the view V_USMD201C_SSW. You need to create a separate implementation for your specific dynamic agent selection step. Standard settings For more information about the standard settings (filters, single or multiple uses), see the Enh. Spot Element Definitions tab in the BAdI Builder (transaction SE18). No default BAdI implementation is preactivated in the standard system. The BAdI is filter-dependent. The BAdI is not designed for mul-tiple uses. 3. Prerequisites Relevant SAP Notes: 1597746 1700197 1837696 How To... Master Data Governance for Material:BADI Definition USMD_SSW_DYNAMIC_AGENT_SELECT for flexible user determination BAdI USMD_SSW_DYNAMIC_AGENT_SELECT July 2013
2 4. Step-by-Step Procedure
2 4. Step-by-Step Procedure 4.1 Customizing 4.1.1 Create new Change Request Type ... How To... Master Data Governance for Material:BADI Definition USMD_SSW_DYNAMIC_AGENT_SELECT for flexible user determination BAdI USMD_SSW_DYNAMIC_AGENT_SELECT July 2013 3 4.1.2 Define Service Names 4.1.3 BRF+ Tables Use customizing or transaction USMD_SSW_RULE - Process Definition of RBWF How To... Master Data Governance for Material:BADI Definition USMD_SSW_DYNAMIC_AGENT_SELECT for flexible user determination BAdI USMD_SSW_DYNAMIC_AGENT_SELECT July 2013 4 4.1.3.1 Single Value Decision Table 4.1.3.2 User Agent Decision Table If the condition alias is not used elsewhere within single value decision table without dynamic agent selection service it is not necessary to add an entry into the user agent decision table. In this case the BAdI-m
ethod GET_DYNAMIC_AGENTS is called wi
ethod GET_DYNAMIC_AGENTS is called with empty parameter CT_USER_AGENT_GROUP andâhasâtoâbeâfilledâwithinâtheâBAdIâ(donâtâforgetâtoâfillâfieldsâAGENT_GROUP and STEP_TYPE). If one or more entries are defined parameter CT_USER_AGENT_GROUP is filled with these entries and you are responsible to process them as required within the BAdI-method. How To... Master Data Governance for Material:BADI Definition USMD_SSW_DYNAMIC_AGENT_SELECT for flexible user determination BAdI USMD_SSW_DYNAMIC_AGENT_SELECT July 2013 5 4.1.3.3 Non-User Agent Decision Table Decision table is not relevant for dynamic user agent selection service! ... How To... Master Data Governance for Material:BADI Definition USMD_SSW_DYNAMIC_AGENT_SELECT for flexible user determination BAdI USMD_SSW_DYNAMIC_AGENT_SELECT July 2013 6 4.2 Enhancement Spot USMD_SS
W_SERVICE_PROCESSOR Customizing:
W_SERVICE_PROCESSOR Customizing: Or use transaction SE18 - Business Add-Ins: Definitions ... How To... Master Data Governance for Material:BADI Definition USMD_SSW_DYNAMIC_AGENT_SELECT for flexible user determination BAdI USMD_SSW_DYNAMIC_AGENT_SELECT July 2013 7 4.2.1 Create Enhancement Implementation How To... Master Data Governance for Material:BADI Definition USMD_SSW_DYNAMIC_AGENT_SELECT for flexible user determination BAdI USMD_SSW_DYNAMIC_AGENT_SELECT July 2013 8 4.2.2 Create BAdI Implementation 4.2.3 Create Filter How To... Master Data Governance for Material:BADI Definition USMD_SSW_DYNAMIC_AGENT_SELECT for flexible user determination BAdI USMD_SSW_DYNAMIC_AGENT_SELECT July 2013 9 4.2.4 Method IF_USMD_SSW_DYNAMIC_AGT_SELECT~GET_DYNAMIC_AGENTS For the interface method you can use and adapt the code from example enhanc
ement implementation MDG_BS_MAT_SEL
ement implementation MDG_BS_MAT_SELECT_AGENT (Example implementation: Dynamic agent select). Implementing class is CL_MDG_BS_MAT_SELECT_AGENT that has interface method IF_USMD_SSW_DYNAMIC_AGT_SELECT~GET_DYNAMIC_AGENTS and private method READ_MATERIAL. Attention: the example code wonât change the entries of table parameter CT_USER_AGENT_GROUP that has been filled with role SAP_MDGM from the user agent decision table (see â4.1.3.2). How To... Master Data Governance for Material:BADI Definition USMD_SSW_DYNAMIC_AGENT_SELECT for flexible user determination BAdI USMD_SSW_DYNAMIC_AGENT_SELECT July 2013 10 4.2.5 Maintain your Z-Table 4.3 Check Workflow Log With transaction SWI6 you are able to check whether the dynamic user agent selection service BAdI has been called and returned the desired result. www.sdn.sap.com/irj/sdn