SRMMDM

SAP AG 2006 - SAP INTERNAL USE ONLY - 1 -

SRM-MDM Catalog 2.0:Configuration Guide

SRM Server 5.5


Copyright

Copyright 2007 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may be changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents 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, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere,Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, OpenPower and PowerPC are trademarks orregistered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registeredtrademarks 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 aretrademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World WideWeb Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technologyinvented 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 andservices mentioned herein as well as their respective logos are trademarks or registeredtrademarks of SAP AG in Germany and in several other countries all over the world. All otherproduct and service names mentioned are the trademarks of their respective companies. Datacontained in this document serves informational purposes only. National product specificationsmay vary.

These materials are subject to change without notice. These materials are provided by SAP AGand its affiliated companies ("SAP Group") for informational purposes only, without representationor 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 setforth in the express warranty statements accompanying such products and services, if any.Nothing herein should be construed as constituting an additional warranty.


Icons in Body Text

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types ofinformation at a glance. For more information, see Help on Help? General Information Classesand Information Classes for Business Information Warehouse on the first page of any version ofSAP Library.

Typographic Conventions

Type Style Description

Example text Words or characters quoted from the screen. These include fieldnames, 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 Technical names of system objects. These include report names,program names, transaction codes, table names, and key concepts of aprogramming language when they are surrounded by body text, forexample, SELECT and INCLUDE.

Example text Output on the screen. This includes file and directory names and theirpaths, messages, names of variables and parameters, source text, andnames of installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in thesystem exactly as they appear in the documentation.

Variable user entry. Angle brackets indicate that you replace thesewords and characters with appropriate entries to make entries in thesystem.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.


SRM-MDM Catalog 2.0: Configuration Guide............................................................................... 5

Documentation Landscape for SAP Solutions and Business Scenarios .................................... 7

SAP Notes............................................................................................................................... 9

System Connections .............................................................................................................. 10

Initializing the SRM-MDM Catalog Repository..................................................................... 10

Setting Up MDM................................................................................................................. 13

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

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

Defining Business Systems in the Integration Directory....................................................... 17

Setting Up Integration Scenarios ........................................................................................ 18

Creating Communication Channels with Template.............................................................. 19

Interface Determination ...................................................................................................... 19

Process Customizing ............................................................................................................. 20

Restricting the Number of Searchable Catalog Items .......................................................... 20

Setting Up Masks for Searching the Catalog Repository.................................................. 21

Setting Up Named Searches........................................................................................... 22

Setting up External Web Services in SRM .......................................................................... 22

Making the Catalog Web Service Available in the Organizational Plan ................................ 25

Configuring the Search UI: General Tab ............................................................................. 25

Configuring the Search UI: Customize Display Tab............................................................. 29

Configuring the Search UI: Customize Search Tab ............................................................. 29

Mapping Catalog Fields to OCI Fields................................................................................. 30

Mapping Catalog Fields to OCI Fields................................................................................. 32

Integrating Electronic Forms............................................................................................... 33

Setting Up Contract Replication.......................................................................................... 34

Setting Up the Key Mapping for Contract Item Categories ............................................... 34

Implementing BAdI to Enrich Contract Data..................................................................... 35

Configuring Role for Data Import via Import Server.......................................................... 36

Appendix................................................................................................................................... 37

How To Enable Web Approval Process with iViews ................................................................... 37


SRM-MDM CatalogThis business scenario configuration guide applies to the scenario SRM-MDM Catalog with thecorresponding releases of its SAP application components.

Business Scenario and Application Components

Business Scenario Application Component with MinimumRelease

SRM-MDM Catalog SAP SRM-MDM Catalog 2.0, includingthe following MDM 5.5 SP5 components:

? MDM Server

? MDM Import Server

? MDM Console

? MDM Data Manager

? MDM Import Manager

? MDM Workflow

? MDM CLIX

SAP SRM Server (any Release)

SAP Exchange Infrastructure optional(Release depending on SAP SRM Serverversion)

mySAP ERP 2005 optional

See the table below for dependencies between SRM and XI (Exchange Infrastructure) content:

SRM Server Release XI Content Version PredeliveredXI Content

6.0 [SRM 6.0] XI Content 7.0 (withNetWeaver Basis 2004s)

Yes


Yes


No

EBP 3.5 XI Content 2.0 No

ContentsThe business scenario configuration guide contains all steps required to implement the SRM-MDM Catalog business scenario. The guide specifies the sequence of the configuration activities,and their dependencies.

It includes information about the following topics:

? System Connections


? Business Customizing

For more information about the SRM-MDM Catalog business scenario, see SAP ServiceMarketplace at service.sap.com/instguides

Target group

? Technical consultants

? Application consultants

? Project team members during the implementation of an SAP solution

? SAP customer IT department

The System Connections section is aimed at technical consultants in particular. The remainingsections are of equal interest to both groups of consultants. The importance of sections to theother target groups depends on their responsibilities.

It is a prerequisite that consultants have completed all relevant training coursesbefore starting to work with this guide.


SRM-MDM Catalog: Component View

mySAPERPFile System

CatalogManager

Catalog filesin variousformats

Producthierarchy

SAP XI

Catalog Admin. /Config.Manager

mySAPSRM

CatalogUser / * Administrator

Import Manager+ Console

SRM-MDM Catalog

Data Manager Config UI

Importcatalog data

Importproduct

hierarchy

Enrichproduct data

Launchcatalog

search viaURL

Transferitems to

procurementsystem

Transferproduct data

from SRM

Transfer inforecords and

contractsfrom ERP

Transfercontract

data fromSRM

XML mapping/routing

XML mapping/routing

Search UI

Auto-importcontracts +info records

from ERP

Contractsand info

records fromERP

Map importdata tocatalog

repository

Auto-importcontracts

andproductsfrom SRM

Contractsand

productsfrom SRM

Search forproducts in

catalogrepository

Continuewith

procurementactivity

Approveproduct data

CatalogUser

*

Enable Webcontent

Configuresearch UI

* Set up Webservice

**Define masks,named searchesand validations

Assignproductsto mask(required ifyou usemasks)

Documentation Landscape for SAP Solutions andBusiness ScenariosPurposeThis documentation gives you an overview of the major sources of information available to youon SAP solutions and business scenarios. Always use the current documents in yourimplementation.

Current Documents

Document Quick Link on the SAP Service Marketplace(service.sap.com)

Master Guide, Installation and Upgrade Guides instguidesBusiness-Scenario Configuration Guide instguidesImplementation Guide (IMG) Note: This is in the SAP system, not in SAP

Service Marketplace


Business Scenario Description instguidesSAP Library helpportal with all releases of a SAP

component

Note: Available in the SAP system under Help? SAP Library

The following information supplements the individual documents:

Current Supplementary Information

Information Quick Link on the SAP Service Marketplace(service.sap.com)

SAP notes notes for the note searchinstguides listed by installation and upgradeguide

Technical infrastructure (for example hardwaresizing, platforms, network security)

ti

FeaturesThe following documents are available for a SAP solution.

Master Guide, Installation and Upgrade GuidesThese documents describe how you install or upgrade the system landscape required by abusiness scenario. The central initial access document for each SAP solution is the MasterGuide. It lists the SAP application components and third-party applications required by eachbusiness scenario, and refers to their installation and upgrade guides. These are componentinstallation guides, business scenario upgrade guides, and component upgrade guides.

Business-Scenario Configuration GuideThis document describes the settings you use to configure the SAP application components andthird-party applications required for a business scenario. It contains information specific tobusiness scenarios for the particular IMG activity. It does not reiterate the IMG documentation butmakes reference to particular IMG texts.

Implementation Guide (IMG)This tool adjusts SAP systems to customer requirements. The IMG contains the IMG activities forall SAP components, and general documentation. The structure is component-oriented, withoutreference to a business scenario. The Business-Scenario Configuration Guide establishes the linkbetween the IMG and the various business scenarios.

Business Scenario DescriptionThis document describes how a business scenario runs once all components have been installedand configured. All the business processes of a business scenario are represented graphically inthe component view, which illustrates the process steps of each SAP component.

SAP LibraryThis contains the entire documentation of SAP components and business scenarios. TheBusiness Scenario description is part of the SAP Library.


SAP NotesBefore you start to configure this business scenario, consult the following SAP notes.

Make sure that you read the Release Information for the current support package toget all the required information.

SAP Notes

Note Number Title

723129 Support Package 00 for SRMRelease 4.0 (RIN)

675131 XI 2.0 (SP1 and higher):Importing XI Content

750433 SRM 4.0 SP stack 08/2004:Release and information note(RIN)

705541 XI 3.0 (Support Package 1 andhigher): Importing XI Content

759473 SRM 4.0 SP stack 09/2004:Release and information note(RIN)

769901 SRM 4.0 SP-Stack 10/2004(SAPKIBKS03): Release andInformat. (RIN)

790376 SRM 4.0 Support Release 01

796295 SRM 4.0 SP-Stack 03/2005(SAPKIBKS05): Release andInformat. (RIN)

876423 SRM 4.0 SP-Stack 12/2005(SAPKIBKS08): ReleaseInformation

842250 SRM 4.0 SP-Stack 06/2005(SAPKIBKS06): Release andInformat.

852894 SRM 5.0 SP-Stack 01(10/2005): ReleaseInformation Note

884148 SRM 5.0 SP-Stack 02(12/2005) (SAPKIBKT02):Release/Info Note


925982 SRM 5.0 SP-Stack 04(04/2006) (SAPKIBKT04)

923462 SRM 4.0 SP-Stack 04/2006(SAPKIBKS09): Release


Information


964991 MDM 5.5: Generic extractorfor Customizing data

1057316 SRM-MDM Catalog 2.0Installation & Configuration

System ConnectionsPurposeThis section contains information about connecting the systems in a SAP system landscape.

This involves, for example:

? Determining the systems, servers, clients and other components, in the system in whichthe SAP application component is installed

? Completing the configuration settings and performing other activities required for theinteractions in a SAP system landscape

PrerequisitesThe SAP Note 1057316 has been applied.

Initializing the SRM-MDM Catalog Repository1. 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 Catalogrepository.

In this task you replicate data such as currencies, units of measure, product groups andpurchasing organizations into SAP MDM.

You replicate purchasing organizations from SAP ERP only.

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

? MDM Import Manager

? MDM Data Manager

Prerequisites? The SAP Note 964991 has been applied in your SAP SRM or SAP ERP system.

? The configuration file MDMGX_Catalog.txt has been downloaded to your local drive.


The file MDMGX_Catalog.txt is in SAP Note 1057316.? 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.

Configuring the Extraction Framework1. Logon to your SAP SRM client or SAP ERP client system.

2. Start transaction SE38.3. Enter report name MDM_GX_UPLOAD_MDMGXC1 and choose Execute.

The initial report screen appears.

4. Select Catalog as Object Type.

5. Select the downloaded file MDMGX_Catalog.txt from your local drive.6. Select Remove Header Line.

7. Choose Execute.

Uploading the Configuration File and a Report1. Start transaction MDMGX in the SAP client system (SAP SRM or SAP ERP).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) andchoose Execute.The system displays an overview of customizing tables and their assignment to MDM portcodes.

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 ServerSet the home directory of your FTP server to the following path:

\Server\Distributions

Replace with the directory nameof 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 homedirectory.

Replicating SAP SRM or ERP Customizing Data to the Repository1. Start transaction MDMGX on the SAP client system (SAP SRM or SAP ERP).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 to enter 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

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.

For more information about replicating configuration data, see the How to LoadReference Data with SRM-MDM Catalog guide at service.sap.com/srm??mySAP SRM in Detail?? SAP SRM in Detail ? Archive ? SRM 5.0??Procurement?? Catalog Content Management.

7. Choose Start Extraction. The system opens a screen to enter extraction parameters.

8. Select the repository.You use the repository name you have entered in step 3. The system automatically addsthe data such as Address of FTP Server that you configured in step 3.

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 downloadand specify a local directory in the FIL_DIR field.

Checking the Replication Result in SAP MDMPerform 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 Ports dropdown list and checkthat the following ports are available(have been processed successfully)

? LT_Currencies

? LT_ProductGroups

? LT_UOM_ISO_Code

? LT_PurchasingOrganization(only SAP ERP)

and that no exceptions have occurred.

Open the following lookup tables andcheck their entries:

? Product Groups

? Currencies

? UoM ISO Code

? Purchasing Organizations (onlySAP ERP)

You can select a lookup table via thedropdown box in the upper left pane of theMDM Data Manager.

Setting Up MDMPurposeThis section refers you to the IT Scenario Configuration Guide for SAP NetWeaver MDM 5.5(Document Version 2.00 September 2006) available on the SAP Service Marketplace via quicklink MDM ? Installation and Upgrade Guides ? Previous Releases ? MDM 5.5 SP04 Planningand Installation Guides ? MDM 5.5 SP04 IT Scenario Configuration Guide.

For the SRM-MDM Catalog scenario see the sections listed below:

To adjust a shipped repository template, see:

? Setting up a Repository Structure

? Adapting Repository Templates for SAP Client Systems

To make your client systems known to MDM, see:Setting u p a R eposi tory St ruct ureAdapting Rep ositor y Templ ates f or SAP Client System s

? Setting up Connection Information

? Defining Client Systems and Key Generation

? Setting Up MDM Ports

To provide the check tables in MDM as reference data, see:Setting Up MD M Ports

? Loading Reference Data

? Cross-System Repositories: Importing Automatically

If you use SAP XI, see the section Setting up XI.

The section SAP Exchange Infrastructure of the SRM-MDM Catalog configurationguide is also important.


SAP Exchange Infrastructure (SAP XI)PurposeIn this section, you make the settings in SAP XI required for the SRM-MDM Catalog 2.0 businessscenario. With these settings you can upload data using SAP XI and enable the SRM Server andSRM-MDM Catalog to communicate with each other using the Integration Server.

SAP XI is not required if:

? You want to provide supplier catalogs only in a Web-based environment.? You do not replicate product or contract data.

The SAP XI is required between SRM or ERP and the SRM-MDM Catalog system for thefollowing data exchanges:

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

? Product data replication from SRM

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

If you use SAP XI, see the section Setting up XI of the MDM 5.5 SP05 - IT Scenario ConfigurationGuide.

We recommend that you use an Integration Scenario (and preferably the top downapproach) since the use of semi-automatic (wizard-driven) procedures simplifiesconfiguration.

If you are not familiar with the communication scenarios of Process Integration (PI),demo examples are available to demonstrate the technical concepts and tools step-by-step. See help.sap.com?? SAP NetWeaver 7.0 (2004s) ? SAP NetweaverLibrary? SAP NetWeaver by Key Capability ? Process Integration by KeyCapability? SAP NetWeaver Exchange Infrastructure? Overview ? Examples.

Prerequisites? A system connection has been set up and configured between the SRM Server and SAP

XI (for the exchange of messages with the Exchange Infrastructure and the IntegrationServer by using ABAP proxies).

? The Integration Server has been installed. For more information, see SAP ServiceMarketplace at service.sap.com/instguides?? SAP NetWeaver? SAP NetWeaver7.0 ( 2004s)? Installation.

? The SAP components required for the SRM-MDM Catalog 2.0 business scenario havebeen installed. For more information, see SAP Note 1057316.

? The SAP XI content for SRM Server and for SRM-MDM Catalog 2.0 has been imported.

The SAP XI content for SRM-MDM Catalog 2.0 is not part of the standard SRMServer XI content.

See also:

? SAP Notes

? 675131: XI 2.0 (SP1 and higher): Importing XI Content


? 705541: XI 3.0 (Support Package 1 and higher): Importing XIContent

? SAP Service Marketplace at service.sap.com/ibc-srm? MasterGuide for mySAP SRM.

Configuring the System Landscape DirectoryPurposeTo use SAP Exchange Infrastructure (XI) as part of the SRM-MDM Catalog 2.0 businessscenario, you must define the following in the System Landscape Directory (SLD):

? The systems that use SAP XI to send messages: SRM Server

? The systems that receive messages from SAP XI: SAP MDM Server

In this section, you define the system landscape in the SLD. The figure below shows the requiredsystem connections and protocols, the processes for which those system connections andprotocols are required, and a sample system landscape for the SRM-MDM Catalog businessscenario.

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

SAP SRM Server

SAP NW PI Integration Server

Web Browser & Client File System

File adaptor

Plain HTTP(S)

FTP(S)(2b)

(2a)

XI protocol

Numbered connections and corresponding processes:(1) Upload of supplier catalogs via Server File System to SAP MDM Catalog, for example in XML format.(2 a+b) Replication of product and contract data. You use the integration scenario SRM_MDM_Catalog.(3) OCI communication when starting the URL to search the catalog repository.

SAP SRM-MDM Catalog

SAP MDMConsole

SAP MDMData Manager

SAP MDMImport Manager

SAP MDMServer

Integration EngineSAP MDM

Import Server

*

Client Components

Server Components

SRM-MDMAdmin UI

SRM-MDMSearch UI

(3)

MDMConnector

Inte

rnal

MD

M p

roto

col

HTT

P(S

); in

clud

es O

CI c

omm

unic

atio

n

Server File SystemSupplier Catalogs

(1)

SAP NWAS Java


ProcedureConfigure the technical and business system landscape for the following installed components:

? SAP SRM Server (Role: Application System)

? SAP NW PI Integration Server (Role: Integration Server)

? SAP SRM-MDM Catalog (Role: Application System)

For information about configuring the technical and business system landscape, see thedocumentation below:

Subject Title of Documentation Path in the SAP Help Portal

Configuring the technicalsystem landscape for 3rdParty Applications (Non-ABAP / Non-Java Systems)

Technical System Landscape(System LandscapeDirectory)

(At help.sap.com?) SAPNetWeaver 7.0 (2004s)?SAP NetWeaver Library?Administrators Guide?Technical Operations Manualfor SAP NetWeaver ?Administration of SAPNetWeaver Systems ??Process Integration (PI)

Configuring the businesssystem landscape(Registering an ExternalSystem as a BusinessSystem)

Configuring a BusinessSystem

SAP NetWeaver 7.0 (2004s)? SAP NetWeaver Library? SAP NetWeaver by KeyCapability? ProcessIntegration by Key Capability? SAP NetWeaverExchange Infrastructure?Design and ConfigurationTime? Configuration?System Landscape Directoryin SAP ExchangeInfrastructure

Configuring IntegrationScenarios

Business SolutionConfiguration

SAP NetWeaver 7.0 (2004s)? SAP NetWeaver Library? SAP NetWeaver by KeyCapability? ProcessIntegration by Key Capability? SAP NetWeaverExchange Infrastructure?Enabling Application-to-Application Processes ?Core Development Tasks

ResultYou have now defined business systems for each of the installed components.


Defining Business Systems in the IntegrationDirectoryUseIn this section, you define the technical communication parameters between the IntegrationServer and the SRM-MDM Catalog business system you configured in the System LandscapeDirectory (SLD).

Prerequisites? The business systems that you want to use have been defined in the SLD

? The SAP XI content for the SRM-MDM Catalog has been imported (as part of theinstallation process).

The Checklist: Developing XI Content in the Integration Repository can assist you inyour activities. See help.sap.com?? SAP NetWeaver?? SAP NetWeaver 7.0 (2004s)?? SAP Netweaver Library?? IT Scenarios at a Glance?? EnablingApplication-to-Application Processes?? Reference.


Procedure...

1. In the Assign Party step, do not make an entry in the Party field

In the Select Business System step:

1. Choose the Business System for the SRM-MDM catalog.

2. Deselect the indicator Create Communication Channels Automatically.

Setting Up Integration ScenariosUseIn this section, you import the predefined SRM-MDM Catalog integration scenario from theIntegration Repository and generate the corresponding Configuration Scenario. Doing thisautomates the definition of receiver routing and interface routing.

Use the following integration scenario for the SRM-MDM Catalog:SRM_MDM_Catalog

This integration scenario is contained in the namespace http://sap.com/xi/SRM-MDMCatalog.

PrerequisitesThe System Landscape Directory (SLD) is preconfigured.

Procedure

1. Choose Integration Builder: Configuration to start SAP Integration Builder.

2. Choose Tools? Transfer Integration Scenario from Integration Repository.3. Select the predefined SRM_MDM_Catalog integration scenario and assign the (customer-

specific) name you want to use for your scenario .

The integration scenario configurator (wizard) opens automatically.

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

5. Select the component view SRM_MDM_Catalog.

6. Under Assign Services select the relevant business systems:

? The business system for the SRM-MDM Catalog? The business system for SRM or ERP

7. Configure Connections.

In addition to the above you must:

? Create a receiver channel with the adapter type XI for each connection.

For more information, see Creating Communication Channels with Template.

? Set the Generation indicator in the Create Configuration Objects dialog box.

? Set the Receiver Determination, Interface Determination, and Sender/ReceiverAgreement indicators in the Create Configuration Objects dialog box


For more information, see Editing Interface Determination.

Once you have completed the steps in the integration scenario configurator, the systemdisplays a results list.

Check the results list for any errors.

For more information about defining and configuring scenarios, see the SAP Help Portal athelp.sap.com ? SAP NetWeaver? SAP NetWeaver 7.0 ( 2004s)?? SAP NetWeaver Library??SAP Netweaver by Key Capability? Process Integration by Key Capability? SAP NetWeaverExchange Infrastructure? Design and Configuration Time.

Creating Communication Channels with TemplateUseOn your component view, XI uses Communication Channel Templates to establish connectionsbetween two actions, that is the details related to the line between two rectangles. Use the wizardstep Configure Connections to generate these connections.

Procedure...

1. Navigate to the empty field Communication Channel.

2. Choose Create Communication Channel with Template.

A wizard-driven dialog opens.

3. Choose Select Template and follow the wizard, using the Continue and Finish functions.

The wizard automatically fills the relevant fields.

4. Choose Create New Communication Channel and follow the wizard until finished.

Repeat this procedure for all your connections in the Component View.

The Integration Scenario includes actions for the upload of products and contractsoriginating either from SRM or ERP. Generate the Communication Channels thatare relevant to your business scenario.

After creating the relevant connections for the FTP upload, specify attributes such as File AccessParameters or FTP parameters.

Editing Interface DeterminationUseTo ensure that the upload of contract and product data uses the adequate interfaces, edit theInterface Determination in the Integration Directory for the scenario as in Setting up Integration Scenarios.

Procedure1. In the SAP Exchange Infrastructure Tools start the Integration Directory (Integration

Builder: Configuration).

2. Select your catalog scenario and expand the sublevels.

3. Open the node Interface Determination.

Inbound interfaces - three of them dealing with contracts, one with products aredisplayed:


Interface Used for:

MDMContractDataTransmission4ProductID_In Contract items containing a productID.

MDMContractDataTransmission4ProductCategory_In Contract items containing a productcategory.

MDMContractDataTransmission4SupplierPartNumber_In Contract items containing aSupplier Part Number.

MDMProductDataTransmission_In Transmitted product data.

If a transmitted record includes several types of content (as stated above in theUsed for column), the system routes this data to several interfaces.

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 and the correspondingnamespace 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 combinetwo operands using the following Boolean operators:

? represents AND

The system indicates an AND-condition by putting a bracket in front of the twoconnected lines.

? represents OR

? represents NOT

For more information on the Xpath expression see SAP Note 1057316.

Process CustomizingIn this process, you make settings to control your catalog process. These settings are located inthe:

? MDM, for example settings for masks in the MDM Data Manager

? SRM-MDM application for example settings to configure the search UI

? SRM Implementation Guide for example setting up the Web Service(s) for your catalog(s)

Restricting the Searchable Catalog ItemsIn this process you make the settings required to reduce the number of catalog items available ina catalog search by using the following alternatives for your catalog Web services:

? Setting up Masks for Searching the Catalog Repository


? Creating Named Searches

Setting Up Masks for Searching the CatalogRepositoryUseTo restrict the number of search items that a user can retrieve when running a search in the SRM-MDM Catalog, the Catalog Manager or Administrator specifies masks in the SAP MDM DataManager, assigns products to the mask, and assigns the mask to roles or users.

To restrict catalog access using masks you specify

Existing masks in the SRM customizing of the catalog Web service. Per Web service you specifyone mask and one user. See Setting up External Web Services in SRM

.

Or

? Constraints for the Masks table in the MDM Console.

To do this:

1. Navigate via Admin? Roles

2. Select the Tables and Fields tab

3. Under Masks, select one or more values in the Constraints column.

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service.

In the URL to open the search UI of the SRM-MDM catalog, the mask and user parameters areindependent from each other. However in the search UI you can also use the mask parameter torestrict the scope of products available in the search result.

Procedure9. ...

1. In SAP MDM Data Manager, create a mask.

2. Run a search to create a result set of the products you want to group in the mask.

3. Select the relevant products and choose Add to Mask.

To adjust an existing mask, you can Replace or Remove products from the mask.

To update several masks at a time, in the Records menu, choose Modify Mask. You canmodify the mask and add a search selection to the mask.

In the SRM Customizing of the catalog Web service, you specify a mask for accessing thecatalog.

You can also pass the parameter mask dynamically using a Business Add-In (BAdI).For more information see the IMG documentation: Supplier RelationshipManagement? SRM Server? Business Add-Ins (BAdIs)? External Web Services(Catalogs, Vendor Lists etc.)? Transfer Additional Parameters.

ResultYou have set up a search constraint that you can apply to a runtime search to limit the initial set ofcatalog item records in the search result.


Creating Named SearchesUseTo reduce the number of searchable catalog items, use the SAP MDM Named Searches function.You can create named searches in MDM Data Manager and use them as an alternative to masks.You can apply a named search by means of the namedsearch parameter in the configuration ofyour catalog Web services. See Setting up External Web Services in SRM

You can also pass the namedsearch parameter dynamically using a BAdI. For more information,see the IMG documentation: Supplier Relationship Management?? SRM Server?? BusinessAdd-Ins (BAdIs)?? External Web Services (Catalogs, Vendor Lists etc.)?? Transfer AdditionalParameters.

Prerequisites? In SAP MDM Data Manager the Named Searches have been added with relevant names

and assigned to the Named Searches lookup table.

You can specify any name, for example, a name that refers to a user group such asCatalog for managers. You can assign authorizations for users who areallowed to create or change Named Searches.

For more information about Saving and Restoring Named Searches, see the MDM5.5. Data Manager Reference Guide, available atservice.sap.com/nw04operation?? SAP MDM.

Procedure10. ...

1. Open the MDM Data Manager and change to Record mode.

2. Run a search to create a search result.

3. Open the Search menu.

4. Select the Set Named Search option, and select an entry.

The entry belongs to the set you have assigned to the lookup table mentioned in thePrerequisites.

ResultYou have set up a search constraint that you can apply to a runtime search to limit the initial set ofcatalog item records in the search result.

Setting up External Web Services in SRMUseTo use the SRM-MDM Catalog with SAP SRM and to access the SRM-MDM Catalog via URLfrom SRM applications, you must specify a corresponding Web Service. In Customizing for SRM,define the Web service by choosing: SRM Server? Master Data? Define External WebServices (Catalogs, Vendor Lists etc.).

To set up multiple URLs to access the catalog, set up the corresponding number of Web servicesas described below:

Procedure11. ...


In the IMG activity Define External Web Services (Catalogs, Vendor Lists etc.), create a Webservice with an ID that refers to your catalog, for example, SRM-MDM-Catalog.

1. In Customizing for SRM, create a web service with an ID such as SRM-MDM-Catalog thatrefers to your catalog by choosing: SRM Server? Master Data? Define External WebServices (Catalogs, Vendor Lists etc.).

2. To assign the catalog to a particular purchasing organization, enter the organization in thePurch. 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 OCI. Only with this setting the Detailaction ( glasses symbol) in the overview list of catalog items opens productdetails.

? Validate Product Data From SAP Enterprise Buyer

Enables the use of the OCI Validate feature assuming that in OCI Mapping,the field NEW_ITEM-EXT_PRODUCT_ID has been filled with the databasekey of the product in the catalog when the product is transferred for the firsttime from the product catalog to the SRM Server System. The system cancheck whether products still exist in the catalog, and whether the price is stillup to date. If the product data has changed, the current data is transferred toEnterprise Buyer.

? Cross-Catalog Search

Enables the selected catalog to be searched by a keyword search thatexpands over all catalog Web services having this indicator.

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

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

4. The system opens a maintenance screen. Maintain the parameters listed below, takinginto account the information available in the Remark column.

ParameterName

Parameter Value Type Remark

Use the following syntax:

http:///SRM-MDM/SRM_MDM

URL is the host onwhich the J2EEserver isinstalled

isthe http port ofthe J2EE server.

username

Refers to the user in SAP MDM (not theend user starting the catalog search inSRM).

FixedValue

Required

The value canbe that of anyuser maintainedfor the catalogrepository inSAP MDMConsole under


Admin? Users.password Fixed

ValueRequired

server FixedValue

Required

Host on whichyour MDMserver isinstalled.

catalog SRM_MDM_CATALOG FixedValue

Required

The name ofyour catalogrepository inSAP MDM.

port For example:

FixedValue

Required

The value mustbe identical tothe port that isassigned to yourcatalogrepository inSAP MDMConsole.

uilanguage SY-LANGU SAP-Field

Required

The systemuses the logonlanguage ofSRM.

datalanguage For example:

or

SY-LANGU

FixedValueorSAP-Field

Required

This setting canbe used tocontrol thelanguage forlanguagedependent fieldsof your catalogrepository.

mask FixedValue

Optional

If you do notspecify a mask,all users havethe sameunrestrictedaccess to thecatalog.

namedsearch FixedValue

Optional

If you do notspecify a namedsearch, all usershave the sameunrestrictedaccess to thecatalog.


HOOK_URL ReturnURL

Required

Making the Catalog Web Service Available in theOrganizational PlanUseTo enable users of your organizational plan to access the catalog web service, configure theparameter Catalog ID in the Organizational Management.

Procedure5. ...

1. In Customizing for SRM, choose: SRM Server? Cross-Application Basic Settings?Organizational Management ? Change Organizational Plan (Transaction PPOMA_BBP).

2. Select an organizational unit, for example, a Purchasing Unit.

3. Open the Attributes tab and fill the value for parameter Catalog ID with the Web serviceID that you created in section Setting up External Web Services in SRM.

You can assign the parameter on top level so that all users inherit this setting andare authorized to use the web service. Or, you can assign the parameter on a lowerlevel and restrict authorization to specific users on a position level.

To make the catalog available to users in the SRM system, add the Catalog ID tothe attributes for the organizational unit to which the user of the SRM-MDM catalogis assigned.

Configuring the Search UI: General TabUseAs a UI Configuration Manager, you can configure the Java-based (Web Dynpro) search userinterface of the SRM-MDM Catalog for

? General behavior, for example the availability of the Shopping Cart Preview.? Search behavior, for example the usage of advanced search or tree and selection

list search.

? Availability of content, for example which fields are available to which users.? OCI Mapping

The OCI Mapping can be configured to be search user dependent. For moreinformation, see Mapping Catalog Fields to OCI Fields

? User ConfigurationIn the standard, a configuration is assigned to the Default User. The Default Useris used for all search users who are not assigned individual settings.Individual Settings.You can make individual settings for each search user available in the catalogrepository by assigning the role Catalog User to a user in the MDM Console. Thisrole, Catalog User, can then be used in the Search UI. You can preview and


restore this configuration. It is also possible to restore the configuration settingsinitially delivered by SAP

PrerequisitesThe SAP MDM components of SRM-MDM Catalog 2.0 are installed and you have verified thatthese components use a consistent build version.

Procedure6. ...

1. Start the URL to access the configuration UI:

http:///SRM-MDM/SRM_MDMThe system opens a logon screen.

If you want to use a language other then English, please call the URL above withparameters uilanguage and datalanguage: the following languages are available: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)

2. Log on to the MDM Server by entering the following data under:

? Server Name, specify the host on which your MDM server is installed? Password specify the server password (if set at all) and choose Connect.? Login, choose the relevant repository and specify a user name and password.

The user must have the role UI Configuration Manager assigned, as specified inMDM Console under Roles.

3. Select the configuration options as listed below for the Default User or for each searchuser that requires a user-specific configuration.

General Tab: Shopping Option

Configuration Option Possible Settings Additional Information

Shopping Cart Radio Button This setting does not offer theShopping Cart Preview beforetransferring items to theshopping cart application.

Shopping Cart Preview Radio Button This setting offers thepossibility of previewing theshopping cart beforetransferring items to theshopping cart application.

Catalog Exploring (DisplayOnly)

Radio Button This setting is for display only.Purchasing items is notpossible.

General Tab: Item Display Criteia


Configuration Option Possible Entries Additional Information

List View Available Yes/No Enables or disables the displayof items as a list with a shortdescription on which users canclick to trigger access to theitem details. Images are alsoavailable.

Context View Available Yes/No Enables or disables the displayof items with an enlargedimage size along with multipleconfigurable user fields suchas Supplier Part Number,Manufacturer Number and soon.

Use Minimum Quantity asDefault

Yes/No Ensures that a warningmessage is issued if the useradds an item to the shoppingcart with an order quantity lessthan the minimum orderspecified.

Show Price Based Quantity Yes/No Compares items based on thequantity entered so that theright scale price is calculated.

No. of Results Numerical entry: Userdefined

Allows configuration of thenumber of hits displayed.

Display entire hierarchy if founditems less than

Numerical entry: Userdefined

Used Fixed table layout in listview

Yes/No Allows you to change thelayout of the list view.

To have the same height for allrows, choose Yes.

To have the height of rowscontrolled by the content in thecolumns, choose No.

Note: You configure thecolumn width in the CustomizeDisplay tab in the option ItemList. If the width is set to 0, astandard width is used.

Enable Use of Electronic Forms Yes/No To integrate electronic formsvia OCI, choose Yes.

For more information, see

Integrating Electronic Forms.

General Tab: Search


Advanced Search is Available Yes/No Allows for a maximum of twolookup fields and a maximumof four fields comprised of anymix such as non-lookup fields,range, and so on. This option


is only available if the systemsearch field type is defined asCategory in the CustomizeSearch tab. See ConfiguringThe Search UI: CustomizeSearch Tab.

Advanced Search As Default Yes/No Enables or disables the aboveas the default search.

Use Attribute Search Yes/No Refines the search forcategories and suppliers ifattributes have beenmaintained. In the CustomizeSearch configuration, thehierarchy Category must beselected to enable the AttributeSearch.

General Tab: Compare

Configuration Option Possible Entries Additional Information

Use attribute if priority higherthan

From one to onehundred.

General Tab: Shopping Lists


Shopping Lists Available Yes/No Enables or disables thisfeature that allows users tosave a collection of itemswithout quantity that can beused as a template for futureorders.

Shopping Lists as Default Yes/No Can be used to make thisfeature a default setting

Manage own Shopping Lists Yes/No Enables or disables userauthorization to create, modifyand, delete their own ShoppingLists.

Other Shopping Lists: Delete Yes/No Enables or disables userauthorization for deleting theShopping Lists of others.

Other Shopping Lists: Modify Yes/No Enables or disables userauthorization for modifying theShopping Lists of others.

4. Choose Preview Configuration, Save, or Restore to SAP Default


Configuring the Search UI: Customize Display Tab

1. Choose Customize Display tab.

You can customize the available fields for the following screens:

Item Lists, Shopping Cart Preview, Compare, Item Details, and Context View

2. Select one of the above options, for example: Item List.

The selected UI fields are displayed and the column width. You can configure the width tomeet your requirements. If it is set to zero, a standard width is used.

3. In the left frame, SRM-MDM Repository Fields, select the fields that you want such asSupplier Catalog Name and Supplier Part Number, and choose Add, or if you want allfields, choose All.

The system moves the selected fields to the frame on the right, Selected UI Fields. This framedisplays the fields currently displayed in the screen selected in the previous step.

To change the sort order, use the Up and Down function.

To copy the selected fields to all screens meaning that all screens will display the samefields use the Copy To All button.

4. Select the Default Sorting.

5. Choose Preview Configuration, Save, or Restore to SAP Default.

Configuring the Search UI: Customize Search Tab1. Select your preference, Yes or No for the configuration options:

Show Hierarchy and Selection Search in Search Tab

Show Hierarchy and Selection Search in Advance Search Tab

2. In the dropdown box Hierarchy, choose system search field type. There are two options:

Hierarchy

Category (taxonomy)

To enable the search via attributes, you must select Category for the system searchfield type.

3. Choose the Selection List, for example Supplier, Manufacturer, Unit Measure, and so on.

4. In Advanced Search Fields, choose the field to be included in the Selection List such asSupplier, Supplier Catalog Name

SAP delivers the following selection of searchable fields as default:

? Supplier Part Number

? Product ID

? Product Group

? Price Information (with Range)


? External Manufacturer

5. Choose the corresponding Searchable indicator, Drop Down, Free Form, or Range tomake the field available in the Advanced Search.

6. To enable a search range for specific fields listed in the Field Name column, set thecorresponding Range indicator.

Only fields with the check box on a white background can be selected.


Mapping Catalog Fields to Open Catalog Interface(OCI) FieldsUseTo overwrite, if necessary, the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalog.

UI Configuration Managers and Administrators use this procedure to

? Change, if necessary, the system settings for each catalog individually.? To map non-standard fields, that is the fields that a customer added to the SRM-MDM

repository such as, NEW_ITEM-CUSTFIELD1 to OCI fields.

This table contains the pre-mapped (hard-coded) fields that cannot be changed.

OCI Hard-Coded Field SRM-MDM Field

NEW_ITEM-PRICE Price Amount

NEW-ITEM_CURRENCY Price Currency

NEW-ITEM_PRICEUNIT Price Base Quantity UOM

NEW_ITEM-UNIT Price Base Quantity

NEW_ITEM-PURCHORG Purchasing Organization

NEW_ITEM-PURCHINFREC Purchasing Info Record ID

NEW_ITEM-CONTRACT Contract ID

NEW_ITEM-CONTRACT_ITEM Contract Item ID

NEW-ITEM_ATTACHMENT URL

NEW-ITEM_ATTACHMENT_TITLE URL Description

This table contains the default OCI mapping delivered

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier P/N


NEW-ITEM-DESCRIPTION Short Description

NEW_ITEM-MATGROUP Product Group

NEW_ITEM-MATNR Product ID

NEW_ITEM-SERVICE Service Item

NEW_ITEM-MANUFACTCODE External Manufacturer

NEW_ITEM-MANUFACTMAT Manufacturer Part Number

NEW-ITEM_LEADTIME Delivery Time in Day

Procedure8. ...

1. In the General tab, choose OCI Mapping.

2. Choose an OCI field and select the SRM-MDM field to which you want to map the OCIfield selected.

OCI fields Mappable to the SRM-MDM Catalog Fields:


? NEW_ITEM-VENDOR

? NEW_ITEM-VENDORMAT

? NEW_ITEM-DESCRIPTION

? NEW_ITEM-MATGROUP

? NEW_ITEM-MATNR

? NEW_ITEM-SERVICE

? NEW_ITEM-MANUFACTCODE

? NEW_ITEM-MANUFACTMAT

? NEW_ITEM-LEADTIME

? Supplier

? Supplier Catalog Name

? Supplier Part Number

? Short Description

? Product Group

? Product ID

? Category

? Hierarchy

? Service Item

? Price Information

? Contract Price

? Long Description

? Special Search Terms

? External Manufacturer

? Manufacturer Part Number

? Standardized Manufacturer Part Number

? Delivery Time in Days

? Unit of Measure

? Order Unit

? Minimum Quantity

? Minimum Quantity UOM

? Hyperlink

? Product GUID

? Supplier Item Status

? Item Status


Extending OCI FieldsUseAs a UI Manager or Administrator, this procedure allows you to define your own OCI fields.

Procedure9. ...


1. On the Login screen, enter your server, user and password and choose TransportConfiguration.The Epic Editor screen is called that contains the OCI fields.

2. Using the formulation , add your ownOCI field at the end within tag OCIFields.

3. Save the changed XML file.

4. Import the changed XML file.

Integrating Electronic FormsUseTo order items that require information in a structured manner, such as business cards, electronicforms (e-forms) can be called from the shopping cart preview (SCP).


Procedure1. In the configuration search interface (UI), choose General Settings.

2. In Shopping Options, choose Shopping Cart Preview.

3. In Item Display Criteria, choose Yes for Enable Use of Electronic Forms.

4. In the MDM Data Manager, add the entry Eform to the lookup table Hyperlink Types.

The settings you made in the Open Catalog Interfacte (OCI) mapping determines the fields thatare sent to SAP SRM. These settings are also relevant for eForms. Data passed from eforms ispassed to SAP SRM with the exception of the following fields:

? NEW_ITEM-VENDOR? NEW_ITEM-MATNR? NEW_ITEM-VENDORMAT? NEW_ITEM-EXT_PRODUCT_ID

The value for these fields is always taken from the MDM repository.

Contract ReplicationPurposeIn this section, you make the following settings that are required for the import of contracts fromclient systems:

? Setting Up the Key Mapping for Contract Item Categories]

? Enriching Contract Data

? Configuring Role for Data Import via Import Server]

Setting Up the Key Mapping for Contract ItemCategoriesUseIn this procedure you configure the Key Mapping for the pre-delivered content of the ContractItem Categories table. By default, this table contains the following entries:

? Normal

? Product Category

If you create your own additional client system(s), maintain the key mapping for the contract itemcategories. SAP delivers editable key mappings for the SAP SRM and SAP ERP client systems,for example:

Default Item Category Name Client System Key


[x] Normal ERP

[x] Normal SRM Normal

Prerequisites? You have logged on to the SAP MDM Data Manager.? The SRM-MDM Catalog repository is loaded.? The SRM-MDM Catalog repository is switched to Record mode.

Procedure1. Select the table Contract Item Categories in the upper left pane.

2. Open the context menu of a record with the right mouse button andselect Edit Key Mapping.

The system opens a dialog window for maintaining key mappings.

3. Choose Add to enter an additional key mapping.

4. Adjust the new entry

5. Select your client system

6. Using the existing entries as a template, set the key.

Repeat Steps 2 4 for each Contract Item Category.

Enriching Contract DataUseIf the upload of contract data is part of your scenario, implement the BADI below to enrich thecontract data.

In Customizing for SRM, implement the BADI by choosing: Supplier Relationship Management ?SRM Server? Business Add-Ins (BAdIs)? SAP XML Interfaces? Change SAP XML OutboundMapping (BBP_SAPXML1_OUT_BADI).

If you need discounts and price scales in your catalog data, you must transfercontracts by means of this BAdI.

The BAdI implementation supports the following category-specific conditions:

? Item Category: Normal

? Price (Contract/Quotation)

? Price (Contract/Quotation) with scales

? Discount (Percent)

? Discount (Percent) with scales

? Item Category: Product Category

? Discount (Percent)


When using scales, note that any interval starting with a lower bound value of 0 willbe changed to 1.

Procedure5. ...

1. Copy the delivered default implementation of the above BAdI to the customernamespace.

2. Set up the interface method Catalog and set the filter to Catalog.

3. Save and activate your custom implementation.

Configuring Role for Data Import via Import ServerUseIf you use the MDM Import Server for an automatic upload of contract data, you can configure theoptional External Integration role.

In the standard system, this technical role has the user System assigned instead of the defaultuser. By default, the Import Server uses the Administrator user (which is assigned to theAdministrator role) to upload the external data through XML inbound interface XML and filesystem.

The External Integration role allows you to track responsibilities and differentiate between importsperformed by the Administrator and those done by the System user. Thus, you can compareupdates originating from human interaction with automatic updates.

Prerequisites? The basic configuration of the MDM Import Server is complete.? The Import Server is shut down.

Procedure1. 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

This initiates system creation of a database-specific entry for your catalog repositoryin the mdis.ini file. You change this entry in the following step.5. Shut down the Import Server and modify the repository section of mdis.ini

Change the following data:

Old New

login = Admin login = Systempassword = password =

By default, user System uses the password system.

For security reasons, you should change the password during configuration.


Appendix

How To Enable Web Approval Process with iViews


Business Scenario

With each upload of new catalog content to the SRM MDM Catalog, the content must beapproved by people with the Content Approver Role. To guarantee data quality; this mayinvolve tasks such as approving or disapproving records of products, setting approval-status flags for records, role-based task distribution, and automatic check-in of approvedrecords.

SAP delivers a set of predefined IViews to help customers set up a web-based processthat enables users execute the tasks listed above.


Introduction

Enterprise Portal is the SAP technology for establishing a single entry point to theenterprise.

Universal Work List (UWL) is a Portal technology that enables users to view and processworkflow tasks in a central place in Portal.

MDM Workflow is the MDM workflow technology that focuses on core tasks aroundmaster data processing. For more information about MDM Workflow, please refer to [1].This solution combines existing MDM technologies, MDM Workflow and MDM UWLConnector, to integrate a content approval process defined in MDM Workflow into PortalUWL.

Basic Scenario

The user defines the content approval process in the MDM Workflow. This process isstarted either automatically or manually after an import of catalog content and triggersthe distribution of workflow tasks, containing all newly imported catalog records, to userswith specific roles.In the Portal UWL; these users can execute tasks such as approve ordisapprove records, or split the records into smaller groups to delegate the job to otherusers.

At the end of the process, all imported records are checked-in to the MDM repository.

To implement this approach, you must:

1. Define your content approval process in the form of an MDM workflow in MDMData Manager.

2. Install SRM MDM Catalog 2.0.3. Deploy MDM Business Packages.4. Deploy SRM MDM Catalog Business Packages.5. Configure Portal and Portal User.6. Configure UWL.

The Step By Step SolutionPrerequisites

? You have advanced knowledge of Portal Administration.


? You have a Portal user with authorizations for system administration, useradministration and content administration.

? You have access to SDM for deployment on Portal.? You have a Portal installation with KMC (to use UWL functionality).? You understand concepts of MDM, like records checkout, table code.? You understand the concepts of MDM Workflow.? You understand the user management of MDM.

Define workflow in MDM Data ManagerDefine your own approval process in the form of an MDM workflow.

Please refer to [1] for details of MDM workflow functionality.

Note: SAP only supports the two pre-delivered MDM roles Catalog Manager andCatalog Content Approver. SAP recommends assigning each workflow step to anMDM role instead of to an MDM user.The following figure represents a sample workflowin the MDM Data Manager.

1. After the new catalog content is imported, the new records have the statuschecked-out and are added to your workflow.The workflow is then started (First step, Start).

2. At the second step Enrich Data, users with MDM role Catalog Manager canreview the content of the records and make modifications to the records in MDMData Manager, if necessary.

3. At the step Approve, users with the MDM role Catalog Content Approver canapprove/disapprove records, or split records into new workflow tasks to delegatethe job to other users.

4. At the step Set Status, the items are updated on a defined field with a new valueto indicate the approval status; for example,. the field Item Status can beupdated to Approved.

5. The last step Stop, all records are checked in automatically.

Hint: For the Start step, you can define in the MDM Import Manager that the newrecords are checked out and added to a workflow after a successful import of new


catalog content. The workflow can be started automatically successive to the import ormanually later, depending on import settings.

Install SRM MDM Catalog 2.0See SAP Note 1057316 to install and configure SRM MDM Catalog 2.0.

Deploy MDM Business PackagesPlease refer to [2].

Deploy MDM SRM Catalog Business PackagesUse SDM to deploy BP_SRM_MDM.sca.

Configure Portal and Portal User1. Define connection properties and system alias.

Logon into Portal as system administrator. In the Portal Content Browser,choose System Administration -> System ConfigurationChoose Portal Content -> Content Provided by SAP -> specialist ->SRM MDM Catalog -> System.The object MDM Catalog appears.Open this object, select property category Connection Properties andmaintain properties MDM Host Server, Repository Name, Server Password, ifany. Tables with Workflows must be MDMSRM_CATALOG_ITEMS.In the dropdown list Display, select entry System Aliases; and add twoaliases SAP_SRM_MDMCAT, SAP_SRM_MDMCAT_WFORIG for thissystem object.

SAP Online Help 10.12.2007

SRM-MDM Catalog 2.0: Configuration GuideSRM2007 2

2. Define User Mapping.Choose User Administration, find the Portal user that you want to map to anMDM user.Choose Modify mode, then go to User Mapping for System Access, selectsystem SAP_SRM_MDMCAT. Type in the MDM User and password andsave.This Portal user gets all the MDM workflow tasks that are assigned to themapped MDM user, in the UWL.



3. Test system connection to MDM repository.Repeat the same user mapping for your Administrator user as described instep 2. Choose the system object MDM Catalog as described in 1, open it,choose Connection Tests and test if the connection to MDM repository isworking.

Note: The target MDM repository much be loaded to make the connectionwork.

4. Assign the SRM Catalog Content Manager role to the Portal user.Choose Modify mode of the Portal user as in 2. Choose Assigned Roles, in



the panel Available Roles and search for the rolecom.sap.pct.srm.mdmcat.role.cat_cont_mgr and assign it to the user.Logout. Logon with the Portal user. A new tab Workflow appears at the toplevel.

Configure UWL1. Create connection between UWL and MDM Workflow engine.

Logon into Portal as system administrator and choose SystemAdministration, in the navigation tray. Select Universal Worklist & Workflow-> Universal Worklist - Administration and create a new connection, with thesystem alias SAP_SRM_MDMCAT, connector type MdmUwlConnector,and save your change. A new connection appears in the table.



2. Change the UWL configuration.On the same page, go to section Universal Worklist Content Configurationand select the link Click to Administrate Item Types and View Definitions.You should find a configuration named mdm. Download this to your local filesystem. Open the XML file with a text editor and delete all content under thetag , add following content:

3. Upload the configuration. On the same page as in 2, choose Upload NewConfiguration, select the file youve just edited and upload it with namemdm. Select OK to overwrite the old configuration.



4. Clear the cache.Choose Universal Worklist & Workflow -> Universal Worklist -Administration, in the section Universal Worklist Content Configuration andselect the link Cache Administration Page, clear cache.

ResultNow you are ready to use Web Approver in Portal. Choose the top level tabWorkflow to start working!



FAQ:1. I cannot find the connector type MdmUwlConnector at step 1 of section 3.6,

what do I do?

Follow [2], do exactly the same, especially the part of removing archives.

2. At step 3 of section 3.5, the connection test fails. What could be the reason?

Check if the connection properties of system object MDM Catalog aremaintained correctly, check if the target MDM repository is loaded. As the lastresort, you can try to restart the MDM server and J2E.

3. Can I customize the display fields of records? Which customization can Iperform?

Please refer to [3].

4. When I logon as administrator, I cannot find the content from SRM MDMCatalog?

Make sure you have the permission to see the content. Check Portal SystemAdministration Guide for more information about the Portal Permission concept.

5. As I try to define User Mapping for a portal user, I cannot find the system aliasSAP_SRM_MDMCAT?

Please see 4.

ReferencesAvailable at service.sap.com/mdm

[1] MDM Documentation MDM Data Manager, Section Workflow.

[2] MDM Portal Business Package documentation, Section 1.1 Importing the BusinessPackage.

[3] MDM Portal Content Development Guide.

SRMMDM

Documents

Transcript of SRMMDM