SRM-MDM Catalog (Catalog Content Management)

SAP Enhancement Package 2 for SAP SRM 7.0: SRM-MDM Catalog (Catalog Content Management)Based on SAP Solution Manager Content

Target Audience ■ System Administrators ■ Consultants

PUBLICDocument version: 1.0 – 2011-11-08

Document History

CAUTION

Before you start the implementation, make sure you have the latest version of SAP Solution

Manager Content. For more information on the SAP Solution Manager content, see SAP Note

1461039.

The following table provides an overview of the most important document changes.

Version Date Description

1.0 2011-11-08 Initial Version

2/30 PUBLIC 2011-11-08

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1461039&_NLANG=en&_NVERS=0

Table of Contents

Chapter 1 Important Information About This Document . . . . . . . . . . . . . . . . . . . . . 5

Chapter 2 Basic Settings for SRM-MDM Catalog (Catalog Content

Management) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.1 System Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.1.1 Initializing the SRM-MDM Catalog Repository . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.1.1.1 Initializing the SRM-MDM Catalog Repository . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.1.1.2 Setting Up Master Data Management (MDM) . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.1.2 Portal settings for MDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2.1.2.1 Making Portal Settings for SRM-MDM Catalog . . . . . . . . . . . . . . . . . . . . . . . . 10

2.1.2.2 Making Portal User Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.1.2.3 MDM Workflows and Approval of Catalog Content . . . . . . . . . . . . . . . . . . . . 11

2.1.2.4 Making Universal Worklist Settings for the SRM-MDM Catalog . . . . . . . . . . . 13

2.1.3 SAP Exchange Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.1.3.1 Making SAP NetWeaver Process Integration Settings . . . . . . . . . . . . . . . . . . . . 14

2.1.3.2 Configuring the System Landscape Directory . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.1.3.3 Defining Business Systems in the Integration Directory . . . . . . . . . . . . . . . . . . 16

2.1.3.4 Setting Up Integration Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.1.3.5 Editing Interface Determination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2.1.3.6 More Information About SAP Exchange Infrastructure . . . . . . . . . . . . . . . . . . 19

2.2 Organizational Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2.2.1 Define External Catalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2.2.1.1 Catalog-Specific Role Maintenance in SAP MDM . . . . . . . . . . . . . . . . . . . . . . 19

2.2.1.2 Setting Up External Web Services in SAP SRM . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.2.1.3 More Information About Defining External Catalogs . . . . . . . . . . . . . . . . . . . 22

2.2.2 Configuring the Search User Interface (UI) . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

2.3 SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 3 Catalog Content Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3.1 Managing Service Content in SRM-MDM Catalog . . . . . . . . . . . . . . . . . . . . . . 23

3.1.1 Configuring the External Integration Role . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2011-11-08 PUBLIC 3/30

3.1.2 Transferring Service Hierarchy from SAP ERP . . . . . . . . . . . . . . . . . . . . . . . . . 24

3.1.3 Transferring Service Hierarchy and Non-Hierarchical Items from RFx

Response in SAP SRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

3.1.4 Transferring Service Hierarchy and Non-Hierarchical Items from Central

Contracts (SRM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3.1.5 Import and Mapping of Catalog Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3.2 Managing Product Content in SRM-MDM Catalog . . . . . . . . . . . . . . . . . . . . . 27

4/30 PUBLIC 2011-11-08

1 Important Information About This Document

The configuration documentation for SAP Supplier Relationship Management (SAP SRM) is delivered

with the SAP Solution Manager content. To implement and configure SAP SRM, you must use SAP

Solution Manager, which contains the complete configuration documentation including links to

Customizing, SAP Notes, and SAP ERP documentation.

This guide contains only the SAP SRM configuration documentation and references to other

documentation. It provides you with a quick overview of the required SAP SRM configuration settings.

CAUTION

This guide is a supplement to the SAP Solution Manager content and does not replace it. The

complete configuration content and tool support is only available in SAP Solution Manager.

For more information on the SAP Solution Manager content, see SAP Note 1461039 and the SAP SRM

master guide at http://service.sap.com/instguides under Installation & Upgrade Guides SAP Business

Suite Applications SAP SRM SAP SRM Server 7.01 .

Business Functions

SAP enhancement package 1 for SAP Supplier Relationship Management 7.0 (SAP SRM 7.0) includes

the following business functions:

■ SRM, Strategic Sourcing Innovations

■ SRM, Catalog Innovations

■ SRM, Approval Process

■ SRM, Continuous Innovations

■ SRM, Implementation Simplification

■ SRM, Service Procurement Innovations

■ SRM, PI-Independent Enterprise Services

■ SRM, Supplier Collaboration

■ SRM, Self-Service Procurement

■ SRM, Analytics

For more information about these business functions, see SAP Help Portal at http://help.sap.com

SAP Supplier Relationship Management Business Functions and Customizing Switches .

1 Important Information About This Document

2011-11-08 PUBLIC 5/30


http://service.sap.com/instguides

http://help.sap.com

This page is left blank for documents that are printed on both sides.

2 Basic Settings for SRM-MDM Catalog (Catalog Content Management)

2.1 System Connections

2.1.1 Initializing the SRM-MDM Catalog Repository

2.1.1.1 Initializing the SRM-MDM Catalog Repository

Prerequisites

■ The SAP Note 964991 has been applied in your SAP Supplier Relationship Management (SAP SRM)

or SAP ERP system.

■ The SAP Note 1641186 has been applied.

■ The MDM Server and Import Server have been started and the SRM-MDM Catalog repository has

been loaded before the replication or checking of Customizing data.

■ The configuration file MDMGX_Catalog.txt is downloaded to your local drive.

NOTE

The file MDMGX_Catalog.txt is contained in SAP Note 1177780.

Procedure

Initializing the SRM-MDM Catalog repository comprises:

1. Configuring the Extraction Framework.

2. Uploading the configuration file and a report.

3. Setting the home directory for the FTP server.

4. Replicating SAP SRM or SAP ERP customizing data to the SRM-MDM Catalog repository.

In this task you replicate data such as currencies, units of measure, product groups, and purchasing

organizations into SAP Master Data Management (MDM).

NOTE

You replicate purchasing organizations from SAP ERP only.

5. Checking the replication result in one of the SAP MDM applications:

■ MDM Import Manager

■ MDM Data Manager

Configuring the Extraction Framework

1. Start transaction se38 in the SAP SRM or SAP ERP client system.

2. Enter report name MDM_GX_UPLOAD_MDMGXC1 and choose Execute.

The initial screen appears.



2011-11-08 PUBLIC 7/30




3. Select Catalog as Object Type.

4. Select the downloaded file MDMGX_catalog.txt from your local drive.

5. Select Remove Header Line and choose Execute.

Uploading the Configuration File and a Report

1. Start transaction MDMGX in the SAP SRM or SAP ERP client system.

2. Select the Maintain Ports and Check-Tables menu item.

The system opens a selection screen.

3. Select Catalog as Object Type – You can click the field and use the input help (F4) – and choose

Execute.

The system displays an overview of Customizing tables and their assignment to MDM port codes.

4. Review the table content and check that there are entries for the relevant system types (R3 and

SRM).

Setting the Home Directory for the FTP Server

Set the home directory of your FTP server to the following path:

<SAP NetWeaver MDM 7.1 installation directory>\Server\Distributions>

NOTE

Replace <SAP NetWeaver MDM 7.1 installation directory> with the directory name of your

MDM Server installation.

If you have changed the Distribution Root Dir setting in the mds.ini file (configuration file) of the

MDM Server, make the corresponding setting in the home directory.

Replicating SAP SRM or SAP ERP Customizing Data to the Repository

1. Start transaction MDMGX in the SAP SRM or SAP ERP client system.

2. Choose Define Repositories and FTP Servers

3. Change to Edit mode.

4. Select the SAP_SP4_PRODUCT repository template and choose Copy As....

The system opens a screen for entering the repository and FTP details.

5. Enter a name for the Logical Repository and change the following settings as required:

■ Object Type

Using the input help, select Catalog

■ Repository Name (Code)

This must be identical to the SRM-MDM Catalog repository name in SAP MDM.

■ FTP Server

URL to your FTP server that contains the port folder structure.

■ MDM Root

Root folder of your local port folder structure.

■ Client Code



8/30 PUBLIC 2011-11-08

Refers to the system client.

■ Client System Type

The entries R3 and SRM represent the SAP SRM and SAP ERP client systems.

■ Languages

The SRM-MDM Catalog repository supports the languages:

Chinese (ZH), Czech (CS), Danish (DA), Dutch (NL), English (EN), Finnish (FI), French (FR),

German (DE), Greek (EL), Hebrew (HE), Hungarian (HU), Italian (IT), Japanese (JA), Korean

(KO), Norwegian (NO), Polish (PL), Portuguese (PT), Russian (RU), Slovakian (SK), Spanish

(ES), Swedish (SV), Thai (TH), Turkish (TR)

■ Timeout (Minutes)

6. Save your changes and return to the MDM 5.5 Generic Extractor main screen.

7. Choose Start Extraction.

The system opens a screen for entering extraction parameters.

8. Select the <SRM-MDM Catalog> repository.

You use the repository name you have entered in step 3. The system automatically adds the data

such as Address of FTP Server.

9. Set the FTP_DWNL indicator to activate the FTP download and choose Execute.

Prior to Execute you can set the FTP_DWNL indicator to activate the FTP download and specify a

local directory in the FIL_DIR field.

Checking the Replication Result in SAP MDM

Perform the following steps in one of the following SAP-MDM applications:

MDM Import Manager MDM Data Manager

Select Port as Type of the data source.Select the relevant client system (SAP SRM or SAP ERP).

Open the following lookup tables and check their entries: ■ Product Groups

■ Currencies

■ UoM ISO Code

■ Purchasing Organizations (only SAP ERP)NOTE

You can select a lookup table via the dropdown box in the upper left pane of the MDM Data Manager. Select the relevant client system (SAP SRM or SAP ERP).

Open the Ports dropdown list and check that the following ports are available (have been processed successfully) and that no exceptions have occurred. ■ LT_Currencies

■ LT_ProductGroups

■ LT_UOM_ISO_Code

■ LT_PurchasingOrganization(only SAP ERP)

2.1.1.2 Setting Up Master Data Management (MDM)

PrerequisitesSRM-MDM Catalog 7.02 runs on top of SAP NetWeaver MDM 7.1. Refer to the corresponding IT

Scenario Configuration guide for MDM on SAP Service Marketplace at http://service.sap.com/

installMDM for information on the topics listed below:



2011-11-08 PUBLIC 9/30

http://service.sap.com/installMDM


Procedure

Referring to the corresponding IT Scenario Configuration guide for MDM for information, you need

to:

■ Adjust the shipped repository structure

■ Make your client systems known to MDM

■ Provide the check tables in MDM as reference data

■ Set up SAP NetWeaver Process Integration (SAP PI), if you are using SAP PI.

More Information

If you are using SAP NetWeaver Process Integration (SAP PI), see Making SAP NetWeaver Process Integration

Settings. [external document]

2.1.2 Portal settings for MDM

2.1.2.1 Making Portal Settings for SRM-MDM Catalog

This procedure is used for the business process step Enabling Web Approval Process with iViews (Optional)

[external document].

Prerequisites

■ The SAP components required for the SRM-MDM Catalog 3.0 business scenario have been installed.

For more information, see SAP Note 1177780.

■ The MDM business packages have been deployed.

For more information, see SAP Service Marketplace at http://service.sap.com/installMDM.

■ The SRM-MDM Catalog business packages have been deployed, using SDM to deploy

BP_SRM_MDM.sca

■ You have System Administrator authorization.

Procedure

1. Log on to the Portal Content Browser as a System Administrator and choose System Administration

System Configuration .

2. Choose Portal Content Content Provided by SAP Specialist SRM-MDM Catalog System .

The object MDM Catalog appears.

3. Open MDM Catalog and maintain the properties for MDM Host Server, Repository Name and, if required,

Server Password.

NOTE

You must insert the value MDMSRM_CATALOG_ITEMS for Tables with Workflows

4. In the dropdown list Display, select the entry System Aliases and insert the aliases SAP_SRM_MDMCAT

and SAP_SRM_MDMCAT_WFORIG



10/30 PUBLIC 2011-11-08



ResultYou have defined the connection properties and the system aliases.

2.1.2.2 Making Portal User Settings

To implement the optional process step of Enabling Web Approval Process with iViews, you have to

ensure that the MDM workflow tasks are assigned to a specific portal user. To ensure that the portal

user gets the task in a UWL (Universal Worklist), you have to map the portal user to an MDM user.

Prerequisites

■ The MDM user to which the portal user is mapped is assigned the MDM roles Catalog Manager and

Catalog Content Approver.

For more information, see Enabling Web Approval Process with iViews (Optional) [external document].

■ You have System Administrator authorization.

■ The target MDM repository is loaded.

Procedure1. Log on to the Portal Content Browser as a System Administrator and choose User Administrator to

locate the portal user that you want to map to an MDM user.

2. Choose Modify User Mapping for System Access.

3. Select SAP_SRM_MDMCAT and enter the MDM user and password. Save your entries.

4. Repeat the above process for your Administrator user.

5. Assign the role SRM Catalog Content Manager (com.sap.pct.srm.mdmcat.role.cat_cont_mgr) to

the portal user by choosing Modify Available Roles . Add the role

com.sap.pct.srm.mdmcat.role.cat_cont_mgr to the portal user.

6. In the System Administrator tab, choose System Configuration Portal Content Content Provided by SAP

Specialist SRM-MDM Catalog System and open the object SRM-MDM Catalog.

7. Choose Connection Tests to test if the connection to the MDM repository is working.

ResultWhen you next log on with the portal user, a new tab Workflow appears at the top level. This new tab

displays all workflow tasks assigned to the mapped MDM user, assuming that you have carried out the

business process step Making Universal Settings for the SRM-MDM Catalog [external document].

2.1.2.3 MDM Workflows and Approval of Catalog Content

You use these functions in the MDM Data Manager to create, design, and, execute workflows.

The import, change, or creation of records triggers MDM workflows.

You use these MDM workflows for functions such as approving catalog content, for example a workflow

Automatic Approval leads to the following result:



2011-11-08 PUBLIC 11/30

■ All supplier items containing a price change of less than 5% are automatically updated and receive

the status Approved.

■ Supplier items that did not successfully pass the check specified in the validation expression receive

the status To Be Approved.

Features

You can define MDM workflows, add records, or add model workflow steps that include, for example,

validations or assignments.

For more information, see the Data Management Reference Guide for MDM 7.1 on SAP Service

Marketplace at http://service.sap.com/installmdm

Based on specific trigger actions (such as import or update) you can start workflows automatically. For

example, in the MDM Import Manager, you can configure a map that launches and assigns records to

a workflow after import.

After the workflow job has been launched, a workflow job task appears for the responsible user, for

example, the owner of the Catalog Content Approver role. On completion of the workflow step, the user

sends the workflow to the next step.

EXAMPLE

An MDM workflow could comprise the following workflow steps that are triggered after new

catalog content is imported and records are assigned the status Checked-Out:

1. Start

2. Enrich Data

Users with the MDM role Catalog Manager can review the content of the records, and, if required,

modify records in the MDM Data Manager.

3. Approve

Users with the MDM role Catalog Content Approver can approve or disapprove records, or split

records into new workflow tasks to delegate the job to other users.

4. Set Status

Items are updated with the new value that indicates the approval status, such as Approved.

5. Stop

All records are checked in automatically.

Integration

MDM workflows are designed using Microsoft Visio 2003 Standard. These workflows comprise

predefined steps for user activities and workflow elements such as validations, approvals, and

notifications.

CAUTION

MDM workflows run independently of the SAP workflow framework and are not the same as

other SAP SRM workflows.



12/30 PUBLIC 2011-11-08

http://service.sap.com/installmdm

More Information

Validations [external document]

Enabling Web Approval Process with iView (Optional) [external document]

2.1.2.4 Making Universal Worklist Settings for the SRM-MDM Catalog

To use web-based approval workflows in the Portal, you need to create a connection between the UWL

(Universal Worklist) and the MDM Workflow engine.

Procedure

1. Log on to the Portal as System Administrator and choose System Administration Universal Worklist

& Workflow Universal Worklist — Administration.

2. Create a new connection with the system alias SAP_SRM_MDMCAT and connector type

MdmUwlConnector. Save your entries.

A new connection appears in the table.

3. Choose Universal Worklist Content Configuration Click to Administrate Item Types and View Definitions.

Download the configuration MDM to your local file system.

4. Open the XML file with a text editor and delete all the content in the tag <Item Types> and add

the following:

<ItemType

name="uwl.task.mdm.tasks.SAP_SRM_MDMCAT.MDMSRM_CATALOG_ITEMS"

connector="MdmUwlConnector" defaultView="MdmViewTasks"

defaultAction="showMdmDetails" executionMode="default">

<Actions>

<Action name="showMdmDetails" groupAction="no" handler="IViewLauncher"

returnToDetailViewAllowed="yes" launchInNewWindow="yes">

<Properties>

<Property name="taskId" value="${item.jobId}"/>

<Property name="externalRequestEvent"

value="com.sap.pct.mdm.appl.masteriviews.events.externals.ViewTaskRecordsHandler"/>

< Property name="iview" value="portal_content/com.sap.pct/specialist/

com.sap.pct.srm.mdmcat.root/role/com.sap.pct.srm.mdmcat.role.cat_cont_mgr/

com.sap.pct.srm.mdmcat.wf_items"/>

<Properties>

<Descriptions default="Show Record Details"/>

</Action>

</Actions>



2011-11-08 PUBLIC 13/30

</Item Types>

5. Choose Upload New Configuration and select the file you edited in the previous step. Upload it with

the name MDM.

6. Select OK to overwrite the old configuration.

7. In the section Universal Worklist Content Configuration, choose Universal Worklist & Workflow Universal

Worklist — Administration and select the link Cache Administration Page to clear the cache.

2.1.3 SAP Exchange Infrastructure

2.1.3.1 Making SAP NetWeaver Process Integration Settings

To enable communication between the SAP Supplier Relationship Management (SAP SRM) server and

the SRM-MDM catalog with the integration server, you make settings in SAP NetWeaver Process

Integration (PI).

SAP NetWeaver PI is required between SAP SRM or SAP ERP for:

■ Contract replication (upload from SAP SRM to the SRM-MDM repository)

■ Product data replication from SAP SRM

■ Replication of info records with material master data and contracts from SAP ERP

■ Transfer of supplier from SAP SRM to SRM-MDM repository

NOTE

SAP NetWeaver PI is not required if:

■ You want to provide supplier catalogs only in a Web-based environment.

■ You do not replicate product or contract data.

Prerequisites

■ A system connection has been set up and configured between the SRM Server and SAP NetWeaver

PI.

■ The Integration Server has been installed.

For more information, see SAP Service Marketplace at http://service.sap.com/instguides

SAP NetWeaver SAP NetWeaver 7.0 ( 2004s) Installation

■ The SAP components required for the SRM-MDM Catalog 3.0 business scenario have been installed.

For more information, see SAP Note 1177780.

■ The SAP NetWeaver XI content for SRM Server and for SRM-MDM Catalog 3.0 has been imported.

NOTE

The SAP NetWeaver XI content for SRM-MDM Catalog 3.0 is not part of the standard SRM

Server XI content.

Procedure

1. Enabling Use of Process Integration



14/30 PUBLIC 2011-11-08

http://service.sap.com/instguides


For more information, see SAP Solution Manager under <project name> Configuration SAP SRM

<release> Basic Settings for SRM-MDM Catalog (Catalog Content Management) System Connections SAP

Process Integration Enable Use of Process Integration

2. Configuring the System Landscape Directory [external document]

3. Defining Business Systems in the Integration Directory [external document]

4. Setting up Integration Scenarios [external document]

5. Creating Communication Channels with Templates [external document]

6. Editing Interface Determination [external document]

2.1.3.2 Configuring the System Landscape Directory

To use SAP NetWeaver Process Integration (PI) as part of the Catalog Content Management business scenario,

you must define the following in the System Landscape Directory (SLD):

■ The systems that use SAP PI to send messages: SRM Server

■ The systems that receive messages from SAP PI: SAP MDM Server

Prerequisites

Implement SAP Note 836200.

Procedure

Configure the technical and business system landscape for:

■ SAP SRM Server (Role Application System)

■ SAP NW Integration Server (Role Integration Server)

More Information

The figure below shows the required system connections and protocols, the processes for which those

system connections and protocols are required, and a sample system landscape for the Catalog Content

Management business scenario.

Figure 1:

The bold lines represent connections that are always required. The arrows show the direction of the

requests.

See the table below for more information on key topics:

Topic Title Available in the SAP Help Portal (help.sap.com)

Configuring the technical system landscape for

Technical System Landscape (System

SAP NetWeaver <release> Library SAP Library SAP NetWeaver LibraryAdministrator's Guide Technical Operations for SAP NetWeaver Administration of SAP

NetWeaver Systems Process Integration (PI)



2011-11-08 PUBLIC 15/30


Topic Title Available in the SAP Help Portal (help.sap.com)3rd Party Applications (Non-ABAP/Non-Java Systems)

Landscape Directory)

Configuring the business system landscape (Registering an External System as a Business System)

Configuring a Business System

SAP NetWeaver <release> Library SAP Library SAP NetWeaver Library SAP NetWeaver by Key Capability Process Integration by Key Capability SAP NetWeaver Exchange Infrastructure Design and Configuration Time Configuration System Landscape Directory in SAP Exchange Infrastructure

Configuring Integration Scenarios

Business Solution Configuration

SAP NetWeaver <release> Library SAP Library SAP NetWeaver LibraryAdministrator's Guide Technical Operations for SAPNetWeaver Administration of SAP

NetWeaver IT Scenarios Enabling Application-to-Application Processes Tasks

2.1.3.3 Defining Business Systems in the Integration Directory

To define the technical communication parameters between the Integration Server and the SRM-MDM

Catalog business system, configured in the System Landscape Directory (SLD), you define business

systems in the Integration Directory.

Prerequisites

■ The required business systems have been defined in the SLD.

■ The SAP NetWeaver Process Integration (SAP PI) for the SRM-MDM Catalog has been imported

during the installation process.

Procedure

1. In the Assign Party step, leave the Party field empty.

2. In the Select Business System step, choose the business system for the SRM-MDM Catalog.

3. Deselect the checkbox Create Communication Channels Automatically.

2.1.3.4 Setting Up Integration Scenarios

To automate the definition of receiver routing and interface routing, you import the predefined SRM-

MDM Catalog integration scenario from the Integration Repository and generate the corresponding

Configuration Scenario.



16/30 PUBLIC 2011-11-08

Prerequisites

■ The integration scenario SRM_MDM_Catalog is used for the SRM_MDM_Catalog for product

procurement. It is available in the namespace http://sap.com/xi/SRM-MDMCatalog

■ The integration scenario SRM_MDM_Catalog_3.0 is used for the SRM_MDM_Catalog in service

procurement. It is available in the namespace http://sap.com/xi/SRM-MDMCatalog

■ The System Landscape Directory (SLD) is preconfigured.

Procedure

1. Choose Integration Builder: Configuration

2. Choose Tools Transfer Integration Scenario from Integration Repository

3. Select the predefined integration scenario and assign the (customer-specific) name you want to

use for your scenario <Customer_Specific__SRM-MDM_catalog_scenario>.

The integration scenario wizard opens.

4. Follow the configuration steps in the left-hand frame of the integration scenario wizard.

5. Select the corresponding view of the integration scenario.

6. Under Assign Services select the relevant business systems:

■ The business system for the SRM-MDM Catalog

■ The business system for SAP SRM or SAP ERP

7. Configure Connections.

Follow On Activities

■ Create a receiver channel for the adapter type XI for each connection. For more information, see

Creating Communication Channels with Template [external document].

■ In the Create Configuration Objects dialog box, set the following indicators

● Generation

● Receiver Determination

● Interface Determination

● Sender/Receiver Agreement

For more information, see Editing Interface Determination [external document]

■ Manually create business services for normal hierarchy upload and price upload

■ Manually assign the communication channels to the above business services

■ Manually branch messages

Branching messages enables them to reach multiple destinations, for example the business services

defined for the normal hierarchy and price upload.

To enable this, add business service to the Service column of the configured receivers table in the

receiver determination. The Conditions column must be blank.

■ Manually create communication channels for _price business scenarios

■ Manually create receiver agreements for _price business scenarios

■ Manually create the interface determinations related to _price business scenarios



2011-11-08 PUBLIC 17/30

■ Manually create the two new inbound interfaces related to hierarchies for sender service ERP

More Information

See the SAP Help Portal at http://help.sap.com SAP NetWeaver SAP NetWeaver 7.0 ( 2004s) SAP

NetWeaver Library SAP Netweaver by Key Capability Process Integration by Key Capability SAP NetWeaver

Exchange Infrastructure Design and Configuration Time.

2.1.3.5 Editing Interface Determination

To ensure that the upload of contract and product data uses the correct interfaces, you edit the interface

determination in the integration directory for the scenario you defined in the business process step,

Setting up Integration Scenarios.

Procedure

1. In the SAP Process Integration Tools, start the Integration Directory (Integration Builder: Configuration).

2. Select your Catalog scenario and expand the sublevels.

3. Open the node Interface Determination.

The inbound interfaces are displayed. Three of the interfaces handle contracts, one products and

five services.

Interface Used For

MDMContractDataTransmission4ProductID_In Contract items containing a product ID.

MDMContractDataTransmission4ProductCategory_In Contract items containing a product category.

MDMContractDataTransmission4SupplierPartNumber_In Contract items containing a Supplier Part Number.

ERPMSSUploadHierItem_In Items associated to Hierarchy from ERP MSS (Catalog Type Code: 07) and Contracts (Catalog Type Code: 14)

ERPMSSUploadStructure_In Hierarchy Structure (headers and outlines) from ERP MSS (Catalog Type Code: 06) and Contracts (Catalog Type Code: 12)

MDMHierarchyTransmissionFunctional_In Items associated to Hierarchy from SRM RFx (Catalog Type Code: 07) and Contracts (Catalog Type Code: 14)

MDMHierarchyTransmissionNonHierarchy_In Items NOT associated to any Hierarchy from SRM RFx ( Catalog Type Code: 08)

MDMHierarchyTransmissionStructure_In Hierarchy Structure (headers and outlines) from SRM RFx (Catalog Type Code: 06) and Contracts (Catalog Type Code: 12)

NOTE

If a transmitted record includes several types of content (as stated above in the “Used for”

column), the system routes this data to several interfaces.



18/30 PUBLIC 2011-11-08

http://help.sap.com

4. Choose Standard as the type of Interface Determination.

5. Deselect the Maintain Order At Runtime indicator.

For each of the above interfaces you need to configure a Condition.

6. Navigate into the empty Condition field.

The Condition Editor opens

7. Specify the Namespace <http://sap.com/xi/EBP> and the corresponding namespace Prefix nr1 for the

first interface that you are setting up.

8. Click a line to open the expression editor and set up the Xpath expression.

Each line of the condition editor represents one operand of the condition. You can combine two

operands using the following Boolean operators:

■ AND

The system indicates an AND condition by putting a bracket in front of the two connected

lines.

■ OR

■ NOT

NOTE

For more information on the Xpath expression see SAP Note 1177780

More Information

Setting Up Integration Scenarios [external document]

2.1.3.6 More Information About SAP Exchange Infrastructure

Perform the following activity in Customizing for SAP SRM:

SAP Supplier Relationship Management SRM Server Cross Application Basic Settings Enable Use of Exchange

Infrastructure

2.2 Organizational Management

2.2.1 Define External Catalogs

2.2.1.1 Catalog-Specific Role Maintenance in SAP MDM

To use the SRM-MDM Catalog, you need to assign catalog-specific roles in SAP MDM Console.

You assign the corresponding roles for the following tasks:

Task Role Description

Manage catalog content

Catalog Manager Responsible for importing, managing, and classifying product and contract data in the MDM Import Manager and MDM Data Manager.



2011-11-08 PUBLIC 19/30


Task Role Description

Approve catalog content

Catalog Content Approver

Responsible for approving or rejecting catalog items in the SRM-MDM Catalog workflow.

Launch catalog search

Catalog User This role refers to the search users assigned to the catalog Web service.You configure this Web service in Customizing under SAP Supplier Relationship Management SRM Server Master Data Content Management

Define External Web Services

Configure catalog search UI

UI Configuration Manager

Responsible for setting up user-specific configuration for users who are assigned the Catalog User role.The owner of this role is authorized to configure the Java-based Web Dynpro search UI and the open catalog interface (OCI) mapping.

Upload content to catalog

External Integration

Responsible for tracking responsibilities, differentiate imports, and compare updates originating from human interaction with the updates that are system-driven.

2.2.1.2 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM), and to access

the SRM-MDM Catalog via URLs from SAP SRM applications, you must set up external Web Services

in SAP SRM.

Procedure

1. To create a Web Service with an ID, such as SRM-MDM Catalog, see Customizing for SAP Supplier

Relationship Management under SRM Server Master Data Content Management Define External Web

Services (Catalogs, Supplier Lists etc)

2. To assign the catalog to a particular purchasing organization, enter the organization in the Purch.

Organization field.

3. Under Additional Functions in the Product Catalog, set the following indicators:

■ Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the

Details option is selected in the overview list of catalog items, product details are displayed.

■ Validate Product Data From SAP SRM

Enables the use of the OCI validate feature.

For this feature to work, the field NEW_ITEM-EXT_PRODUCT_ID must be filled with the

catalog database key of the product when the product is transferred for the first time from

the product catalog to the SRM Server System. The system checks if products are still available

in the catalog, and if the price is still up to date. If the product data has changed, the current

data is transferred to SAP Enterprise Buyer.

■ Cross-Catalog Search



20/30 PUBLIC 2011-11-08

Enables the selected catalog to be searched by a keyword search that expands over all catalog

Web Services having this indicator.

In the navigation tree of the Customizing transaction, double-click Integrated Call Structure.

NOTE

Do not define a call structure for your catalog, as these catalogs are designated to be

displayed as integrated catalogs.

4. Maintain the parameters listed below, taking into account the additional information.

Parameter Name Parameter Value Type Additional Information

n.a http://<J2EEserver:

J2EEport>/SRM-MDM/SRM_MDM

URL Required<J2EEserver> is the host on which the J2EE server is installed. <J2EEport>is the http port of the J2EE server.

username <your_user_name>Refers to the user in SAP MDM (not the end user starting the catalog search in SRM).

Fixed Value RequiredThe value can be that of any user maintained for the catalog repository in SAP MDM Console Admin

Users.

password <your_password> Fixed Value Required

server <your_MDM_server>[:<MDM Server Host n>]

Fixed Value RequiredSee SAP Note 1170807

repositoryType <Repository Type>[:<Repository Type n>]

Fixed Value OptionalSee SAP Note 1170807

catalog <SRM_MDM_CATALOG> Fixed Value RequiredThe name of your catalog repository in SAP MDM.

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon language of SRM.

datalanguage For example<EN>orSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the language dependent fields of your catalog repository.

mask <your_mask_name> Fixed Value Optional

NOTE

If you do not specify a mask, all users have the same unrestricted access to the catalog.

namedsearch <your_named_search_name>

Fixed Value Optional

NOTE

If you do not specify a named search, all users have the same unrestricted access to the catalog.



2011-11-08 PUBLIC 21/30



Parameter Name Parameter Value Type Additional Information

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required. This parameter determines and informs the catalog to which target OCI data has to be returned.

1hwc_search False, if you do not want to use left-hand wildcards

Fixed Value Optional. For more information, see SAP Note 1147662

2.2.1.3 More Information About Defining External Catalogs

Run the following system transaction in SAP SRM: Change Attributes (PPOMA_BBP).

2.2.2 Configuring the Search User Interface (UI)

For more information, see SAP Help Portal at http://help.sap.com/saphelp_srm70/helpdata/en/

2a/37290780d74681b6a6ee55ec0ba752/content.htm.

2.3 SAP Notes

The following SAP Note applies: 1171711.


2.3 SAP Notes

22/30 PUBLIC 2011-11-08


http://help.sap.com/saphelp_srm70/helpdata/en/2a/37290780d74681b6a6ee55ec0ba752/content.htm

http://help.sap.com/saphelp_srm70/helpdata/en/2a/37290780d74681b6a6ee55ec0ba752/content.htm


3 Catalog Content Management

This section describes the settings that are required to run the Catalog Content Management scenario.

You can find a scenario description in SAP Solution Manager under <project name> Scenarios Catalog

Content Management . Select the Documentation tab.

3.1 Managing Service Content in SRM-MDM Catalog

The process Managing Service Content in SRM-MDM Catalog consists of the following process steps:

1. Transfer Service Hierarchy through transaction MECCM (ERP)

2. Transfer Service Hierarchy and Non Hierarch. Items from RFx Response (SRM)

You can find a process description in SAP Solution Manager under <project name> Scenarios Catalog

Content Management Business Processes Managing Service Content in SRM-MDM Catalog

3.1.1 Configuring the External Integration Role

You use this technical role to track responsibilities, differentiate imports, and compare updates

originating from human interaction with those originating from system-driven updates.

In the standard system, this role is assigned to the System, that is the human, user. However, by default

the MDM Import Server uses the Administrator user that is assigned the Administrator role to upload

external data through the XML bound interface and the file system.

In this procedure, you change the default user for uploading external data in the MDM Import Server

from Administrator to System.

Prerequisites

■ The user System is assigned the role External Integration.

■ The basic configuration of the MDM Import Server is complete.

■ The MDM Import Server is shut down.

■ The SRM-MDM Catalog repository is setup for Product information

Procedure

1. In the installation directory, open the mdis.ini file.

2. Enter the appropriate name for the Server setting.

3. Start the MDM Server and then the Import Server.

4. In the MDM Console, load the catalog repository.



2011-11-08 PUBLIC 23/30

This initiates system creation of a database-specific entry for your catalog repository in the

mdis.ini file. You change this entry as described below.

5. Shut down the Import Server and modify the repository section of the mdis.ini and change the

following data:

Old New

login = Admin login = System

password = password = <your_password>

NOTE

By default, the user System has the password system. In the interests of security, change this

password during configuration.

3.1.2 Transferring Service Hierarchy from SAP ERP

You use this function to import service hierarchies with contracts and Model Service Specification

(MSS) from SAP ERP to the SRM-MDM Catalog repository using the MDM Import Server.

Integration

The following table displays the message interface that the system uses to transfer MSS and contract

hierarchies from the ERP system:

PI Message Type PI Outbound Interface MDM Inbound Interface MDM Message TypeCatalog Type Code

CatalogueUpdateNotification CatalogueUpdateNotification_Out ERPMSSUploadStructure_In MDMHierarchyTransmission 06 (MSS) and 12 (contracts)

CatalogueUpdateNotification CatalogueUpdateNotification_Out ERPMSSUploadHierItem_In MDMHierarchyTransmission 07 (MSS) and 14 (Contracts)

NOTE

You can export the MSS and contract hierarchy data together in one message if you select both

of them in the export transaction.

Prerequisites

■ SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currencies,

units of measure, product groups, and purchasing organizations) has been initialized.

■ The Model Service Specification (MSS) or contracts to be uploaded exists in the SAP ERP system

and does not have the status Blocked or Configurable MSS.

■ The transaction MECCM is available in the SAP ERP system for uploading the MSS into the SRM-

MDM Catalog.



24/30 PUBLIC 2011-11-08


Procedure

1. Run MECCM in the SAP ERP system you are using for testing.

2. Enter the catalog name in the Catalog Designation sub-screen. This is a mandatory field.

3. Enter the date on which the price of the service master items is to be calculated.

4. Deselect the Test Run checkbox, and choose Execute.

5. Check the Log for any errors.

Result

The service hierarchy has been transferred from SAP ERP to SAP SRM.

Use transaction sxmb_moni to check that the XML containing the hierarchical structure and the XML

containing the service items have been passed.

To check that the service hierarchy has been transferred to the catalog, you can check the catalog UI

to see if Categories displays the header that was imported into the repository. When you select the header,

the entire hierarchy (outlines and services) is displayed in the services table. Check if the outlines, service

items, and their prices correspond to the ones uploaded from SAP ERP.

3.1.3 Transferring Service Hierarchy and Non-Hierarchical Items from RFx Response in SAP SRM

Procedure

1. Log on as Purchaser.

2. Create a new RFx with hierarchical and non hierarchical items.

3. Publish the RFx.

4. Log on as Bidder.

5. Create an RFx Response.


7. Accept the RFx Response.

8. Choose Responses and Awards and choose the RFx response from the Bidder.

9. Choose Items tab.

10. Choose Publish to Catalog in the item table to transfer the items to the catalog.

Result

Items are transferred and published to the catalog. To check this:

1. Run transaction SXMB_MONI, and check that three XMLs have been passed from SAP SRM to

SAP Process Integration (SAP PI).

2. Check that the transferred hierarchy has been passed to the catalog and is visible in the catalog UI.



2011-11-08 PUBLIC 25/30

3.1.4 Transferring Service Hierarchy and Non-Hierarchical Items from Central Contracts (SRM)

You use this function to transfer service hierarchies and non hierarchical items with contract data from

the SAP Supplier Relationship Management (SRM) to the SRM-MDM Catalog repository using the

MDM Import Server.

Integration

The following table contains the message interface that the system uses to transfer contract hierarchies

from the SRM system to the MDM Catalog repository.

PI Message Type PI Outbound Interface MDM Inbound Interface MDM Message Type

Catalog Type Code

CatalogTransmission CatalogUpdateNotification_Out MDMHierarchyTransmissionStructure_In MDMHierarchyTransmission 12

CatalogTransmission CatalogUpdateNotification_Out MDMHierarchyTransmissionFunctional_In MDMHierarchyTransmission 14

CatalogTransmission CatalogUpdateNotification_Out MDMContractDataTransmission4ProductID_In MDMContractDataTransmission 03

Prerequisites

SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currencies,

units of measure, and product groups) has been initialized.

Procedure


2. Create a new Contract of type Central Contract (CCTR) with hierarchical and non hierarchical items.

3. In Header, set the value for Distribute Contract to Catalog to Yes.

4. Release the contract to transfer it to the catalog.

Result

Items are transferred and published to the catalog. To check this:

1. Run transaction SXMB_MONI, and check that three XMLs have been passed from SAP SRM to

SAP Process Integration (SAP PI).

2. Check that the transferred hierarchy has been passed to the catalog and is visible in the catalog UI.

3.1.5 Import and Mapping of Catalog Data

You use this function to import and map service hierarchy data to the SRM-MDM Catalog.

Prerequisites

To use the MDM Server for an automatic upload of data:

■ The import maps have been set up with the MDM Import Manager.

■ References from MDM inbound ports to the import maps have been created.



26/30 PUBLIC 2011-11-08


■ The automatic import has started and is dependent on your operating system. For example in

Microsoft Windows, the automatic import is started as a service.

Features

In the MDM Import Manager, you can:

■ Perform parametric imports that list the distinct values for each field in the source data.

NOTE

If you change a value during the import in a mapping or converting step, this changes the

value in all records.

■ Save your mappings and conversions in an import map in the SRM-MDM Catalog repository for

reuse during future imports.

EXAMPLE

You can create import maps for importing service structures.

In the MDM Import Server, the following activities take place:

■ Automatic upload of data

■ Record Filtering for Catalog Import

For more information, see the Data Management Reference Guide on SAP Service Marketplace at

http://service.sap.com/installMDM.

Integration

To use this function, you need the following SAP NetWeaver Master Data Management (SAP NetWeaver

MDM) components:

■ MDM Import Manager

Provides data transformation capabilities to preprocess the source data one field at a time prior to

the import.

For more information about using the MDM Import Manager, see the Import Manager Reference

Guide on SAP Service Marketplace at http://service.sap.com/installMDM.

■ MDM Import Server

You use this module for an automatic upload of data.

More Information

■ Import of Products, Contracts, and Suppliers from SAP Supplier Relationship Management (SAP SRM) [external

document]

■ Import of Contracts and Purchase Information Records from SAP ERP [external document]

3.2 Managing Product Content in SRM-MDM Catalog

The process Managing Product Content in SRM-MDM Catalog consists of the following process steps:

1. Import product hierarchy



2011-11-08 PUBLIC 27/30



2. Upload supplier product data

3. Map imported hierarchy and products to repository

4. Transfer info records and contracts from ERP

5. Transfer product data from SRM

6. Transfer contract data from SRM

7. Enrich product data

8. Approve product data

9. Define masks and named searches

10. Define validations

11. Enable web content

You can find a process description in SAP Solution Manager under <project name> Scenarios Catalog

Content Management Business Processes Managing Product Content in SRM-MDM Catalog



28/30 PUBLIC 2011-11-08

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

Documents

SRM-MDM Catalog (Catalog Content Management)