MDM Workflow: Import Trigger, Matching and on-Demand ... Data...MDM Workflow: Import Trigger, Matching and on-Demand Syndication . Applies to: SAP NetWeaver Master Data Management

MDM Workflow: Import Trigger, Matching and on-Demand Syndication

Applies to: SAP NetWeaver Master Data Management (MDM) SP5,SP6

Summary This article deals with a scenario where a workflow is trigged by record import, executes a matching strategy and then syndicates only the changed records.

Author: Sukant Dhar Pandey

Company: Wipro

Created on: 14 March 2008

Author Bio

Sukant Dhar Pandey is working as a project manager with Wipro. He is a member of the MDM core competency team and has over a decade of experience in enterprise applications.

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2008 SAP AG 1


Table of Contents Business Case....................................................................................................................................................3

Workflow .........................................................................................................................................................3 Setups in data manager: ..............................................................................................................................................3 Setups in import manager: ...........................................................................................................................................7 Setups in syndicator:....................................................................................................................................................8 Setups in console:........................................................................................................................................................9 Workflow execution: ...................................................................................................................................................10

Related Content................................................................................................................................................16 Disclaimer and Liability Notice..........................................................................................................................17



Business Case This article aims to supplement the paper outlining the basics of MDM workflow: https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9180cbaf-0801-0010-f882-f2af6dc975d0.This paper was written in Jan 2006 and since then three more shapes have been added to the standard MDM stencil. These are: match, assign and syndicate.

The business scenario that shall be covered in this article is that master data is being imported using import maps. A workflow has been setup to be triggered by import manager upon import of records. After the workflow is triggered, imported records are matched against existing records in the repository based on a pre-defined matching strategy. Post this, new records are submitted for approval and then syndicated post an assignment.

Workflow

The workflow consists of the following steps: 1. Start 2. Process 3. Match 4. Approve 5. Assign 6. Syndicate 7. Stop

Note: All the steps in this example are configured as execution type=”All concurrent” to enable push based processing.

Setups in data manager:

Matching rule: Create a matching rule specifying the fields on which matching is to be performed and the success / failure scores. This rule shall be called in the workflow via a matching strategy.

Matching strategy: Create a matching strategy specifying the rules to be included. This strategy shall be invoked in the “match” step of workflow.


https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9180cbaf-0801-0010-f882-f2af6dc975d0



Assignment: Create a new assignment. This assignment shall be invoked in the “assign” step of workflow.

Workflow:

Select the workflow table in the drop-down list.

Add a new record to the workflow table. Mention the “table” as the main table in the repository.



Select the trigger action as “record import”. Only then will this workflow appear in the import manager configuration options.

Then click in the “workflow” field to invoke Visio. Design the workflow and specify the step properties for each step of the workflow:

(a) Start



(b) Process

(c) Match

(d) Approve



(e) Assign

(f) Syndicate

Setups in import manager:

Open Import manager and create a map by specifying the source and destination files, map fields.

Specify the configuration options. Specify the earlier created workflow in the option ”Checkout/Workflow”.



Save the import map.

Setups in syndicator:

Open syndicator and create a map by specifying the destination properties (remote system, port) and mapping fields.



Save the map.

Note: The property “suppress unchanged records” should be checked. This will ensure that only newly imported records are syndicated.

Setups in console:

Unload the repository and add the map created earlier to the port intended to be used for syndication.

Note: The property “processing type” for the port should be manual.



Workflow execution:

In a real life business scenario, import maps shall be used to import records at a fixed interval using MDIS.

Alternatively, to test the setups performed in earlier steps, one can launch Import Manager and open the previously created import map.

Once the map is loaded, one can navigate to the import status tab and execute the import.

As soon as the import is finished, the workflow is launched. In the example workflow configured earlier the first step is “process” which assigns the step to “Admin” user.

When “Admin” user logins to data manager, the step is visible in the tab “workflows”. At this stage all records are visible in the “records” pane.

As soon as the status selection is changed to received, only imported records are presented as attached to the workflow step.



The workflow history displays the workflow as “launched” and the first step as “started”.

One can move to the next step by selecting “Next step” from the right-click context menu.

The user’s vies shall now display the latest step as received for execution.



The history shall display “match” step as started.

User can choose “perform” from the right click context menu to perform matching using the strategy specified in the workflow.

When one switches to the matching mode, the results are displayed. Upon completing all the required actions like merge etc, one can move the workflow forward.



This will change the relevant user’s display to reflect the next step to be performed.

The next step is approve. This can be executed by clicking in the records pane and selecting “workflows” and “mark as approved / disapproved” from the menu.



A check mark shall appear besides each record.

Once all the records have been actioned upon, one can move to the next step.

As soon as the next step is selected, the assignment and syndication steps are executed. The records are syndicated to the port folder specified in the step properties of workflow.

The workflow shall now feature in the completed section of workflow tab in data manager and the complete history can be viewed.





Related Content https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9180cbaf-0801-0010-f882-f2af6dc975d0.

http://help.sap.com/saphelp_mdmgds55/helpdata/en/43/e0615a82b40a2ee10000000a11466f/frameset.htm



http://help.sap.com/saphelp_mdmgds55/helpdata/en/43/e0615a82b40a2ee10000000a11466f/frameset.htm



Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.

SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk.

SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.

Documents

MDM Workflow: Import Trigger, Matching and on-Demand ... Data...MDM Workflow: Import Trigger, Matching and on-Demand Syndication . Applies to: SAP NetWeaver Master Data Management