How To... MDG-S: Dynamic Workflow Processing based on changes to bank details This Guide is also valid for MDG-C and MDG-BP (Data Model BP) Applicable Releases: MDG7.0 and Later Version 1.0 Jan 2017How To... MDG-S: Dynamic Workflow Processing based on changes to bank details © Copsright 2017 SAP AG. All rights reserved. ‘No part ofthis 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 icrosoft Corporation. IBM, DB2, DB2 Universal Database, 03/2, Parallel Sysplex, MVS/ESA, AIX, 8/390, AS/400, 0S/390, (05/400, iSeries, Series, xSeries, zSeries, 2/05, AFP, Intelligent Miner, WebSphere, Netfinity, Tol, Informix, 45/08, POWER, POWERS, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. ‘Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or reistered trademarks of Adobe ‘Systems Incorporated inthe United States and/or other countries. Oracle isa registered trademark of Oracle Corporation. ‘UNIX, X/Open, OSF/s, and Motif are rezistered trademarks ofthe Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, ‘WinFrame, VideoFrame, and Mulin are trademarks or registered trademarks of Citrix Systems, Inc. HITML, XOML, XHTML and WC are trademarks or registered trademarks of W3CB, World Wide Web Consortiur, Massachusetts Institute of Technology. Java's a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Ine. used under Heense for technology invented and iamplemented by Netscape. DlaxDB isa trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.oom, xApps, xApp, SAP ‘NetWeaver, and other SAP products and services ‘mentioned herein as wel as their respective logos are trademars or registered trademarks of SAP AG in Germany and in several other countries all ver the world. All other product and service names mentioned are the ‘trademarks oftheir respective companies. Data contained {in this document serves informational purpoces only. National product specifications may vary. ‘These materials are subject to change without notice, ‘These materials are provided by SAP AG and its afiiated ‘companies (‘SAP Group’) for informational purposes onl, ‘without representation or warranty of any kind, and SAP ‘Group shall not be liable for errors or omissions with respect tothe materials, The only warranties for SAP ‘Group products and services are those that are st 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 “a 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 nt be liable for damages ofany kind including ‘without limitation direc, special, indinec, or consequential damages that may result from the use ofthese material. SAP doesnot warrant the accuracy or completeness ofthe 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 procedure typically are explained ina practical business context, it is not implied that those features and procedures ae the only approach in solving specific business problem using SAP NetWeaver. Should ‘you wish o receive additional information, danifcation 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 ‘ot intended to be used in a productive system ‘environment. The Code is only intended better explain and visualize the syntax and phrasing rls of certain coding. SAP does not warrant the correctness and completeness of ‘the Code given herein, and SAP shall not be linble for cervors or damages caused by the usage ofthe Code, except sfsuch damages were caused by SAP intentionally or ose negligent Disclaimer Some components ofthis product ae based on Java™. Any ‘code change in these components may cause unpredictable and severe malfunctions and is therefore expressively ‘robiited, as is any decompilation of these components. Any Java™ Source Code delivered with this products only tobe used by SAP's Support Services and may not be ‘modified or altered in any way.www.sap.com Document History Document Version Description 1.00 First official release of this guideHow To... MDG-S: Dynamic Workflow Processing based on changes to bank details TABLE OF CONTENTS 1. BUSINESS SCENARIO. 2. PREREQUISITES. 3. INTRODUCTION wnssnnnnmnnnnnnnininnnnnnnninnninnnnnnnnnnnnnnnninnnannnnnnnnnnsnn 5 3.1. STORY BOOK... 3.2, HIGH LEVEL STEPS 4. STEP-BY-STEP EXPLANATION .nnnssnntsnmnnnninnnnnnnnnnnnnnninnnnnninnnainnnninnninnssnn 6 4.1, CREATE NEw CuaNGe REQUEST TyPE 6 4.2. _ IMPLEMENTATION OF BADI 7 4.3. CREATE ABAP DICTIONARY OBIECTS snsonnnnnnnnn son eon 10 4.4. MODELING BRF+ ELEMENTS AND THE PROCESS FLOW IN BRE a 4.5. IMPLEMENT ABAP c1ass, v7 46, Test 20 2 5. REMARKS..How To... MDG-S: Dynamic Workflow Processing based on changes to bank details 1. BUSINESS SCENARIO SAP Master Data Governance for Supplier (MDG-S) provides business processes to find, create, change, and mark supplier master data for deletion. It supports the governance of supplier master data on a central hub ang the distribution of supplier master data to connected operational and business intelligence systems. ‘The processes ere workflow-driven and can include several approval and revision phases, including collaboration between all users participating in master data maintenance. The workflows which are delivered in MDG-S standard are classic workflows and do support most of the existing business use cases such as: = Approval of global relevant attributes ~ Parallel processing based on organizational units - Final approval by organizationel unit. ‘Sometimes the business requirements are different, and the classic workflow templates shipped by SAP do not fit to the customer needs. Because of that, customers can also use the Rule-Based Workflow template (RBW) which gives full fiexibility for the workflow modeling. This is done by maintaining BRF+ decision tables. SAP MDG delivers this RBW Template as standard and it can be used in MDG-S (and MDG-C). It is integrated into the SAP MDG customizing (Shortcut: mdgimg). Based on this template itis possible to have dynamic workflow routing based on values entered during runtime by the user. This How-To guide shows how to use these capabilities and how to implement such requirements. The ‘example scenario we are using is the following: An existing supplier can be changed using SAP MDG-S without any approval. Only if the bank details have been changed an approver must review the changes done by the requestor. The following graphic shows you the process flow in a simplified way. a sem sore pee With the Rule-Based Workflow (RBW) you can modal all forms of rejections, parallel processing, and more complex flows. These are not part of this How To guide. 2. PREREQUISITES ~ Guide was written on a SAP MDG 9.0 environment but should work starting with SAP MDG 7.0 = ABAP development skills 3. INTRODUCTION 3.1. STORY BOOK ‘Ata company, existing suppliers can be changed easily using MDG-S Change Requests without any approvals. A review by an additional approver is only required if the Bank details are changed by @ requestor. Only if the approver is convineed that the newly entered bank details or changes are correct will he approve the change. This prevents possible fraud. 3.2. HIGH LEVEL STEPS The implementation consists of 6 steps: 1. Configure new MDG Change Request Type with the Rule-Based Workflow template. This step is done in the Master Data Governance implementation guide (mdgima). 2. Implementation of the BAD! 3. Create ABAP dictionary abjects 4, Modeling BRF+ elements and the process flow in BRF+How To... MDG-S: Dynamic Workflow Processing based on changes to bank details 5. Implement ABAP class 6. Test 4, STEP-BY-STEP EXPLANATION 41. Create new Change Request Type 1, Go to transaction mdgimg and navigate to General Settings > Process Modeling > Change Requests and execute activity Create Change Request Type Display IMG SS SJ | Existing BC sets BC Sets for Act ’ General Settings : General Settings for Finances General Settings for Materal General Settings for Business Partn Technical Settings for Master Data Data Modeling UI Modeling Data Qualty and Search Process Modelng « BS @ Define Governance Scope + BS @ Create Edition Type > Business Actwties Change Requests WDgDg9 cvvvye + BS @ Edit statuses of change Requests 2. Choose New Entries and enter the following: Type of Chg. Request: ZSUP_BAN Data Model : BP. Description: “MDG-S: Dynamic Approval (Bank Demo)" Select “Single Object” Main Entity: BP_HEADER Workflow: WS60800086 g. Choose Enter Change View "Tipe of ame Request Orenion ee 3. Select the CR Type and choose Entity Types: Add new Entity Type: BP_Header ‘Change View "Entity Types": Overview 3 newemes BRO RB AC Set: Change Feld Vatues Dabog Structure ‘Tyee of Chg. Request |ESUPER ¥ Bi Tipe of Cage Reaues Sours ena 0 * i scope on entty | EEY TS I vanes Actvtes | ErtRy Type [Scena Conigtion Ontonal Message Ovtout Baserce evelageer) seen [5] seanaaraHow To... MDG-S: Dynamic Workflow Processing based on changes to bank details 4, Add the Business Scenario: SUP2 New Entries: Overview of Added Entries SRE ER B Dialog Structure Type of Chg. Request _[2SUPEAN © I Type of Change Reques. ¥ Bu Entity Types ” Ba Scope on & Busness Actwities + WW Business Activities. _Bus. Actwty Description (medium text) + Bu Service Level Agreer Process Supper 7 a._ Save all changes. ignore the warning 5. Define Change Request Steps for Rule based Workflows ‘a. In the Master Data Governance implementation guide (mdgimg) go to General Settings > Process Modeling > Workflow and execute activity Define Change Request Steps for Rule based Workfiows b. Add 4 new Entries: Change View "Workflow Step Numbers": Overview & Newentiess —S ROS ‘Workfiow Step Numbers KB Bi. _ acset: change Fed values Type of Chg. Request CRStep Keys Vakation Description (medium text) ‘ZSUPBAN ° Processing ZSUPBAN 90 v Final Check ‘ZSUEBAN BT ‘Actwation ‘ZSUEBAN 92 Revision ‘ZSUEBAN 95 Revision Processng ¢._ Save all changes. Ignore the warning 6. Define Service Name for Rule based Workfiows a. In the Master Data Governance implementation guide (mdgimg) go to General Settings -> Process Modeling > Workflow and execute activity ‘Define Service Names for Rule based Workfows” b. Add new Entry ZMDGS_RBW_CONTEXT BANK Demo XY - Dyn. Context for MDGS REW Context Change View "Maintenance View of Table USMD201C_SSW": Overview & Newentres BR MRK HK Mantenance View of Table USMD201¢_SSW Service Name Descrption (long text) @ ‘2406S_RBW_CONTEXT_BANK Demo XY - Dyn. Context for MDGS RBW Context + c. Save all changes 4.2. Implementation of BAdI 1.1n the Master Data Governance implementation guide (mdgimg) go to General Settings > Process Modeling > Workflow > Rule-based Workflow > Business Add-Ins: Execute the activity BAdl: Rule Context Preparation for Rule-Based WorkfiowHow To... MDG-S: Dynamic Workflow Processing based on changes to bank details Display IMG a Existing BC Sets BC Sets for Activity Activated Structure Master Data Governance, Central Governance cee General Settings General Settings for Financials General Settings for Material General Settings for Business Partner Technical Settings for Master Data Data Modeling UI Modeling Data Qualty and Search Process Modelng @ Define Governance Scope @ Greate Edition Type Busness Activities Change Requests workfow @ Actnate Event Type Linkage © Configure Workflow Tasks @ Define Change Request Actions @ Define Change Request Step Types and Assign Actions B B B . wep SDSDID ID < Rule-Based Workfow @ Define Change Request Steps for Rule-Based Workflow @ Define Service Names for Rule-Based Workflow @ Configure Rule-Based Workflow <- * ES @ BAdI: Caling of System Method for Rule-Based Workflow 2. Choose New:How To... MDG-S: Dynamic Workflow Processing based on changes to bank details Implementations for BAdI Defintion USMD_SSW_RL ‘Actve(IMG) Actve(Im... Enhancement Implements (2HDG_BS_MAT_BRE_CONT! Mi Mi 26DG_CCODE_couNTRY EnkancementImplementaten Shor Text ‘Compost Enhancement Implementation elo (ole) 4, Choose Ok and assign package 5. In the next screen enter ‘a. Badi Impl: ZMDGS_RBW_DYN_CONTEXT_IMPL. b. Class: ZCL_MDGS_RBW_DYN_CONTEXT (reste Baal Implementations for Beetng Bad Defneons tha nleertaton “Fone cos ct ototen shot Tet Ipocs.ror par comert_oo ‘be. oos fo pr cOMEXT C20 FOL_COMEATPREARE _~RueBsed Walfow pete 6. In the next popup select “Copy sample class": This is an example from MDG-M and we will change it later. 7. In the BAdl: define Filter Val.How To... MDG-S: Dynamic Workflow Processing based on changes to bank details ee {Banat rowmentatons SERVICE NAME 8. Save all and Activate all (will be done later again) 4.3. Create ABAP dictionary objects 1.Go to SE80 and create a new Domain: ZMDGS_BANK_CHANGED with CHAR 1 Doran 24D6S_BANK_ CHANGED Actwe Short Descrntion __|Flag is Bank has changed Properties: Value Range Format. Data Type (CHAR Character String No. Characters 1 Decimal Places o Output Characteristics Output Length 1 Routine sion \Case-senstive 2. Define a Value Range: 10How To... MDG-S: Dynamic Workflow Processing based on changes to bank details Domain ‘2MDGS_BANK_CHANGED Actwe Short Description _|Flag is Bank has changed (Proper —|Defoesn fal | Single Vals 1 Fx.Val. ‘Short Descript. x ranged bE not changed 3. Create a Data Element: ZMDGS_BANK_CHANGED Data element 24DG3_BANK CHANGED Active Short Description _[ZMDGS_BANK_CHANGED Attrbutes MDEERMEEMD Further characterstics | Field Label ® Doma 2aDGS_BANK CHANGED Flag is Bank has changed Data Type (CHAR Character Sting Length Data Type Length ° Data Type Length [0 4. Activate both objects 4.4. Modeling BRF+ elements and the process flow in BRF+ 1.In the Master Data Governance implementation guide (magimg) go to General Settings -> Process Modeling > Workflow > Rule-based Workflow: Execute activity Configure Rule-Based Workfiow: a popup appears and the BRF* workbench opens with the right parameters "How To... MDG-S: Dynamic Workflow Processing based on changes to bank details Display IMG Technical Settings for Master Data > Data Modeling > UIModeing > Data Quaity and Search . Process Modeling + BS @ Define Governance Scope BS © Create Edition Type Business Actvties Change Requests Workflow + B @ Actwate Event Type Linkage + BS @ Configure Workflow Tasks + BS @ Define change Request Actions + BS @ Define Change Request Step Types and Assign Actions . Rule-Based Workfow + BS @ Define Change Request Steps for Rule-Based Workflow BS _@ Define Service Names for Rule-Based Workflow «> [@ [Reninre Rae Saved workon|| > Business Add-Ins cue 2. Enter the newly created CR Type: ZSUPBAN and continue 3. Create new Data Object type “Element” called ZMDGS_BANK_ CHANGED with DDIC reference to ZMDGS_BANK_CHANGED Ey Workbench || Toots Repository Catalog Switch to Other Catalog | Dy || Dt Catalog Structure Ha Status UsMO_SsW_CATA 2808, > EqBR- Ap CPRae Folder Node > rere EY ome en > EgRueset Cite Catton Node >) Select xsting Object. > eqoretypeR, > EaDedsion Ta Expand > Ccotapse. Element User Sotings > 2How To... MDG-S: Dynamic Workflow Processing based on changes to bank details Create Element General data Type * Name ‘Short Text Text ‘Appcation USMD_0007TJUMSSXDBAB40WLTSAUBI Element Properties Define Data Binding Element Attributes Bement Type, Bind bexsing BRFplus element No Binding perry ener 4, Activate the new element oy Se epetey cata = © element (Text: ZMDGS_BANK CHANGED Sree ove ewan | Da OF a cee o- ae ae cay te fa te = ve sn.onA aire ~— stawossmoue Saat + exo seen + erin hein nn ts ing mer At a eet nara ee + arset tic een aeeat ‘Brae © care onte a ooNGED = exon ee Ran rt Deine Been Properties + expen ae va os emerson Ee Ae . Fl aeons . Flowaeaieonaie . 5, Add element to function signature Go to Trigger function and add the new element and Activate 13How To... MDG-S: Dynamic Workflow Processing based on changes to bank details 6 Define the Service Name Define the Service in the BRF+ application ay —— 1 comme cHST PROC. PTO Z8UPSAN pesieora amy [04] Ce | get [fo [Be | nee tema i o one feces 7. Setup the decision table Now you can add the newly created date objects to the conditions for the workflow modeling - Open table DT_SINGLE_VAL_ZSUPBAN - Choose Edit = Choose on Table Settings ~ Define these settings: “4How To... MDG-S: Dynamic Workflow Processing based on changes to bank details List of Columns Mandatory Input Column Accessibilty 7 Full Access (Changes Full Access (Changes Full Access (Changes. Ful Access (Changes Result Columns Colum Name Tet Acton Column Mandatory input Column Accessbiy |2COND_ALIAS Conan Alas Full Access (Changes thew step Now cnng, Reg. Stop Ful Access (Changes. ENEW_CR STATUS New CR Situs Full Access (Changes. 2EXP_COMPLET...._ Hours to Completion Ful Access (Changes. SEMERGETYPE Merge Type Fut Access (Changes. SEMEROE_PARAM — Merge Parameter Full Access (Changes. | | pRDYNAMIC_AGT... Dyn AgtSel Service Full Access (Changes. 8. Import the BRF+ examples Now you can import the example 15How To... MDG-S: Dynamic Workflow Processing based on changes to bank details ay Workbench || Tools v bata imported into decision table successfully Repository Catalog Switch to Other Catalog || Dy || Dt © Decision Table: DT_SINGLE_VAL_ZSUPBAN « Back ||| &p Display ||| ZB Check | EB Save ||| 4 Ad stucue a staus catog , ~ uswo_ssw cata 25uP8 1 2005. BANK CHAN . eta > eqORF* Applicaton a text Overview || Stat Sulton * GiTrigger Function A Function to Cal Rule . > earaieset | & #)| me = €20R Type Rettod Sora Provus “get Senos Name Ve ° ° + Decision Tables 8 Dept To Be e ee ne eee =09 (Activ: . 20 Final cneoo © =10 Sena e '=91 (Activation) © =31 (Activ: ~ Repeat this for all 3 tables ae a + se icons rant 16How To... MDG-S: Dynamic Workflow Processing based on changes to bank details 1 onion ate TANGLE VAL 20 (7am) oe) a | |g oan 1 ore TaOTNCLE VAL ZSUPOAN at | ee [be a | | Beem | me eet | Genome | uraree) =i [mt noes eee nora soins hereon co = Assign the right users or roles in the DT_USER_AGT_GRP_ZSUPBAN I ~ In Table DT_SINGLE_VAL_ZSUPBAN the first 2 lines are interesting: Dependent on the custom condition the workflow is dynamically routed. 4.5. Implement ABAP class Now you must implement the ABAP class with the corresponding functionality. The class was created during the wizard usage in former step. The example class in this How-To guide has the following methods: Classinterface Ct wo0s_RBW_DMH_CONTEXT Implemented / Actve [iteces [fends attrbutes_] [Events| Types Aes) [Ml Parmeter] 7% Sxcentons | Sourcecode [ye |SE|] Poo BI WA] [FP] reer Method Level Vesbity —M.. Descoton cet_evpext_tD ‘Stacic Meched Privace emant 1D aD cae guest ‘Static Method Private ry 15_pP_BNDTL,_TNCLODED ‘Static Method Private entity BP_BKDTL n tagng ofthe CR EAD DATA ‘Stavic Meched Privace the whole BP objectin a genenc table sbucture ~ No class attributes defined ~ No events attributes defined ~ No types attributes defined - The interfaces have been defined during the wizard based creation: 7How To... MDG-S: Dynamic Workflow Processing based on changes to bank details Model... Descroton Invertace san BhdI: US/0_ SSW RULE_CFTX PREPARE ‘Tag Interface for Als © IF_LUSMD_SSW_RULE_CNTX_PREPARE-PREPARE_RULE_CONTEXT: This is the method which is called by the MDG framework and can have these lines: DATA: lv_brf_expr_id TYPE if_fdt_types—>id. DATA: Is_cOntext ‘TYPE Uemd_s fdt_context_value. DATA: lvcrequest TYPE usmd_s FIELO-SYMBOLS: TYPE any. Prepare export parameter, CLEAR et_message. CLEAR et_rule context_value. TE Tl _ number - iv_cr_number - PORTING iv_ex_type = lv _crequest-usmd_creq type Oi T2MDGS BANK CHANGED'” IMPORTING ev brf expr id = Ivibrf_expr_id ). Ts_context-id + 1v bef expr_id. CREATE DATA 1s context=value TYPE amdgs bank ASSIGN 12_context-value->* 70 . anged. CALL METHOD zel_mdgs_sbw_dyn_context=>is bp bkdtl_included EXPORTING iv_cr_number = iv_cr number IMPORTING ev_included . APPEND 1s_context 70 et_rule context_value. © GET_ELEMENT_ID: This method returns the ID of the element defined in the BRF+ application in former step METHOD GET_ELEMENT_ID. DATA: lv_application_id lo_brf_factory REE [0 if cdt_query, if_fdt_query->ts_selection, LINE OF 1t_selection, if Edt_quety—>= object category s#l, if Edt query—>t2_name, if fdt_query—>s_hame. lslebj_category it names lernames ASSERT iv_cr_type IS NOT INITIAL. ASSERT iviname IS NOT INITIAL. bret depending on the CR typ _ "_sew_rlle_service->get_cr_| d( iv_er_type ). IF lv_application_id IS INITIAL. MESSAGE x000(uamdl). “no brf+ application r 18How To... MDG-S: Dynamic Workflow Processing based on changes to bank details DIF. lo_brf_factory = cl_fdt_factory->if_fdt_factory~get_inetance( ). lo brf_query ~ lo brf_factory->get_query( iv_object_type if_fdt_constante->gc_object_type_data_object iv_data_object_type = if_fdt_constante—>ge_date_object_type_elemel it_admin data quezy->ge_fn_neme. 1s_selection-quez if_fdt_admin date tion-option = "EQ". - n-low 6 INSERT 1s_selection INTO TABLE 1t_selection. 1s_obj_category-system _cbjecte ls obj _category-customizing objects la ob}_category-masterdata objects abap_true. abap_true. = abap_false. 1o_brf_query->select_data( ExroRTInc its_selection is_dbject_category_sel IMPORTING ete_data = lt_nanes ). 1t_selection ls_obj_category READ TABLE 1t_names INTO 1s names INDEX 1. ev_brf_expr_id = 1s_names-id. ENDMETHOD. READ_CREQUEST ~ reads CR Header data (like CR Type) method READ_CREQUEST. DATA: lr_model TYPE REF TO if_usmd_model_ext. DATA: 1t) TYPE usmd_ta_sel. DATA: la eel ‘TvPE uamd_e Sel. DATA: lterequest TYPE uamd_ta_crequest. CONSTANTS: 1¢ incl TYPE ddgign VALUE 'I'. CONSTANTS: 1evequal TYPE ddoption VALUE 'EQ'. CLEAR: es_crequ * Get read-only access to U data CALL METHOD cl_uemd model, instance EXPORTING i_uamd_model = if _mdg_be_mat_gen_e->ge_model_mm IMPORTING eo instance = 1r model. * Read the CR itself (to get R As_sel-sicn 19How To... MDG-S: Dynamic Workflow Processing based on changes to bank details value os_fld-crequest 1t_sel abap_ t_czequest. AD TRBLE 1t_crequest INTO ea_crequest INDEX 1. ASSERT sy-subEc ~ 0. " CR not foun endnethod. © IS_BP_BKDTL_INCLUDED: This class returns if the MDG entity 'BP_BKDTL' was changed within the CR. if uses another class to read the “staging” area content METHOD is bp bkdtl included. aging TYPE uamd | s_all_staging TYPE usmd_: zel_mdgs_sbw dyn. ede = itt 1_ext: entity - 1t_all_staging. LOOP AT 1t_all_staging INTO 1s all_estaging IE 1a_el7_staging-uemd entity cont EQ 'BP_BKDTL'. ev_inclided = 'x". RETURN. ENDIF. ENDLOOP. ev_include ENDMETHOD. © READ_DATA: This method can be implemented by you to read all entities in staging typically you use readmode “go_reacucds_no_act” to get only inactivelsteging data, Please use the MDG-API to retrieve this data 46. Test ‘Step by Step guide for testing Test 1: Change of existing customer including bank det ‘Step 1: Requestor = Login as requestor Goto MDG-S > Search ‘Search for an existing Business Partner Select the record in the result list and click on EDIT = Select CR Type MDG-S: Dynamic Approval (Bank Demo) from CR Type List > Approval 20How To... MDG-S: Dynamic Workflow Processing based on changes to bank details . oe * me 00 o o oe es = oe et @ to Ana change gt amt toutes pantrtone | HPO SS Se a] ee Peer on = Change the Address (or any other) attribute. ~ Add (or change) bank details! account number within the bank details Yank accounts [new sank ouney > laenticaton Numoers + Submit your request - Remember the CR ID: ~ Logoff from the NWBC. Step 2: Approver Login as approver - Goto MDG-S and page “My Change Requests” - Review the list and you will see that the CR_ID from last step is in the list + Open the MDG CR ~ _ System informs you about changed Bank details by color highlighting = Approve the CR. Test 2: Change of existing customer without changing bank det ‘Step 1: Requestor = Login as requestor = Goto MDG-S > Search = Search for existing Business Partner = Select the record in the result list and click on change - Select CR Type "MDG-S: Dynamic Approval (Bank Demo)" from CR Type List = Change the Address (or any other) attribute. = Donot change the bank details ~ Submit your request - Remember the CR ID: - Logoff from the NWBC. > auto approval Step 2: Approver = Login as approver 21How To... MDG-S: Dynamic Workflow Processing based on changes to bank details - Goto MDG-S and page My Change Requests - _ Review the list and you will see that the CR_ID from last step is NOT in the list - Goto page Display Change Requests and search for the CR_ID from last step = You will identify that the CR is already approved without any approval. 5. REMARKS This guide can also be used for all other kinds of dynamic routing; it is not limited to bank details only = Due to the fact that the BP data model is used you can also use it for MDG-C and MDG-BP related processes: Amore general guide on the BAdl USMD_SSW_RULE_CONTEXT_PREPARE is located here. ps://archive.sap.com/documents/docs/DOC-14881 ‘The Code in this Guide, SAP Code or application samples and tutorials are NOT FOR PRODUCTIVE. USE. You may not demonstrate, test, examine, evaluate or otherwise use them in a live operating environment or with data that has not been sufficiently backed up. You may not rent, lease, lend, or resell SAP code or application samples and tutorials. 2