Configuration of SSF and MDG Integration

This document describes the settings that you need to make to facilitate the integration of the Shared Services Framework (SSF) and Master Data Governance (MDG).

You need to activate the following business functions:

• Integration of MDG and SSF for Financials (FIN_SSC_MDGINT)

• FI, Enablement for Financial Shared Services (FIN_SSC_AIC_1)

You need to configure both your SSF system (Customer Relationship Management (CRM)) system and your MDG system. You need to configure your CRM system as follows:

1. First, you need to define the correct settings for the business context profile in Customizing for Customer Relationship Management under  Transactions  Settings for Service Requests  Define Settings for Business Context . You double click on the SSF_ALL entry, select link type BUS2250 and select the checkboxes for create, add and search. Save your changes.

2. You need to create a mapped logical system. You use transaction CRMS_IC_CROSS_SYS to create a new entry called MDGFLOGSYS. You also need to select the Local ITS check box. Do not make any other selections or entries.

3. Finally you need to map the logical system for MDG to the business role that is used to create change requests. You use transaction CRMC_IC_AIC_LOGROL to add the business role IC_AIC_AGENT (or the role that is used to create change requests in your implementation)

Once this is complete, you need to configure your MDG system as follows:

1. You need to activate the integration of the service request and the change request in Customizing for Cross-Application Components under  Processes and Tools for Enterprise Applications  Master Data Governance  Master Data Governance for Financials . Alternatively you can use transaction SM30 to activate the integration directly in the table SSC_MDG_CONFIG.

2. You need to create a new workflow template. You should copy the workflow template that you are already using for MDG, for example, WS75700040 or WS75700027. The example below uses WS75700040. To copy a template, you need to:

   1. Use transaction SWDB to open the Workflow Builder.

   2. Enter WS75700040 and press enter. In the Workflow menu, choose Save as to save the template as a new template.

   3. You need to add the class CL_IM_SSC_WF_SR_UPDATE to the Program Exit tab for each workflow step where you want the system to update the service request with the change request’s status. For example, you could add the class to the following workflow steps for the WS75700040 workflow:

      • 000047 Execution of Changes

      • 000068 Final Check

      • 000288 Revision After Rejection

      • 000298 Activate Changes

3. Once this is complete, you choose the Transfer and to graphic pushbutton to transfer the changes step to the workflow and to return to the workflow graphic. Save your change and activate the workflow.

4. You need to create a logical system for the corresponding SSF (CRM) system as follows:

   1. Use transaction SM59 to create the RFC destination for the CRM system.

      Note

      Do not use the current user as the log on user.

   2. Use transaction SALE to create a logical system for the CRM system under  IDoc Interface/Application Link Enabling (ALE)  Communication  Determine RFC Destinations for Method Calls. 

   3. Find the logical system that you created previously and select Standard BAPI Destination. Select the RFC destination that you created previously. Save your changes.

5. Implement the Business Add-In (BAdI) Retrieve RFC destination for CRM RFC invocation (SSC_RFC_DESTINATION). The default implementation of this BAdI reads the RFC destination of the CRM system from the CRM middleware settings. If there is no CRM middleware setting in the system, you need to create a BAdI implementation to specify the RFC destination for the CRM system.

6. Finally, you need to ensure that you also create a change request type with the new workflow template. For more information about MDG specific configuration, see Configuration of Master Data Governance for Financials.